Method and apparatus for transmitting information

Abstract

The present application provides a method and apparatus for transmitting information. The method for transmitting information includes: a terminal device sending first information to a network device, where the first information includes information on a radio link failure occurring between the terminal device and a first cell, or the first information includes information indicating beam failure recovery between the terminal device and the first cell; the first information further includes information on a resource, and the information on the resource includes at least one of information on a beam, information on an uplink carrier, or information on a bandwidth part; and the network device performs mobile robustness optimization based on the first information. The method for transmitting information according to the embodiments of the present application helps the network device perform mobile robustness optimization (MRO) in a timely and accurate manner.

Description

[0001] This application is a divisional application of the invention application with the application date of September 28, 2018, the Chinese application number of 201811142479.7, and the invention name of "Method and Apparatus for Transmitting Information". Technical Field

[0002] This application relates to the field of communications, and more particularly, to a method and apparatus for transmitting information. Background Art

[0003] Improper handover (HO) parameter settings can have a negative impact on the user experience and also cause waste of network resources due to ping-pong handovers, handover failures, and radio link failures. Moreover, radio link failures caused by improper handover parameters affect both the user experience and network resources.

[0004] In the long term evolution (LTE) system, it is mentioned that manually setting the handover parameters of the system in the current system is very time-consuming, and it is quite costly to update the mobility parameters after the initial network deployment. At the same time, in some cases, the radio resource management (RRM) in the network device can detect problems and adjust the mobility parameters, but in some cases, RRM cannot solve the problems either. Therefore, mobility robust optimization (MRO) is proposed.

[0005] In the LTE system, MRO optimization is mainly used to optimize mobility parameters, such as parameters like the bias of the A3 handover event. Specifically, the network device determines whether it is necessary to optimize the mobility parameters based on the radio link failure (RLF) report reported by the terminal device, as well as the radio link failure indication (RLF indication) and handover report (HO report) interacted through the interface.

[0006] Currently, in the new radio (NR) system, there is no good mechanism to perform MRO in a timely and accurate manner. Summary of the Invention

[0007] In view of this, this application provides a method for transmitting information, which helps the network device to perform MRO in a timely and accurate manner.

[0008] In a first aspect, a method for transmitting information is provided. The method includes: a first network device receives first information from a terminal device, where the first information includes information about a radio link failure occurring between the terminal device and a first cell, or the first information includes information about beam failure recovery occurring between the terminal device and the first cell; the first information further includes information about a resource, and the information about the resource includes at least one of information about a beam, information about an uplink carrier, or information about a bandwidth part; the first network device performs mobile robustness optimization based on the first information.

[0009] In some possible implementation manners, the information about the resource includes any one or several of the following: an identifier of a beam, an identifier of an uplink carrier, or an identifier of a bandwidth part.

[0010] In the NR system, a beam (beam), an uplink carrier (conventional uplink carrier / supplementary uplink carrier), and a bandwidth part (bandwidth part, BWP) are introduced. Selecting different beams, uplink carriers, or broadband parts by the terminal device may cause a radio link failure (RLF) or a beam failure (beam failure, BF).

[0011] In some possible implementation manners, the first information includes information about a radio link failure occurring between the terminal device and a first cell, and the first information is an RLF report.

[0012] In some possible implementation manners, the first information includes information about beam failure recovery occurring between the terminal device and the first cell, and the first information is a BFR report.

[0013] In some possible implementation manners, the beam includes a synchronization signal block SSB and / or a channel state information reference signal CSI-RS.

[0014] In some possible implementation manners, the uplink carrier includes a conventional uplink carrier and a supplementary uplink carrier.

[0015] In the method for transmitting information according to the embodiments of the present application, when the terminal device has an RLF or BF, it can report a radio link failure report (RLF report) or a beam failure recovery report (BFR report) to the network device. Among them, the RLF report or the BFR report carries one or more of the information about the beam, the information about the uplink carrier, or the information about the broadband part, which helps the network device perform MRO in a timely and accurate manner.

[0016] In combination with the first aspect, in some possible implementations of the first aspect, when the first information includes information on beam failure recovery occurring between the terminal device and the first cell, the first information further includes at least one of the number of beam failures, the number of beam failure recoveries, or the duration of beam failure recovery.

[0017] In combination with the first aspect, in some possible implementations of the first aspect, the first cell is a cell under the first network device. When the first information includes information on beam failure recovery occurring between the terminal device and the first cell, the first network device performs mobility robustness optimization based on the first information, including: the first network device adjusts the configuration of the resources, or the first network device sends second information to a second network device, where the second information is used to instruct the second network device to adjust mobility parameters.

[0018] Exemplarily, the first network device may be a target network device, the second network device may be a source network device, the first cell is a cell under the target network device, the terminal device successfully switches from the second network device to the first network device. After a period of time, when BF occurs in the first cell under the first network device but BFR is successful, the terminal device sends the first information to the first network device, and the first network device determines the cause of BF. If it is a resource configuration problem, the first network device adjusts the resource configuration. If it is a downlink mobility parameter problem, the first network device may instruct the second network device to adjust the downlink mobility parameters.

[0019] In some possible implementations, the information on the resources reported by the terminal device includes information on beams (such as SSB and / or CSI-RS) (e.g., identification information). When the first network device determines that BF is caused by an unreasonable configuration of the beam threshold, the first network device adjusts the resource configuration, including: the first network device adjusts the first threshold corresponding to the SSB; and / or, the first network device adjusts the second threshold corresponding to the CSI-RS.

[0020] In some possible implementations, the information on the resources of the terminal device includes information on beams (e.g., identification information) and information on the uplink carrier (e.g., the identification of the uplink carrier). When the first network device determines that BF is caused by unreasonable configurations of the beam threshold and the uplink carrier threshold, the first network device adjusts the resource configuration, including: the first network device adjusts the first threshold corresponding to the SSB; and / or, the first network device adjusts the second threshold corresponding to the CSI-RS; and / or, the first network device adjusts the third threshold corresponding to the supplementary uplink carrier.

[0021] In some possible implementations, the first network device may also adjust the random access channel (RACH) resources.

[0022] In combination with the first aspect, in some possible implementations of the first aspect, the first cell is a cell under the first network device. When the first information includes information on a radio link failure occurring between the terminal device and the first cell, the first network device receives the first information from the terminal device, including: the first network device receives the first information sent by the second network device; wherein, based on the first information, the first network device performs mobility robustness optimization, including: the first network device adjusts the configuration of the resources, or the first network device sends second information to the second network device, and the second information is used to instruct the second network device to adjust mobility parameters.

[0023] Exemplarily, the first network device may be a target network device, the second network device may be a source network device, the first cell is a cell under the target network device. The terminal device experiences RLF during the process of switching from the second network device to the first network device, or the terminal device experiences RLF after successfully switching to the first network device. After the terminal device reconnects to the second network device, it sends the first information to the second network device, and the second network device forwards the first information to the first network device. The first network device determines the cause of the RLF. If it is a resource configuration problem, the first network device adjusts the resource configuration. If it is a downlink mobility parameter problem, the first network device may instruct the second network device to adjust the downlink mobility parameters.

[0024] In some possible implementations, the information on the resources reported by the terminal device includes information on beams (such as SSB and / or CSI-RS) (e.g., identification information). The first network device determines that the RLF is caused by an unreasonable configuration of the beam threshold. The first network device adjusts the resource configuration, including: the first network device adjusts the first threshold corresponding to the SSB; and / or the first network device adjusts the second threshold corresponding to the CSI-RS.

[0025] In some possible implementations, the information on the resources of the terminal device includes information on beams (e.g., identification information) and information on the uplink carrier (e.g., the identification of the uplink carrier). The first network device determines that the RLF is caused by unreasonable configurations of the beam threshold and the uplink carrier threshold. The first network device adjusts the resource configuration, including: the first network device adjusts the first threshold corresponding to the SSB; and / or the first network device adjusts the second threshold corresponding to the CSI-RS; and / or the first network device adjusts the third threshold corresponding to the supplementary uplink carrier.

[0026] In some possible implementations, the first network device may also adjust the random access channel (RACH) resources.

[0027] In combination with the first aspect, in some possible implementations of the first aspect, the information of the beam includes the identification of the beam and / or the measurement information of the beam. The identification of the beam includes the synchronization signal block (SSB) group number and / or the channel state information reference signal (CSI-RS) group number. The information of the uplink carrier includes the identification of the uplink carrier and / or the measurement information of the uplink carrier. The identification of the uplink carrier includes the frequency information of the uplink carrier. The uplink carrier includes a regular uplink carrier and / or a supplementary uplink carrier.

[0028] In combination with the first aspect, in some possible implementations of the first aspect, the first network device adjusts the configuration of the resources, including any one or any combination of the following: the first network device adjusts the first threshold value corresponding to the SSB; the first network device adjusts the second threshold value corresponding to the CSI-RS; the first network device adjusts the third threshold value corresponding to the supplementary uplink carrier; or, the first network device adjusts the random access channel (RACH) resources.

[0029] In combination with the first aspect, in some possible implementations of the first aspect, the protocol layer functions of the first network device include at least one of the radio link control protocol layer, the media access control layer, and the physical layer functions; and / or, the protocol layer functions of the second network device include at least one of the radio resource control protocol layer, the service data adaptation layer, and the packet data convergence protocol layer functions.

[0030] In combination with the first aspect, in some possible implementations of the first aspect, the first cell is a cell under the second network device. When the first information includes the information of beam failure recovery between the terminal device and the first cell, the first network device receives the first information from the terminal device, including: the first network device receives the first information sent by the second network device; wherein, based on the first information, the first network device performs mobile robustness optimization, including: the first network device adjusts the mobility parameters, or, the first network device sends the third information to the second network device, and the third information is used to instruct the second network device to adjust the configuration of the resources.

[0031] Exemplarily, the first network device may be a source network device, the second network device may be a target network device, the first cell is a cell under the target network device, the terminal device successfully switches from the first network device to the second network device. Within a period of time, when beamforming (BF) occurs in the first cell under the second network device but beamforming recovery (BFR) is successful, the terminal device sends the first information to the second network device, and the second network device forwards the first information to the first network device. The first network device determines the reason for BF. If it is a resource configuration problem, the first network device instructs the second network device to adjust the resource configuration. If it is a problem with downlink mobility parameters, the first network device adjusts the downlink mobility parameters.

[0032] In some possible implementation manners, the first network device adjusts the mobility parameters, including: the first network device adjusts the parameters related to A3 event.

[0033] Combined with the first aspect, in some possible implementation manners of the first aspect, the first cell is a cell under the second network device. When the first information includes the information that a radio link failure occurs between the terminal device and the first cell, the first network device performs mobility robustness optimization according to the first information, including: the first network device adjusts the mobility parameters, or the first network device sends a third information to the second network device, and the third information is used to instruct the second network device to adjust the resource configuration.

[0034] Exemplarily, the first network device may be a source network device, the second network device may be a target network device, the first cell is a cell under the target network device. The terminal device has a radio link failure (RLF) during the process of switching from the first network device to the second network device, or the terminal device has an RLF within a period of time after successfully switching from the first network device to the second network device. After the terminal device reconnects to the first network device, it sends the first information to the first network device. The first network device determines the reason for RLF. If it is a resource configuration problem, the first network device instructs the second network device to adjust the resource configuration. If it is a problem with downlink mobility parameters, the first network device adjusts the downlink mobility parameters.

[0035] In some possible implementation manners, the first network device adjusts the mobility parameters, including: the first network device adjusts the parameters related to A3 event.

[0036] Combined with the first aspect, in some possible implementation manners of the first aspect, the method further includes: the first network device receives a fourth indication information sent by the second network device, and the fourth indication information is used to indicate the adjusted resource configuration.

[0037] In combination with the first aspect, in some possible implementations of the first aspect, the protocol layer functions of the first network device include at least one of radio resource control protocol layer, service data adaptation layer, and packet data convergence protocol layer functions; and / or, the protocol layer functions of the second network device include at least one of radio link control protocol layer, media access control layer, and physical layer functions.

[0038] In a second aspect, a method for transmitting information is provided. The method includes: the first network device receives first information sent by a terminal device, where the first information includes information about beam failure recovery of the terminal device with a first cell.

[0039] In some possible implementations, the first information is a BFR report.

[0040] In a third aspect, a method for transmitting information is provided. The method includes: the first network device sends first information to a second network device, where the first information includes information about beam failure recovery of a terminal device with a first cell.

[0041] In some possible implementations, the first information is a BFR report.

[0042] In a fourth aspect, a method for transmitting information is provided. The method includes: the first network device sends indication information to a second network device, where the indication information is used to instruct the second network device to adjust the configuration of resources.

[0043] In some possible implementations, the resources include one or more of beams, uplink carriers, BWPs, or RACH resources.

[0044] In a fifth aspect, a method for transmitting information is provided. The method includes: the second network device receives indication information sent by the first network device, where the indication information is used to instruct the second network device to adjust the configuration of resources;

[0045] The second network device adjusts the configuration of the resources.

[0046] In some possible implementations, the resources include one or more of beams, uplink carriers, BWPs, or RACH resources.

[0047] In some possible implementations, the second network device adjusting the configuration of resources includes any one or any combination of the following: the second network device adjusts a first threshold value corresponding to the SSB; the second network device adjusts a second threshold value corresponding to the CSI-RS; the second network device adjusts a third threshold value corresponding to the supplementary uplink carrier; or, the second network device adjusts random access channel RACH resources.

[0048] In a sixth aspect, a method for transmitting information is provided. The method includes: a terminal device sending first information, where the first information includes information on a radio link failure occurring between the terminal device and a first cell, or the first information includes information on beam failure recovery occurring between the terminal device and the first cell; the first information further includes information on a resource, and the information on the resource includes at least one of information on a beam, information on an uplink carrier, or information on a bandwidth part.

