Wireless communication method, terminal, and network device

Abstract

The present application relates to the technical field of communications, and discloses a wireless communication method, a terminal, and a network device. The wireless communication method in embodiments of the present application comprises: a terminal is configured with at least three cell groups (CG). The method comprises: when a first CG among the at least three CGs fails, on the basis of a target reporting mode, the terminal determines a second CG; and by means of the second CG, the terminal reports failure information of the first CG. The target reporting mode comprises any one of the following: a first reporting mode, in which the failure information of the first CG is reported by means of all of the other CGs except the first CG among the at least three CGs, and a second reporting mode, in which the failure information of the first CG is reported by means of one CG among all of the other CGs except the first CG among the at least three CGs.

Description

Wireless communication method, terminal and network equipment

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on January 12, 2024, with application number 202410052552.0 and invention name “Wireless Communication Method, Terminal and Network Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application belongs to the field of communication technology, and specifically relates to a wireless communication method, terminal and network equipment. Background Art

[0003] Dual connectivity (DC) technology provides the terminal with the resources of two network devices, one of which is called the Master Node (MN) and the other is called the Secondary Node (SN). For each network device, carrier aggregation (CA) technology can also be used to configure a series of service cells controlled by the device for the terminal. These service cells form a cell group (CG), where the cell group controlled by the MN is the Master Cell Group (MCG) and the cell group controlled by the SN is the Secondary Cell Group (SCG). Multi-connectivity technology is similar to dual connectivity technology, except that it provides the terminal with the resources of more than two network devices.

[0004] Currently in a dual-connection scenario, if any cell group (CG) in the master cell group (MCG) and the secondary cell group (SCG) fails, the terminal can report the failure information of the failed CG through the other one of the MCG and SCG to quickly restore the abnormal link.

[0005] In a multi-connection scenario, if a CG fails, how the terminal reports the failure information of the CG to quickly restore the abnormal link is a technical problem that needs to be solved urgently in this application. Summary of the Invention

[0006] The embodiments of the present application provide a wireless communication method, terminal and network device, which can solve the technical problem of how the terminal reports the failure information of a CG to quickly restore the abnormal link if a CG fails in a multi-connection scenario.

[0007] In a first aspect, a wireless communication method is provided, performed by a terminal. The method includes: the terminal is configured with at least three cell groups (CGs). The method includes: when a first CG among the at least three CGs fails, the terminal determines a second CG according to a target reporting mode; and the terminal reports failure information of the first CG through the second CG.

[0008] The target reporting method includes any of the following:

[0009] First reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0010] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0011] In a second aspect, a wireless communication method is provided, performed by a network device, the method comprising: the network device receiving failure information of a first CG reported by a terminal via a second CG; wherein the terminal is configured with at least three cell group CGs, the first CG is a CG in which the failure occurs among the at least three CGs, and the second CG is determined by the terminal according to a target reporting mode;

[0012] Target reporting methods include any of the following:

[0013] First reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0014] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0015] In a third aspect, a wireless communication device is provided, wherein the device is configured with at least three CGs, and the device includes:

[0016] a processing module, configured to determine a second CG according to a target reporting method when a first CG among at least three CGs fails;

[0017] A communication module, configured to report failure information of the first CG through the second CG;

[0018] The target reporting method includes any of the following:

[0019] First reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0020] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0021] According to a fourth aspect, a wireless communication device is provided, including:

[0022] A communication module, configured to receive failure information of a first CG reported by a terminal through a second CG;

[0023] The terminal is configured with at least three cell groups CG, the first CG is the CG in which the failure occurs among the at least three CGs, and the second CG is determined by the terminal according to the target reporting method;

[0024] Target reporting methods include any of the following:

[0025] First reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0026] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0027] In a fifth aspect, a terminal is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the method of the first aspect are implemented.

[0028] In the sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is used to determine the second CG according to the target reporting method when the first CG among at least three CGs fails, and the communication interface is used to report the failure information of the first CG through the second CG.

[0029] The target reporting method includes any of the following:

[0030] First reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0031] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0032] In a seventh aspect, a network device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the method of the second aspect are implemented.

[0033] In an eighth aspect, a network device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive failure information of a first CG reported by a terminal via a second CG;

[0034] The terminal is configured with at least three cell groups CG, the first CG is the CG where the failure occurs among the at least three CGs, and the second CG is determined by the terminal according to the target reporting mode;

[0035] Target reporting methods include any of the following:

[0036] First reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0037] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0038] In a ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method of the first aspect or the steps of the method of the second aspect are implemented.

[0039] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network device, wherein the terminal can be used to execute the steps of the method of the first aspect, and the network device can be used to execute the steps of the method of the second aspect.

[0040] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method of the first aspect, or to implement the method of the second aspect.

[0041] In a twelfth aspect, a computer program / program product is provided. The computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the wireless communication method of the first aspect.

[0042] In an embodiment of the present application, the terminal is configured with at least three CGs, and the method includes: when the first CG among at least three CGs fails, the terminal determines the second CG according to the target reporting method; the terminal reports the failure information of the first CG through the second CG; wherein the target reporting method includes any one of the following: a first reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs; a second reporting method: reporting the failure information of the first CG through one CG among all other CGs except the first CG among at least three CGs. That is, a method for reporting CG failure information by the terminal in a multi-connection scenario is provided to quickly restore the abnormal link. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] FIG1 is a schematic diagram of a multi-connection scenario provided in an embodiment of the present application;

[0044] Figure 2 is a schematic diagram of the load from the network side perspective;

[0045] Figure 3 is a schematic diagram of the load bearing at the terminal side angle;

[0046] FIG4 is an interactive flow chart of a wireless communication method provided in an embodiment of the present application;

[0047] FIG5 is a schematic diagram of a type A separation load provided in an embodiment of the present application;

[0048] FIG6 is a schematic diagram of another type A separation load provided in an embodiment of the present application;

[0049] FIG7 is a schematic diagram of a type B separated load provided in an embodiment of the present application;

[0050] FIG8 is a schematic diagram of another type B separated load provided in an embodiment of the present application;

[0051] FIG9 is a schematic diagram of a wireless communication device 900 provided in an embodiment of the present application;

[0052] FIG10 is a schematic diagram of a wireless communication device 1000 provided in an embodiment of the present application;

[0053] FIG11 is a schematic block diagram of a communication device provided in an embodiment of the present application;

[0054] FIG12 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application;

[0055] FIG13 is a schematic diagram of the hardware structure of a network device implementing an embodiment of the present application. DETAILED DESCRIPTION

[0056] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0057] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0058] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0059] It is worth noting that the embodiments of the present application relate to multi-connection technology, wherein the multiple wireless communication systems corresponding to the multiple connections can adopt the same radio access technology (Radio Access Technology, RAT) or different RATs, and the embodiments of the present application are not limited to this. The wireless communication system corresponding to each connection is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, and can also be used for other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description. However, these technologies can also be applied to systems other than NR systems, such as 6G communication systems.

[0060] FIG1 is a schematic diagram of a multi-connection scenario provided by an embodiment of the present application. As shown in FIG1 , a terminal 11 is connected to a first network device 12 , a second network device 13 , and a third network device 14 .

[0061] The wireless communication system formed by the first network device 12 and the terminal 11, the wireless communication system formed by the second network device 13 and the terminal 11, and the wireless communication system formed by the third network device 14 and the terminal 11 can adopt the same RAT or different RATs, which is not limited in this embodiment of the present application. For example, the wireless communication system formed by the first network device 12 and the terminal 11 adopts LTE technology, the wireless communication system formed by the second network device 13 and the terminal 11 adopts NR technology, and the wireless communication system formed by the third network device 14 and the terminal 11 adopts LTE-A technology. For another example, the wireless communication system formed by the first network device 12 and the terminal 11, the wireless communication system formed by the second network device 13 and the terminal 11, and the wireless communication system formed by the third network device 14 and the terminal 11 all adopt NR technology.

[0062] For any one of the first network device 12, the second network device 13 and the third network device 14, it can correspond to a CG. One of the CGs can be used as an MCG, and the remaining CGs can be used as SCGs. Multiple SCGs can be distinguished by the respective identifiers or names of the SCGs. For example, one of the SCGs in the network configuration is a primary SCG, or a special SCG, or a default SCG, and the remaining SCGs are normal SCGs. For another example, the network configures multiple SCGs as a second cell group (secondary CG), a third cell group (third CG), and so on. In short, the embodiment of the present application does not limit how to model and distinguish between multiple CGs. For the convenience of description, the embodiment of the present application adopts a description method including one MCG and multiple SCGs.

[0063] The terminal 11 may be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipborne equipment, pedestrian user equipment (PUE), smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM or self-service machine, etc. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. The vehicle-mounted device may also be referred to as a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application.

[0064] In some implementations, the first network device 12, the second network device 13, and the third network device 14 may be three different access network devices, and the first network device 12, the second network device 13, and the third network device 14 all have user plane interfaces with the core network to receive data from the core network.

[0065] In other implementations, the first network device 12, the second network device 13, and the third network device 14 may be three distributed units (DUs), which share a central unit (CU). Alternatively, one of the first network device 12, the second network device 13, and the third network device 14 is an access network device, and the other two network devices are two DUs, which share a CU. For example, the first network device 12 is an access network device, and the second network device 13 and the third network device 14 may be two DUs connected to the same CU. In this implementation, data from the core network first reaches the CU and is then sent by the CU to the corresponding DU, and there is no user plane interface between the DU and the core network.

[0066] Access network equipment may also be referred to as radio access network (RAN) equipment, radio access network functions, or radio access network units. Access network equipment may include base stations, wireless local area network (WLAN) access points (AS), or wireless fidelity (WiFi) nodes. Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (homeevolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0067] It should be understood that what is shown in Figure 1 is an example of a multi-connection scenario. In the multi-connection scenario shown in Figure 1, three connections are included. In fact, the multi-connection scenario may include more connections. In short, the embodiments of the present application do not limit the multi-connection scenario.