[0049] In combination with the sixth aspect, in some possible implementation manners of the sixth aspect, when the first information includes information on beam failure recovery occurring between the terminal device and the first cell, the first information further includes at least one of the number of beam failures, the number of beam failure recoveries, or the duration of beam failure recovery.

[0050] In some possible implementation manners, before the terminal device sends the first information, the method further includes: the terminal device determining that the number of beam failures is greater than or equal to a first value; and / or the terminal device determining that the number of beam failure recoveries is greater than or equal to a second value; and / or the terminal device determining that a timer expires.

[0051] In some possible implementation manners, the first value and the second value are configured by a network device.

[0052] In combination with the sixth aspect, in some possible implementation manners of the sixth aspect, the information on the beam includes an identifier of the beam and / or measurement information of the beam, the identifier of the beam includes a synchronization signal block (SSB) group number and / or a channel state information reference signal (CSI-RS) group number, the information on the uplink carrier includes an identifier of the uplink carrier and / or measurement information of the uplink carrier, the identifier of the uplink carrier includes frequency information of the uplink carrier, and the uplink carrier includes a regular uplink carrier and / or a supplementary uplink carrier.

[0053] In the method for transmitting information according to the embodiments of the present application, when a terminal device has an RLF or BF, it can report a radio link failure report (RLF report) or a beam failure recovery report (BFR report) to a network device. Among them, the RLF report or the BFR report carries one or more of information on a beam, information on an uplink carrier, or information on a broadband part, which helps the network device perform MRO in a timely and accurate manner.

[0054] In a seventh aspect, a device for transmitting information is provided, which is used to execute the methods in the above first aspect to the fifth aspect and any possible implementation manners of the first aspect to the fifth aspect. Exemplarily, the device for transmitting signals may include units for executing the methods in the first aspect to the fifth aspect and any possible implementation manners of the first aspect to the fifth aspect.

[0055] In an eighth aspect, there is provided a device for transmitting information, configured to execute the method in the sixth aspect or any possible implementation manner thereof. Exemplarily, the device for transmitting signals may include units for executing the method in the sixth aspect or any possible implementation manner thereof.

[0056] In a ninth aspect, there is provided a device for transmitting signals, which may be a network device (a first network device or a second network device) in the above method design or a chip disposed in a network device. The device includes: a processor coupled to a memory and configured to execute instructions in the memory to implement the methods in the first aspect to the fifth aspect and any possible implementation manner of the first aspect to the fifth aspect. Optionally, the device further includes a memory. Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface.

[0057] When the device is a first network device, the communication interface may be a transceiver or an input / output interface.

[0058] When the device is a chip disposed in a first network device, the communication interface may be an input / output interface.

[0059] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0060] In a tenth aspect, there is provided a device for transmitting signals, which may be a terminal device in the above method design or a chip disposed in a terminal device. The device includes: a processor coupled to a memory and configured to execute instructions in the memory to implement the method executed by the terminal device in the sixth aspect or any possible implementation manner thereof. Optionally, the device further includes a memory. Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface.

[0061] When the device is a terminal device, the communication interface may be a transceiver or an input / output interface.

[0062] When the device is a chip disposed in a terminal device, the communication interface may be an input / output interface.

[0063] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0064] In an eleventh aspect, there is provided a program which, when executed by a processor, is configured to execute the methods provided in the first aspect to the sixth aspect.

[0065] In a twelfth aspect, there is provided a program product, which includes program code that, when run by a communication unit, a processing unit, a transceiver, or a processor of a device (such as a network device or a terminal device), causes the device to execute any of the methods in the first aspect to the sixth aspect and their possible implementation manners described above.

[0066] In a thirteenth aspect, there is provided a computer-readable medium storing a program that causes a device (such as a network device or a terminal device) to execute any of the methods in the first aspect to the sixth aspect and their possible implementation manners described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 FIG. is a schematic diagram of a communication system provided by an embodiment of the present application.

[0068] Figure 2 FIG. is a schematic diagram of an application scenario of the technical solution provided by an embodiment of the present application.

[0069] Figure 3 FIG. is another schematic diagram of an application scenario of the technical solution provided by an embodiment of the present application.

[0070] Figure 4 FIG. is a schematic diagram of a network architecture provided by an embodiment of the present application.

[0071] Figure 5 FIG. is another schematic diagram of a network architecture provided by an embodiment of the present application.

[0072] Figure 6 FIG. is a schematic flowchart of a method for transmitting information provided by an embodiment of the present application.

[0073] Figure 7 FIG. is another schematic flowchart of a method for transmitting information provided by an embodiment of the present application.

[0074] Figure 8 FIG. is another schematic flowchart of a method for transmitting information provided by an embodiment of the present application.

[0075] Figure 9 FIG. is another schematic flowchart of a method for transmitting information provided by an embodiment of the present application.

[0076] Figure 10 FIG. is another schematic flowchart of a method for transmitting information provided by an embodiment of the present application.

[0077] Figure 11 FIG. is another schematic flowchart of a method for transmitting information provided by an embodiment of the present application.

[0078] Figure 12It is another schematic flowchart of the method for transmitting information provided by an embodiment of the present application.

[0079] Figure 13 It is another schematic flowchart of the method for transmitting information provided by an embodiment of the present application.

[0080] Figure 14 It is another schematic flowchart of the method for transmitting information provided by an embodiment of the present application.

[0081] Figure 15 It is another schematic flowchart of the method for transmitting information provided by an embodiment of the present application.

[0082] Figure 16 It is another schematic flowchart of the method for transmitting information provided by an embodiment of the present application.

[0083] Figure 17 It is another schematic flowchart of the method for transmitting information provided by an embodiment of the present application.

[0084] Figure 18 It is another schematic flowchart of the method for transmitting information provided by an embodiment of the present application.

[0085] Figure 19 It is another schematic flowchart of the method for transmitting information provided by an embodiment of the present application.

[0086] Figure 20 It is a schematic block diagram of the device for transmitting information provided by an embodiment of the present application.

[0087] Figure 21 It is another schematic block diagram of the device for transmitting information provided by an embodiment of the present application.

[0088] Figure 22 It is a schematic structural diagram of the network device provided by an embodiment of the present application.

[0089] Figure 23 It is another schematic structural diagram of the network device provided by an embodiment of the present application.

[0090] Figure 24 It is a schematic structural diagram of the terminal device provided by an embodiment of the present application. Detailed implementation manners

[0091] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0092] The technical solution of the embodiment of this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, future 5th generation (5G) system or New Radio (NR), etc.

[0093] The terminal device in the embodiment of this application may refer to user equipment, access terminal device, user unit, user station, mobile station, mobile terminal, remote station, remote terminal device, mobile device, user terminal device, terminal device, wireless communication device, user agent or user device. The terminal device may also be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in the future 5G network or terminal device in the future evolved Public Land Mobile Network (PLMN), etc. The embodiment of this application does not limit this.

[0094] The network device in the embodiments of the present application can be a device for communicating with a terminal device. The network device can be a base transceiver station (BTS) in a global system for mobile communications (GSM) system or a code division multiple access (CDMA) system, or a NodeB (NB) in a wideband code division multiple access (WCDMA) system, or an evolved NodeB (eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (CRAN) scenario, or the network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network, etc. The embodiments of the present application do not limit this.

[0095] In the embodiments of the present application, the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called main memory). The operating system can be any one or more computer operating systems that implement service processing through processes. For example, the Linux operating system, the Unix operating system, the Android operating system, the iOS operating system, or the Windows operating system, etc. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. Moreover, the embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application. As long as it can communicate according to the method provided in the embodiments of the present application by running a program recording the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application can be a terminal device or a network device, or a functional module in the terminal device or the network device that can call and execute the program.