[0068] Before introducing the technical solution of this application, the following will explain the relevant knowledge of this application:

[0069] 1. DC

[0070] DC technology provides the terminal with the resources of two network devices, one of which is called MN and the other is called SN. For each network device, CA technology can also be used to configure a series of service cells controlled by the device for the terminal. These service cells form a CG, where the cell group controlled by the MN is the MCG and the cell group controlled by the SN is the SCG. Each CG contains a special cell (SpCell) and a series of secondary cells (SCell). In the MCG, the special cell is called the primary cell (PCell), and in the SCG, the special cell is called the primary secondary cell (PSCell).

[0071] 2. Release (R) 15 SCG Failure Information Process

[0072] 1. When one of the following conditions is met and neither MCG nor SCG transmission is suspended, the terminal initiates the SCG failure information process to report the SCG failure information:

[0073] -SCG radio link failure;

[0074] -SCG synchronization reconfiguration failed;

[0075] -SCG configuration failed;

[0076] -Integrity check of Signalling Radio Bearer (SRB) 3 failed.

[0077] 2. Once the SCG failure information process is initiated, the terminal performs the following steps:

[0078] -Suspend SCG transmission of all SRBs and Data Radio Bearers (DRBs);

[0079] -Reset SCG Media Access Control (MAC);

[0080] -If SCG's T304 is running, stop SCG's T304;

[0081] - If a conditional PSCell change (CPC) is configured, stop performing CPC evaluation;

[0082] - Send SCG failure information.

[0083] 3. The SCG failure message will include the following information:

[0084] -SCG failure reason (failureType): The terminal needs to set a reasonable SCG failure reason based on the actual situation. The current SCG failure reasons include: {t310 expiration (t310-Expiry), random access problem (randomAccessProblem), Radio Link Control (RLC) layer reaching the maximum number of retransmissions (rlc-MaxNumRetx), SCG synchronization reset failure (synchReconfigFailureSCG), SCG reset failure (scg-ReconfigFailure), SRB3 integrity check failure (srb3-IntegrityFailure), other cases in R16 (other-R16), spare case (spare)1}

[0085] - Measurement results corresponding to the measurements configured in the measurement configuration (measConfig);

[0086] -Measurement results corresponding to the measurements configured by the SN.

[0087] 3. R16 MCG failure information process, also known as the MCG fast recovery process:

[0088] 1. When one of the following conditions is met, when the terminal detects an MCG radio link failure (Radio Link Failure, RLF), the terminal triggers the MCG fast recovery process instead of triggering the Radio Resource Control (RRC) RRC connection reestablishment process.

[0089] -The network configures the terminal with timer T316;

[0090] - The network configures the terminal to split SRB1 and / or SRB3;

[0091] -After the access stratum (AS) of the terminal is securely activated, and SRB2 and at least one DRB are established.

[0092] 2. The terminal triggers the Fast MCG recovery process, that is, the terminal sends MCG failure information (Failure Information) to the MN through SCG (split SRB1 or SRB3):

[0093] If the terminal sends the MCG failure information through SRB3, the terminal encapsulates the MCG failure information in a ULInformationTransferMRDC message container and sends it to the SN. After receiving the message, the SN transmits the MCG failure information to the MN.

[0094] If the terminal receives the MCG failure information through Split SRB1, the terminal sends the MCG failure information on split SRB1. After sending the MCG failure information, the terminal starts T316 and performs the following operations:

[0095] -Suspend transmission on all SRBs and DRBs of the MCG;

[0096] -Reset MCG MAC;

[0097] - Save the current measurement configuration of MN and SN;

[0098] -Continue to perform measurements based on the configuration.

[0099] After the MN receives the MCG failure information, it can send an RRC reconfiguration message or an RRC release message to the terminal, which is passed to the terminal through the SN's DLInformationTransferMRDC. After the terminal receives the RRC release message, the terminal releases all radio bearers and configurations. During the operation of T316, if the terminal receives the RRC reconfiguration from the MN, it stops T316 and resumes the transmission of the MCG. If T316 times out and the terminal does not receive the RRC reconfiguration from the MN, the terminal triggers the RRC connection reestablishment process and sets the reestablishment cause value to other failure cause (otherFailure).

[0100] IV. R17 SCG Activation / Deactivation Mechanism

[0101] Release 17 introduced the SCG activation / deactivation mechanism. When there is no data to be transmitted on the SCG, the terminal is currently overheating, or the terminal is saving power, the network and terminal can initiate the SCG deactivation process. When these conditions change, the network and terminal can initiate the SCG activation process again.

[0102] During SCG deactivation, the terminal does not monitor the physical downlink control channel (PDCCH) on the SCG, nor does it transmit the physical uplink shared channel (PUSCH) or sounding reference signal (SRS) to save terminal power consumption.

[0103] In addition, during the SCG deactivation period, the terminal may also perform SCG radio resource management (RRM) measurement, radio link monitoring (RLM), and beam management to ensure that the SCG can operate normally when it is activated.

[0104] 5. Bearer in DC

[0105] It should be understood that in the embodiments of the present application, the RLC bearer is also referred to as RLC, RLC entity, etc., and the embodiments of the present application do not limit this, wherein the RLC bearer includes the configuration of RLC and MAC.

[0106] It should be understood that in the embodiment of the present application, the Packet Data Convergence Protocol (PDCP) bearer is also referred to as PDCP, PDCP entity, etc., and the embodiment of the present application does not limit this.

[0107] It should be understood that in the embodiment of the present application, a certain RLC bearer corresponds to (mapping) a certain CG, which is also referred to as the bearer being located in the CG, or the bearer being located in the network node corresponding to the CG, and the embodiment of the present application does not limit this. In the embodiment of the present application, one RLC bearer corresponds to one RLC entity and corresponds to one CG.

[0108] In DC, there are three types of radio bearers, including:

[0109] -MCG bearer: RLC bearer (i.e. RLC entity) corresponds to the radio bearer of MCG;

[0110] -SCG bearer: RLC bearer corresponds to the radio bearer of SCG;

[0111] -Split bearer: a radio bearer having two RLC bearers corresponding to the MCG and SCG.

[0112] The above three types of radio bearers can be further divided into MN terminated bearers (MN terminated bearer) and SN terminated bearers (SN terminated bearer) according to the PDCP bearer-owning node.

[0113] Figure 2 is a schematic diagram of the load-bearing from the perspective of the network side, and Figure 3 is a schematic diagram of the load-bearing from the perspective of the terminal side.

[0114] MN terminated MCG bearer: As shown in Figure 2, after the downlink data reaches the User Plane Function (UPF) of the core network, it is sent by the core network to the MN. After being processed by the Service Data Adaptation Protocol (SDAP) and PDCP, the MN sends it to the terminal through the MN's air interface resource configuration, where the MN's air interface resource configuration includes: MN RLC and MN MAC. MN RLC is also called MN RLC entity, MN RLC bearer, MCG RLC, MCG RLC entity, and MCG RLC bearer. MN MAC is also called MN MAC entity, MN MAC bearer, MCG MAC, MCG MAC entity, and MCG MAC bearer. As shown in Figure 3, after the terminal receives the data through MCG MAC, it is sequentially submitted to MCG RLC, PDCP, and SDAP for processing, where the terminal's PDCP corresponds to the MN's PDCP.

[0115] MN terminated SCG bearer: As shown in Figure 2, the difference between MN terminated SCG bearer and MN terminated MCG bearer is that after MN is processed by SDAP and PDCP, MN sends the PDCP data to SN through the Xn interface, and then sends it to the terminal through the air interface resource configuration of SN, where the air interface resource configuration of SN includes: SN RLC and SN MAC. SN RLC is also called SN RLC entity, SN RLC bearer, SCG RLC, SCG RLC entity, and SCG RLC bearer. SN MAC is also called SN MAC entity, SN MAC bearer, SCG MAC, SCG MAC entity, and SCG MAC bearer. As shown in Figure 3, after the terminal receives the data through SCG MAC, it submits it to SCG RLC, PDCP, and SDAP for processing.

[0116] MN terminated split bearer: As shown in Figure 2, after downlink data reaches the UPF of the core network, it is sent to the MN by the core network. After being processed by SDAP and PDCP at the MN, it is sent to the terminal through the air interface resource configuration of the MN and SN. As shown in Figure 3, after the terminal receives the data through the MN MAC, it is submitted to the MN RCL. At the same time, after the terminal receives the data through the SCG MAC, it is submitted to the SCG RLC. The data will be aggregated at the PDCP and then submitted to the SDAP for processing.

[0117] SN terminated SCG bearer: As shown in Figure 2, after downlink data reaches the core network's UPF, it is sent to the SN by the core network. After being processed by SDAP and PDCP in the SN, it is sent to the terminal using the SN's air interface resource configuration. As shown in Figure 3, after the terminal receives the data through the SN MAC, it is sequentially submitted to the SCG RLC, PDCP, and SDAP for processing. The terminal's PDCP corresponds to the SN's PDCP.

[0118] SN-terminated MCG bearer: As shown in Figure 2, the difference between an SN-terminated MCG bearer and an SN-terminated SCG bearer is that after SDAP and PDCP processing, the SN sends the PDCP data to the MN via the Xn interface, which is then sent to the terminal using the MN's air interface resource configuration. As shown in Figure 3, after the terminal receives the data via the MCG MAC, it passes it up to the MCG RLC, PDCP, and SDAP for processing.

[0119] SN terminated split bearer: As shown in Figure 2, after the downlink data reaches the UPF of the core network, it is sent to the SN by the core network. After being processed by SDAP and PDCP at the SN, it is sent to the terminal through the air interface resource configuration of the MN and SN. As shown in Figure 3, after the terminal receives the data through the MCG MAC, it is submitted to the MCG RLC. At the same time, after the terminal receives the data through the SCG MAC, it is submitted to the SCG RLC. The data will be aggregated at the PDCP and then submitted to the SDAP for processing.

[0120] 6. Multiple connections

[0121] On the one hand, multi-connection technology can aggregate the transmission resources of more than two network devices, fully utilize the discretely distributed resources of the communication system, and improve system capacity.

[0122] On the other hand, to increase system capacity, 6G communication systems may introduce higher communication frequencies. While high-frequency signals offer the benefit of large bandwidth, they also have significant disadvantages: unstable signal quality. High-frequency signals can experience significant degradation when blocked by obstacles. Multi-connection technology, with its multiple available transmission paths, can improve terminal stability under these high-frequency transmissions.

[0123] As mentioned above, in a multi-connection scenario, if a CG fails, how the terminal reports the failure information of the CG to quickly restore the abnormal link is a technical problem that needs to be solved urgently in this application.

[0124] In order to solve the above technical problems, an embodiment of the present application provides a method for a terminal to report CG failure information in a multi-connection scenario.

[0125] The wireless communication method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0126] FIG4 is an interactive flow chart of a wireless communication method provided by an embodiment of the present application. The method can be executed by a terminal and a network device. The terminal can be the terminal 11 in FIG1 , but is not limited thereto. The network device can be the first network device 12, the second network device 13, or the third network device 14 in FIG1 , but is not limited thereto. , wherein the terminal is configured with at least three CGs, or the terminal is connected to at least three network devices, or the terminal is in a multi-connection scenario. As shown in FIG4 , the method may include:

[0127] S410: When a first CG among at least three CGs fails, the terminal determines a second CG according to a target reporting method;

[0128] S420: The terminal reports the failure information of the first CG to the network device corresponding to the first CG through the second CG.

[0129] The target reporting method includes any of the following:

[0130] The first reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs.

[0131] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0132] In some implementations, the first CG can be an MCG or any SCG.

[0133] In some implementations, the situation where the first CG fails includes at least one of the following, but is not limited to:

[0134] (1) The wireless link of the first CG fails;

[0135] (2) Synchronous reconfiguration of the first CG fails;

[0136] (3) Configuration of the first CG fails;

[0137] (4) The integrity check of the SRB corresponding to the first CG fails.

[0138] In some implementations, the SRB corresponding to the first CG includes at least one of the following, but is not limited to:

[0139] (1) A dedicated SRB owned by the first CG;

[0140] (2) The first CG has a target separation SRB.

[0141] In a multi-connection scenario, for any CG, the dedicated SRB of the CG refers to the PDCP bearer and the RLC bearer corresponding to the CG.

[0142] For example, assuming that the MN terminated MCG bearer in FIG2 is the MN terminated MCG SRB, since both the PDCP bearer and the RLC bearer of the MN terminated MCG SRB correspond to the MCG, the MN terminated MCG SRB is a dedicated bearer of the MCG.

[0143] For another example, assume that the SN terminated SCG bearer in FIG2 is the SN terminated SCG SRB. Since the PDCP bearer and the RLC bearer of the SN terminated SCG SRB are both located in the SCG, the SN terminated SCG SRB is a dedicated bearer of the SCG.

[0144] For another example, SRB3 is the SN dedicated signaling bearer in NR-DC, that is, the SRB3 is configured for SN. From the network side perspective, the PDCP of the SRB3 is in the SN, and the RLC bearer / entity is located in the SN. From the terminal perspective, the PDCP of the SRB3 corresponds to the SCG, and the RLC bearer / entity corresponds to the SCG.

[0145] The following describes the split bearer in a multi-connection scenario, taking a terminal configured with one MCG and two SCGs as an example:

[0146] Assume that the terminal is configured with MCG, SCG 1, and SCG 2. In this scenario, split bearer can include two types:

[0147] Type A: The PDCP bearer of this bearer corresponds to a single network node and includes the following three RLC bearers: the MN RLC bearer, the SN1 RLC bearer, and the SN2 RLC bearer. In other words, the PDCP bearer of this Type A bearer corresponds to a single network node and consists of the MN RLC bearer, the SN1 RLC bearer, and the SN2 RLC bearer, forming the three legs of this Type A bearer.

[0148] Type B: A Type B PDCP bearer corresponds to a single network node and includes two of the following three RLC bearers: the MN RLC bearer, the SN1 RLC bearer, and the SN2 RLC bearer. In other words, the PDCP bearer of this Type B bearer corresponds to a single network node and consists of two of the following: the MN RLC bearer, the SCG 1 RLC bearer, and the SCG 2 RLC bearer, forming the two legs of the Type B bearer.

[0149] The RLC bearer includes the configuration of RLC and MAC. The above two types of split bearers can be further divided into MN terminated split bearer, SN1 terminated split bearer and SN2 terminated split bearer according to the node to which the PDCP bearer belongs.

[0150] In a multi-connection scenario, when the network configures a split bearer, the split bearer configuration includes at least one of the following:

[0151] - The type of the split bearer: Type A or Type B;

[0152] -When the split bearer type is type B, the two associated branches may correspond to two SNs respectively, or one branch corresponds to the MN and the other branch corresponds to SN1 or SN2.

[0153] -The location of the PDCP bearer of the split bearer.

[0154] It should be noted that the network node to which the PDCP bearer of the split bearer belongs is configured by the network node.

[0155] For example, Figure 5 is a schematic diagram of a type A split bearer provided in an embodiment of the present application, wherein Figure 5 respectively shows a type A MN terminated split bearer, a type A SN1 terminated split bearer, and a type A SN2 terminated split bearer.

[0156] For example, FIG6 is a schematic diagram of another type A split bearer provided in an embodiment of the present application, wherein FIG6 shows a type A MN terminated split bearer and a type A SN1 terminated split bearer respectively.

[0157] For example, Figure 7 is a schematic diagram of a type B split bearer provided in an embodiment of the present application, wherein Figure 7 respectively shows a type B MN terminated split bearer, a type B SN1 terminated split bearer, and a type B SN2 terminated split bearer.

[0158] For example, FIG8 is a schematic diagram of another type B split bearer provided in an embodiment of the present application, wherein FIG8 shows a type B MN terminated split bearer and a type B SN1 terminated split bearer respectively.

[0159] For example, a split SRB1 associated with SCG2 (split SRB1 with SCG2) has two RLC bearers, one of which corresponds to the MCG and the other corresponds to SCG2. In addition, the PDCP bearer of the split SRB1 associated with SCG2 corresponds to the MCG.

[0160] For example, a split SRB3 associated with SCG2 has two RLC bearers, one of which corresponds to SCG1 and the other to SCG2. In addition, the PDCP bearer of the split SRB3 associated with SCG2 corresponds to SCG1.

[0161] In some implementations, the target separation SRB has at least two RLC bearers, one of which corresponds to the first CG.

[0162] In some implementations, the PDCP entity corresponding to the above-mentioned target separation SRB is located in the network node corresponding to the first CG.

[0163] In some implementations, the terminal may determine the second CG based solely on the target reporting method.

[0164] For example, assume that the terminal is connected to three CGs, including MCG, SCG1 and SCG2, SCG1 fails, and the terminal is configured to use the first reporting method to report the failure information. Based on this, the terminal can report the failure information of SCG1 through MCG and SCG1 at the same time.

[0165] In some implementations, the terminal may determine the second CG based on the target reporting method and the target condition;

[0166] In some implementations, the second CG satisfies a target condition, which includes at least one of the following:

[0167] (1) The transmission is not in a suspended state;

[0168] (2) in the activated state;

[0169] (3) With SRB;

[0170] (4) Be configured or allowed to report the failure information of the first CG.

[0171] In some implementations, the second CG having the SRB includes at least one of the following, but is not limited to:

[0172] (1) The second CG has a dedicated SRB;

[0173] (2) The second CG has a first separated SRB;

[0174] The first separated SRB has at least two RLC bearers, one of which corresponds to the second CG.

[0175] It should be understood that the explanation of separating SRB can be referred to above, and the embodiments of the present application will not be repeated here.

[0176] In some implementations, the PDCP entity corresponding to the first separated SRB is located in the MN or the SN corresponding to the first CG.

[0177] For example, assuming that the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and SCG1 fails, and assuming that the failure information of SCG1 is reported through SCG2, then the PDCP entity corresponding to the first detached SRB of SCG2 is located in the MN or SN1 corresponding to SCG1.

[0178] For example, assuming that the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and SCG1 fails, and assuming that the failure information of SCG1 is reported through MCG, then the PDCP entity corresponding to the first separated SRB of MCG is located in the MN or the SN1 corresponding to SCG1.

[0179] For example, assuming that the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and MCG fails, and assuming that the failure information of MCG is reported through SCG1, then the PDCP entity corresponding to the first detached SRB of SCG1 is located in the MN.

[0180] In some implementations, the terminal may receive a first indication message; wherein the second CG is configured or allowed to report failure information of the first CG, including: the first indication message indicates that the second CG can report failure information of the first CG; or, the first indication message indicates one or more CGs that can report failure information, wherein the one or more CGs include the identifier of the second CG.

[0181] For example, assuming that the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and SCG1 fails, the terminal receives the first indication information sent by the network device indicating that SCG2 can report the failure information of SCG1, then the terminal can report the failure information of SCG1 through SCG2.

[0182] For example, assuming that the terminal is connected to three CGs, including: MCG, SCG1 and SCG2, SCG1 fails, and assuming that the target reporting method is the first reporting method, the terminal receives the first indication information sent by the network device indicating that the CGs that can report failure information are MCG and SCG2, then the terminal can report the failure information of SCG1 through MCG and SCG2 at the same time.

[0183] For example, assuming that the terminal is connected to three CGs, including: MCG, SCG1 and SCG2, SCG1 fails, and assuming that the target reporting method is the second reporting method, the terminal receives the first indication information sent by the network device indicating that the CGs that can report failure information are MCG and SCG2, then the terminal can report the failure information of SCG1 through MCG or SCG2.