[0096] In addition, various aspects or features of the present application can be implemented as a method, an apparatus, or an article of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used in the present application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media can include, but are not limited to: magnetic storage devices (such as hard disks, floppy disks, or magnetic tapes, etc.), optical discs (such as compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (such as erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable media" can include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0097] Figure 1 FIG. 4 is a schematic diagram of a communication system 100 provided by an embodiment of the present application. As Figure 1 shown, the terminal device 130 accesses the wireless network to obtain services from the external network (such as the Internet) through the wireless network, or communicates with other terminal devices through the wireless network. The wireless network includes a radio access network (RAN) 110 and a core network (CN) 120, where the RAN 110 is used to connect the terminal device 130 to the wireless network, and the CN 120 is used to manage the terminal device and provide a gateway for communicating with the external network.

[0098] It should be understood that the communication method provided by the present application is applicable to wireless communication systems. For example, Figure 1 the wireless communication system 100 shown in FIG. 4. There is a wireless communication connection between two communication devices in the wireless communication system. One of the two communication devices can correspond to Figure 1 the terminal device 130 shown in FIG. 4. For example, it can be Figure 1 the terminal device 130 in FIG. 4, or it can be a chip configured in the terminal device 130. The other of the two communication devices can correspond to Figure 1 the RAN 110 shown in FIG. 4. For example, it can be Figure 1 the RAN 110 in FIG. 4, or it can be a chip configured in the RAN 110.

[0099] Hereinafter, without loss of generality, the interaction process between the terminal device and the network device is taken as an example to detail the embodiments of the present application. It can be understood that any terminal device in the wireless communication system can communicate with one or more network devices having a wireless communication connection based on the same method. The present application makes no limitation thereto.

[0100] Figure 2 It is a schematic diagram of the application scenario of the technical solution provided by the embodiment of the present application. For example, as Figure 2 shown, for example, the terminal device 131 is in cell A under RAN111. At a certain moment, the terminal device 131 receives a handover command (HO command) from RAN111, instructing the terminal device 131 to hand over to cell B under RAN112. Before the handover is completed, an RLF occurs. The terminal device 131 performs cell selection, selects cell A and attempts to perform radio resource control (RRC) re-establishment. The terminal device 131 re-establishes a connection to cell A. After the re-establishment is successful, RAN111 can recognize that this is a scenario where the handover is too early.

[0101] For another example, as Figure 2 shown, the terminal device 131 is in cell A under RAN111. At a certain moment, the terminal device 131 receives an HO command from RAN111, instructing the terminal device 131 to hand over to cell B under RAN112. The terminal device 131 successfully hands over to cell B under RAN112. RAN112 sends context release information to RAN111 and starts a timer timer. An RLF occurs within a period of time after the handover is completed. The terminal device 131 performs cell reselection, selects the source cell A and then attempts to perform an RRC connection. After the RRC re-establishment is completed, RAN111 sends an RLF indication to RAN112. If the timer is still running when RAN112 receives the RLF indication, then RAN112 will send a handover report (HO report) to RAN111, thereby indicating to RAN111 that this handover is a case of too early handover.

[0102] For yet another example, the terminal device 131 is in cell A under RAN111. At a certain moment, the terminal device 131 receives an HO command from RAN111, instructing the terminal device 131 to hand over to cell B under RAN112. Before the handover is completed, an RLF occurs. The terminal device 131 performs cell selection, selects cell B and performs RRC re-establishment. After re-establishing a connection to cell B, RAN112 sends an RLF indication to RAN111. The RLF indication includes information such as an RLF report. RAN111 can recognize that this is a scenario where the handover is too late.

[0103] For another example, in cell A of the terminal device 131 under RAN111, at a certain moment, the terminal device 131 receives an HO command from RAN111, instructing the terminal device 131 to hand over to cell B under RAN112. The terminal device 131 successfully hands over to cell B under RAN112. After the handover is completed, within a period of time, the terminal device experiences beam failure (BF) or beam failure recovery (BFR) in cell B. At this time, since the RRC connection between the terminal device 131 and cell B still exists, the terminal device 131 can report a beam failure recovery report (BFR report) to RAN112. RAN112 can determine the cause of the beam failure. If it is determined that the handover was too early, then RAN112 will send a handover report (HO report) to RAN111, thereby indicating to RAN111 that this handover is a premature handover. Or if it is determined that it was not caused by a premature handover, then other scenarios can be defined. The specific names of other scenarios are not limited in the embodiments of this application.

[0104] Figure 3 It is another schematic diagram of the application scenario of the technical solution provided by the embodiments of this application. As Figure 3 shown, for example, at a certain moment, the terminal device 131 receives an HO command from RAN111, instructing the terminal device 131 to hand over to cell B under RAN112. Before the handover is completed, RLF occurs. The terminal device 131 performs cell selection, selects cell C under RAN113 and performs RRC re - establishment. After re - establishing the connection to cell C, RAN113 identifies the source cell A and then sends an RLF indication to RAN111. RAN111 can identify that this is a scenario of handing over to the wrong cell.

[0105] For another example, in cell A of the terminal device 131 under RAN111, at a certain moment, the terminal device 131 receives an HO command from RAN111, instructing the terminal device 131 to hand over to cell B under RAN112. The terminal device 131 successfully hands over to cell B under RAN112. RAN112 sends context release information to RAN111 and starts a timer, timer. After the handover is completed, within a period of time, RLF occurs. The terminal device 131 performs cell reselection, selects cell C under RAN113 and performs RRC re - establishment. After the RRC re - establishment is completed, RAN111 sends an RLF indication to RAN112. If the timer is still running when RAN112 receives the RLF indication, then RAN112 will send an HO report to RAN111, thereby indicating to RAN111 that the handover is to the wrong cell.

[0106] Figure 4 is a schematic diagram of a network architecture provided by an embodiment of the present application. As Figure 4 shown, the network architecture includes a CN device and a RAN device. The RAN device includes a baseband device and a radio frequency device. The baseband device can be implemented by one node or multiple nodes. The radio frequency device can be remotely implemented independently from the baseband device, integrated in the baseband device, or partially remotely implemented and partially integrated in the baseband device. For example, in an LTE communication system, the RAN device (eNB) includes a baseband device and a radio frequency device, and the radio frequency device can be remotely arranged relative to the baseband device. For example, a remote radio unit (RRU) is remotely arranged relative to a BBU.

[0107] The communication between the RAN device and the terminal device follows a certain protocol layer structure. For example, the control plane protocol layer structure can include functions of protocol layers such as a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, and a physical layer. The user plane protocol layer structure can include functions of protocol layers such as the PDCP layer, the RLC layer, the MAC layer, and the physical layer; in one implementation, a service data adaptation protocol (SDAP) layer can also be included above the PDCP layer.

[0108] The functions of these protocol layers can be implemented by one node or multiple nodes; for example, in an evolved structure, the RAN device can include a centralized unit (CU) and a distributed unit (DU), and multiple DUs (for example, DU1 and DU2) can be centrally controlled by one CU. As Figure 2 shown, the CU and DU can be divided according to the protocol layers of the wireless network. For example, the functions of the PDCP layer and the above protocol layers are set in the CU, and the protocol layers below the PDCP layer, such as the RLC layer and the MAC layer, are set in the DU.

[0109] The RAN device can implement the functions of protocol layers such as RRC, PDCP, RLC, and MAC by one node; or these protocol layer functions can be implemented by multiple nodes; for example, in an evolved structure, the RAN device can include a CU and a DU, and multiple DUs can be centrally controlled by one CU. As Figure 4As shown, the CU and DU can be divided according to the protocol layers of the wireless network. For example, the functions of the protocol layers above the PDCP layer are set in the CU. For instance, the CU has the functions of the PDCP layer and the RRC protocol layer; the protocol layers below the PDCP layer, such as the RLC layer, the MAC layer, and the physical layer, can have their functions set in the DU.

[0110] This division of protocol layers is merely an example. It is also possible to divide at other protocol layers. For example, divide at the RLC layer, set the functions of the RLC layer and the protocol layers above it in the CU, and set the functions of the protocol layers below the RLC layer in the DU; or, divide within a certain protocol layer. For example, set some functions of the RLC layer and the protocol layers above the RLC layer in the CU, and set the remaining functions of the RLC layer and the protocol layers below the RLC layer in the DU. In addition, it can also be divided in other ways. For example, divide according to latency, set the functions whose processing time needs to meet the latency requirements in the DU, and set the functions that do not need to meet this latency requirement in the CU.

[0111] In addition, the radio frequency device can be remotely located and not placed in the DU, or can be integrated in the DU, or partially remotely located and partially integrated in the DU, without any restrictions here.

[0112] Please continue to refer to Figure 5 , Figure 5 which shows a schematic diagram of another network architecture provided by the embodiments of the present application. Relative to Figure 4 the architecture shown, the control plane (CP) and user plane (UP) of the CU can also be separated and implemented as different entities, namely the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity).

[0113] In the above network architecture, the signaling generated by the CU can be sent to the terminal device through the DU (for example, DU1 or DU2), or the signaling generated by the terminal device can be sent to the CU through the DU. The DU can directly encapsulate the signaling through the protocol layer without parsing it and pass it through to the terminal device or the CU. In the following embodiments, if this kind of signaling transmission between the DU and the terminal device is involved, at this time, the DU's sending or receiving of the signaling includes this scenario. For example, the signaling of the RRC or PDCP layer will ultimately be processed into PHY layer signaling and sent to the terminal device, or is transformed from the received PHY layer signaling. In this architecture, this RRC or PDCP layer signaling can also be considered to be sent by the DU, or sent by the DU and the radio frequency.

[0114] In the above embodiments, the CU is divided into a network device on the RAN side. In addition, the CU can also be divided into a network device on the CN side, without any restrictions here.

[0115] In the following embodiments of this application, the device, according to its implemented functions, may be located in a terminal device. When adopting the above CU-DU structure, the network device may be a CU node, or a DU node, or a RAN device including a CU node and a DU node.

[0116] Since the NR system introduces the concept of beams, the random access process in the mobility handover process involves how to select beams. Currently, beams may include synchronization signal blocks (SSBs) and / or channel state information reference signals (CSI-RSs), where CSI-RS can be used in the random access in a non-competitive scenario. The configuration of beams can be configured through RRC. SSBs are sent to the terminal device through broadcast messages, and CSI-RS can be configured to the terminal device through RRC dedicated signaling. Exemplarily, during the handover process, after the target base station receives the handover request message sent by the source base station, it returns a handover request response, and the handover request response includes the beam configuration sent to the terminal device. Among them, two thresholds (rsrp-ThresholdSSB, csirs-Threshold) are respectively configured for SSB and CSI-RS. This threshold is used for the terminal device to select beams. The network device can configure measurement information based on SSB or CSI-RS for the terminal device. The terminal device measures the reference signal receiving power (RSRP) of SSB or CSI-RS. For example, when the RSRP measured by the terminal device for SSB exceeds the RSRP threshold of SSB, it selects the preamble under the corresponding SSB for random access.

[0117] In addition, the NR system also introduces supplementary uplink (SUL), that is, one downlink supports two uplinks. Then a corresponding SUL threshold (sul-RSRP-Threshold) is also introduced. That is, when the terminal device performs initial random access, the terminal device decides whether to select the normal uplink (UL) or SUL by comparing the measured signal strength with the SUL threshold. When the terminal device is in a handover scenario, whether the terminal device uses UL or SUL or both UL and SUL simultaneously can be indicated through RRC dedicated signaling.

[0118] Under the LTE system, MRO optimization is mainly used to optimize mobility parameters, such as parameters like the bias of the A3 handover event. Exemplarily, the network device determines whether to optimize mobility parameters based on the radio link failure (RLF) report reported by the terminal device, as well as the RLFindication and HO report of interface interaction.

[0119] Under the NR system, MRO optimization has not been introduced temporarily. If inheriting the LTE solution, however, due to the introduction of beam-related beam selection, UL / SUL, and broadband parts in the NR system, and beam, SUL, or the broadband part can all cause radio link failure, and the prior art cannot distinguish and solve them. In the embodiments of the present application, a method for transmitting information is provided. When the terminal device has an RLF or BF, it can report a radio link failure report (RLF report) or a beam failure recovery report (BFR report) to the network device. Among them, the RLF report or BFR report carries one or more of the information of the beam, the information of the uplink carrier, or the information of the broadband part, which helps the network device perform MRO in a timely and accurate manner.

[0120] Figure 6 The schematic flowchart of the method 200 for transmitting information provided by the embodiments of the present application is shown, as Figure 6 shown. The execution subject of the method 200 can be a network device or a chip located in the network device (the following takes the execution subject as a network device as an example for illustration). The method 200 includes:

[0121] S210, the network device receives first information from the terminal device. The first information includes the information that a radio link failure occurs between the terminal device and the first cell, or the first information includes the information that a beam failure recovery occurs between the terminal device and the first cell; the first information further includes resource information, and the resource information includes at least one of beam information, uplink carrier information, or bandwidth part information.

[0122] Optionally, the first information includes the information that a radio link failure occurred between the terminal device and the first cell before.

[0123] Optionally, the first information is a radio link failure report (RLF report).

[0124] It should be understood that the resource information is the information of the resources used when the terminal device has a radio link failure.

[0125] It should also be understood that the radio link failure report includes at least one of the information of the radio link failure and the information of the resources used when the radio link failure occurs.

[0126] It should be understood that the technical solution of the embodiment of the present application can be applied to a handover scenario. For example Figure 2 and Figure 3 in the cases of premature handover, late handover, and handover to the wrong cell as shown, for example, as Figure 2 shown, the terminal device 131 can send an RLF report to the RAN 111, or send an RLF report to the RAN 112 and the RAN 112 sends an RLFindication to the RAN 111, so that the RAN 111 can identify that this is a scenario of premature handover or late handover; and again Figure 3 as shown, the terminal device 131 can send an RLF report to the RAN 113, and the RAN 113 sends an RLF indication to the RAN 111, so that the RAN 111 can identify that this is a scenario of handover to the wrong cell.

[0127] The technical solution of the embodiment of the present application can also be applied to a scenario of a single network device. For example, the first cell is a cell under the first network device, and the terminal device re - establishes an RRC connection with the first cell within a period of time after a radio link failure occurs in the first cell. The terminal device can send an RLF report to the first network device, and the RLF report includes information about the radio link failure and information about the resources.

[0128] Optionally, the information about the resources recorded by the terminal device includes the information about the resources used by the terminal device when RLF occurs, or it can also be the information about the resources used (or ever used) when RLF occurs, or it can also be the information about the resources of the last service when RLF occurs, or it can also be the information about the resources used by the terminal device before RLF occurs.

[0129] Optionally, the information about the resources includes information about the beam, and the information about the beam includes but is not limited to one or more of the following: the identifier of the beam, the random access information of the terminal device in the beam, the cell information to which the beam belongs (physical cell identifier (PCI), cell global identifier (CGI), frequency information of the cell, etc.), the measurement information of the terminal device in the beam (including the measurement of adjacent beams and the measurement of the serving beam). Optionally, the information about the beam further includes the measurement information of the cell where the beam is located, and the measurement information of the cells where the adjacent beams are located.

[0130] Optionally, the identifier of the beam can be the group number of the beam (such as SSB - index and CSI - RS - index, etc.).

[0131] Optionally, the information on radio link failure includes one or more of the following:

[0132] (1) The time period from the occurrence of handover to connection failure of the terminal device, and / or the time period from the occurrence of handover to the reporting of RLF report by the terminal device.

[0133] (2) The reason for the RLF of the terminal device. Exemplarily, it may include at least one of timer timeout, random access problem, beam recovery failure problem, RLC reaching the maximum retransmission count, etc.

[0134] (3) The indication of connection failure of the terminal device. Exemplarily, it may include handover failure, beam recovery failure or radio link failure.

[0135] (4) The cell radio network temporary identifier (C-RNTI) allocated to the terminal device in the last serving cell.

[0136] (5) The information on the cell to be re-established by the terminal device (e.g., CGI and PCI) and the information on the re-established beam (e.g., SSB-index, CSI-RS-index, etc.).

[0137] (6) The time period from the occurrence of beam failure to radio link failure of the terminal device, and / or the number of beam failures.

[0138] Optionally, the random access information includes one or more of the following: the number of preambles sent, the preamble information used during preamble attempts, contention detected information, the load information of the random access channel, the load information of the physical uplink shared channel, the maximum power arrival indication information, the failure duration information, the access delay information, the path loss estimation information, the backoff time information, the data available for transmission information, and the type of random access.

[0139] Among them, the number of preambles sent can be the information on the number of times the terminal device attempts to send preambles during the process of successfully randomly accessing the network from the initiation of preamble transmission;

[0140] The contention detected information can be the information on whether contention resolution is unsuccessful or whether preamble contention is detected;

[0141] The maximum power arrival indication information may be information on whether the transmitted preamble reaches the maximum power level;

[0142] The failure duration information may be information on the time when the terminal device conducts a random access attempt;

[0143] The access delay information may be information on the time during the process from the terminal device initiating preamble transmission to successful random access;

[0144] The path loss estimation information may be information on the path loss when the terminal device conducts a random access attempt;

[0145] The backoff time information may be information on the delay time of the network backoff control mechanism during the random access process.

[0146] The types of random access may include at least one of on demand system information, RRC connection establishment, and beam failure recovery (BFR). Among them, for the random access type of on demand system information, it may also include at least one of the types of random access process message 1 (Msg1) request and random access process message 3 (Msg3) request.

[0147] Optionally, when the reason for the terminal device to have RLF is a random access problem or a beam recovery failure problem, the resource information includes random access information, and the random access information includes information on the beam used when random access fails and / or information on the beam used when random access succeeds.

[0148] Optionally, the information of the resource includes information on the uplink carrier. Similar to the description of the beam information, the identifier of the beam can be replaced with the identifier of the uplink carrier, where the identifier of the uplink carrier can be any one or several of the uplink carrier frequency information, uplink carrier identifier, etc., and the uplink carrier can be SUL or UL.

[0149] Optionally, the information on the uplink carrier is the information on the uplink carrier used when the terminal device has RLF, or it can also be the information on the uplink carrier used before the terminal device has RLF.

[0150] Optionally, the information of the resource includes the information of the bandwidth part, and a description similar to the beam information, where the identifier of the beam is replaced by the identifier of the BWP. The information of the BWP may further include any one or more of the following: location and bandwidth, subcarrier spacing, information used for the uplink of the BWP, information used for the downlink of the BWP. Among them, the information used for the uplink or downlink of the BWP may include any one or more of the following: common configuration, dedicated configuration, etc.

[0151] Optionally, the information of the bandwidth part is the information of the uplink carrier used when the terminal device has an RLF, or may also be the information of the bandwidth part used before the terminal device has an RLF.

[0152] It should be understood that in the embodiments of the present application, the first information may be sent to the network device through an existing RLF report, or may also be sent to the network device through a re-establishment request message, or may also be sent through other existing messages or reports, or may also be sent through a new report or message. The present application does not make any limitation thereto.

[0153] It should be noted that when the first information is sent to the network device through a re-establishment request message, the re-establishment request message may include at least one or a combination of multiple types in the first information. The present application does not make any limitation thereto.

[0154] Optionally, the first information includes the information of beam failure occurring between the terminal device and the first cell.

[0155] Optionally, the first information is a Beam Failure Recovery report (BFR report), and the BFR report includes the information of beam failure and the information of the resource.

[0156] For example, as Figure 2 shown, the terminal device 131 may send a BFR report to RAN112, and after RAN112 determines the cause of the BF, MRO is performed.

[0157] For another example, the first cell is a cell under the first network device. When the terminal device has a BF in the first cell and the BFR is successful, the terminal device may send a BFR report to the first network device, and the BFR report includes the information of beam failure and the information of the resource.

[0158] Optionally, the information about the resources recorded by the terminal device includes the information about the resources used by the terminal device when BFR / BF occurs, or the information about the resources that have been used (or were once used) when BFR / BF occurs, or the information about the resources that were last served when BFR / BF occurs, or the information about the resources used by the terminal device before BFR / BF occurs.

[0159] Optionally, the descriptions of the information about the beam, the uplink carrier, and the wideband part included in the information about the resources are similar to the above descriptions. For the sake of brevity, they will not be elaborated here.

[0160] Optionally, the information about the beam failure includes but is not limited to one or more of the following:

[0161] (1) The time period from when the beam failure occurs to when the beam failure recovery is successful for the terminal device, and / or the time period from when the beam failure occurs to when the BFR report is sent for the terminal device.

[0162] (2) The reason for the beam failure of the terminal device. Exemplarily, it may include at least one of timer timeout, random access problem, RLC reaching the maximum retransmission count, etc.

[0163] (3) The cell radio network temporary identifier (C-RNTI) allocated to the terminal device in the last served cell.

[0164] (4) The information about the cell for re-establishment (such as CGI and PCI) and / or the information about the beam for reconstruction (such as SSB-index, CSI-RS-index, etc.) of the terminal device.

[0165] Optionally, the first information further includes at least one of the number of beam failures, the number of beam failure recoveries, or the duration of beam failure recovery.

[0166] Optionally, at least one of the number of beam failures, the number of beam failure recoveries, or the duration of beam failure recovery may also be directly included in the BFR report.

[0167] S220. The network device performs mobile robustness optimization according to the first information.

[0168] Specifically, in the embodiments of the present application, after receiving the first information, the network device may perform mobile robustness optimization. In the handover process, the first network device may be the target network device or the source network device. The following will be combined with Figures 7 to 19Describe in detail the specific optimization process of the network device in the handover scenario.

[0169] Figure 7 Fig. 4 shows a schematic flowchart of a method 300 for transmitting information according to an embodiment of the present application. As Figure 7 shown, the method 300 includes:

[0170] S310, the terminal device sends first information to a first network device, and the first network device receives the first information sent by the terminal device. The first information includes information about beam failure recovery occurring between the terminal device and the first cell.

[0171] Optionally, before the terminal device sends the first information to the first network device, the method 300 further includes:

[0172] A second network device sends a handover command to the terminal device, and the terminal device receives the handover command sent by the second network device. The handover command is used to instruct the terminal device to hand over from a second cell under the second network device to a first cell under the first network device;

[0173] The terminal device hands over from the second cell under the second network device to the first cell under the first network device;

[0174] The terminal device experiences beam failure in the first cell and beam failure recovery is successful.

[0175] Specifically, the first network device may be a target network device, the second network device may be a source network device, the first cell is a target cell under the target network device, and the second cell is a source cell under the first network device. After the terminal device hands over to the first cell under the target network device, BF occurs and BFR is successful. Then, the terminal device may report the first information to the first network device.

[0176] For example, as Figure 2 shown, the terminal device 131 receives a handover command sent by the source cell A. The terminal device 131 performs random access (RACH) to the target cell B and successfully accesses the cell B. However, within a very short period of time (e.g., less than 3 s) after successfully accessing the target cell B, multiple BFRs occur and are successfully recovered. Although the recovery is successful, the signal quality of the terminal device in the cell B may not be very good. At this time, the terminal device 131 triggers the reporting of the BFR report.

[0177] Optionally, before the terminal device sends the first information to the first network device, the method further includes:

[0178] The terminal device determines that the number of BFs is greater than or equal to a first value; and / or,

[0179] The terminal device determines that the number of beam failure recoveries (BFRs) is greater than or equal to a second value; and / or,

[0180] The terminal device determines that the timer expires.

[0181] The first value, the second value, and the timer may be configured by a network device for the terminal device, or may be specified by a protocol, or determined in other ways, and the present application does not make any limitations in this regard.

[0182] Specifically, the terminal device may trigger the reporting of the first information due to an event trigger. For example, the number of beam failures (BFs) or BFRs is greater than or equal to a certain value. It may also be triggered by a timer. Among them, the first value, the second value, and the timer in the event trigger may be configured by a network device (such as a target network device) for the terminal device.

[0183] Optionally, the first information is a BFR report.

[0184] It should be understood that the description of the first information is the same as that of the first information in the above method 200. For the sake of brevity, it will not be elaborated here.

[0185] It should also be understood that the BFR report may be reported through the radio resource control (RRC) connection between the terminal device and the first network device, or may also be reported through other existing messages, or may also be reported through a newly defined message. The embodiments of the present application do not make any limitations in this regard.

[0186] S320. The first network device determines the cause of the beam failure.

[0187] Optionally, the first network device determines the cause of the beam failure, including:

[0188] The first network device determines that the beam failure is caused by unreasonable configuration of the resource.

[0189] Among them, the method 300 further includes:

[0190] S331. The first network device adjusts the configuration of the resource.

[0191] Optionally, the resource includes one or more of a beam, an uplink carrier, or a bandwidth part. The first network device adjusts the configuration of the resource, including any one or any combination of the following:

[0192] The first network device adjusts the first threshold value corresponding to the synchronization signal block (SSB);

[0193] The first network device adjusts the second threshold value corresponding to the channel state information reference signal (CSI-RS);

[0194] The first network device adjusts the third threshold value corresponding to the supplementary uplink carrier; or,

[0195] The first network device adjusts the random access channel (RACH) resources, such as the time-frequency resources corresponding to each SSB or CSI-RS, or the preamble packet included in each SSB or CSI-RS, or reasonably adjusts parameters such as the initial transmit / receive power and step size of the preamble, etc.

[0196] Optionally, the method 300 further includes:

[0197] The first network device sends fourth information to the second network device, and the second network device receives the fourth information sent by the first network device, where the fourth information is used to indicate the configuration of the adjusted resource.

[0198] Optionally, the first network device determines the cause of beam failure, including:

[0199] The first network device determines that the beam failure is caused by unreasonable configuration of mobility parameters.

[0200] Optionally, the first network device directly determines that the beam failure is caused by scenarios such as too early handover or too late handover.

[0201] Wherein, the method 300 further includes:

[0202] S332, the first network device sends second information to the second network device, and the second network device receives the second information sent by the first network device, where the second information is used to instruct the second network device to adjust mobility parameters;

[0203] S333, the second network device adjusts mobility parameters.

[0204] Optionally, the second network device adjusts mobility parameters, including:

[0205] The second network device adjusts the parameters related to A3 event.

[0206] Optionally, the second network device determines whether it is caused by unreasonable configuration of mobility parameters according to the second information, that is, determines whether it is a scenario such as too early handover or too late handover, so as to adjust mobility parameters.

[0207] Optionally, the second information is an indication of too early handover, and the second network device adjusts mobility parameters after receiving the second information.

[0208] In an embodiment of the present application, if the first network device determines that there is a resource configuration problem, then the first network device adjusts the resource configuration, for example, adjusts the configuration of beam, SUL related thresholds, etc., for subsequent handover configuration; otherwise, if the first network device determines that there is no resource configuration problem, then it sends an indication to the second network device, and after receiving it, the second network device determines whether it is a scenario of premature handover or other newly defined scenario, so as to adjust the relevant mobility parameters.

[0209] It should be understood that the process of the network device performing mobile robustness optimization in S210 of method 200 may include S320 and S331, or may also include S320, S332 and S333.

[0210] Figure 8 Another schematic flowchart of the method 300 for transmitting information according to an embodiment of the present application is shown. Compared with Figure 7 the method shown, Figure 7 in the method shown, the reason for beam failure may be determined by the target network device (the first network device), Figure 8 in the method shown, the reason for beam failure may be determined by the source network device (the second network device). The method 700 includes:

[0211] S311, the terminal device sends first information to the first network device, and the first network device receives the first information sent by the terminal device. The first information includes information about beam failure recovery between the terminal device and the first cell.

[0212] It should be understood that S311 is the same as S310. For the sake of brevity, it will not be elaborated here.

[0213] S312, the first network device sends the first information to the second network device, and the second network device receives the first information sent by the first network device.

[0214] Specifically, after receiving the first information, the first network device forwards the first information to the second network device, and the second network device determines the reason for beam failure.

[0215] S321, the second network device determines the reason for beam failure.

[0216] Optionally, the second network device determines the reason for beam failure, including:

[0217] the second network device determines that the beam failure is caused by unreasonable configuration of the resource.

[0218] Wherein, the method 300 further includes:

[0219] S334. The second network device sends third information to the first network device, and the first device receives the third information sent by the second network device. The third information is used to instruct the first network device to adjust the configuration of the resource.

[0220] S335. The first network device adjusts the configuration of the resource.

[0221] Optionally, the resource includes one or more of a beam, an uplink carrier, or a bandwidth part. The first network device adjusts the configuration of the resource, including any one or any combination of the following:

[0222] The first network device adjusts the first threshold value corresponding to the SSB;

[0223] The first network device adjusts the second threshold value corresponding to the CSI-RS;

[0224] The first network device adjusts the third threshold value corresponding to the supplementary uplink carrier; or,

[0225] The first network device adjusts the RACH resource. For example, the time-frequency resource corresponding to each SSB or CSI-RS, or the preamble packet included in each SSB or CSI-RS, or reasonably adjusts parameters such as the initial transmission / reception power and step size of the preamble, etc.

[0226] Optionally, the third information is used to instruct the first network device to adjust the configuration of a specific resource, and the configuration of the specific resource is one or more of a beam, an uplink carrier, or a bandwidth part.

[0227] Optionally, the second network device determines the reason for the beam failure, including:

[0228] The second network device determines that the beam failure is caused by unreasonable configuration of mobility parameters.

[0229] Optionally, the second network device directly determines that the beam failure is caused by scenarios such as too early handover or too late handover.

[0230] Among them, the method 300 further includes:

[0231] S336. The second network device adjusts the mobility parameters.

[0232] It should be understood that when the second network device determines that the beam failure is caused by unreasonable configuration of mobility parameters, the second network device determines the handover problem (such as too early handover or too late handover) and adjusts the mobility parameters.

[0233] In the embodiments of the present application, if the second network device determines that it is a resource configuration problem, then the second network device instructs the first network device to adjust the resource configuration, such as adjusting the configuration of beam, SUL related thresholds, etc., for subsequent handover configuration; otherwise, if the second network device determines that it is not a resource configuration problem but a mobility parameter problem, then the second network device determines that it is an early handover scenario, or a newly defined scenario, and thus adjusts the relevant mobility parameters.

[0234] In the method for transmitting information according to the embodiments of the present application, when a beam failure occurs, the information carried in the information reported by the terminal device includes information about resources, which helps the network device perform mobile robustness optimization in a timely and accurate manner, thereby helping to avoid handover failures and improve the success rate of handovers.

[0235] Figure 9 FIG. shows a schematic flowchart of a method 400 for transmitting information according to the embodiments of the present application, as Figure 9 shown, the method 400 includes:

[0236] S410, the terminal device sends a first piece of information to the second network device, and the second network device receives the first piece of information sent by the terminal device, where the first piece of information includes information about a radio link failure that occurs between the terminal device and the first cell;

[0237] S411, the second network device sends the first piece of information to the first network device, and the first network device receives the first piece of information sent by the second network device.

[0238] Optionally, before the terminal device sends the first piece of information to the second network device, the method 300 further includes:

[0239] The second network device sends a handover command to the terminal device, and the terminal device receives the handover command sent by the second network device, where the handover command is used to instruct the terminal device to hand over from the second cell under the second network device to the first cell under the first network device;

[0240] The terminal device determines that a radio link failure occurs before handing over to the first cell under the first network device, or the terminal device determines that a radio link failure occurs after handing over to the first cell under the first network device;

[0241] The terminal device reconnects to the second cell under the second network device.

[0242] Specifically, the first network device may be the target network device, the second network device may be the source network device, the first cell is the target cell under the target network device, the second cell is the source cell under the source network device, the terminal device has a radio link failure during the process of switching to the first cell, and after the terminal device reconnects to the second cell, it may report the first information to the second network device. Or, the terminal device has a radio link failure some time after successfully switching to the first cell, and after the terminal device reconnects to the second cell, it may report the first information to the second network device.

[0243] For example, as Figure 2 shown, the terminal device 131 receives a handover command sent by the source cell A, the terminal device 131 performs random access (RACH) to the target cell B, and a RLF occurs during the random access process. The terminal device 131 reconnects to the source cell A. At this time, the terminal device 131 triggers to report an RLF report to the RAN 111. Or, optionally, the terminal device 131 does not send an RLF report to the RAN 111, and the terminal device 131 directly sends a reconstruction request to the RAN 111.

[0244] Another example, as Figure 2 shown, the terminal device 131 receives a handover command sent by the source cell A, the terminal device 131 performs random access (RACH) to the target cell B and successfully accesses the cell B, but an RLF occurs within a very short period of time (for example, less than 3 s) after successfully accessing the target cell B. At this time, the terminal device 131 triggers to report an RLF report to the RAN 111, and the RAN 111 forwards the RLF report to the RAN 112.

[0245] It should be understood that the RLF in the above two scenarios may be caused by the failure of BFR recovery, or may also be caused by unreasonable UL and SUL configurations, or may also be caused by unreasonable RACH resource configurations, or may also be caused by other existing reasons. The present application does not make any limitation thereto.

[0246] For example, the terminal device has a BFR in the target cell B but fails to recover successfully, resulting in an RLF and reconnection to the source cell A; or, the UL / SUL configuration or RACH resource configuration of the target cell B is unreasonable, resulting in the terminal device being unable to successfully access the target cell B, resulting in an RLF and reconnection to the source cell A.

[0247] Optionally, the first information is an RLF report.

[0248] It should be understood that the description of the first information is the same as the description of the first information in the above method 200. For the sake of brevity, it will not be repeated here.

[0249] It should also be understood that the RLF report can be reported through the RRC connection between the terminal device and the first network device, or it can be reported through other existing messages, or it can also be reported through a newly defined message. The embodiments of the present application do not make any limitations on this.

[0250] S420, the first network device determines the cause of the radio link failure.

[0251] Optionally, the first network device determines the cause of the radio link failure, including:

[0252] The first network device determines that the radio link failure is caused by unreasonable configuration of the resource.

[0253] Wherein, the method 300 further includes:

[0254] S431, the first network device adjusts the configuration of the resource.

[0255] Optionally, the resource includes one or more of a beam, an uplink carrier, or a bandwidth part. The first network device adjusts the configuration of the resource, including any one or any combination of the following:

[0256] The first network device adjusts the first threshold value corresponding to the SSB;

[0257] The first network device adjusts the second threshold value corresponding to the CSI-RS;

[0258] The first network device adjusts the third threshold value corresponding to the supplementary uplink carrier; or,

[0259] The first network device adjusts the RACH resource, for example, the time-frequency resource corresponding to each SSB or CSI-RS, or the preamble packet included in each SSB or CSI-RS, or reasonably adjusts parameters such as the initial transmission / reception power and step size of the preamble, etc.

[0260] Optionally, the first network device determines the cause of the radio link failure, including:

[0261] The first network device determines that the beam failure is caused by unreasonable configuration of the mobility parameter.

[0262] Wherein, the method 400 further includes:

[0263] S432, the first network device sends second information to the second network device, and the second network device receives the second information sent by the first network device. The second information is used to instruct the second network device to adjust the mobility parameter;

[0264] S433, the second network device adjusts the mobility parameter.

[0265] It should be understood that the above S420 to S433 are similar to Figure 6 the processes of S320 to S333 in method 300. For the sake of brevity, they will not be elaborated here.

[0266] Figure 10 Another schematic flowchart of the method 400 for transmitting information according to an embodiment of the present application is shown. Compared with Figure 9 the method shown, Figure 9 in the method shown, the reason for the radio link failure can be determined by the target network device (the first network device), Figure 10 in the method shown, the reason for the radio link failure can be determined by the source network device (the second network device). The method 400 includes:

[0267] S412, the terminal device sends the first information to the second network device, and the second network device receives the first information sent by the terminal device. The first information includes the information that a radio link failure has occurred between the terminal device and the first cell.

[0268] It should be understood that at this time, the second network device may not forward the first information to the first network device.

[0269] S421, the second network device determines the reason for the radio link failure.

[0270] Optionally, the second network device determines the reason for the radio link failure, including:

[0271] The second network device determines that the radio link failure is caused by unreasonable configuration of the resource.

[0272] Wherein, the method 400 further includes:

[0273] S434, the second network device sends the third information to the first network device, and the first network device receives the third information sent by the second network device. The third information is used to instruct the first network device to adjust the configuration of the resource;

[0274] S435, the first network device adjusts the configuration of the resource.

[0275] Optionally, the third information is used to instruct the first network device to adjust the configuration of a specific resource, and the configuration of the specific resource is one or more of beam, uplink carrier, or bandwidth part.

[0276] It should be understood that the process of the first network device adjusting the configuration of the resource in method 400 is the same as the process of the first network device adjusting the configuration of the resource in the above method 300. For the sake of brevity, it will not be elaborated here.

[0277] Optionally, the second network device determines the cause of the radio link failure, including:

[0278] The second network device determines that the beam failure is caused by unreasonable configuration of mobility parameters.

[0279] Wherein, the method 400 further includes:

[0280] S436, the second network device adjusts the mobility parameters.

[0281] As described above, in combination with Figures 6 to 10 it is described in detail the mechanism of the network device performing MRO when the terminal device has BF or RLF in the scenario of premature handover. Next, in combination with Figure 11 and Figure 12 it is described in detail the mechanism of the network device performing MRO when the terminal device has BF or RLF in the scenario of late handover.

[0282] Figure 11 FIG. shows a schematic flowchart of a method 500 for transmitting information according to an embodiment of the present application. As Figure 11 shown, the method 500 includes:

[0283] S510, the terminal device sends first information to a first network device, and the first network device receives the first information sent by the terminal device. The first information includes information about a radio link failure occurring between the terminal device and the first cell.

[0284] Specifically, the first network device may be a target network device, the second network device may be a source network device, the first cell is a cell under the target network device, the second cell is a cell under the source network device. The terminal device has a radio link failure in the second cell before receiving a handover command, and the terminal device re - establishes a connection to the first cell. The terminal device may report the first information to the first network device.

[0285] For example, as Figure 2 shown, the terminal device 131 has an RLF in cell A before receiving the handover command sent by source cell A. The terminal device 131 reselects to target cell B under RAN112. At this time, the terminal device 131 triggers the reporting of RLFreport.

[0286] Optionally, the first information is an RLF report.

[0287] It should be understood that the description of the first information is the same as the description of the first information in the above - mentioned method 200. For the sake of brevity, it will not be elaborated here.

[0288] S520, the first network device determines the cause of the radio link failure.

[0289] It should be understood that S520 is similar to Figure 8 S420 - S433 in [reference], and for the sake of brevity, it will not be elaborated here.

[0290] Optionally, the second network device may also determine the cause of the radio link failure.

[0291] The method 500 further includes:

[0292] S521, the first network device forwards the first information to the second network device;

[0293] S522, the second network device determines the cause of the radio link failure.

[0294] It should be understood that S521 - S522 is similar to Figure 9 S421 - S436 in [reference], and for the sake of brevity, it will not be elaborated here.

[0295] Figure 12 FIG. shows a schematic flowchart of a method 600 for transmitting information according to an embodiment of the present application. As Figure 12 shown, the method 600 includes:

[0296] S610, the terminal device sends first information to the second network device, and the second network device receives the first information sent by the terminal device. The first information includes information about beam failure occurring between the terminal device and the second cell.

[0297] Specifically, the first network device may be the target network device, the second network device may be the source network device, the second cell is a cell under the source network device, and beam failure occurs in the second cell and beam failure recovery is successful for the terminal device. For example, the terminal device frequently experiences beam failure and successful beam failure recovery in the second cell without receiving a handover command. The terminal device may report the first information to the second network device.

[0298] For example, as Figure 2 shown, the terminal device 131 has not received the handover command (indicating that the terminal device 131 switches from cell A to cell B) sent by the RAN111, but BF occurs in cell A and BFR is successful. At this time, the terminal device 131 may report a BFR report to the RAN111.

[0299] It should be understood that the BFR report here is the same as the content in the above embodiment, and for the sake of brevity, it will not be elaborated here.

[0300] S620, the second network device determines the cause of the beam failure.

[0301] Optionally, the second network device determines that the beam failure is caused by unreasonable resource configuration;

[0302] Wherein, the method 600 further includes:

[0303] S631, the second network device adjusts the configuration of the resource.

[0304] It should be understood that the process of the second network device adjusting the resource configuration is similar to the process in the above embodiment, and for the sake of brevity, it will not be described herein again.

[0305] Optionally, the second network device determines the cause of the beam failure.

[0306] Optionally, the second network device determines that the beam failure is caused by unreasonable mobility parameter configuration;

[0307] Wherein, the method 600 further includes:

[0308] S632, the second network device adjusts the mobility parameter.

[0309] Specifically, the second network device may determine whether it is a resource configuration problem. If it is determined that it is a resource configuration problem, the second network device adjusts the resource configuration, such as adjusting the configuration of beam, SUL related thresholds, etc.; Optionally, the second network device may also, according to the measurement quality of the neighboring cell in the report, if the signal strength of the neighboring cell is good (such as the signal strength of the neighboring cell is better than that of the serving cell, but the handover event is not satisfied), determine that it is a scenario of late handover of a certain type, or other newly defined scenarios, so as to adjust the relevant downlink mobility parameters.

[0310] In the method for transmitting information according to the embodiment of the present application, when a beam failure occurs, the information carried in the information reported by the terminal device includes resource information, which helps the network device to perform mobile robustness optimization in a timely and accurate manner, thereby helping to avoid handover failures and improve the success rate of handovers.

[0311] Above, in combination with Figure 11 and Figure 12 It is described in detail the mechanism of the network device performing MRO when the terminal device has a BF or RLF in the scenario of late handover. Next, in combination with Figure 13 and Figure 14 , it is described in detail the mechanism of the network device performing MRO when the terminal device has a BF or RLF in the scenario of handover to the wrong cell.

[0312] Figure 13 FIG. shows a schematic flowchart of the method 700 for transmitting information according to the embodiment of the present application. As Figure 13 shown, the method 700 includes:

[0313] S710, The terminal device sends a first piece of information to a third network device, and the third network device receives the first piece of information sent by the terminal device. The first piece of information includes information that the terminal device has a radio link failure with a first cell.

[0314] S711, The third network device sends the first piece of information to a second network device, and the second network device receives the first piece of information sent by the third network device.

[0315] It should be understood that the second network device may be Figure 3 RAN111 in Figure 3 and the third network device may be

[0316] For example, as Figure 3 shown, the terminal device 131 receives a handover command sent by RAN111, indicating that the terminal device 131 is to hand over from cell A to cell B. Before the handover is completed, an RLF occurs. The terminal device performs cell reselection and reselects to cell C under RAN113. When the reconstruction is successful, the terminal device 131 reports an RLF report to RAN113. RAN113 identifies that the RLF occurred to the terminal device 131 in cell A. At this time, it sends an RLF indication to RAN111, so that RAN111 records that there is one handover to a wrong cell.

[0317] S720, The second network device determines the cause of the radio link failure.

[0318] Optionally, the second network device determines the cause of the radio link failure, including:

[0319] The first network device determines that the radio link failure is caused by unreasonable resource configuration;

[0320] Wherein, the method 700 further includes:

[0321] S731, The second network device sends a third piece of information to the first network device, and the first network device receives the third piece of information sent by the second network device. The third piece of information is used to instruct the first network device to adjust the resource configuration;

[0322] S732, The first network device adjusts the resource configuration.

[0323] It should be understood that the method for the first network device to adjust the resource configuration may be the same as the method in the above method 300. For the sake of brevity, it will not be elaborated here.

[0324] Optionally, the second network device determines the cause of the radio link failure, including:

[0325] The second network device determines that the radio link failure is caused by unreasonable configuration of mobility parameters;

[0326] Wherein, the method 700 further includes:

[0327] S733, the second network device adjusts the mobility parameters.

[0328] In the method for transmitting information according to the embodiments of the present application, when the terminal device switches to an incorrect cell after a beam failure, the information carried in the information reported by the terminal device helps the network device to perform mobile robustness optimization in a timely and accurate manner, thereby helping to avoid handover failures and improve the success rate of handovers.

[0329] Figure 14 shows a schematic flowchart of the method 800 for transmitting information according to the embodiments of the present application, as Figure 14 shown, the method 800 includes:

[0330] S810, the terminal device sends first information to a third network device, and the third network device receives the first information sent by the terminal device, where the first information includes information that the terminal device has a beam failure with a first cell;

[0331] S811, the third network device sends the first information to a first network device, and the first network device receives the first information sent by the third network device.

[0332] It should be understood that the first network device may be Figure 3 RAN112 in Figure 3 and the third network device may be

[0333] RAN113 in Figure 3 For example, as

[0334] shown, the terminal device 131 receives a handover command sent by RAN111, instructing the terminal device 131 to switch from cell A to cell B. The terminal device 131 successfully switches to cell B, but has an RLF within a period of time after the successful handover. The terminal device performs cell reselection and reselects to cell C under RAN113. When the reconstruction is successful, the terminal device 131 reports an RLF report to RAN113. RAN113 identifies that the RLF of the terminal device 131 occurs in cell B. At this time, it sends an RLFindication to RAN112, so that RAN112 records that a handover to an incorrect cell has occurred once.

[0335] Optionally, the first network device determines the cause of the radio link failure, including:

[0336] The first network device determines that the radio link failure is caused by unreasonable resource configuration;

[0337] Wherein, the method 800 further includes:

[0338] S831, the first network device adjusts the configuration of the resource.

[0339] It should be understood that the method for the first network device to adjust the configuration of the resource may be the same as the method in the above method 300. For the sake of brevity, it will not be elaborated here.

[0340] Optionally, the first network device determines the reason for the radio link failure, including:

[0341] The first network device determines that the radio link failure is caused by unreasonable mobility parameter configuration;

[0342] Wherein, the method 800 further includes:

[0343] S832, the first network device sends second information to the second network device, the second network device receives the second information sent by the first network device, and the second information is used to instruct the second network device to adjust the mobility parameter;

[0344] S833, the second network device adjusts the mobility parameter.

[0345] In the method for transmitting information according to the embodiments of the present application, when the terminal device switches to an incorrect cell after a beam failure, the information carried in the information reported by the terminal device includes resource information, which helps the network device to perform mobile robustness optimization in a timely and accurate manner, thereby helping to avoid handover failures and improve the success rate of handovers.

[0346] Above, in combination with Figures 6 to 14 It has been described in detail the mechanism of the network device performing MRO when the terminal device has BF or RLF in the scenarios of premature handover, late handover, and handover to an incorrect cell. The methods 900 to 1100 for transmitting information according to the embodiments of the present application will be described below with reference to the accompanying drawings. The methods 900 to 1100 describe the mechanism of the network device performing MRO when the network device is divided into CU and DU.

[0347] Figure 15 The schematic flowchart of the method 900 for transmitting information according to the embodiments of the present application is shown. As Figure 15 shown, the method 900 includes:

[0348] S910, the terminal device sends first information to the fourth network device through the fifth network device, the fourth network device receives the first information from the terminal device, and the first information includes the information that the terminal device has a radio link failure with the first cell.

[0349] Optionally, before the terminal device sends the first information to the fourth network device, the method further includes:

[0350] S901. The fourth network device triggers a handover, where the handover is from a fifth network device to a sixth network device;

[0351] S902. The fourth network device establishes context information of the terminal device with the sixth network device;

[0352] S903. The fourth network device sends a handover command to the terminal device through the fifth network device.

[0353] Optionally, the handover command is RRC reconfiguration information.

[0354] S904. The terminal device fails to initiate a random access procedure to the sixth network device;

[0355] S905. The terminal device sends a reestablishment request message to the fifth network device and reestablishes a connection to the fifth network device.

[0356] Optionally, the first information is carried in the reestablishment request message.

[0357] It should be understood that S901 - S904 is similar to existing practices and will not be elaborated here for the sake of brevity.

[0358] It should also be understood that method 900 can also be applicable when the terminal device can successfully initiate a random access procedure to the sixth network device, but an RLF occurs at the sixth network device, and the terminal device reselects to the fifth network device (the PCI of the first cell carried in the reestablishment message is the sixth network device).

[0359] It should also be understood that in S901, the fourth network device determines to trigger the handover based on an A3 measurement event.

[0360] Optionally, the first cell is a cell under the sixth network device.

[0361] Optionally, the fourth network device has at least one of the functions of a radio resource control protocol layer, a service data adaptation layer, and a packet data convergence protocol layer; and / or,

[0362] The fifth network device has at least one of the functions of a radio link control protocol layer, a media access control layer, and a physical layer; and / or,

[0363] The sixth network device has at least one of the functions of a radio link control protocol layer, a media access control layer, and a physical layer.

[0364] Optionally, the first information is an RLF report.

[0365] It should be understood that the fourth network device may be Figure 4 the CU in Figure 5 or the CU-CP or CU-UP in Figure 4 the DU1 in Figure 5 or the DU1 in Figure 4 the sixth network device may be the DU2 in Figure 5 or the DU2 in

[0366] For example, as shown in Figure 4 or Figure 5 a CU may communicate with multiple DUs. The CU may trigger a change in the DU. The CU may previously communicate with the terminal device through DU1. The CU may change the DU so that the CU communicates with the terminal device through DU2. RLF occurs during the random access process of the terminal device with the target DU2. The terminal device reselects to the source DU1 and accesses the CU. The terminal device may carry the PCI of the failed cell, which is the cell of DU2, in the message reported to the CU.

[0367] Optionally, the RLF report may be sent to the CU when the terminal device re-establishes to the CU with DU1, or may be directly sent to the CU. The content of the RLF report is the same as that described in the above embodiments. For the sake of brevity, it will not be elaborated here.

[0368] S920, the fourth network device sends the first information to the sixth network device, and the sixth network device receives the first information sent by the fourth network device.

[0369] Optionally, the fourth network device carries the first information in a new message (e.g., through F1AP Radio Link Failure Indication (RLF indication) information) or an existing message and sends it to the sixth network device.

[0370] Optionally, the existing message may be an F1AP message, including but not limited to the following messages:

[0371] UE context setup request / response message, UE context modification request / response / required message, UE context release request / response / required message, or F1 setup request / response message.

[0372] S930, the sixth network device determines the cause of the radio link failure.

[0373] Optionally, the sixth network device determines the cause of the radio link failure, including:

[0374] The sixth network device determines that the radio link failure is caused by unreasonable resource configuration;

[0375] Wherein, the method 900 further includes:

[0376] S931, the sixth network device adjusts the configuration of the resource.

[0377] For example, DU2 confirms problems such as RACH resource configuration, beam configuration, SUL / UL configuration, etc. according to the content of the RLF report. If it is a resource configuration problem, DU2 directly modifies the configuration.

[0378] It should be understood that the method for the sixth network device to adjust the configuration of the resource can be the same as the method in the above method 300. For the sake of brevity, it will not be described in detail here.

[0379] Optionally, the sixth network device determines the cause of the radio link failure, including:

[0380] The sixth network device determines that the radio link failure is caused by unreasonable mobility parameter configuration;

[0381] Wherein, the method 900 further includes:

[0382] S932, the sixth network device sends second information to the fourth network device, and the fourth network device receives the second information sent by the sixth network device. The second information is used to instruct the fourth network device to adjust mobility parameters;

[0383] Optionally, the second information can also be used to indicate that the sixth network device has completed the resource configuration modification, or to indicate mobility problems, such as too early or too late handover, etc.

[0384] S933, the fourth network device adjusts the mobility parameter.

[0385] For example, DU2 may send a DU change report to CU. The report includes whether it is a configuration problem, or configuration modification completion information, or a problem of premature handover, etc. That is, if it is not a resource configuration problem of DU2, DU2 indicates in the DU change report that the handover is premature, so that CU optimizes the downlink mobility parameter. Or, if it is a resource configuration problem of DU2, DU2 indicates in the DU change report that the resource configuration of DU2 has been modified and completed. Optionally, the DU change report is sent through a newly defined F1AP message or an existing F1AP message.

[0386] In one embodiment, Figure 16 FIG. 900 shows another schematic flowchart of the method for transmitting information according to an embodiment of the present application, as Figure 16 shown, the method 900 includes:

[0387] S911, the terminal device sends first information to the fourth network device through the fifth network device, and the fourth network device receives the first information sent by the terminal device. The first information includes information that the terminal device has a radio link failure with the first cell.

[0388] It should be understood that S911 is the same as S910. For the sake of brevity, it will not be described herein again.

[0389] S934, the fourth network device determines the cause of the radio link failure.

[0390] Optionally, the fourth network device determines the cause of the radio link failure, including:

[0391] The fourth network device determines that the radio link failure is caused by unreasonable resource configuration;

[0392] Wherein, the method 900 further includes:

[0393] S935, the fourth network device sends third information to the sixth network device, and the sixth network device receives the third information sent by the fourth network device. The third information is used to instruct the sixth network device to adjust the configuration of the resource;

[0394] S936, the sixth network device adjusts the configuration of the resource.

[0395] Optionally, the third information is used to instruct the sixth network device to adjust the configuration of a specific resource, and the configuration of the specific resource is one or more of a beam, an uplink carrier, or a bandwidth part.

[0396] For example, DU2 modifies the configuration of the corresponding resource according to the indication of the third piece of information.

[0397] It should be understood that the configuration of this resource is the same as the configuration of the resource in the above method 300, and for the sake of brevity, it will not be elaborated here.

[0398] It should also be understood that the method by which the sixth network device adjusts the configuration of this resource may be the same as the method in the above method 300, and for the sake of brevity, it will not be elaborated here.

[0399] For example, the CU determines the problem according to the RLF report, such as determining that it is a problem of premature handover of DU2, or a configuration problem of DU2. The configuration problem may include at least one of RACH resource configuration, beam configuration, bandwidth part BWP configuration, or SUL / UL configuration, etc. If it is a resource configuration problem, the CU sends a problem indication to DU2. The problem indication may be a RACH resource configuration problem indication, a beam problem indication, a BWP configuration, a SUL / UL configuration problem indication, etc., so that DU2 modifies the corresponding resource configuration.

[0400] DU2 may send a DU change report to the CU, and the report includes whether it is a configuration problem, configuration modification completion information, etc.

[0401] Optionally, the fourth network device determines the cause of the radio link failure, including:

[0402] The fourth network device determines that the radio link failure is caused by unreasonable configuration of mobility parameters;

[0403] Among them, the method 900 further includes:

[0404] S937, the fourth network device adjusts the downlink mobility parameters.

[0405] For example, if the CU determines that the RLF is caused by premature handover of DU2, the CU directly optimizes the downlink mobility parameters. Optionally, the optimized downlink mobility parameters include the related parameters of A3 event.

[0406] Above, in combination with Figure 15 and Figure 16 the mechanism of MRO by the network device when the DU has a premature handover and the terminal device has an RLF is described in detail. Next, in combination with Figure 17 and Figure 18 the mechanism of MRO by the network device when the DU has a premature handover and the terminal device has a BF is described.

[0407] Figure 17 Fig. shows a schematic flowchart of a method 1000 for transmitting information provided by an embodiment of the present application. As Figure 17 shown, the method 1000 includes:

[0408] S1010, The terminal device sends the first information to the fourth network device, and the fourth network device receives the first information sent by the sixth network device. The first information includes information about the beam failure of the terminal device with the first cell.

[0409] Optionally, the terminal device sending the first information to the fourth network device includes:

[0410] The terminal device directly sends the first information to the fourth network device; or,

[0411] The terminal device sends the first information to the fourth network device through the sixth network device.

[0412] Optionally, the first information includes a BFR report.

[0413] It should be understood that the description of the BFR report is the same as that in the above embodiments. For the sake of brevity, it will not be elaborated here.

[0414] Optionally, before the terminal device sends the first information to the fourth network device, the method further includes:

[0415] S1001, The fourth network device triggers a handover, and the handover is from the fifth network device to the sixth network device;

[0416] S1002, The fourth network device establishes context information of the terminal device with the sixth network device;

[0417] S1003, The fourth network device sends a handover command to the terminal device through the fifth network device.

[0418] Optionally, the handover command is RRC reconfiguration information.

[0419] S1004, The terminal device successfully initiates a random access procedure to the sixth network device, but the terminal device experiences multiple BFRs in the first cell and no RLF occurs.

[0420] It should be understood that S1001 - S1004 is similar to the existing practice. For the sake of brevity, it will not be elaborated here.

[0421] Optionally, before the terminal device sends the first information to the fourth network device, the method further includes:

[0422] The terminal device determines that the number of BFs is greater than or equal to a first value; and / or,

[0423] The terminal device determines that the number of BFRs is greater than or equal to a first value; and / or,

[0424] The terminal device determines that the timer has expired.

[0425] Specifically, the triggering of the reporting of the first information by the terminal device can be event-triggered. For example, the number of times of BF or BFR is greater than or equal to a certain value, or it can be timer-triggered. Among them, the first value, the second value, and the timer in the event-triggering can be configured by a network device (such as a CU) to the terminal device.

[0426] Optionally, the first cell is a cell under the sixth network device.

[0427] Optionally, the fourth network device has at least one of the functions of the radio resource control protocol layer, the service data adaptation layer, and the packet data convergence protocol layer; and / or,

[0428] The fifth network device has at least one of the functions of the radio link control protocol layer, the media access control layer, and the physical layer; and / or,

[0429] The sixth network device has at least one of the functions of the radio link control protocol layer, the media access control layer, and the physical layer.

[0430] It should be understood that the fourth network device can be the Figure 4 CU in, or can also be the Figure 5 CU-CP or CU-UP in. The fifth network device can be the Figure 4 DU1 in, or Figure 5 DU1 in. The sixth network device can be the Figure 4 DU2 in, or Figure 5 DU2 in.

[0431] For example, as shown in Figure 4 or Figure 5 , the CU triggers a handover to the DU. Subsequently, the CU establishes the context of the terminal device with the target DU2. The CU sends a handover command (such as RRC reconfiguration information) to the terminal device through the source DU1, enabling the terminal device to randomly access the target DU2. The terminal device successfully randomly accesses the DU2, but within a very short period of time (timer) after success, BF occurs frequently but BFR is successful and no RLF occurs.

[0432] The terminal device records and sends a BFR report to the CU. Exemplarily, the BFR report of the terminal device is directly reported to the CU (for example, through an RRC message), or first reported to the DU2 (for example, through a layer 1 or layer 2 message), and then sent to the CU through the DU2.

[0433] S1020, the fourth network device sends the first information to the sixth network device, and the sixth network device receives the first information sent by the fourth network device.

[0434] Optionally, the fourth network device carries the first information in a new message (e.g., in a newly defined F1AP Beam Failure Report (BFR) indication message) or an existing F1AP message and sends it to the sixth network device.

[0435] Optionally, the existing F1AP messages include but are not limited to the following messages:

[0436] UE context setup request / response message, UE context modification request / response / required message, UE context release request / response / required message, or F1 setup request / response message.

[0437] S1030, the sixth network device determines the cause of the beam failure.

[0438] Optionally, the sixth network device determines the cause of the beam failure, including:

[0439] The sixth network device determines that the beam failure is caused by unreasonable resource configuration;

[0440] Wherein, the method 1000 further includes:

[0441] S1031, the sixth network device adjusts the configuration of the resource.

[0442] For example, DU2 confirms the problem according to the content of the BFR report, such as RACH resource configuration, beam configuration, SUL / UL configuration, etc. If it is a resource configuration problem, DU2 directly modifies the configuration.

[0443] It should be understood that the method for the sixth network device to adjust the configuration of the resource may be the same as the method in the above method 300. For the sake of brevity, it will not be elaborated here.

[0444] Optionally, the first network device determines the cause of the beam failure, including:

[0445] The sixth network device determines that the beam failure is caused by unreasonable mobility parameter configuration;

[0446] Among them, the method 1000 further includes:

[0447] S1032. The sixth network device sends second information to the fourth network device, and the fourth network device receives the second information sent by the sixth network device. The second information is used to instruct the fourth network device to adjust mobility parameters;

[0448] S1033. The fourth network device adjusts the mobility parameters.

[0449] For example, DU2 can send a DU change report to CU. The report includes whether it is a configuration problem, modified configuration completion information, or a problem of too early handover, etc. That is, if it is not a resource configuration problem of DU2, DU2 indicates in the DU change report that the handover is too early, so that CU optimizes the downlink mobility parameters. Or, if it is a resource configuration problem of DU2, DU2 indicates in the DU change report that the resource configuration of DU2 has been modified and completed. Optionally, the DU change report can be sent through a newly defined F1AP message or an existing F1AP message.

[0450] In one embodiment, Figure 18 shows another schematic flowchart of the method 1000 for transmitting information provided by the embodiment of the present application, as Figure 18 shown, the method 1000 includes:

[0451] S1011. The terminal device sends first information to the fourth network device, and the first information includes information about beam failure of the terminal device with the first cell.

[0452] Optionally, the terminal device sending the first information to the fourth network device includes:

[0453] The terminal device directly sends the first information to the fourth network device; or,

[0454] The terminal device sends the first information to the fourth network device through the sixth network device.

[0455] Optionally, the first information is a BFR report.

[0456] It should be understood that the content of the BFR report is the same as that of the BFR report in the above embodiment. For the sake of brevity, it will not be elaborated here.

[0457] It should be understood that the process of S1011 is the same as that of S1010. For the sake of brevity, it will not be elaborated here.

[0458] S1034. The fourth network device determines the cause of the beam failure.

[0459] Optionally, the fourth network device determines the cause of the beam failure, including:

[0460] The fourth network device determines that the beam failure is caused by unreasonable resource configuration;

[0461] Wherein, the method 1000 further includes:

[0462] S1035, the fourth network device sends third information to the sixth network device, and the sixth network device receives the third information sent by the fourth network device, where the third information is used to instruct the sixth network device to adjust the configuration of the resource;

[0463] S1036, the sixth network device adjusts the configuration of the resource.

[0464] For example, the CU determines the problem according to the BFR report, such as determining that it is a problem of premature handover of DU2 or a configuration problem of DU2. The configuration problem may include at least one of RACH resource configuration, beam configuration, or SUL / UL configuration, etc. If it is a resource configuration problem, the CU sends a problem indication to DU2, and the problem indication may be a RACH resource configuration problem indication, a beam problem indication, a SUL / UL configuration problem indication, etc., so that DU2 modifies the corresponding configuration.

[0465] DU2 may send a DU change report to the CU, and the report includes whether it is a configuration problem, information on completion of configuration modification, etc.

[0466] Optionally, the method further includes:

[0467] The sixth network device sends fourth information to the fourth network device, and the fourth network device receives the fourth information sent by the sixth network device, where the fourth information is used to indicate the configuration of the modified resource.

[0468] Optionally, the fourth network device determines the cause of the beam failure, including:

[0469] The fourth network device determines that the beam failure is caused by unreasonable configuration of mobility parameters;

[0470] Wherein, the method 1000 further includes:

[0471] S1037, the fourth network device adjusts the downlink mobility parameters.

[0472] For example, if the CU determines that the RLF is caused by premature handover of DU, the CU directly optimizes the downlink mobility parameters. Optionally, the optimized downlink mobility parameters include parameters related to A3 events.

[0473] In the method for transmitting information according to the embodiments of the present application, when BF or RLF occurs during the DU handover process in the CU-DU architecture, the information of the resources is carried in the information reported by the terminal device, which helps the network device to perform mobile robustness optimization in a timely and accurate manner, thereby helping to avoid handover failures and improve the success rate of handovers.

[0474] In combination with Figures 15 to 18 , the mechanism for the network device to perform MRO when the DU handover is too early and the terminal device experiences RLF or BF is described in detail. Next, in combination with Figure 19 Figure 20 the mechanism for the network device to perform MRO when the DU handover is too late and the terminal device experiences RLF or BF is described.

[0475] Figure 19 FIG. shows a schematic flowchart of a method 1100 for transmitting information according to an embodiment of the present application. As Figure 19 shown, the method 1100 includes:

[0476] S1110, the terminal device experiences RLF at a fifth network device;

[0477] S1120, the terminal device sends a reestablishment request message to a fourth network device through a sixth network device, and the reestablishment request message includes the identification information of the fifth network device;

[0478] S1130, the terminal device reselects to the sixth network device and successfully reestablishes;

[0479] S1140, after receiving the reestablishment request message, the fourth network device can determine that the cell to be reestablished is a cell under the sixth network device, which is different from the identification information of the current serving cell, and the sixth network device can directly determine that the handover is too late.

[0480] For example, as Figure 4 or Figure 5 shown, the terminal device experiences RLF under DU1, then reselects to the target DU2 and successfully reestablishes. The RRC reestablishment request message of the terminal device includes the cell identification of the failed DU1. At this time, after receiving the reestablishment request, the CU can know that the cell to be reestablished is in DU2, which is different from the identification of the current serving cell. Therefore, the CU can directly determine that the DU handover is too late once.

[0481] It should be understood that the scenario of too late handover may also include: the terminal device experiences BF under DU1 but the BFR is successful, the terminal device sends a BFR report to the CU through DU1, and the BFR report includes the measurement results of neighboring cells. After receiving it, the CU judges the problem (resource configuration problem or too late DU handover problem). If it is a configuration problem, the CU sends a problem indication to DU1 to make DU1 reconfigure. Otherwise, the CU counts one case of too late handover. This process is similar to the process in the above method 1000. For the sake of brevity, it will not be elaborated here.

[0482] In the method for transmitting information according to the embodiments of the present application, when BF or RLF occurs during the DU handover process in the CU-DU architecture, the information reported by the terminal device carries the information of the resources, which helps the network device perform mobile robustness optimization in a timely and accurate manner, thereby helping to avoid handover failures and improve the success rate of handovers.

[0483] As described above in conjunction with Figures 6 to 19 , the method for transmitting information according to the embodiments of the present application has been described in detail. Next, in conjunction with the drawings, the apparatus for transmitting information according to the embodiments of the present application will be described in detail.

[0484] The embodiments of the present application also provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, including units (or means) for implementing each step performed by the network device in any of the above methods. Another example is that another apparatus is provided, including units (or means) for implementing each step performed by the terminal device in any of the above methods.

[0485] Figure 20 FIG. shows a schematic block diagram of the apparatus 1200 for transmitting information provided by the embodiments of the present application. As Figure 20 shown, the apparatus 1200 for transmitting information may include a transceiver unit 1210 and a processing unit 1220.

[0486] In a possible design, the apparatus for transmitting information may be the first network device, the second network device, the fourth network device or the sixth network device in the above method 300 to method 1100, or a chip configured in the corresponding network device.

[0487] Specifically, the transceiver unit 1210 is configured to receive first information from the terminal device, where the first information includes information on a radio link failure between the terminal device and a first cell, or the first information includes information on beam failure recovery between the terminal device and the first cell;

[0488] The first information further includes information on resources, and the information on resources includes at least one of information on beams, information on uplink carriers or information on bandwidth parts;

[0489] A processing unit 1220, configured to perform mobility robustness optimization according to the first information.

[0490] Optionally, when the first information includes information about beam failure recovery between the terminal device and the first cell, the first information further includes at least one of the number of beam failures, the number of beam failure recoveries, or the duration of beam failure recovery.

[0491] Optionally, the first cell is a cell under the first network device. When the first information includes information about beam failure recovery between the terminal device and the first cell, the processing unit 1220 is specifically configured to:

[0492] Adjust the configuration of the resource; or,

[0493] The transceiver unit 1210 is further configured to send second information to a second network device, where the second information is used to instruct the second network device to adjust mobility parameters.

[0494] Optionally, the first cell is a cell under the first network device. When the first information includes information about radio link failure between the terminal device and the first cell, the transceiver unit 1210 is specifically configured to:

[0495] Receive the first information sent by the second network device;

[0496] Wherein, the processing unit 1220 is specifically configured to:

[0497] Adjust the configuration of the resource; or,

[0498] The transceiver unit 1210 is further configured to send second information to the second network device, where the second information is used to instruct the second network device to adjust mobility parameters.

[0499] Optionally, the information about the beam includes the identifier and / or measurement information of the beam. The identifier of the beam includes the synchronization signal block (SSB) group number and / or the channel state information reference signal (CSI-RS) group number. The information about the uplink carrier includes the identifier and / or measurement information of the uplink carrier. The identifier of the uplink carrier includes the frequency information of the uplink carrier. The uplink carrier includes a regular uplink carrier and / or a supplementary uplink carrier.

[0500] Optionally, the processing unit 1220 is specifically configured to perform any one or more of the following:

[0501] Adjust the first threshold value corresponding to the SSB;

[0502] Adjust the second threshold value corresponding to the CSI-RS;

[0503] Adjust the third threshold value corresponding to the supplementary uplink carrier; or,

[0504] Adjust the RACH resources, for example, the time-frequency resources corresponding to each SSB or CSI-RS, or the preamble group included in each SSB or CSI-RS, or reasonably adjust parameters such as the initial transmission / reception power and step size of the preamble, etc.

[0505] Optionally, the protocol layer functions of the device are at least one of radio link control protocol layer, media access control layer, and physical layer functions; and / or,

[0506] The protocol layer functions of the second network device are at least one of radio resource control protocol layer, service data adaptation layer, and packet data convergence protocol layer functions.

[0507] Optionally, the first cell is a cell under the second network device. When the first information includes information on beam failure recovery between the terminal device and the first cell, the transceiver unit 1210 is specifically configured to:

[0508] Receive the first information sent by the second network device;

[0509] Wherein, the processing unit 1220:

[0510] Adjust the mobility parameters; or,

[0511] The transceiver unit 1210 is further configured to send third information to the second network device, where the third information is used to instruct the second network device to adjust the configuration of the resources.

[0512] Optionally, the first cell is a cell under the second network device. When the first information includes information on radio link failure between the terminal device and the first cell, the processing unit 1220 is specifically configured to:

[0513] Adjust the mobility parameters; or,

[0514] The transceiver unit 1210 is further configured to send third information to the second network device, where the third information is used to instruct the second network device to adjust the configuration of the resources.

[0515] Optionally, the transceiver unit 1210 is further configured to receive fourth indication information sent by the second network device, where the fourth indication information is used to indicate the configuration of the adjusted resources.

[0516] Optionally, the protocol layer functions of the first network device are at least one of radio resource control protocol layer, service data adaptation layer, and packet data convergence protocol layer functions; and / or,

[0517] The protocol layer functions of the second network device include at least one of radio link control protocol layer, media access control layer, and physical layer functions.

[0518] It should be understood that the device 1200 for transmitting information may correspond to the network device in the above method embodiments. The device 1200 for transmitting information may include units for performing the methods executed by the network device in methods 200 to 1100 for transmitting information. Moreover, each unit in the device 1200 for transmitting information and the above other operations and / or functions respectively implement the corresponding processes of the methods 200 to 1100 for transmitting information. For the specific processes of each unit executing the above corresponding steps, please refer to the description of the method embodiments in the previous text. For the sake of brevity, it will not be elaborated here. Figures 6 to 19 For the sake of brevity, it will not be elaborated here.

[0519] Figure 21 Fig. shows a schematic block diagram of the device 1300 for transmitting information provided in the embodiments of the present application. As Figure 21 shown, the device 1300 for transmitting information may include a processing unit 1310 and a transceiver unit 1320.

[0520] In a possible design, the device for transmitting information may be the terminal device in the above methods 300 to 1100, or a chip configured in the terminal device.

[0521] Specifically, the processing unit 1310 is configured to determine first information, where the first information includes information on radio link failure occurring between the terminal device and the first cell, or the first information includes information on beam failure recovery occurring between the terminal device and the first cell;

[0522] The first information further includes information on resources, and the information on resources includes at least one of information on beams, information on uplink carriers, or information on bandwidth parts;

[0523] The transceiver unit 1320 is configured to transmit the first information.

[0524] Optionally, when the first information includes information on beam failure recovery occurring between the terminal device and the first cell, the first information further includes at least one of the number of beam failures, the number of beam failure recoveries, or the duration of beam failure recovery.

[0525] Optionally, the information on the beam includes the identifier of the beam and / or measurement information of the beam. The identifier of the beam includes the synchronization signal block SSB group number and / or the channel state information reference signal CSI-RS group number. The information on the uplink carrier includes the identifier of the uplink carrier and / or measurement information of the uplink carrier. The identifier of the uplink carrier includes the frequency information of the uplink carrier. The uplink carrier includes a regular uplink carrier and / or a supplementary uplink carrier.

[0526] It should be understood that the device 1300 for transmitting information may correspond to the terminal device in the method 200 to method 1100 for transmitting information according to the embodiments of the present application. The device 1300 for transmitting information may include units for performing the methods executed by the terminal device in the method 200 to method 1100 for transmitting information. Moreover, each unit in the device 1300 for transmitting information and the above other operations and / or functions respectively serve to implement the corresponding processes of the method 200 to method 1100 for transmitting information. For the specific processes of each unit executing the above corresponding steps, please refer to the description of the method embodiments in the foregoing text. For the sake of brevity, it will not be elaborated here. Figures 6 to 19 For the sake of brevity, it will not be elaborated here.

[0527] Figure 22 The structural schematic diagram of the network device provided by the embodiments of the present application is shown. It may be the network device in the above embodiments (any one of the first network device to the sixth network device) and is used to implement the operations of the network device (any one of the first network device to the sixth network device) in the above embodiments. As Figure 22 shown, the network device includes: an antenna 1401, a radio frequency device 1402, and a baseband device 1403. The antenna 1401 is connected to the radio frequency device 1402. In the uplink direction, the radio frequency device 1402 receives the information sent by the terminal device through the antenna 1401 and sends the information sent by the terminal device to the baseband device 1403 for processing. In the downlink direction, the baseband device 1403 processes the information of the terminal device and sends it to the radio frequency device 1402. After the radio frequency device 1402 processes the information of the terminal device, it is sent to the terminal device through the antenna 1401.

[0528] The baseband device 1403 may include one or more processing elements 14031, for example, including a main control CPU and other integrated circuits. In addition, the baseband device 1403 may further include a storage element 14032 and an interface 14033. The storage element 14032 is used to store programs and data; the interface 14033 is used to interact with the radio frequency device 1402, and this interface is, for example, a common public radio interface (CPRI). The above devices for the network device may be located in the baseband device 1403. For example, the above devices for the network device may be chips on the baseband device 1403. This chip includes at least one processing element and an interface circuit, where the processing element is used to execute each step of any of the methods executed by the above network device, and the interface circuit is used to communicate with other devices. In one implementation, the units for the network device to implement each step of the above method may be implemented in the form of a processing element scheduler. For example, the device for the network device includes a processing element and a storage element, and the processing element calls the program stored in the storage element to execute the method executed by the network device in the above method embodiments. The storage element may be a storage element on the same chip as the processing element, that is, an on-chip storage element, or a storage element on a different chip from the processing element, that is, an off-chip storage element.

[0529] In another implementation, the units for the network device to implement each step of the above method may be configured as one or more processing elements, and these processing elements are arranged on the baseband device. Here, the processing element may be an integrated circuit. For example: one or more application specific integrated circuits (ASICs), or, one or more digital signal processors (DSPs), or, one or more field programmable gate arrays (FPGAs), or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.

[0530] The units for the network device to implement each step of the above method may be integrated together and implemented in the form of an SOC. For example, the baseband device includes this SOC chip for implementing the above method. At least one processing element and a storage element may be integrated in this chip, and the method executed by the above network device is implemented in the form of the processing element calling the program stored in the storage element; or, at least one integrated circuit may be integrated in this chip for implementing the method executed by the above network device; or, the above implementation methods may be combined, and the functions of some units are implemented in the form of the processing element calling a program, and the functions of some units are implemented in the form of an integrated circuit.

[0531] As can be seen, the above device for a network device may include at least one processing element and an interface circuit, where at least one processing element is used to execute any of the methods performed by the network device provided in the above method embodiments. The processing element may execute some or all of the steps performed by the network device in a first way: that is, by calling a program stored in a storage element; or in a second way: that is, by integrating logic circuits in hardware in the processor element in combination with instructions to execute some or all of the steps performed by the network device; of course, some or all of the steps performed by the above network device may also be executed by combining the first way and the second way.

[0532] The processing element here is the same as described above and may be a general-purpose processor, such as a CPU, or may also be one or more integrated circuits configured to implement the above method, for example: one or more ASICs, or one or more microprocessors DSPs, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.

[0533] The storage element may be a memory or a collective term for multiple storage elements.

[0534] Optionally, Figure 22 The network device shown may be the fifth network device or the sixth network device in the above method embodiments.

[0535] Figure 23 Another structural schematic diagram of the network device provided in the embodiments of the present application is shown, which may be the network device in the above embodiments and is used to implement the operations of the network device in the above embodiments.

[0536] As Figure 23 shown, the network device includes: a processor 1510, a memory 1520, and an interface 1530. The processor 1510, the memory 1520, and the interface 1530 are signal-connected.

[0537] The above device 1200 for transmitting information may be located in the network device, and the functions of each unit may be implemented by the processor 1510 calling a program stored in the memory 1520. That is, the above device 1200 for transmitting information includes a memory and a processor. The memory is used to store a program, and this program is called by the processor to execute the method in the above method embodiments. The processor here may be an integrated circuit with signal processing capabilities, such as a CPU. Or the functions of each of the above units may be implemented by one or more integrated circuits configured to implement the above method. For example: one or more ASICs, or one or more microprocessors DSPs, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Or, the above implementation manners may be combined.

[0538] Optionally, Figure 23 the network device shown may be the first network device, the second network device, the third network device, or the fourth network device in the foregoing method embodiments.

[0539] Figure 24 The schematic structural diagram of the terminal device provided in the embodiments of the present application is shown, which may be the terminal device in the foregoing embodiments and is used to implement the operations of the terminal device in the foregoing embodiments. As Figure 24 shown, the terminal device includes: an antenna 1610, a radio frequency part 1620, and a signal processing part 1630. The antenna 1610 is connected to the radio frequency part 1620. In the downlink direction, the radio frequency part 1620 receives the information sent by the network device through the antenna 1610 and sends the information sent by the network device to the signal processing part 1630 for processing. In the uplink direction, the signal processing part 1630 processes the information of the terminal device and sends it to the radio frequency part 1620. After the radio frequency part 1620 processes the information of the terminal device, it is sent to the network device through the antenna 1610.

[0540] The signal processing part 1630 may include a modulation and demodulation subsystem for implementing the processing of each communication protocol layer of the data; it may also include a central processing subsystem for implementing the processing of the operating system and application layer of the terminal device; in addition, it may also include other subsystems, such as a multimedia subsystem, a peripheral subsystem, etc. The multimedia subsystem is used to implement the control of the camera, screen display, etc. of the terminal device, and the peripheral subsystem is used to implement the connection with other devices. The modulation and demodulation subsystem may be a separately provided chip. Optionally, the foregoing device for the terminal device may be located in the modulation and demodulation subsystem.

[0541] The modulation and demodulation subsystem may include one or more processing elements 1631, for example, including a main control CPU and other integrated circuits. In addition, the modulation and demodulation subsystem may further include a storage element 1632 and an interface circuit 1633. The storage element 1632 is used to store data and programs, but the programs for executing the methods performed by the terminal device in the above methods may not be stored in the storage element 1632, but in a memory outside the modulation and demodulation subsystem, and are loaded and used by the modulation and demodulation subsystem when in use. The interface circuit 1633 is used to communicate with other subsystems. The above device for the terminal device may be located in the modulation and demodulation subsystem, and the modulation and demodulation subsystem may be implemented by a chip, which includes at least one processing element and an interface circuit, where the processing element is used to execute each step of any of the methods performed by the above terminal device, and the interface circuit is used to communicate with other devices. In one implementation, the units for implementing each step in the above method in the terminal device may be implemented in the form of a processing element scheduling program. For example, the device for the terminal device includes a processing element and a storage element, and the processing element calls the program stored in the storage element to execute the method performed by the terminal device in the above method embodiments. The storage element may be a storage element on the same chip as the processing element, that is, an on-chip storage element.

[0542] In another implementation, the program for executing the method performed by the terminal device in the above method may be in a storage element on a different chip from the processing element, that is, an off-chip storage element. At this time, the processing element calls or loads the program from the off-chip storage element onto the on-chip storage element to call and execute the method performed by the terminal device in the above method embodiments.

[0543] In yet another implementation, the units for implementing each step in the above method in the terminal device may be configured as one or more processing elements, and these processing elements are provided on the modulation and demodulation subsystem. Here, the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.

[0544] The units for implementing each step in the above method in the terminal device may be integrated together and implemented in the form of an SOC. The SOC chip is used to implement the above method. At least one processing element and a storage element may be integrated in the chip, and the method performed by the above terminal device is implemented in the form of the processing element calling the program stored in the storage element; or, at least one integrated circuit may be integrated in the chip to implement the method performed by the above terminal device; or, the above implementation methods may be combined, and the functions of some units are implemented in the form of the processing element calling a program, and the functions of some units are implemented in the form of an integrated circuit.

[0545] It can be seen that the above device for a terminal device may include at least one processing element and an interface circuit, where the at least one processing element is used to execute any method performed by the terminal device provided in the above method embodiments. The processing element may execute some or all of the steps performed by the terminal device in a first manner, that is, by calling a program stored in a storage element; or in a second manner, that is, by combining the integrated logic circuit in the processor element with instructions to execute some or all of the steps performed by the terminal device; of course, it may also combine the first manner and the second manner to execute some or all of the steps performed by the terminal device.

[0546] According to the method provided in the embodiments of the present application, the present application also provides a computer program product, which includes: computer program code, when the computer program code runs on a computer, it causes the computer to execute the method in the above embodiments.

[0547] According to the method provided in the embodiments of the present application, the present application also provides a computer-readable medium, which stores program code, and when the program code runs on a computer, it causes the computer to execute the method in the above embodiments.

[0548] The terminal device and the network device in each of the above device embodiments may correspond exactly to the terminal device or the network device in the method embodiments, and the corresponding steps are executed by corresponding modules or units. For example, when the device is implemented in the form of a chip, the receiving unit may be an interface circuit of the chip for receiving signals from other chips or devices. The above unit for sending is an interface circuit of the device for sending signals to other devices. For example, when the device is implemented in the form of a chip, the sending unit is an interface circuit of the chip for sending signals to other chips or devices.

[0549] The embodiments of the present application also provide a communication system, which includes: the above terminal device, and / or, the above network device.

[0550] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0551] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the foregoing method embodiments, and will not be described in detail herein.