[0184] From the network side perspective, the second CG is configured with enabling information for enabling the failure information reporting process, so that the second CG is configured or allowed to report the failure information of the first CG; or, the first CG is configured to use the second CG to report the failure information of the first CG, so that the second CG is configured or allowed to report the failure information of the first CG.

[0185] For example, assume that the terminal is connected to four CGs, including MCG, SCG1, SCG2 and SCG3, and SCG 2 is configured with 1-bit enable information to enable the failure information reporting process. When SCG 1 or SCG 3 fails, the terminal can report the corresponding failure information through SCG 2.

[0186] For example, assuming that the terminal is connected to four CGs, including: MCG, SCG1, SCG2 and SCG3, and SCG 1 is configured to use SCG 2 to report the failure information of SCG1, or the configuration information of SCG 1 includes the recovery branch (Recovery leg) = SCG 2, then only when SCG 1 fails, can the terminal report the failure information of SCG1 through SCG 2. When SCG3 fails, the failure information of SCG3 cannot be reported through SCG2, and MCG can only be notified to report the failure information of SCG3.

[0187] For example, suppose the terminal is connected to three CGs, including MCG, SCG1 and SCG2. MCG fails, SCG 1 is configured with enabling information to enable the failure information reporting process, and SCG2 is not configured with the enabling information. Then the terminal can only report the failure information of MCG through SCG 1, and cannot report the failure information of MCG through SCG 2.

[0188] In some implementations, when the target reporting method is the second reporting method, the terminal can determine the second CG based on the priority rule between the second reporting method and at least three CGs.

[0189] In some implementations, the priority rules among the at least three CGs include any of the following, but are not limited to:

[0190] (1) Priority rules between MCG and any SCG;

[0191] (2) Priority rules between various SCGs;

[0192] (3) determining the priorities of at least three CGs based on the priority parameters of the at least three CGs;

[0193] (4) Among at least three CGs, the CG with higher signal quality has a higher corresponding priority;

[0194] (5) Among at least three CGs, the CG that obtains uplink resources earlier has a higher corresponding priority.

[0195] The following describes the priority rule (1) between at least three CGs:

[0196] In some implementations, the priority rules between the MCG and any SCG include any of the following, but are not limited to:

[0197] (1) The priority of MCG is higher than the priority of any SCG;

[0198] (2) The priority of MCG is lower than the priority of any SCG.

[0199] In some implementations, the priority rules between the MCG and any SCG are configured or predefined on the network side, and the embodiments of the present application do not limit this.

[0200] For example, suppose the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and suppose SCG1 fails. The network side allows SCG2 and MCG to report the failure information of SCG1. Since the priority of SCG2 is higher than that of MCG, the terminal can report the failure information of SCG1 through SCG2.

[0201] For example, suppose the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and suppose SCG1 fails. The network side allows MCG to report the failure information of SCG1, but does not allow SCG2 to report the failure information of SCG1. Based on this, the terminal can report the failure information of SCG1 through MCG.

[0202] The following describes the priority rule (2) between at least three CGs:

[0203] In some implementations, the priority rules between SCGs include any of the following, but are not limited to:

[0204] (1) Determine the priority of each SCG based on its identification;

[0205] (2) Determine the priority of each SCG based on its priority parameters.

[0206] In some implementations, the priority rules between the SCGs are configured or predefined on the network side, and the embodiments of the present application do not limit this.

[0207] In some implementations, the priority parameters of each SCG are configured or predefined on the network side, and the embodiments of the present application do not impose any restrictions on this.

[0208] For example, suppose the terminal is connected to four CGs, including: MCG, SCG1, SCG2 and SCG3, and suppose SCG1 fails. The network side allows SCG2 and SCG3 to report the failure information of SCG1. Assume that the SCG with a smaller identifier has a higher corresponding priority. Since the identifier of SCG2 is 2 and the identifier of SCG3 is 3, based on this, the priority of SCG2 is higher than that of SCG3. Based on this, the terminal can report the failure information of SCG1 through SCG2.

[0209] For example, suppose that the terminal is connected to four CGs, including: MCG, SCG1, SCG2 and SCG3, and suppose that SCG1 fails, the network side allows SCG2 and SCG3 to report the failure information of SCG1, and suppose that the network side configures the priority of SCG3 to be higher than the priority of SCG2. Based on this, the terminal can report the failure information of SCG1 through SCG3.

[0210] The following describes an example of reporting failure information based on the priority rules between the MCG and any SCG, as well as the priority rules between each SCG:

[0211] For example, suppose that the terminal is connected to four CGs, including: MCG, SCG1, SCG2 and SCG3, and suppose that SCG1 fails, the network side allows MCG, SCG2 and SCG3 to report the failure information of SCG1, and suppose that the priority of any SCG is higher than the priority of MCG, and the smaller the SCG identifier, the higher its corresponding priority. Based on this, the terminal can report the failure information of SCG1 through SCG2.

[0212] For example, suppose that the terminal is connected to four CGs, including: MCG, SCG1, SCG2 and SCG3, and suppose that SCG1 fails, the network side allows SCG2 and SCG3 to report the failure information of SCG1, suppose that the priority of any SCG is higher than the priority of MCG, and the network side configures the priority of SCG3 to be higher than the priority of SCG2, based on this, the terminal can report the failure information of SCG1 through SCG3.

[0213] The following describes the priority rule (3) between at least three CGs:

[0214] In some implementations, the priority parameters of at least three CGs are configured or predefined on the network side, and this embodiment of the present application does not impose any restrictions on this.

[0215] For example, suppose that the terminal is connected to four CGs, including: MCG, SCG1, SCG2 and SCG3, and suppose that SCG1 fails, the network side allows SCG2 and SCG3 to report the failure information of SCG1, and suppose that the network side configures the priority rules between MCG, SCG1, SCG2 and SCG3 as: SCG3>SCG2>SCG1>MCG. Based on this, the terminal can report the failure information of SCG1 through SCG3.

[0216] The following describes the priority rule (3) between at least three CGs:

[0217] For example, suppose that the terminal is connected to four CGs, including: MCG, SCG1, SCG2 and SCG3, and suppose that SCG1 fails, the network side allows SCG2 and SCG3 to report the failure information of SCG1, and suppose that the signal quality relationship between MCG, SCG1, SCG2 and SCG3 is: SCG3>SCG2>SCG1>MCG, based on this, the terminal can report the failure information of SCG1 through SCG3.

[0218] The following describes the priority rule (5) between at least three CGs:

[0219] In some implementations, the uplink resource is a PUSCH resource, but is not limited thereto.

[0220] In some possible implementations, the terminal can simultaneously send the failure information of the failed CG to the bottom layers of other CGs through the RRC layer. If the bottom layers of other CGs have uplink resources that can transmit the failure information, an indication information is sent to the RRC layer of the terminal to indicate that it has uplink resources to transmit the failure information. Based on this, the terminal determines that the priority of the CG whose indication information is received first through the RRC layer is higher than that of other CGs.

[0221] For example, assuming that the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and assuming that SCG1 fails, the terminal sends the failure information of SCG1 to the bottom layer of MN corresponding to MCG and SN2 corresponding to SCG 2 through the RRC layer at the same time. If the bottom layer of MN or SN2 has uplink resources that can transmit the failure information, an indication information is sent to the RRC layer of the terminal to indicate that it has uplink resources to transmit the failure information. Assuming that the terminal first receives the indication information sent by MCG through the RRC layer, it determines that the priority of MCG is higher than the priority of SCG2. Based on this, the terminal can report the failure information of SCG1 through SCG2.

[0222] In some possible implementations, when the target reporting method is the second reporting method, the terminal can determine the second CG based on the second reporting method and the target selection method.

[0223] In some implementations, the target selection method includes any of the following, but is not limited to:

[0224] (1) randomly selecting an SCG from the other CGs except the first CG among the at least three CGs;

[0225] (2) selecting the SCG with the highest signal quality among the at least three CGs except the first CG;

[0226] (3) Selecting an SCG with available uplink resources from the other CGs except the first CG among the at least three CGs;

[0227] (4) Select the SCG with the highest priority from among the at least three CGs except the first CG.

[0228] In some implementations, the other CGs among the at least three CGs except the first CG may be all other CGs among the at least three CGs except the first CG.

[0229] In some implementations, the other CGs among the at least three CGs except the first CG may be CGs among the at least three CGs except the first CG that meet the conditions met by the above-mentioned second CG, also referred to as CGs that are allowed to report failure information.

[0230] The following describes the target selection method (1):

[0231] For example, suppose the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and suppose SCG1 fails. The network side allows SCG2 and MCG to report the failure information of SCG1. Based on this, the terminal can randomly select a CG from MCG and SCG2 to report the failure information of SCG1.

[0232] The following describes target selection method (2):

[0233] For example, assume that a terminal is connected to three CGs, including MCG, SCG1, and SCG2. If SCG1 fails, the network allows SCG2 and MCG to report the failure of SCG1, and the signal quality of SCG2 is higher than that of MCG. Based on this, the terminal can report the failure of SCG1 through SCG2.

[0234] The following describes the target selection method (3):

[0235] For example, assume that the terminal is connected to three CGs, including: MCG, SCG1 and SCG2, and assume that SCG1 fails. The network side allows SCG2 and MCG to report the failure information of SCG1, while SCG2 has uplink available resources and MCG does not have uplink available resources. Based on this, the terminal can report the failure information of SCG1 through SCG2.

[0236] In some implementations, if there are multiple CGs with available uplink resources in other CGs except the first CG among at least three CGs, the terminal can randomly select one CG from the multiple CGs with available uplink resources, but is not limited to this.

[0237] For example, suppose the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and suppose SCG1 fails. The network side allows SCG2 and MCG to report the failure information of SCG1, and both SCG2 and MCG have uplink available resources. Based on this, the terminal can randomly select a CG from MCG and SCG2 to report the failure information of SCG1.

[0238] The following describes the target selection method (4):

[0239] In some implementations, the priorities of the at least three CGs other than the first CG are configured or predefined on the network side, and the embodiments of the present application do not impose any restrictions on this.

[0240] For example, assume that a terminal is connected to three CGs, including MCG, SCG1, and SCG2. If an MCG fails, the network allows SCG2 and SCG1 to report the MCG failure information, and the network configures SCG1 to have a higher priority than SCG2. Based on this, the terminal can report the MCG failure information through SCG1.

[0241] For example, assume that a terminal is connected to three CGs: MCG, SCG1, and SCG2. If an MCG fails, the network allows SCG2 and SCG1 to report the MCG failure. SCG1 is configured as the default SCG, and the protocol specifies that the default SCG has the highest priority. Therefore, the terminal can report the MCG failure through SCG1.

[0242] In some implementations, when the second CG is an SCG and the second CG has multiple SRBs, before the terminal reports the failure information of the first CG through the second CG, the terminal further includes: selecting at least one SRB according to a priority rule among the multiple SRBs. Based on this, the terminal can report the failure information of the first CG through the at least one SRB of the second CG.

[0243] In some implementations, the priority rules between multiple SRBs include at least one of the following, but are not limited to:

[0244] (1) The priority of the second split SRB of the second CG is higher than the priority of the third split SRB of the second CG;

[0245] (2) The priority of the second separate SRB is higher than the priority of the dedicated SRB of the second CG;

[0246] (3) The priority of the third separate SRB is higher than the priority of the dedicated SRB of the second CG;

[0247] Among them, the second separated SRB has at least two RLC bearers, one of which corresponds to the second CG, and the PDCP bearer corresponding to the second separated SRB is located in the SN corresponding to the first CG; the third separated SRB has at least two RLC bearers, one of which corresponds to the second CG, and the PDCP bearer corresponding to the third separated SRB is located in the MN.

[0248] For example, assuming that the terminal is connected to three CGs, including MCG, SCG1, and SCG2, and assuming that SCG1 fails and the network side allows SCG2 to report the failure information of SCG1, then the priority relationship between the SRBs of SCG2 includes: Split SRB3 with SCG2>Split SRB1 with SCG2>SRB 5, where Split SRB3 with SCG2 represents a separated SRB of SCG2, which has at least two RLC bearers, one of which corresponds to SCG2, and the PDCP bearer corresponding to the separated SRB is located in the SN1 corresponding to SCG1. Split SRB1 with SCG2 represents a separated SRB of SCG2, which has at least two RLC bearers, one of which corresponds to SCG2, and the PDCP bearer corresponding to the separated SRB is located in the MN corresponding to MCG. SRB 5 represents a dedicated bearer of SCG2.

[0249] In some feasible implementations, when the target reporting method is the first reporting method and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carry the identifier corresponding to the failure information of the first CG, so that the network side can distinguish whether the multiple failure information received are the same failure information or different failure information.

[0250] In some possible implementations, when the target reporting method is the first reporting method, the terminal can use a combination of multiple second CG bearers to report the failure information of the first CG.

[0251] For example, assuming that the terminal is connected to three CGs, including MCG, SCG1, and SCG2, and assuming that MCG fails, the terminal can report the failure information of the first CG through SCG1 and SCG2. The specific bearers of SCG1 and SCG2 are as follows:

[0252] SCG1 bearer = {SRB3, split SRB 1 with SCG1};

[0253] SCG2 bearer = {SRB4, split SRB 1 with SCG2}.

[0254] Split SRB 1 with SCG1 indicates a split SRB of SCG1. The split SRB has at least two RLC bearers, one of which corresponds to SCG1. The PDCP bearer corresponding to the split SRB is located in the MN corresponding to the MCG.

[0255] Split SRB 1 with SCG2 indicates a split SRB of SCG2. The split SRB has at least two RLC bearers, one of which corresponds to SCG2. The PDCP bearer corresponding to the split SRB is located in the MN corresponding to the MCG.

[0256] There are four types of bearer combinations for SCG1 and SCG2:

[0257] {SRB3,SRB4};

[0258] {SRB3,split SRB 1 with SCG2};

[0259] {split SRB 1 with SCG1,SRB4};

[0260] {split SRB 1 with SCG1,split SRB 1 with SCG2}.

[0261] In some implementations, when the terminal is configured with the first reporting mode, the terminal uses the first reporting mode as the target reporting mode, but is not limited thereto.

[0262] Based on this, the network side no longer needs to configure corresponding enabling information for each CG to indicate whether the CG can be used to report failure information of other abnormal CGs.

[0263] In some implementations, when the terminal is not configured with the first reporting method, the terminal uses the second reporting method as the target reporting method, but is not limited thereto.

[0264] In some implementations, when the terminal is configured with the second reporting mode, the terminal uses the second reporting mode as the target reporting mode, but is not limited thereto.

[0265] In some implementations, when the terminal is not configured with the second reporting mode, the terminal uses the first reporting mode as the target reporting mode, but is not limited thereto.

[0266] In some implementations, when the terminal is configured with the first reporting mode and the second reporting mode, the terminal may receive indication information from the network side and determine the target reporting mode based on the indication information, but is not limited thereto. The indication information is used to indicate whether to use the first reporting mode or the second reporting mode as the target reporting mode.

[0267] In some implementations, when the first CG is an MCG, if the terminal is configured with a terminal-level timer, when the terminal transmits failure information of the first CG, the terminal starts the terminal-level timer, and when the terminal-level timer expires, the RRC connection reconstruction process is triggered.

[0268] It should be understood that the terminal-level timer can also be started when the terminal generates failure information of the first CG. The embodiment of the present application does not limit the specific timing of the starting conditions of the terminal-level timer.

[0269] In some possible implementations, when MCG transmission is restored, or when a synchronous reconfiguration or switching command carrying PCell is received by RRC reconfiguration, or when the terminal receives an RRC release message, or when the RRC connection reconstruction process is initiated, the terminal-level timer stops running. The embodiments of the present application do not limit the specific timing of the stop condition of the terminal-level timer.

[0270] In some implementations, the terminal-level timer may be a terminal-level T316 timer, but is not limited thereto.

[0271] For example, in the event of an MCG failure, assuming that the terminal is configured with a T316 timer, no matter which SCG the terminal selects to report the MCG failure information, the terminal starts the T316 timer. When the T316 timer expires, the terminal triggers the RRC connection reconstruction process or initiates RRC connection reconstruction.

[0272] In some implementations, when the first CG is an MCG, if the terminal is not configured with a terminal-level timer, the terminal triggers the RRC connection reestablishment process when the first CG fails.

[0273] For example, in the event of an MCG failure, assuming that the terminal is not configured with a T316 timer, the terminal triggers the RRC connection reestablishment process or the terminal directly executes the RRC connection reestablishment process.

[0274] In some implementation methods, when the first CG is MCG and the target reporting method is the second reporting method, if the terminal is configured with a timer associated with the second CG, when the terminal transmits failure information of the first CG, the terminal starts the timer associated with the second CG.

[0275] It should be understood that the timer associated with the second CG can also be started when the terminal generates failure information of the first CG. The embodiment of the present application does not limit the specific timing of the start conditions of the timer associated with the second CG.

[0276] In some possible implementations, when the MCG transmission is restored, or when the RRC reconfiguration carries the synchronous reconfiguration or switching command of the PCell, or when the terminal receives the RRC release message, the timer associated with the second CG stops running. The embodiment of the present application does not limit the specific timing of the stop condition of the terminal-level timer.

[0277] It should be understood that the timer associated with the second CG is a CG-level timer, which may be a CG-level T316 timer, but is not limited thereto. In other words, each CG may correspond to a T316 timer.

[0278] In some implementations, when the timer associated with the second CG expires, the terminal triggers the RRC connection reestablishment process.

[0279] For example, suppose the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and suppose that MCG fails. Suppose the terminal selects SCG1 to report the failure information of MCG. When the terminal transmits the failure information of MCG, the terminal starts a timer associated with SCG1. When the timer times out, the terminal triggers the RRC connection reconstruction process.

[0280] In some possible implementations, when the timer associated with the second CG times out, the terminal determines whether there are other CGs besides the second CG. If there are other CGs, the terminal reselects a CG from the other CGs and reports the failure information of the first CG by reselecting the CG.

[0281] For example, suppose the terminal is connected to three CGs, including: MCG, SCG1 and SCG2, and suppose that MCG fails. Suppose the terminal selects SCG1 to report the failure information of MCG. After the terminal generates the failure information of MCG, the terminal starts the timer associated with SCG1. When the timer times out, the terminal reselects SCG2 to report the failure information of MCG.

[0282] In some implementations, after the terminal reselects a CG from other CGs, the terminal starts a timer associated with the reselected CG.

[0283] It should be understood that the embodiments of the present application do not limit the specific timing of the start conditions of the timer associated with the reselected CG.

[0284] In some possible implementations, when MCG transmission is restored, or when a synchronous reconfiguration or switching command carrying PCell is received by RRC reconfiguration, or when the terminal receives an RRC release message, the timer associated with the reselected CG stops running. The embodiments of the present application do not limit the specific timing of the stop condition of the timer associated with the reselected CG.

[0285] For example, suppose that the terminal is connected to three CGs, including: MCG, SCG1 and SCG2, and suppose that MCG fails, suppose that the terminal selects SCG1 to report the failure information of MCG, when the terminal transmits the failure information of MCG, the terminal starts the timer associated with SCG1, when the timer times out, the terminal reselects SCG2 to report the failure information of MCG, and starts the timer associated with SCG2, when the timer times out, the terminal has no available CG, in this case, the terminal triggers the RRC connection reconstruction process.