[0552] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

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

[0554] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0555] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0556] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for transmitting information, characterized in that, Including: Sending first information, where the first information includes information on beam failure recovery occurring between a terminal device and a first cell, the first cell being a cell under a first network device or a second network device, the first network device being a target network device, and the second network device being a source network device; The first information further includes information on resources, and the information on resources includes any one or more of information on beams, information on uplink carriers, or information on bandwidth parts; Wherein, the first information is used to adjust mobility parameters or to adjust the configuration of the resources.

2. The method according to claim 1, characterized in that, The first information further includes any one or more of the number of beam failures, the number of beam failure recoveries, or the duration of beam failure recovery.

3. The method according to claim 1 or 2, characterized in that, The first cell is a cell under the first network device, and the sending of the first information includes: Sending the first information to the first network device; Wherein, the first information is used for the first network device to adjust the configuration of the resources, or the first information is used for the first network device to send second information to the second network device, and the second information is used to instruct the second network device to adjust mobility parameters.

4. The method according to claim 3, wherein The information on the beam includes the identification of the beam and / or measurement information of the beam. The identification of the beam includes the synchronization signal block (SSB) group number and / or the channel state information reference signal (CSI-RS) group number. The information on the uplink carrier includes the identification of the uplink carrier and / or measurement information of the uplink carrier. The identification of the uplink carrier includes frequency information of the uplink carrier, and the uplink carrier includes a regular uplink carrier and / or a supplementary uplink carrier.