[0286] In some feasible embodiments, when the first CG is MCG and the target reporting method is the first reporting method, when the terminal transmits the failure information of the first CG, the terminal starts the timers corresponding to the other parts or all CGs among at least three CGs except the first CG; the terminal determines whether to trigger the RRC connection reconstruction process based on the timers corresponding to the other parts or all CGs.

[0287] In some possible implementations, the timers corresponding to some or all of the CGs in at least three CGs except the first CG can also be started when the terminal generates failure information of the first CG. The specific timing of the start conditions of these timers is not limited in the embodiment of the present application.

[0288] In some possible implementations, for any part or all of the at least three CGs except the first CG, when the MCG transmission is restored, or when the RRC reconfiguration carries the synchronous reconfiguration or switching command of the PCell, or when the terminal receives the RRC release message, the timer associated with the CG stops running. The embodiments of the present application do not limit the specific timing of the stop conditions of these timers.

[0289] It should be understood that, for any one of the other or all CGs in the at least three CGs except the first CG, the timer corresponding to the CG is also referred to as the timer associated with the CG, wherein the timer associated with the CG is a CG-level timer, which may be a CG-level T316 timer, but is not limited thereto. In other words, each CG may correspond to a T316 timer.

[0290] In some implementations, the other part of the CGs among the at least three CGs except the first CG may be the CGs among the at least three CGs except the first CG that meet the above-mentioned target conditions, also referred to as CGs that allow reporting of failure information.

[0291] In some possible implementations, the terminal determines whether to trigger the RRC connection reconstruction process based on the timers corresponding to other parts or all CGs, including: the terminal determines whether to trigger the RRC connection reconstruction process based on the longest duration of the timers corresponding to other parts or all CGs.

[0292] For example, suppose that the terminal is connected to three CGs, including: MCG, SCG1 and SCG2, and suppose that MCG fails, suppose that the terminal selects SCG1 and SCG2 to report the failure information of MCG at the same time, when the terminal transmits the failure information of MCG, the terminal starts the timer associated with SCG1 and the timer associated with SCG2. Assuming that the duration of the timer associated with SCG1 is 5ms and the duration of the timer associated with SCG2 is 10ms, then when the timer associated with SCG2 exceeds 10ms, the terminal triggers the RRC connection reconstruction process.

[0293] In some implementations, if there is no CG that meets the target conditions among at least three CGs, the terminal triggers the RRC connection reconstruction process.

[0294] For example, assuming that the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and assuming that MCG fails, assuming that the transmission of SCG1 is in a suspended state, and SCG2 is in a deactivated state, then the terminal triggers the RRC connection reestablishment process.

[0295] For example, assuming that the terminal is connected to three CGs, including MCG, SCG1 and SCG2, and assuming that MCG fails, and assuming that the transmissions of SCG1 and SCG2 are both in a suspended state, the terminal triggers the RRC connection reestablishment process.

[0296] An embodiment of the present application provides a wireless communication method, in which a terminal is configured with at least three CGs, the method comprising: in the event that the first CG among at least three CGs fails, the terminal determines the second CG according to a target reporting method; the terminal reports the failure information of the first CG through the second CG; wherein the target reporting method comprises any one of the following: a first reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs; a second reporting method: reporting the failure information of the first CG through one CG among all other CGs except the first CG among at least three CGs. That is, a method for reporting CG failure information by a terminal in a multi-connection scenario is provided to quickly restore an abnormal link.

[0297] The wireless communication method provided in the embodiment of the present application can be executed by a wireless communication device. In the embodiment of the present application, the wireless communication device provided in the embodiment of the present application is described by taking the wireless communication method executed by the wireless communication device as an example.

[0298] FIG9 is a schematic diagram of a wireless communication device 900 provided in an embodiment of the present application. As shown in FIG9 , the wireless communication device 900 is configured with at least three CGs, and the wireless communication device 900 includes:

[0299] A processing module 910 is configured to determine a second CG according to a target reporting method when a first CG among at least three CGs fails;

[0300] Communication module 920, configured to report failure information of the first CG through the second CG;

[0301] The target reporting method includes any of the following:

[0302] First reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0303] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0304] In some implementations, the processing module 910 is specifically configured to: determine the second CG according to the target reporting method and the target condition;

[0305] The second CG satisfies the target condition, which includes at least one of the following:

[0306] The transfer is not in a pending state;

[0307] In active state;

[0308] With SRB;

[0309] Configured or allowed to report failure information of the first CG.

[0310] In some implementations, the second CG having the SRB includes at least one of the following:

[0311] The second CG has a dedicated SRB;

[0312] The second CG has a first separated SRB;

[0313] The first separated SRB has at least two RLC bearers, one of which corresponds to the second CG.

[0314] In some implementations, the PDCP entity corresponding to the first separated SRB is located in the MN or the SN corresponding to the first CG.

[0315] In some implementations, the communication module 920 is further configured to receive first indication information.

[0316] The second CG is configured or allowed to report the failure information of the first CG, including:

[0317] The first indication information indicates that the second CG can report the failure information of the first CG; or,

[0318] The first indication information indicates one or more CGs that can report failure information, wherein the one or more CGs include the identifier of the second CG.

[0319] In some implementations, the situation where the first CG fails includes at least one of the following:

[0320] The wireless link of the first CG fails;

[0321] Synchronous reconfiguration of the first CG failed;

[0322] The configuration of the first CG failed;

[0323] The integrity check of the SRB corresponding to the first CG failed.

[0324] In some implementations, the processing module 910 is further configured to, when the wireless communication apparatus is configured with the first reporting mode, use the first reporting mode as the target reporting mode.

[0325] In some implementations, the processing module 910 is further configured to use the second reporting mode as the target reporting mode when the wireless communication apparatus is not configured with the first reporting mode.

[0326] In some implementations, when the target reporting method is the second reporting method, the processing module 910 is specifically used to: determine the second CG according to the priority rules between the second reporting method and at least three CGs.

[0327] In some implementations, the priority rules among the at least three CGs include any of the following:

[0328] Priority rules between the MCG and any SCG;

[0329] Priority rules between various SCGs;

[0330] determining priorities of at least three CGs based on priority parameters of the at least three CGs;

[0331] The CG with higher signal quality among at least three CGs has a higher corresponding priority;

[0332] Among at least three CGs, the CG that obtains uplink resources earlier has a higher corresponding priority.

[0333] In some implementations, the priority rules between the MCG and any SCG or the priority rules between various SCGs are configured or predefined on the network side.

[0334] In some implementations, the priority rules between SCGs include any of the following:

[0335] Determine the priority of each SCG based on its identification;

[0336] The priority of each SCG is determined according to the priority parameters of each SCG.

[0337] In some possible implementations, when the target reporting method is the first reporting method and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carry the identifier corresponding to the failure information of the first CG.

[0338] In some implementations, when the second CG is an SCG and the second CG has multiple SRBs, the processing module 910 is further used to: select at least one SRB according to a priority rule among the multiple SRBs.

[0339] In some implementations, the priority rule between the multiple SRBs includes at least one of the following:

[0340] The priority of the second separated SRB of the second CG is higher than the priority of the third separated SRB of the second CG;

[0341] The priority of the second separate SRB is higher than the priority of the dedicated SRB of the second CG;

[0342] The priority of the third separate SRB is higher than the priority of the dedicated SRB of the second CG;

[0343] The second separated SRB has at least two RLC bearers, one of which corresponds to the second CG, and the PDCP bearer corresponding to the second separated SRB is located in the SN corresponding to the first CG;

[0344] The third separated SRB has at least two RLC bearers, one of which corresponds to the second CG, and the PDCP bearer corresponding to the third separated SRB is located in the MN.

[0345] In some implementations, when the first CG is an MCG, the processing module 910 is also used to: if the wireless communication device is configured with a terminal-level timer, when the wireless communication device transmits failure information of the first CG, start the terminal-level timer, and when the terminal-level timer expires, trigger the RRC connection reconstruction process.

[0346] In some implementations, when the first CG is MCG and the target reporting method is the second reporting method, the processing module 910 is also used to: if the wireless communication device is configured with a timer associated with the second CG, when the wireless communication device transmits failure information of the first CG, start the timer associated with the second CG.

[0347] In some possible implementations, when the timer associated with the second CG times out, the processing module 910 is also used to trigger the RRC connection reconstruction process, or, when the timer associated with the second CG times out, the processing module 910 is also used to: determine whether there are other CGs besides the second CG; if there are other CGs, reselect a CG from the other CGs, and report the failure information of the first CG through the reselected CG.

[0348] In some implementations, the processing module 910 is further used to: after reselecting a CG from other CGs, start a timer associated with the reselected CG.

[0349] In some implementable embodiments, when the first CG is an MCG and the target reporting method is the first reporting method, the processing module 910 is also used to: when the wireless communication device transmits the failure information of the first CG, start the timers corresponding to the other parts or all CGs of at least three CGs except the first CG; determine whether to trigger the RRC connection reconstruction process based on the timers corresponding to the other parts or all CGs.

[0350] In some implementations, the processing module 910 is further used to trigger the RRC connection reconstruction process if there is no CG that meets the target conditions among at least three CGs.

[0351] The wireless communication device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiments of the present application.

[0352] The wireless communication device provided in the embodiment of the present application can implement the various processes implemented by the terminal in the method embodiment shown in Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0353] FIG10 is a schematic diagram of a wireless communication device 1000 provided in an embodiment of the present application. The wireless communication device 1000 includes:

[0354] The communication module 1010 is configured to receive failure information of the first CG reported by the terminal through the second CG;

[0355] The terminal is configured with at least three cell groups CG, the first CG is the CG where the failure occurs among the at least three CGs, and the second CG is determined by the terminal according to the target reporting mode;

[0356] Target reporting methods include any of the following:

[0357] First reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0358] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0359] In some implementations, the second CG is determined by the terminal according to a target reporting method and a target condition;

[0360] The second CG satisfies the target condition, which includes at least one of the following:

[0361] The transfer is not in a pending state;

[0362] In active state;

[0363] With SRB;

[0364] Configured or allowed to report failure information of the first CG.

[0365] In some implementations, the second CG having the SRB includes at least one of the following:

[0366] The second CG has a dedicated SRB;

[0367] The second CG has a first separated SRB;

[0368] The first separated SRB has at least two RLC bearers, one of which corresponds to the second CG.

[0369] In some implementations, the PDCP entity corresponding to the first separated SRB is located in the MN or the SN corresponding to the first CG.

[0370] In some implementations, the communication module 1010 is further configured to send first indication information.

[0371] The second CG is configured or allowed to report the failure information of the first CG, including:

[0372] The first indication information indicates that the second CG can report the failure information of the first CG; or,

[0373] The first indication information indicates one or more CGs that can report failure information, wherein the one or more CGs include the identifier of the second CG.

[0374] In some implementations, the situation where the first CG fails includes at least one of the following:

[0375] The wireless link of the first CG fails;

[0376] Synchronous reconfiguration of the first CG failed;

[0377] The configuration of the first CG failed;

[0378] The integrity check of the SRB corresponding to the first CG failed.

[0379] In some implementations, when the target reporting method is the second reporting method, the second CG is determined by the terminal according to a priority rule between the target reporting method and at least three CGs.

[0380] In some implementations, the priority rules among the at least three CGs include any of the following:

[0381] Priority rules between the MCG and any SCG;

[0382] Priority rules between various SCGs;

[0383] determining priorities of at least three CGs based on priority parameters of the at least three CGs;

[0384] The CG with higher signal quality among at least three CGs has a higher corresponding priority;

[0385] Among at least three CGs, the CG that obtains uplink resources earlier has a higher corresponding priority.

[0386] In some implementations, the priority rules between the MCG and any SCG or the priority rules between various SCGs are configured or predefined on the network side.

[0387] In some implementations, the priority rules between SCGs include any of the following:

[0388] Determine the priority of each SCG based on its identification;

[0389] The priority of each SCG is determined according to the priority parameters of each SCG.

[0390] In some possible implementations, when the target reporting method is the first reporting method and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carry the identifier corresponding to the failure information of the first CG.

[0391] In some implementations, when the second CG is an SCG and the second CG has multiple SRBs, a priority rule among the multiple SRBs is used to select at least one SRB.

[0392] In some implementations, the priority rule between the multiple SRBs includes at least one of the following:

[0393] The priority of the second separated SRB of the second CG is higher than the priority of the third separated SRB of the second CG;

[0394] The priority of the second separate SRB is higher than the priority of the dedicated SRB of the second CG;

[0395] The priority of the third separate SRB is higher than the priority of the dedicated SRB of the second CG;

[0396] The second separated SRB has at least two RLC bearers, one of which corresponds to the second CG, and the PDCP bearer corresponding to the second separated SRB is located in the SN corresponding to the first CG;

[0397] The third separated SRB has at least two RLC bearers, one of which corresponds to the second CG, and the PDCP bearer corresponding to the third separated SRB is located in the MN.

[0398] The wireless communication device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a network device, or it can be a device other than a network device. For example, the network device can include but is not limited to the first network device, the second network device, and the third network device listed above. Other devices can be servers, NAS, etc., which are not specifically limited in the embodiments of the present application.

[0399] The wireless communication device provided in the embodiment of the present application can implement the various processes implemented by the network device in the method embodiment shown in Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0400] FIG11 is a schematic block diagram of a communication device provided in an embodiment of the present application; as shown in FIG11 , an embodiment of the present application further provides a communication device 1100, comprising a processor 1101 and a memory 1102, wherein the memory 1102 stores a program or instruction that can be run on the processor 1101. For example, when the communication device 1100 is a terminal, when the program or instruction is executed by the processor 1101, each step performed by the terminal in the method embodiment shown in FIG4 is implemented, and the same technical effect can be achieved. When the communication device 1100 is a network device, when the program or instruction is executed by the processor 1101, each step performed by the network device in the method embodiment shown in FIG4 is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0401] The present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the various steps performed by the terminal in the method embodiment shown in FIG. 4 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and the various implementation processes and implementation methods of the aforementioned method embodiment are applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG. 12 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0402] The terminal 1200 includes but is not limited to: a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209 and at least some of the components of the processor 1210.

[0403] Those skilled in the art will appreciate that the terminal 1200 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1210 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG12 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0404] It should be understood that in an embodiment of the present application, the input unit 1204 may include a graphics processing unit (GPU) 12041 and a microphone 12042, and the graphics processor 12041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1206 may include a display panel 12061, and the display panel 12061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1207 includes a touch panel 12071 and at least one of other input devices 12072. The touch panel 12071 is also called a touch screen. The touch panel 12071 may include two parts: a touch detection device and a touch controller. Other input devices 12072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0405] In the embodiment of the present application, after receiving downlink data from a network device, the RF unit 1201 may transmit the data to the processor 1210 for processing. Furthermore, the RF unit 1201 may send uplink data to the network device. Typically, the RF unit 1201 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0406] The memory 1209 can be used to store software programs or instructions and various data. The memory 1209 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1209 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1209 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0407] Processor 1210 may include one or more processing units. Optionally, processor 1210 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1210.

[0408] The processor 1210 is configured to: when a first CG among at least three CGs fails, the terminal determines a second CG according to a target reporting method;

[0409] The radio frequency unit 1201 is configured to report failure information of the first CG through the second CG;

[0410] The target reporting method includes any of the following:

[0411] First reporting method: reporting the failure information of the first CG through all other CGs except the first CG among at least three CGs;

[0412] The second reporting method: report the failure information of the first CG through one CG among all other CGs among at least three CGs except the first CG.

[0413] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the corresponding method embodiment on the terminal side, and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.

[0414] The present application also provides a network device including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute programs or instructions to implement the various processes implemented by the network device in the method embodiment shown in FIG4 . This network device embodiment corresponds to the method embodiment executed by the aforementioned network device, and the various implementation processes and implementation methods of the aforementioned method embodiment are applicable to this network device embodiment and can achieve the same technical effects.

[0415] Specifically, embodiments of the present application also provide a network device. As shown in Figure 13, network device 1300 includes an antenna 131, a radio frequency device 132, a baseband device 133, a processor 134, and a memory 135. Antenna 131 is connected to radio frequency device 132. In the uplink direction, radio frequency device 132 receives information via antenna 131 and sends the received information to baseband device 133 for processing. In the downlink direction, baseband device 133 processes the information to be transmitted and sends it to radio frequency device 132. Radio frequency device 132 processes the received information and then sends it through antenna 131.

[0416] The method executed by the network device in the above embodiment may be implemented in the baseband device 133 , which includes a baseband processor.

[0417] The baseband device 133 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 13, one of the chips is, for example, a baseband processor, which is connected to the memory 135 through a bus interface to call the program in the memory 135 to execute the network device operations shown in the above method embodiment.

[0418] The network device may further include a network interface 136 , which is, for example, a Common Public Radio Interface (CPRI).

[0419] Specifically, the network device 1300 of an embodiment of the present invention also includes: instructions or programs stored in the memory 135 and executable on the processor 134. The processor 134 calls the instructions or programs in the memory 135 to execute the steps performed by the network device in the method embodiment shown in FIG4 and achieve the same technical effect. To avoid repetition, they will not be described here.

[0420] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by the processor, the various processes of the method embodiment shown in Figure 4 above are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0421] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0422] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the method embodiment shown in Figure 4 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0423] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0424] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the method embodiment shown in Figure 4 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0425] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network device, wherein the terminal can be used to execute the various processes corresponding to the target terminal in the method embodiment shown in Figure 4 as described above, and the network device can be used to execute the various processes corresponding to the network device in the method embodiment shown in Figure 4 as described above.

[0426] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0427] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for causing a terminal or network device to execute the methods described in each embodiment of the present application.

[0428] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A wireless communication method, wherein, The terminal is configured with at least three cell groups CG, and the method includes: When a failure occurs in a first CG among the at least three CGs, the terminal determines a second CG according to a target reporting manner; The terminal reports the failure information of the first CG through the second CG; Wherein, the target reporting manner includes any one of the following: First reporting manner: Reporting the failure information of the first CG through all other CGs among the at least three CGs except the first CG; Second reporting manner: Reporting the failure information of the first CG through one CG among all other CGs among the at least three CGs except the first CG.

2. The method according to claim 1, wherein, The terminal determines the second CG according to the target reporting manner, including: The terminal determines the second CG according to the target reporting manner and target conditions; Wherein, the second CG meets the target conditions, and the target conditions include at least one of the following: The transmission is not in a suspended state; It is in an active state; It has a signaling radio bearer SRB; It is configured or allowed to report the failure information of the first CG.

3. The method according to claim 2, wherein, The second CG having an SRB includes at least one of the following: The second CG has a dedicated SRB; The second CG has a first split SRB; Wherein, the first split SRB has at least two radio link control RLC bearers, and one RLC bearer corresponds to the second CG.

4. The method according to claim 3, wherein, The PDCP entity corresponding to the first split SRB is located in the master node MN or the secondary node SN corresponding to the first CG.

5. The method according to any one of claims 2 - 4, wherein, It further includes: The terminal receives first indication information; Wherein, the second CG being configured or allowed to report the failure information of the first CG includes: The first indication information indicates that the second CG can report the failure information of the first CG; or, The first indication information indicates one or more CGs that can report the failure information, wherein the one or more CGs include the identifier of the second CG.

6. The method according to any one of claims 1-5, wherein, The situation where the first CG fails includes at least one of the following: Radio link failure of the first CG; Synchronization reconfiguration failure of the first CG; Configuration failure of the first CG; Integrity detection failure of the SRB corresponding to the first CG.