5. The method according to claim 4, characterized in that, The first information is used for the first network device to adjust a first threshold value corresponding to the SSB, adjust a second threshold value corresponding to the CSI-RS, adjust a third threshold value corresponding to the supplementary uplink carrier, or adjust one or more of the random access channel (RACH) resources.

6. The method according to claim 3, characterized in that, The protocol layer functions of the first network device include any one or more of the radio link control protocol layer, the media access control layer, and the physical layer functions; and / or, The protocol layer functions of the second network device include any one or more of the radio resource control protocol layer, the service data adaptation layer, and the packet data convergence protocol layer functions.

7. The method according to claim 1 or 2, characterized in that, The first cell is a cell under the second network device, and the sending of the first information includes: Sending the first information to the first network device through the second network device; Wherein, the first information is used for the first network device to adjust mobility parameters, or the first information is used for the first network device to send third information to the second network device, and the third information is used to instruct the second network device to adjust the configuration of the resources.

8. The method according to claim 7, wherein The protocol layer functions of the first network device include any one or more of the radio resource control protocol layer, the service data adaptation layer, and the packet data convergence protocol layer functions; and / or, The protocol layer functions of the second network device include any one or more of the radio link control protocol layer, the media access control layer, and the physical layer functions.

9. A device for transmitting information, characterized in that, Including: A processing unit, configured to determine first information, where the first information includes information about beam failure recovery occurring between the device and a first cell, and the first cell is a cell under a first network device or a second network device, the first network device is a target network device, and the second network device is a source network device; The first information further includes information about resources, and the information about resources includes any one or more of information about beams, information about uplink carriers, or information about bandwidth parts; Wherein, the first information is used to adjust mobility parameters or to adjust the configuration of the resources; A transceiver unit, configured to send the first information.

10. The device according to claim 9, characterized in that, The first information further includes any one or more of the number of beam failures, the number of beam failure recoveries, or the duration of beam failure recovery.

11. The device according to claim 9 or 10, characterized in that, When the first cell is a cell under the first network device, the transceiver unit is specifically configured to: Send the first information to the first network device; Wherein, the first information is used for the first network device to adjust the configuration of the resources, or the first information is used for the first network device to send second information to the second network device, and the second information is used to instruct the second network device to adjust mobility parameters.

12. The device according to claim 11, characterized in that, The information about the beam includes the identifier of the beam and / or the measurement information of the beam. The identifier of the beam includes the synchronization signal block (SSB) group number and / or the channel state information reference signal (CSI-RS) group number. The information about the uplink carrier includes the identifier of the uplink carrier and / or the measurement information of the uplink carrier. The identifier of the uplink carrier includes the frequency information of the uplink carrier, and the uplink carrier includes a regular uplink carrier and / or a supplementary uplink carrier.

13. The device according to claim 12, wherein The first information is used for the first network device to adjust a first threshold value corresponding to the SSB, adjust a second threshold value corresponding to the CSI-RS, adjust a third threshold value corresponding to the supplementary uplink carrier, or adjust one or more of the random access channel (RACH) resources.

14. The device according to claim 11, characterized in that, The protocol layer functions of the first network device include any one or more of the radio link control protocol layer, the media access control layer, and the physical layer functions; and / or, The protocol layer functions of the second network device include any one or more of the radio resource control protocol layer, the service data adaptation layer, and the packet data convergence protocol layer functions.

15. The device according to claim 9 or 10, characterized in that When the first cell is a cell under the second network device, the transceiver unit is specifically configured to: Send the first information to the first network device through the second network device; Wherein, the first information is used for the first network device to adjust mobility parameters, or the first information is used for the first network device to send third information to the second network device, and the third information is used to instruct the second network device to adjust the configuration of the resources.

16. The device according to claim 15, characterized in that, The protocol layer functions of the first network device include any one or more of the radio resource control protocol layer, the service data adaptation layer, and the packet data convergence protocol layer functions; and / or, The protocol layer functions of the second network device include any one or more of the radio link control protocol layer, the media access control layer, and the physical layer functions.

17. A computer program storage medium, characterized in that, The computer program storage medium has program instructions that, when directly or indirectly executed, enable the functions of the method according to any one of claims 1-8 to be implemented on a terminal device.

18. A chip system, characterized in that, The chip system includes at least one processor that, when the program instructions are executed in the at least one processor, enables the functions of the method according to any one of claims 1-8 to be implemented on a terminal device.

19. A computer program product, characterized in that, The computer program product stores a computer program or instructions that, when the computer program or instructions are run on a computer, cause the method according to any one of claims 1-8 to be executed.

Images