7. The method according to any one of claims 1-6, wherein, It further includes: When the terminal is configured with the first reporting manner, the terminal uses the first reporting manner as the target reporting manner.

8. The method according to any one of claims 1-6, wherein, It further includes: When the terminal is not configured with the first reporting manner, the terminal uses the second reporting manner as the target reporting manner.

9. The method according to any one of claims 1-8, wherein When the target reporting manner is the second reporting manner, the terminal determines the second CG according to the target reporting manner, including: The terminal determines the second CG according to the second reporting manner and the priority rule among the at least three CGs.

10. The method according to claim 9, wherein, The priority rule among the at least three CGs includes any one of the following: The priority rule between MCG and any SCG; The priority rule among each SCG; Determining the priority of the at least three CGs according to the priority parameters of the at least three CGs; Among the at least three CGs, the higher the signal quality of a CG, the higher its corresponding priority. Among the at least three CGs, the earlier the uplink resource acquisition time of a CG, the higher its corresponding priority.

11. The method according to claim 10, wherein, The priority rule between the MCG and any SCG or the priority rules between the respective SCGs are configured by the network side or predefined.

12. The method according to claim 10 or 11, wherein The priority rules between the respective SCGs include any one of the following: Determine the priorities of the respective SCGs according to the identities of the respective SCGs. Determine the priorities of the respective SCGs according to the priority parameters of the respective SCGs.

13. The method according to any one of claims 1-8, wherein, When the target reporting method is the first reporting method and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carries the identifier corresponding to the failure information of the first CG.

14. The method according to any one of claims 1-13, wherein, When the second CG is an SCG and the second CG has multiple SRBs, before the terminal reports the failure information of the first CG through the second CG, it further includes: The terminal selects at least one SRB according to the priority rule between the multiple SRBs.

15. The method according to claim 14, wherein, The priority rules between the multiple SRBs include at least one of the following: The priority of the second split SRB of the second CG is higher than the priority of the third split SRB of the second CG. The priority of the second split SRB is higher than the priority of the dedicated SRB of the second CG. The priority of the third split SRB is higher than the priority of the dedicated SRB of the second CG. Among them, the second split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the second split SRB is located in the SN corresponding to the first CG. The third split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the third split SRB is located in the MN.

16. The method according to any one of claims 1-13, wherein, When the first CG is an MCG, the method further includes: If the terminal is configured with a terminal-level timer, when the terminal transmits the failure information of the first CG, the terminal starts the terminal-level timer, and when the terminal-level timer expires, it triggers a radio resource control (RRC) connection reestablishment process.

17. The method according to any one of claims 1 - 12, wherein, When the first CG is an MCG and the target reporting method is the second reporting method, the method further includes: If the terminal is configured with a timer associated with the second CG, when the terminal transmits the failure information of the first CG, the terminal starts the timer associated with the second CG.

18. The method according to claim 17, wherein, It further includes: When the timer associated with the second CG expires, the terminal triggers an RRC connection reestablishment process, Or, When the timer associated with the second CG expires, the terminal determines whether there are other CGs in addition to the second CG. If there are other CGs, the terminal reselection a CG among the other CGs and reports the failure information of the first CG through the reselected CG.

19. The method according to claim 18, wherein, After the terminal reselects a Cell Group (CG) among other CGs, the method further includes: The terminal starts a timer associated with the reselected CG.

20. The method according to any one of claims 1-8, 13, wherein When the first CG is the Master Cell Group (MCG) and the target reporting mode is the first reporting mode, the method further includes: When the terminal transmits the failure information of the first CG, the terminal starts the timers respectively corresponding to the other part or all of the CGs among the at least three CGs except the first CG; The terminal determines whether to trigger the Radio Resource Control (RRC) connection reestablishment process according to the timers respectively corresponding to the other part or all of the CGs.

21. The method according to claim 2, wherein, It further includes: If there is no CG among the at least three CGs that meets the target condition, the terminal triggers the RRC connection reestablishment process.

22. A wireless communication method, wherein, It includes: The network device receives the failure information of the first CG reported by the terminal through the second CG; Wherein, the terminal is configured with at least three Cell Groups (CGs), the first CG is the CG that fails among the at least three CGs, and the second CG is determined by the terminal according to the target reporting mode; The target reporting mode includes any one of the following: The first reporting mode: reporting the failure information of the first CG through all the other CGs among the at least three CGs except the first CG; The second reporting mode: reporting the failure information of the first CG through one CG among all the other CGs among the at least three CGs except the first CG.

23. The method according to claim 22, wherein, The second CG is determined by the terminal according to the target reporting mode and the target condition; Wherein, the second CG meets the target condition, and the target condition includes at least one of the following: The transmission is not in a suspended state; It is in an active state; It has a Signaling Radio Bearer (SRB); It is configured or allowed to report the failure information of the first CG.

24. The method according to claim 23, wherein The second CG having an SRB includes at least one of the following: The second CG has a dedicated SRB; The second CG has a first split SRB; Wherein, the first split SRB has at least two Radio Link Control (RLC) bearers, and one of the RLC bearers corresponds to the second CG.

25. The method according to claim 24, wherein, The Packet Data Convergence Protocol (PDCP) entity corresponding to the first split SRB is located in the Master Node (MN) or the Secondary Node (SN) corresponding to the first CG.

26. The method according to any one of claims 23-25, wherein It further includes: The network device sends first indication information; Wherein, the second CG being configured or allowed to report the failure information of the first CG includes: The first indication information indicates that the second CG can report the failure information of the first CG; or, The first indication information indicates one or more CGs that can report the failure information, and among them, the identity of the second CG is included in the one or more CGs.

27. The method according to any one of claims 22 - 26, wherein The situation where the first CG fails includes at least one of the following: Radio Link Failure (RLF) of the first CG; Synchronization Reconfiguration Failure of the first CG; Configuration Failure of the first CG; Integrity check failure of the SRB corresponding to the first CG.

28. The method according to any one of claims 22-27, wherein When the target reporting mode is the second reporting mode, the second CG is determined by the terminal according to the target reporting mode and the priority rule among the at least three CGs.

29. The method according to claim 28, wherein, The priority rule among the at least three CGs includes any one of the following: Priority rules between the MCG and any SCG; Priority rules between each SCG; Determine the priority of the at least three CGs according to the priority parameters of the at least three CGs; Among the at least three CGs, the higher the signal quality of a CG, the higher its corresponding priority; Among the at least three CGs, the earlier the uplink resource acquisition time of a CG, the higher its corresponding priority.

30. The method according to claim 29, wherein, The priority rules between the MCG and the any SCG or the priority rules between each SCG are configured by the network side or predefined.

31. The method according to claim 29 or 30, wherein, The priority rules between each SCG include any of the following: Determine the priority of each SCG according to the identifier of each SCG; Determine the priority of each SCG according to the priority parameters of each SCG.

32. The method according to any one of claims 22-27, wherein, When the target reporting method is the first reporting method and there are multiple second CGs, the failure information of the first CG reported by the multiple second CGs all carries the identifier corresponding to the failure information of the first CG.

33. The method according to any one of claims 22 - 32, wherein, When the second CG is an SCG and the second CG has multiple SRBs, the priority rules between the multiple SRBs are used to select at least one SRB.

34. The method according to claim 33, wherein The priority rules between the multiple SRBs include at least one of the following: The priority of the second split SRB of the second CG is higher than the priority of the third split SRB of the second CG; The priority of the second split SRB is higher than the priority of the dedicated SRB of the second CG; The priority of the third split SRB is higher than the priority of the dedicated SRB of the second CG; Among them, the second split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the second split SRB is located in the SN corresponding to the first CG; The third split SRB has at least two RLC bearers, one of the RLC bearers corresponds to the second CG, and the PDCP bearer corresponding to the third split SRB is located in the MN.

35. A wireless communication device, wherein, The device is configured with at least three CGs, and the device includes: A processing module, configured to determine a second CG according to a target reporting method when a first CG among the at least three CGs fails; A communication module, configured to report the failure information of the first CG through the second CG; Among them, the target reporting method includes any of the following: The first reporting method: Report the failure information of the first CG through all other CGs among the at least three CGs except the first CG; The second reporting method: Report the failure information of the first CG through one CG among all other CGs except the first CG among the at least three CGs.

36. A wireless communication device, wherein, Includes: A communication module, configured to receive the failure information of the first CG reported by the terminal through the second CG; Among them, the terminal is configured with at least three cell groups CGs, the first CG is the CG that fails among the at least three CGs, and the second CG is determined by the terminal according to the target reporting method; The target reporting method includes any of the following: The first reporting method: reporting the failure information of the first CG through all the other CGs except the first CG among the at least three CGs; The second reporting method: reporting the failure information of the first CG through one CG among all the other CGs except the first CG among the at least three CGs.

37. A terminal, wherein, It includes a processor and a memory. The memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, the steps of the wireless communication method according to any one of claims 1 to 21 are implemented.

38. A network device, wherein, It includes a processor and a memory. The memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, the steps of the wireless communication method according to any one of claims 22 to 34 are implemented.

39. A readable storage medium, wherein, Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the wireless communication method according to any one of claims 1 to 21 is implemented, or the steps of the wireless communication method according to any one of claims 22 to 34 are implemented.

40. A chip, wherein, The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the wireless communication method according to any one of claims 1 to 21, or to implement the wireless communication method according to any one of claims 22 to 34.

41. A computer program product, wherein, The program product is stored in a storage medium. The program product is executed by at least one processor to implement the wireless communication method according to any one of claims 1 to 21, or to implement the wireless communication method according to any one of claims 22 to 34.

42. A wireless communication device, wherein, It includes that the wireless communication device is used to execute the wireless communication method according to any one of claims 1 to 21, or to execute the wireless communication method according to any one of claims 22 to 34.

Images