Beam management method and related device for physical cell

Abstract

The embodiment of the present application discloses a beam management method and related devices for a physical cell, which are used to avoid the problem of PCI conflict that is easily caused by a physical cell identifier PCI being shared by different adjacent cells in a large number of deployed sites. The communication method provided by the embodiment of the present application includes: a first network device determines that the first network device manages one or more first beams and a second network device manages one or more second beams, wherein the one or more first beams and the one or more second beams belong to the same physical cell, and the second network device is a device that accesses the physical cell; the first network device determines the resource information corresponding to the one or more second beams; the first network device sends the resource information to the second network device, and the resource information is used by the second network device to provide communication services for terminal devices that request access to the one or more second beams.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a beam management method for a physical cell and related devices. Background Art

[0002] Existing cellular network deployments suffer from various coverage gaps due to various reasons. These include signal obstruction in high-rise buildings, high signal attenuation indoors or in basements, lack of signal in remote areas, and water meter obstruction within buildings. With the further development of home networks and industrial IoT, more devices are being deployed in every corner of cities and rural areas, from buildings and streets to corridor corners, basements, and even deep underground pipe networks. This creates a need for wider and deeper network signal coverage.

[0003] Currently, coverage extension is primarily achieved by adding base stations, integrated access and backhaul (IAB) nodes, or relay nodes to address coverage gaps. However, adding sites requires additional network resources. For example, each newly added site is assigned a physical cell identity (PCI), but the number of PCIs is limited. Consequently, the deployment of a large number of sites can easily lead to adjacent cells at one or more sites using the same PCI. This prevents terminal devices from correctly identifying adjacent cells based on PCIs, leading to PCI conflicts. Summary of the Invention

[0004] The embodiments of the present application provide a beam management method and related devices for a physical cell, which are used to avoid the PCI conflict problem that is easily caused by a PCI being shared by different adjacent cells in a large number of deployed sites.

[0005] A first aspect of an embodiment of the present application provides a communication method, the communication method comprising:

[0006] A first network device determines that a first network manages one or more first beams and a second network device manages one or more second beams; wherein the one or more first beams and the one or more second beams belong to the same physical cell; the second network device is a device accessing the physical cell; the first network device determines resource information corresponding to the one or more second beams. The first network device sends the resource information to the second network device; the resource information is used by the second network device to provide communication services to a terminal device requesting access to the one or more second beams.

[0007] In this embodiment, the first network device configures resource information for one or more second beams for the second network device. The first network device then sends this resource information to the second network device. This allows the second network device to manage one or more second beams in a physical cell. The second network device is responsible for providing access services, resource scheduling, and other communication services to terminal devices requesting access to these one or more second beams. Because the one or more second beams managed by the second network device and the one or more first beams managed by the first network device belong to the same physical cell, the second network device is not managing a new physical cell. Therefore, there is no need to allocate a new PCI, thus avoiding the PCI conflict that can occur with large deployment sites due to a single PCI being shared by different adjacent cells. Furthermore, compared to the technical solution of adding an IAB node, since the PCIs detected by the terminal device from the first and second network devices are the same, the terminal device only perceives the physical cell and does not distinguish between the first and second network devices. When the terminal device receives signals from multiple beams in a physical cell, it can select and access the beam with the highest signal strength. This avoids handover between the first and second network devices when the terminal device moves, saving network signaling overhead and improving service quality.

[0008] In one possible implementation, the resource information includes at least one of the following: identifiers corresponding to one or more second beams, a set of preamble code numbers corresponding to each second beam, and random access channel time-frequency resource information corresponding to each second beam.

[0009] In this possible implementation, the second network device provides communication services, such as access services, resource scheduling services, and data transmission services, to terminal devices requesting access to one or more second beams through the content included in the resource information.

[0010] In another possible implementation, the method further includes:

[0011] The first network device sends at least one of the following to the second network device:

[0012] System information (SI), time-frequency resource information corresponding to the system information, time-frequency resource information corresponding to the demodulation reference signal (DMRS), time-frequency resource information corresponding to the channel state information reference signal (CSI-RS), cell radio network temporary identifier (C-RNTI) set, control resource set (CORESET) time-frequency resource information, and scheduling time-frequency resource information.

[0013] In this possible implementation, the first network device transmits the at least one parameter to the second network device, so that the second network device manages the one or more second beams of the physical cell, and enables the second network device to provide communication services to terminal devices requesting access to the one or more second beams.

[0014] In another possible implementation, the method further includes: the first network device receives capability information of the second network device sent by the second network device; the capability information includes at least one of the following: information indicating that the second network device is an access point type device, and the transmission power of the second network device.

[0015] In this possible implementation, the first network device may determine, based on the information indicating that the second network device is an access point type device and / or the transmit power of the second network device, that the second network device can serve as an access point and can provide access services, resource scheduling, and other services to terminal devices requesting access to the network device. This facilitates the subsequent reasonable configuration of the first network device by the second network device of the partial beams of the physical cell managed by the second network device.

[0016] In another possible implementation, the capability information also includes at least one of the following: the number of transmitting and receiving antennas of the second network device, location information, the number of supported beams, the number of terminal devices supported for access, and the size of the requested time-frequency resources.

[0017] In this possible implementation, the capability information also includes the parameters shown above to assist the first network device in subsequently reasonably configuring part of the beams of the physical cell managed by the second network device.

[0018] In another possible implementation, the first network device determines that the first network device manages one or more first beams and the second network device manages one or more second beams, including: the first network device determines that the one or more second beams are managed by the second network device based on capability information.

[0019] In this possible implementation, in order to more reasonably configure one or more second beams managed by the second network device, the first network device may obtain capability information of the second network device, and then determine the one or more second beams in combination with the capability information.

[0020] In another possible implementation, the method also includes: the first network device receives the location information and beam measurement results of the second network device, and the beam measurement results include the beam measurement results obtained by the second network device measuring the beam of the physical cell; then, the first network device determines that the first network device manages one or more first beams and the second network device manages one or more second beams, including: the first network device determines that the second network device manages the one or more second beams based on the capability information and the beam measurement results.

[0021] In this possible implementation, to enable the first network device to more appropriately configure one or more second beams managed by the second network device, the first network device may obtain beam measurement results and capability information of the second network device. The first network device then determines, based on the beam measurement results, that the second network device manages the one or more second beams.

[0022] In another possible implementation, when the first terminal device switches from the third beam to the fourth beam, the third beam is one of the one or more second beams, and the fourth beam is one of the one or more first beams; the method further includes:

[0023] The first network device receives the cell radio network temporary identifier (C-RNTI) of the first terminal device and the identifier of the fourth beam sent by the second network device; then, the first network device provides communication services for the first terminal device based on the C-RNTI of the first terminal device and the identifier of the fourth beam.

[0024] In this possible implementation, when the first terminal device is within the signal coverage of the third beam managed by the second network device, the second network device determines, based on the L1 measurement report of the first terminal device, that the fourth beam is used to provide services for the first terminal device. The first network device receives the C-RNTI of the first terminal device and the identifier of the fourth beam sent by the second network device. In this way, the first network device can provide communication services for the first terminal device, thereby enabling the first terminal device to continue to transmit data under the scheduling of the first network device in the beam switching scenario of the first terminal device.

[0025] In another possible implementation, the one or more second beams include a third beam, and the first terminal device accesses the third beam; when the first terminal device moves from a signal coverage range of the third beam to a signal coverage range of a fourth beam, the fourth beam is one of the one or more first beams managed by the first network device; and the method further includes:

[0026] The first network device receives message 1 sent by the first terminal device, where message 1 includes a random access preamble code; the first network device determines, based on the random access preamble code of message 1, that the first terminal device requests beam failure recovery in the fourth beam; the first network device sends message 2 to the first terminal device, where message 2 includes a random access response message; the first network device sends information to the second network device for instructing the second network device to stop scheduling the first terminal device.

[0027] In this possible implementation, the first terminal device moves from the signal coverage of the third beam managed by the second network device to the signal coverage of the fourth beam managed by the first network device, and the first terminal device initiates a beam failure recovery (BFR) request to the first network device to enable the first network device to provide services to the first terminal device, thereby enabling the first terminal device to continue to transmit data under the scheduling of the first network device in the event of a beam failure on the first terminal device. In addition, the first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device, so that the second network device can stop scheduling the first terminal device, so that the first network device can provide communication services to the first terminal device.

[0028] In another possible implementation, one or more first beams include a fourth beam, and the first terminal device accesses the fourth beam; the method also includes: the first network device receives a layer 1 (Layer 1, L1) measurement report of the first terminal device; the first network device determines a third beam based on the L1 measurement report; the third beam is one of the one or more second beams managed by the second network device; then, the first network device sends an identifier of the third beam to the first terminal device, and the identifier of the third beam is used for the first terminal device to switch from the fourth beam to the third beam; the first network device sends the C-RNTI of the first terminal device and the identifier of the third beam to the second network device.

[0029] In this possible implementation, the first terminal device is within the signal coverage of the second beam managed by the first network device. The first network device determines, based on the L1 measurement report of the first terminal device, that the third beam managed by the second network device provides services for the first terminal device. The first network device sends an identifier of the third beam to the first terminal device so that the first terminal device switches from the fourth beam to the third beam. In addition, the first network device sends the C-RNTI of the first terminal device and the identifier of the third beam to the second network device, thereby enabling the first terminal device to continue to transmit data under the scheduling of the second network device in the beam switching scenario of the first terminal device.

[0030] In another possible implementation, the one or more first beams include a fourth beam, and the first terminal device accesses the fourth beam; when the first terminal device moves from a signal coverage range of the fourth beam to a signal coverage range of a third beam, the first terminal device initiates a beam failure recovery request to the first network device, and the third beam is one of the one or more second beams managed by the second network device. The method further includes:

[0031] The first network device receives information from the second network device for instructing the first network device to stop scheduling the first terminal device; the first network device stops scheduling the first terminal device according to the information for instructing the first network device to stop scheduling the first terminal device.

[0032] In this possible implementation, the first terminal device moves from the signal coverage of the fourth beam managed by the first network device to the signal coverage of the third beam managed by the second network device. The first terminal device initiates a beam failure recovery request to the second network device so that the second network device can provide services to the first terminal device. In the scenario where a beam failure occurs in the first terminal device, the first terminal device continues to transmit data under the scheduling of the second network device. The first network device receives information from the second network device that instructs the first network device to stop scheduling the first terminal device. In this way, the first network device can stop scheduling the first terminal device so that the second network device can provide communication services to the first terminal device.

[0033] In another possible implementation, the method also includes: the first network device receives a layer 3 (Layer 3, L3) measurement report of the first terminal device; the first network device determines to switch the first terminal device from the first network device to the fourth network device based on the L3 measurement report; the first network device sends a switching request message to the fourth network device; the first network device receives a switching request confirmation message from the fourth network device, and the switching request confirmation message includes a switching command message sent by the fourth network device to the first terminal device; the switching command message includes a random access channel dedicated parameter; the random access channel dedicated parameter includes a C-RNTI allocated by the fourth network device to the first terminal device, an identifier of the sixth beam, and a random access preamble code corresponding to the sixth beam, and the sixth beam is a beam managed by the fourth network device; the first network device sends information to the second network device for instructing the second network device to stop scheduling the first terminal device.

[0034] In this possible implementation, the first terminal device is within the signal coverage of the third beam managed by the second network device. The first network device determines to switch the first terminal device from the third beam to the beam managed by the fourth network device based on the L3 measurement report of the first terminal device. Then, the first network device sends a switching request message to the fourth network device, and then receives a switching request confirmation message sent by the fourth network device. The switching request confirmation message includes a switching command message. The fourth network device then sends a switching command message to the first terminal device. In this way, the first terminal device switches from the third beam to the sixth beam according to the information of the third beam carried in the switching command message, thereby realizing the switching of the first terminal device between the first network device and the fourth network device. In addition, the first network device sends information to the second network device for instructing the second network device to stop scheduling the first terminal device, so as to instruct the second network device to stop scheduling the first terminal device. In this way, after the first terminal device switches to the sixth beam managed by the fourth network device, the second network device can stop scheduling the first terminal device in a timely manner.

[0035] In another possible implementation, the method also includes: the first network device receives a switching request message from the fourth network device; the first network device sends a switching request confirmation message to the fourth network device, and the switching request confirmation message includes a switching command message sent by the first network device to the first terminal device; the switching command message includes a random access channel dedicated parameter; the random access channel dedicated parameter includes a C-RNTI allocated by the first network device or the second network device to the first terminal device, an identifier of the third beam, and a random access preamble code corresponding to the third beam; the third beam is one of one or more second beams managed by the second network device; the first network device sends the C-RNTI of the first terminal device and the random access preamble code corresponding to the third beam to the second network device.

[0036] In this possible implementation, the first terminal device is within the signal coverage of the sixth beam managed by the fourth network device. The first network device receives a switching request message sent by the fourth network device. The first network device sends a switching request confirmation message to the fourth network device. The switching request confirmation message includes a switching command message. In this way, the fourth network device can send a switching command message to the first terminal device. The switching command message includes an identifier of the third beam. In this way, the first terminal device can determine to switch from the sixth beam managed by the fourth network device to the third beam managed by the second network device based on the identifier of the third beam. The first network device sends to the second network device information such as the C-RNTI allocated by the first network device to the first terminal device and the random access preamble code corresponding to the third beam. In this way, the switching of the first terminal device between the second network device and the fourth network device is realized, so that after the first terminal device switches to the second network device, the second network device provides communication services for the first terminal device.

[0037] A second aspect of an embodiment of the present application provides a communication method, the communication method comprising:

[0038] The second network device receives resource information corresponding to one or more second beams sent by the first network device; the one or more second beams and the one or more first beams managed by the first network device belong to the same physical cell; the second network device is a device accessing the physical cell; then, the second network device provides communication services for the terminal device requesting access to the one or more second beams based on the resource information.

[0039] In this embodiment, a network device receives resource information corresponding to one or more second beams sent by a first network device. The second network device then provides access services, resource scheduling, and other communication services to terminal devices requesting access to the one or more second beams based on the resource information. Because the one or more second beams managed by the second network device belong to the same physical cell as the one or more first beams managed by the first network device, the second network device does not manage a new physical cell. Therefore, there is no need to allocate a new PCI, thus avoiding the PCI conflict that can occur with large deployment sites due to a single PCI being shared by different adjacent cells. Furthermore, compared to the technical solution of adding an IAB node, because the PCI detected by the terminal device from the first and second network devices is the same, the terminal device only perceives the physical cell and does not distinguish between the first and second network devices. When the terminal device receives signals from multiple beams in the physical cell, it can select and access the beam with the highest signal strength. This avoids handover between the first and second network devices when the terminal device moves, saving network signaling overhead and improving service quality.

[0040] In one possible implementation, the resource information includes at least one of the following: identifiers corresponding to the one or more second beams, a set of contention-based preamble code numbers corresponding to each second beam, and random access channel time-frequency resource information corresponding to each second beam.

[0041] In this possible implementation, the second network device provides communication services, such as access services, resource scheduling services, and data transmission services, to terminal devices requesting access to one or more second beams through the content included in the resource information.

[0042] In another possible implementation, the method also includes: the second network device receives at least one of the following items sent by the first network device: system information, time-frequency resource information corresponding to the system information, time-frequency resource information corresponding to the demodulation reference signal, time-frequency resource information corresponding to the channel state information reference signal, cell wireless network temporary identification set, control resource set time-frequency resource information, and scheduling time-frequency resource information.

[0043] In this possible implementation, the second network device receives the at least one parameter sent by the first network device, so that the second network device manages the one or more second beams of the physical cell, and enables the second network device to provide communication services to terminal devices requesting access to the one or more second beams.

[0044] In another possible implementation, the method further includes: the second network device determines the time-frequency resources corresponding to the system information based on the time-frequency resource information corresponding to the system information; then, the second network device sends the system information on the time-frequency resources corresponding to the system information.

[0045] In this possible implementation, the second network device determines the time-frequency resources for the system information and broadcasts the system information of the physical cell. In this way, terminal devices in one or more second beam periods managed by the second network device can receive the system information and request access to the one or more second beams.

[0046] In another possible implementation, the method further includes: the second network device sends capability information of the second network device to the first network device; the capability information includes at least one of the following: information indicating that the second network device is an access point type device, and the transmission power of the second network device.

[0047] In this possible implementation, the first network device may determine, based on the information indicating that the second network device is an access point type device and / or the transmit power of the second network device, that the second network device can serve as an access point and can provide access services, resource scheduling, and other services to terminal devices requesting access to the network device. This facilitates the subsequent reasonable configuration of the first network device by the second network device of the partial beams of the physical cell managed by the second network device.

[0048] In another possible implementation, the capability information also includes at least one of the following: the number of transmitting and receiving antennas of the second network device, location information, the number of supported beams, the number of terminal devices supported for access, and the size of the requested time-frequency resources.

[0049] In this possible implementation, the capability information also includes the parameters shown above to assist the first network device in subsequently reasonably configuring part of the beams of the physical cell managed by the second network device.

[0050] In another possible implementation, the method further includes: the second network device sends a beam measurement result of the second network device to the first network device, where the beam measurement result includes a beam measurement result obtained by the second network device measuring the beam of the physical cell.

[0051] In this possible implementation, to enable the first network device to more appropriately configure one or more second beams managed by the second network device, the second network device may send its beam measurement results to the first network device. In this way, the first network device may determine that the second network device manages the one or more second beams based on the beam measurement results.

[0052] In another possible implementation, one or more second beams include a third beam, and the first terminal device accesses the third beam; the method also includes: the second network device receives the L1 measurement report sent by the first terminal device; then, the second network device determines the fourth beam based on the L1 measurement report; the fourth beam is one of the one or more first beams managed by the first network device; the second network device sends the identifier of the fourth beam to the first terminal device; the identifier of the fourth beam is used for the first terminal device to switch from the third beam to the fourth beam; the second network device sends the C-RNTI of the first terminal device and the identifier of the fourth beam to the first terminal device.

[0053] In this possible implementation, when the first terminal device is within the signal coverage of the third beam managed by the second network device, the second network device determines that the fourth beam provides services for the first terminal device based on the L1 measurement report of the first terminal device. The second network device sends the identifier of the fourth beam to the first terminal device so that the first terminal device can switch from the third beam to the fourth beam. The second network device sends the C-RNTI and the identifier of the fourth beam allocated by the second network device to the first terminal device to the first network device. In this way, the first network device can provide communication services for the first terminal device, so that in the beam switching scenario of the first terminal device, the first terminal device continues to transmit data under the scheduling of the first network device.

[0054] In another possible implementation, the one or more second beams include a third beam, and the first terminal device accesses the third beam; when the first terminal device moves from a signal coverage range of the third beam to a signal coverage range of a fourth beam, the first terminal device initiates a beam failure recovery request to the first network device, where the fourth beam is one of the one or more first beams managed by the first network device. The method further includes:

[0055] The second network device receives information from the first network device for instructing the second network device to stop scheduling the first terminal device; the second network device stops scheduling the first terminal device according to the information for instructing the second network device to stop scheduling the first terminal device.

[0056] In this possible implementation, a first terminal device moves from the signal coverage of a third beam managed by a second network device to the signal coverage of a fourth beam managed by the first network device, and the first terminal device initiates a beam failure recovery request to the first network device so that the first network device can provide services to the first terminal device. The second network device receives information from the first network device that instructs the second network device to stop scheduling the first terminal device, so that the second network device can stop scheduling the first terminal device, allowing the first network device to provide communication services to the first terminal device.

[0057] In another possible implementation, when the first terminal device switches from the fourth beam to the third beam, the third beam is one of the one or more second beams, and the fourth beam is one of the one or more first beams managed by the first network device; the method further includes:

[0058] The second network device receives the C-RNTI of the first terminal device and the identifier of the third beam sent by the first network device; the second network device provides communication services for the first terminal device based on the C-RNTI of the first terminal device and the identifier of the third beam.

[0059] In this possible implementation, the first terminal device is within the signal coverage of the second beam managed by the first network device. The first network device determines, based on the L1 measurement report of the first terminal device, that the third beam managed by the second network device provides service for the first terminal device. The second network device receives the C-RNTI of the first terminal device and the identifier of the third beam sent by the first network device, thereby enabling the first terminal device to continue to transmit data under the scheduling of the second network device in the beam switching scenario of the first terminal device.

[0060] In another possible implementation, the one or more first beams include a fourth beam, and the first terminal device accesses the fourth beam; when the first terminal device moves from a signal coverage range of the fourth beam to a signal coverage range of the third beam, the third beam is one of the one or more second beams managed by the second network device; and the method further includes:

[0061] The second network device receives message 1 from the first terminal device, where message 1 includes a random access preamble code; then, the second network device determines, based on the random access preamble code of message 1, that the first terminal device requests beam failure recovery in the third beam; the second network device sends message 2 to the first network device, where message 2 includes a random access response message; the second network device sends information to the first network device for instructing the first network device to stop scheduling the first terminal device.

[0062] In this possible implementation, the first terminal device moves from the signal coverage of the fourth beam managed by the first network device to the signal coverage of the third beam managed by the second network device. The first terminal device initiates a beam failure recovery request to the second network device so that the second network device can provide services to the first terminal device. In the scenario where a beam failure occurs in the first terminal device, the first terminal device continues to transmit data under the scheduling of the second network device. The second network device sends information to the first network device to instruct the first network device to stop scheduling the first terminal device. In this way, the first network device can stop scheduling the first terminal device so that the second network device can provide communication services to the first terminal device.

[0063] In another possible implementation, when the first terminal device switches from the first network device to the fourth network device, the method further includes:

[0064] The second network device receives information sent by the first network device for instructing the second network device to stop scheduling the first terminal device; then, the second network device stops scheduling the first terminal device according to the information for instructing the second network device to stop scheduling the first terminal device.

[0065] In this possible implementation, the first terminal device is within the signal coverage of the third beam managed by the second network device. The first network device determines to switch the first terminal device from the third beam to the beam managed by the fourth network device based on the L3 measurement report of the first terminal device. The second network device receives information sent by the first network device instructing the second network device to stop scheduling the first terminal device. The second network device then stops scheduling the first terminal device. In this way, after the first terminal device switches to the sixth beam managed by the fourth network device, the second network device can promptly stop scheduling the first terminal device.

[0066] In another possible implementation, when the first terminal device switches from the fourth network device to the first network device, the method further includes:

[0067] The second network device receives the C-RNTI of the first terminal device and the random access preamble code corresponding to the third beam sent by the first network device; then, the second network device provides communication services for the first terminal device based on the C-RNTI of the first terminal device and the random access preamble code corresponding to the third beam.

[0068] In this possible implementation, the first terminal device is within the signal coverage of the sixth beam managed by the fourth network device. The first network device receives a handover request message sent by the fourth network device. The second network device receives the C-RNTI of the first terminal device and the random access preamble corresponding to the third beam sent by the first network device. This enables handover of the first terminal device between the second network device and the fourth network device, so that after the first terminal device is handed over to the second network device, the second network device provides communication services for the first terminal device.

[0069] According to a third aspect of an embodiment of the present application, a first network device is provided, the first network device including:

[0070] a processing unit, configured to determine that a first network manages one or more first beams and a second network device manages one or more second beams; wherein the one or more first beams and the one or more second beams belong to the same physical cell; and the second network device is a device accessing the physical cell; and determine resource information corresponding to the one or more second beams;

[0071] The transceiver unit is used to send resource information to the second network device; the resource information is used by the second network device to provide communication services for terminal devices requesting access to one or more second beams.

[0072] In one possible implementation, the resource information includes at least one of the following: identifiers corresponding to one or more second beams, a set of preamble code numbers corresponding to each second beam, and random access channel time-frequency resource information corresponding to each second beam.

[0073] In another possible implementation, the transceiver unit is further configured to:

[0074] Send at least one of the following to the second network device:

[0075] System information, time-frequency resource information corresponding to the system information, time-frequency resource information corresponding to the demodulation reference signal, time-frequency resource information corresponding to the CSI-RS, cell radio network temporary identifier set, control resource set time-frequency resource information, and scheduling time-frequency resource information.

[0076] In another possible implementation, the transceiver unit is further configured to:

[0077] Capability information of the second network device sent by the second network device is received; the capability information includes at least one of the following: information indicating that the second network device is an access point type device, and transmission power of the second network device.

[0078] In another possible implementation, the capability information also includes at least one of the following: the number of transmitting and receiving antennas of the second network device, location information, the number of supported beams, the number of terminal devices supported for access, and the size of the requested time-frequency resources.

[0079] In another possible implementation, the processing unit is specifically configured to:

[0080] Determine, based on the capability information, that the one or more second beams are managed by the second network device.

[0081] In another possible implementation, the transceiver unit is further configured to:

[0082] receiving location information and a beam measurement result of a second network device, where the beam measurement result includes a beam measurement result obtained by the second network device measuring a beam of a physical cell;

[0083] The processing unit is specifically used to:

[0084] Determine, based on the capability information and the beam measurement result, that the second network device manages the one or more second beams.

[0085] In another possible implementation, when the first terminal device switches from the third beam to the fourth beam, the third beam is one of the one or more second beams, and the fourth beam is one of the one or more first beams; the transceiver unit is further configured to:

[0086] Receiving the C-RNTI of the first terminal device and the identifier of the fourth beam sent by the second network device;

[0087] The processing unit is also used to:

[0088] Communication services are provided to the first terminal device according to the C-RNTI of the first terminal device and the identifier of the fourth beam.

[0089] In another possible implementation, the one or more second beams include a third beam, and the first terminal device accesses the third beam; when the first terminal device moves from the signal coverage of the third beam to the signal coverage of the fourth beam, the fourth beam is one of the one or more first beams managed by the first network device; the transceiver unit is further configured to:

[0090] Receive a message 1 sent by a first terminal device, where the message 1 includes a random access preamble;

[0091] The processing unit is also used to:

[0092] Determining, based on the random access preamble of message 1, that the first terminal device requests beam failure recovery in the fourth beam; the first network device sends message 2 to the first terminal device, where message 2 includes a random access response message;

[0093] The transceiver unit is also used to:

[0094] Information is sent to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0095] In another possible implementation, the one or more first beams include a fourth beam, and the first terminal device accesses the fourth beam; and the transceiver unit is further configured to:

[0096] receiving an L1 measurement report of the first terminal device;

[0097] The processing unit is also used to:

[0098] Determining a third beam according to the L1 measurement report; the third beam is one of the one or more second beams managed by the second network device;

[0099] The transceiver unit is also used to:

[0100] Sending an identifier of the third beam to the first terminal device, where the identifier of the third beam is used by the first terminal device to switch from the fourth beam to the third beam;

[0101] Send the C-RNTI of the first terminal device and the identifier of the third beam to the second network device.

[0102] In another possible implementation, the one or more first beams include a fourth beam, and the first terminal device accesses the fourth beam; when the first terminal device moves from the signal coverage range of the fourth beam to the signal coverage range of the third beam, the first terminal device initiates a beam failure recovery request to the first network device, and the third beam is one of the one or more second beams managed by the second network device, and the transceiver unit is further used to:

[0103] receiving information from the second network device for instructing the first network device to stop scheduling the first terminal device;

[0104] The processing unit is also used to:

[0105] Stop scheduling the first terminal device according to the information used to instruct the first network device to stop scheduling the first terminal device.

[0106] In another possible implementation, the transceiver unit is further configured to:

[0107] receiving an L3 measurement report of the first terminal device;

[0108] The processing unit is also used to:

[0109] Determining, according to the L3 measurement report, to switch the first terminal device from the first network device to the fourth network device; the first network device sending a switching request message to the fourth network device;

[0110] The transceiver unit is also used to:

[0111] Receive a switching request confirmation message from the fourth network device, where the switching request confirmation message includes a switching command message sent by the fourth network device to the first terminal device; the switching command message includes a random access channel dedicated parameter; the random access channel dedicated parameter includes the C-RNTI allocated by the fourth network device to the first terminal device, an identifier of the sixth beam, and a random access preamble corresponding to the sixth beam, where the sixth beam is a beam managed by the fourth network device; and send information to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0112] In another possible implementation, the transceiver unit is further configured to:

[0113] Receive a handover request message from a fourth network device; send a handover request confirmation message to the fourth network device, where the handover request confirmation message includes a handover command message sent by the first network device to the first terminal device; the handover command message includes a random access channel-specific parameter; the random access channel-specific parameter includes a C-RNTI allocated by the first network device or the second network device to the first terminal device, an identifier of the third beam, and a random access preamble corresponding to the third beam; the third beam is one of one or more second beams managed by the second network device; and send the C-RNTI of the first terminal device and the random access preamble corresponding to the third beam to the second network device.

[0114] A fourth aspect of an embodiment of the present application provides a second network device, the second network device including:

[0115] a transceiver unit, configured to receive resource information corresponding to one or more second beams sent by a first network device; the one or more second beams and the one or more first beams managed by the first network device belong to the same physical cell; the second network device is a device accessing the physical cell;

[0116] A processing unit is used to provide communication services for terminal devices requesting access to the one or more second beams based on the resource information.

[0117] In one possible implementation, the resource information includes at least one of the following: identifiers corresponding to the one or more second beams, a set of contention-based preamble code numbers corresponding to each second beam, and random access channel time-frequency resource information corresponding to each second beam.

[0118] In another possible implementation, the transceiver unit is further configured to:

[0119] Receive at least one of the following items sent by the first network device: system information, time-frequency resource information corresponding to the system information, time-frequency resource information corresponding to the demodulation reference signal, time-frequency resource information corresponding to the channel state information reference signal, cell wireless network temporary identifier set, control resource set time-frequency resource information, and scheduling time-frequency resource information.

[0120] In another possible implementation, the processing unit is further configured to:

[0121] Determine the time-frequency resource corresponding to the system information according to the time-frequency resource information corresponding to the system information;

[0122] The transceiver unit is also used to:

[0123] The system information is sent in the time-frequency resources corresponding to the system information.

[0124] In another possible implementation, the transceiver unit is further configured to:

[0125] Send capability information of the second network device to the first network device; the capability information includes at least one of the following: information indicating that the second network device is an access point type device, and transmission power of the second network device.

[0126] In another possible implementation, the capability information also includes at least one of the following: the number of transmitting and receiving antennas of the second network device, location information, the number of supported beams, the number of terminal devices supported for access, and the size of the requested time-frequency resources.

[0127] In another possible implementation, the transceiver unit is further configured to:

[0128] The beam measurement result of the second network device is sent to the first network device, where the beam measurement result includes the beam measurement result obtained by the second network device measuring the beam of the physical cell.

[0129] In another possible implementation, the one or more second beams include a third beam, and the first terminal device accesses the third beam; and the transceiver unit is further configured to:

[0130] Receiving an L1 measurement report sent by the first terminal device;

[0131] The processing unit is also used to:

[0132] Determining a fourth beam according to the L1 measurement report; the fourth beam being one of the one or more first beams managed by the first network device;

[0133] The transceiver unit is also used to:

[0134] Sending an identifier of the fourth beam to the first terminal device; the identifier of the fourth beam is used by the first terminal device to switch from the third beam to the fourth beam;

[0135] Send the C-RNTI of the first terminal device and the identifier of the fourth beam to the first terminal device.

[0136] In another possible implementation, the one or more second beams include a third beam, and the first terminal device accesses the third beam; when the first terminal device moves from the signal coverage of the third beam to the signal coverage of the fourth beam, the first terminal device initiates a beam failure recovery request to the first network device, and the fourth beam is one of the one or more first beams managed by the first network device, and the transceiver unit is further used to:

[0137] receiving information from the first network device for instructing the second network device to stop scheduling the first terminal device;

[0138] The processing unit is also used to:

[0139] Stop scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0140] In another possible implementation, when the first terminal device switches from the fourth beam to the third beam, the third beam is one of the one or more second beams, and the fourth beam is one of the one or more first beams managed by the first network device; the transceiver unit is further configured to:

[0141] Receiving the C-RNTI of the first terminal device and the identifier of the third beam sent by the first network device;

[0142] The processing unit is also used to:

[0143] Communication services are provided to the first terminal device according to the C-RNTI of the first terminal device and the identifier of the third beam.

[0144] In another possible implementation, the one or more first beams include a fourth beam, and the first terminal device accesses the fourth beam; when the first terminal device moves from the signal coverage of the fourth beam to the signal coverage of the third beam, the third beam is one of the one or more second beams managed by the second network device; the transceiver unit is further configured to:

[0145] Receive a message 1 from a first terminal device, where the message 1 includes a random access preamble;

[0146] The processing unit is also used to:

[0147] Determining, according to the random access preamble of message 1, that the first terminal device requests beam failure recovery in the third beam;

[0148] The sending unit is also used to:

[0149] Sending message 2 to the first network device, where message 2 includes a random access response message;

[0150] Information is sent to the first network device to instruct the first network device to stop scheduling the first terminal device.

[0151] In another possible implementation, when the first terminal device switches from the first network device to the fourth network device, the transceiver unit is further configured to:

[0152] receiving information sent by the first network device for instructing the second network device to stop scheduling the first terminal device;

[0153] The processing unit is also used to:

[0154] Stop scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0155] In another possible implementation, when the first terminal device switches from the fourth network device to the first network device, the transceiver unit is further configured to:

[0156] Receive a C-RNTI of the first terminal device and a random access preamble corresponding to the third beam sent by the first network device;

[0157] The processing unit is also used to:

[0158] Communication services are provided for the first terminal device according to the C-RNTI of the first terminal device and the random access preamble code corresponding to the third beam.

[0159] In a fifth aspect, an embodiment of the present application provides a network device, comprising: a processor, a memory, and a transceiver; the processor is used for the transceiver to transmit and receive signals; a computer program is stored in the memory; the processor is also used to call and run the computer program stored in the memory, so that the processor executes the above-mentioned first aspect or any possible implementation method of the first aspect.

[0160] In a sixth aspect of an embodiment of the present application, a network device is provided, comprising: a processor, a memory, and a transceiver; the processor is used for the transceiver to transmit and receive signals; a computer program is stored in the memory; the processor is also used to call and run the computer program stored in the memory, so that the processor executes the above-mentioned second aspect or any possible implementation method of the second aspect.

[0161] A seventh aspect of an embodiment of the present application provides a computer program product comprising instructions, characterized in that when the computer program product is run on a computer, the computer is enabled to execute any one of the above-mentioned first to second aspects, or any one of the implementation methods of any one of the first and second aspects.

[0162] An eighth aspect of an embodiment of the present application provides a computer-readable storage medium, comprising computer instructions. When the computer instructions are executed on a computer, the computer executes any one of the above-mentioned first to second aspects, or any one of the implementation methods of any one of the first and second aspects.

[0163] A ninth aspect of an embodiment of the present application provides a chip device, comprising a processor, which is connected to a memory and calls a program stored in the memory so that the processor executes any one of the above-mentioned first to second aspects, or any one of the implementation methods of any one of the first and second aspects.

[0164] A tenth aspect of an embodiment of the present application provides a communication system, which includes a first network device as in the third aspect and a second network device as in the fourth aspect.

[0165] Through the above technical solution, it can be known that the first network device determines one or more first beams managed by the first network device and one or more second beams managed by the second network device. Among them, the one or more first beams and the one or more second beams belong to the same physical cell. The second network device is a device that accesses the physical cell. Then, the first network device determines the resource information corresponding to the one or more second beams and sends the resource information to the second network device. The resource information is used by the second network device to provide access services and resource scheduling for terminal devices requesting access to the one or more second beams. Through the technical solution of the embodiment of the present application, it can be known that the first network device configures the resource information of one or more second beams for the second network device, so that the second network device manages the one or more second beams of the physical cell and is responsible for providing access services and resource scheduling for terminal devices requesting access to the one or more second beams. Since the second network device manages one or more second beams of the physical cell, it is not a new physical cell, so there is no need to allocate a new PCI, thereby avoiding the problem of PCI conflict caused by a PCI shared by different adjacent physical cells, which is easy to occur in a large number of deployment sites. BRIEF DESCRIPTION OF THE DRAWINGS

[0166] Figure 1A This is a schematic diagram of the architecture of the communication system according to an embodiment of the present application;

[0167] Figure 1B This is another schematic diagram of the architecture of the communication system according to an embodiment of the present application;

[0168] Figure 2 This is a schematic diagram of the structure of the gNB according to an embodiment of the present application;

[0169] Figure 3 This is a schematic diagram of an embodiment of the communication method of the present application;

[0170] Figure 4A This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0171] Figure 4B A schematic diagram of a control plane protocol stack of a terminal device, a control plane protocol stack of a first network device, and a control plane protocol stack of a second network device according to an embodiment of the present application;

[0172] Figure 4C A schematic diagram of a user plane protocol stack of a terminal device, a user plane protocol stack of a first network device, and a user plane protocol stack of a second network device according to an embodiment of the present application;

[0173] Figure 5 This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0174] Figure 6AThis is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0175] Figure 6B A schematic diagram of an application scenario of the communication method according to an embodiment of the present application;

[0176] Figure 7A This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0177] Figure 7B This is a schematic diagram of another application scenario of the communication method according to an embodiment of the present application;

[0178] Figure 7C This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0179] Figure 8 This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0180] Figure 9A This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0181] Figure 9B This is a schematic diagram of another application scenario of the communication method according to an embodiment of the present application;

[0182] Figure 10A This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0183] Figure 10B This is a schematic diagram of another application scenario of the communication method according to an embodiment of the present application;

[0184] Figure 11 This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0185] Figure 12 This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0186] Figure 13A This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0187] Figure 13B This is a schematic diagram of another application scenario of the communication method according to an embodiment of the present application;

[0188] Figure 14 This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0189] Figure 15A This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0190] Figure 15BThis is a schematic diagram of another application scenario of the communication method according to an embodiment of the present application;

[0191] Figure 16A This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0192] Figure 16B This is a schematic diagram of another application scenario of the communication method according to an embodiment of the present application;

[0193] Figure 17A This is a schematic diagram of another embodiment of the communication method according to the embodiment of the present application;

[0194] Figure 17B This is a schematic diagram of another application scenario of the communication method according to an embodiment of the present application;

[0195] Figure 18 This is a structural diagram of a first network device according to an embodiment of the present application;

[0196] Figure 19 This is a structural diagram of the second network device according to an embodiment of the present application;

[0197] Figure 20 This is another structural diagram of the first network device according to an embodiment of the present application;

[0198] Figure 21 This is another structural diagram of the second network device according to an embodiment of the present application;

[0199] Figure 22 A schematic diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0200] In order to make the purpose, technical solutions and advantages of this application clearer, this application will be further described below with reference to the accompanying drawings.

[0201] The terms "including" and "having" and any variations thereof in the specification, claims, and drawings of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, product, or apparatus.

[0202] References to "embodiments" herein mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive of other embodiments. It will be understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0203] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0204] See also Figure 1A , Figure 1A This is a schematic diagram of the architecture of the communication system of the embodiment of the present application. Figure 1A In the example, physical cell 1 of the next generation Node B (gNB) in the 5G system includes the signal coverage of beam 1. User equipment 1 (UE1) and node X are within the signal coverage of physical cell 1. UE1 can access physical cell 1, and node X can access physical cell 1 as a UE.

[0205] NodeX is an access point type device that has functions such as providing access services and resource scheduling for UEs. The main feature that distinguishes NodeX from existing IAB nodes is that when NodeX acts as an access point type device, the physical cell identifier (PCI) of the physical cell it manages and the system information it broadcasts are the same as the PCI of the physical cell that NodeX accesses as a UE and the system information broadcast by the physical cell. That is, NodeX is only used to expand the signal coverage of the physical cell it accesses and does not introduce new cells. The name NodeX is only an example and can also be called by other names.

[0206] For example, Figure 1AAs shown in the figure, NodeX, acting as a UE, accesses physical cell 1 of the gNB. The gNB determines to add beam 2 to the physical cell, and NodeX manages beam 2. NodeX, acting as an access point, manages beam 2 of physical cell 1. The PCI of physical cell 1 of NodeX is the same as the PCI of physical cell 1 of the gNB, and the system information of physical cell 1 broadcast by NodeX is the same as the system information of physical cell 1 broadcast by the gNB.

[0207] NodeX is placed at the edge of physical cell 1 of the gNB, extending the coverage of physical cell 1 and providing coverage extension services for the gNB. This means that the signal coverage of physical cell 1 is expanded from the original coverage of beam 1 to include the coverage of beam 1 and beam 2. NodeX manages a portion of the beams in physical cell 1 and does not belong to the newly added physical cell.

[0208] For UE3, the signal strength of Beam 1 from the gNB is not as strong as the signal strength of Beam 2 from NodeX. Therefore, UE3 can choose to access Beam 2 managed by NodeX. Because UE3 only detects one PCI, it cannot distinguish between the gNB and NodeX. UE3 can detect the signal strength of different beams within physical cell 1 and select the beam with the higher signal strength. For example, if the signal strength of Beam 2 managed by NodeX is higher, UE3 selects the random access resource corresponding to Beam 2 and requests access to it.

[0209] For UE2, before NodeX provides coverage extension services, physical cell 1 includes the signal coverage of beam 1. This means that UE2 is originally outside the signal coverage of physical cell 1. However, after NodeX provides coverage extension services, physical cell 1 includes the signal coverage of both beam 1 and beam 2. UE2 now falls within the signal coverage of physical cell 1. UE2 can access beam 2 managed by NodeX through NodeX, and its data is ultimately sent to the gNB via NodeX's relay, enabling cellular network communication.

[0210] In the embodiment of the present application, the second network device (for example, the above Figure 1AA first network device (e.g., the gNB shown in FIG1 ) accesses the physical cell of a first network device (e.g., the gNB shown in FIG1 ) as a terminal device. The first network device determines one or more first beams managed by the first network device and one or more second beams managed by a second network device. The first network device then determines resource information corresponding to the one or more second beams. The first network device sends the resource information corresponding to the one or more second beams to the second network device. The resource information is used by the second network device to provide access services and resource scheduling for terminal devices requesting access to the one or more second beams.

[0211] Figure 1B This is another schematic diagram of the architecture of the communication system according to the embodiment of the present application. Figure 1B In the example, the physical cell includes Beam 1, Beam 2, Beam 3, and Beam 4. The first network device manages Beam 1, Beam 2, and Beam 3. The second network device first accesses the physical cell of the first network device as a terminal device. The first network device then configures the second network device to manage Beam 4. This allows the second network device to provide access services and resource scheduling for terminal devices requesting access to Beam 4. Furthermore, the second network device is placed at the edge of the physical cell, extending the signal coverage of the physical cell and providing coverage extension services to the first network device.

[0212] In this application, a terminal device may also be referred to as user equipment (UE). A terminal device is a device with wireless transceiver capabilities that can communicate with one or more core network (CN) devices (or core devices) via a radio access network (RAN) device (or access device).

[0213] Terminal devices may also be called access terminals, terminals, subscriber units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, user agents, or user devices. Terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water (such as ships); or in the air (such as aircraft, balloons, and satellites).

[0214] Alternatively, the terminal device may also include a limited device, such as a device with low power consumption, a device with limited storage capacity, or a device with limited computing power, etc. Examples include information sensing devices such as barcodes, radio frequency identification (RFID), sensors, global positioning systems (GPS), laser scanners, and the like.

[0215] Alternatively, the terminal device may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a smart phone, a mobile phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), etc. Alternatively, the terminal device may be a handheld device with wireless communication capabilities, a computing device, or other device connected to a wireless modem, an in-vehicle device, a wearable device, an unmanned aerial vehicle device, or a terminal in the Internet of Things or the Internet of Vehicles, a terminal of any form in a 5G network or future networks, a relay user device, or a terminal in a future evolved PLMN, etc. The relay user device may be, for example, a 5G residential gateway (RG). For example, the terminal device may be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. The embodiments of the present application do not limit the type or category of the terminal device.

[0216] The first network device and the second network device can both be access network devices, which are devices that provide wireless communication functions for terminal devices, and can also be called access devices, (R)AN devices or network devices, etc. For example, the access device includes but is not limited to: gNB, long term evolution (LTE) base station (next generation evolved Node B, ng-eNB) for connecting to the 5G core network, evolved node B (evolved node B, eNB) in the LTE system, radio network controller (RNC), node B (node ​​B, NB), base station controller (basestation controller, BSC), base transceiver station (base transceiver station, BTS), home evolved node B (home evolved node B, or home node B, HNB), base band unit (base band unit, BBU), transmission and receiving point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), small base station equipment (pico), mobile switching center, or network equipment in future networks, etc. It can be understood that the present application does not limit the specific type of wireless access network equipment. In systems using different wireless access technologies, the name of the device with wireless access network device functions may be different.

[0217] It should be noted that the above Figure 1B This example shows a first network device managing three beams of a physical cell and a second network device managing one beam of the physical cell. In actual applications, the physical cell includes at least two beams. The first network device manages at least one beam of the physical cell. The second network device manages at least one beam of the physical cell. The beams of the physical cell managed by the first and second network devices are different.

[0218] The following describes a possible split structure of the first network device as an access network device. This is described using the gNB as an example. The same applies to other types of access network devices. Figure 2 , Figure 2 This is a structural diagram of the gNB embodiment of the present application.

[0219] In the 5G communication system, gNBs are connected to each other via the Xn interface, and gNBs are connected to the 5th generation mobile communication technology core network (5GC) via the NG interface. Figure 2 As shown in Figure 1, gNB1 and gNB2 are connected via the Xn interface. gNB1 is connected to 5GC via NG interface 1, and gNB2 is connected to 5GC via NG interface 2.

[0220] A gNB can be composed of a centralized unit (CU) and a distributed unit (DU). This splits the base station functionality of the original access network equipment, deploying some base station functions in a gNB-CU and the remaining functions in a gNB-DU. Multiple gNB-DUs share a single gNB-CU, saving costs and facilitating network expansion.

[0221] The gNB-CU and gNB-DU can be divided according to protocol stacks. For example, the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layer protocol stacks are deployed in the gNB-CU. The radio link control (RLC), medium access control (MAC), and physical (PHY) layer protocol stacks are deployed in the gNB-DU. The gNB-CU and gNB-DU are connected via the F1 interface. The above examples are only for the purpose of introducing the gNB-CU and gNB-DU. The embodiments of this application do not limit the protocol stacks deployed in the gNB-CU and gNB-DU.

[0222] When the gNB-CU is further divided based on the control plane and user plane, it can be divided into a gNB-CU-CP (or CU-CP) and at least one gNB-CU-UP (or CU-UP). The CU-CP is primarily responsible for RRC and the PDCP entities corresponding to signaling radio bearers (SRBs). The CU-UP is primarily responsible for SDAP and the PDCP entities corresponding to data radio bearers (DRBs). The above example is merely an introduction to the gNB-CU and does not limit the specific division of the gNB-CU. Furthermore, when the gNB-CU is divided into the gNB-CU-CP and at least one gNB-CU-UP, the embodiments of this application do not limit the protocols primarily responsible by the gNB-CU-CP and at least one gNB-CU-UP.

[0223] For example, Figure 2 As shown, gNB1 includes gNB-CU1, gNB-DU1, and gNB-DU2. gNB-CU1 connects to gNB-DU1 via F1 interface 1 and to gNB-DU2 via F1 interface 2. The structure of gNB2 is similar to that of gNB1 and is not described here.

[0224] The technical solutions of the embodiments of the present application are described below in conjunction with specific embodiments.

[0225] See also Figure 3 , Figure 3 This is a schematic diagram of an embodiment of the communication method of the present application. Figure 3 , the communication method comprises:

[0226] 301. A first network device determines that the first network device manages one or more first beams and a second network device manages one or more second beams.

[0227] The one or more first beams and the one or more second beams belong to the same physical cell. The second network device is a device accessing the physical cell.

[0228] The second network device accesses the physical cell as a terminal device. The second network device is an access point type device.

[0229] An access point device refers to a network device that can serve as an access point and provide services such as access and resource scheduling to terminal devices requesting access to the network device. Furthermore, the network device can provide functions such as signal coverage extension services. The PCI of the physical cell managed by the access point device is the same as the PCI of the physical cell of the network device it accesses. Furthermore, the system information broadcast by the access point device for the physical cell is the same as the system information broadcast by the network device it accesses. In other words, an access point device is used to expand the signal coverage of a physical cell and does not add a new physical cell.

[0230] For example, Figure 1B As shown, the first network device is a gNB, and the second network device is NodeX. NodeX, as a terminal device, first accesses the physical cell and establishes an RRC connection with the gNB. NodeX is an access point device. The physical cell includes signal coverage corresponding to beams 1 through 4, respectively. The gNB determines which beams 1 through 3 are managed by the gNB, and which beam 4 is managed by NodeX.

[0231] The one or more second beams are described below.

[0232] 1. The one or more second beams may be beams originally included in the physical cell, that is, beams generated by the first network device.

[0233] 2. The one or more second beams may be: beams newly generated by the second network device in the physical cell after the first network device determines the second network device as the access point. These newly generated beams are managed by the second network device.

[0234] 3. Some of the one or more second beams are: some of the beams originally managed by the first network device in the physical cell. Another part of the one or more second beams are: beams newly generated by the first network device in the physical cell.

[0235] The one or more second beams managed by the second network device realize the signal coverage extension of the physical cell, which is not limited in this application.

[0236] For example, Figure 1B As shown, if the physical cell originally only includes beams 1 through 3, but the first network device discovers that the second network device can serve as an access point, the first network device can modify the physical cell's original support of three beams to support four beams. Furthermore, beams 1 through 3 are managed by the first network device, while beam 4 is managed by the second network device. In other examples, the first network device can manage beams 1 and 2, while the second network device can manage beams 3 and 4.

[0237] In order for the first network device to more reasonably configure the one or more second beams managed by the second network device, the first network device may obtain capability information of the second network device and then determine the one or more second beams based on the capability information. Optionally, this embodiment further includes step 301a, and step 301a is performed before step 301.

[0238] Step 301a: The second network device sends its capability information to the first network device.

[0239] The capability information of the second network device includes at least one of the following:

[0240] 1. Information indicating that the second network device is an access point type device;

[0241] 2. Transmit power of the second network device.

[0242] Optionally, the capability information also includes at least one of the following:

[0243] 1. The number of transmitting and receiving antennas of the second network device;

[0244] 2. Location information of the second network device;

[0245] 3. The number of beams supported by the second network device;

[0246] 4. The number of terminal devices supported by the second network device;

[0247] 5. The second network device requests the size of the time-frequency resources.

[0248] The specific uses of the parameters included in the capability information can be found in the relevant introduction to step 301 later, which will not be repeated here.

[0249] The above step 301a is a possible implementation method for the first network device to obtain the capability information of the second network device. In actual application, the capability information of the second network device can also be pre-configured in the first network device, or sent to the first network device through other devices, which is not limited in this application.

[0250] In this embodiment, there are multiple specific ways for the second network device to send the capability information of the second network device in the above step 301a. Two possible implementation ways are shown below.

[0251] 1. In step 301a above, the second network device sends its capability information to the first network device via a newly defined RRC message. For example, the newly defined RRC message is named NodeXCapabilityInformation.

[0252] 2. In step 301a above, the second network device sends its capability information to the first network device via a new information element in an existing RRC message. For example, a new information element is added to the user equipment capability information (UECapabilityInformation). The name of the new information element can be NodeXCapabilityInformation.

[0253] There are many ways for the first network device to determine that the second network device is an access point type device. The following examples illustrate several possible implementations.

[0254] 1. The capability information of the second network device includes information indicating that the second network device is an access point type device. The first network device determines that the second network device is an access point type device or that the second network device can serve as an access point based on the information indicating that the second network device is an access point type device.

[0255] 2. The first network device determines, according to the newly defined RRC message or the newly added information element in the RRC message, that the second network device is an access point type device, or determines that the second network device can serve as an access point.

[0256] 3. The first network device determines whether the second network device is an access point type device based on the transmit power carried in the UE capability information of the second network device. For example, when the transmit power is 23 dBm (decibel milliwatts), the second network device is a normal UE; when the transmit power is 30 dBm or other values, the first network device may determine that the second network device is an access point type device.

[0257] Then, based on the above step 301a, the above step 301 specifically includes: the first network device determines, according to the capability information of the second network device, that the first network device manages one or more first beams and the second network device manages one or more second beams.

[0258] The following describes a process in which the first network device determines that the second network device manages one or more second beams in conjunction with the capability information of the second network device.

[0259] The first network device can determine that the second network device can serve as an access point based on the information indicating that the second network device is an access point type device or the transmit power information. The second network device can provide access services and resource scheduling functions for the terminal device. The first network device can then configure the one or more second beams to be managed by the second network device, and further use the second network device to provide signal coverage extension services.

[0260] The first network device determines which second beam or beams are managed by the second network device according to the number of transceiver antennas of the second network device, the number of beams supported by the second network device, and the location information of the second network device.

[0261] For example, Figure 1B As shown, the first network device determines that the second network device is located between beams 2 and 3 of the physical cell. The second network device supports management of one beam and has two transceiver antennas. Then, the first network device can add beam 4 and have it managed by the second network device. The first network device determines the size of the scheduled time-frequency resources used by the second network device to manage beam 4 based on the size of the time-frequency resources requested by the second network device. Furthermore, the first network device determines the number of C-RNTIs to allocate to the second network device based on the number of terminal devices supported by the second network device.

[0262] Since one C-RNTI corresponds to one terminal device, the first network device configures the corresponding C-RNTI to the second network device according to the number of terminal devices, so that the second network device can allocate corresponding C-RNTI to the terminal device requesting access to one or more second beams managed by the second network device.

[0263] To more effectively configure one or more second beams managed by the second network device, the first network device may obtain beam measurement results from the second network device. The first network device then determines, based on the beam measurement results, that the second network device manages the one or more second beams. Optionally, this embodiment further includes step 301b. Step 301b is performed before step 301.

[0264] Step 301b: The second network device sends the beam measurement result to the first network device.

[0265] The beam measurement result includes the beam measurement result obtained by the second network device measuring the beam of the physical cell.

[0266] Specifically, the second network device measures the beam of the physical cell and reports a measurement report to the first network device. The measurement report includes a beam measurement result. The beam measurement result includes a beam measurement result based on a synchronization signal and physical broadcast channel block (SS / PBCH block) or a synchronization signal block (SSB). Alternatively, the beam measurement result includes a beam measurement result based on a channel state information reference signal (CSI-RS).

[0267] For example, the terminal device reports a measurement result list (ResultsPerSSB-IndexList) corresponding to the SSB identifier (e.g., SSB index (SSB index)). ResultsPerSSB-IndexList includes a set of SSB identifiers and corresponding measurement results (MeasQuantityResults). Alternatively, the terminal device reports a measurement result list (ResultsPerCSI-RS-IndexList) corresponding to the CSI-RS identifier (e.g., CSI-RS index (CSI-RS-index)).

[0268] ResultsPerSSB-IndexList includes the CSI-RS identifier and the corresponding measurement results (MeasQuantityResults).

[0269] The measurement results (MeasQuantityResults) may include: Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), and Signal to Interference Plus Noise Ratio (SINR).

[0270] Then, based on step 301a and step 301b, the above step 301 specifically includes:

[0271] The first network device determines, based on the capability information of the second network device and the beam measurement result, that the first network device manages one or more first beams and the second network device manages one or more second beams.

[0272] The first network device may determine that the second network device manages one or more second beams based on the capability information of the second network device. The specific determination process is described above and is not further described here. In addition to referencing the capability information of the second network device, the second network device may further determine that the second network device manages one or more second beams based on the beam measurement results.

[0273] For example, Figure 1B As shown, the first network device determines, based on the beam measurement results, that the RSRP (or RSRQ, or SINR) of Beam 2 and Beam 3 of the physical cell measured by the second network device is higher. The first network device then adds Beam 4 between Beam 2 and Beam 3, and the second network device manages Beam 4. This provides a better communication environment for devices at the edge of Beam 2 and Beam 3 and extends signal coverage.

[0274] 302. The first network device sends resource information corresponding to the one or more second beams to the second network device.

[0275] The resource information includes at least one of the following:

[0276] 1. Identifiers corresponding to one or more second beams;

[0277] Specifically, the identifiers corresponding to the one or more second beams may be a synchronization signal and physical broadcast channel block index (SS / PBCH block index), or a synchronization signal block index (SSBindex), which is hereinafter collectively referred to as SSB index.

[0278] 2. The set of preamble code numbers corresponding to each second beam;

[0279] Specifically, each second beam corresponds to an SSB index, and each SSB index corresponds to a set of contention-based preamble indexes.

[0280] 3. Time-frequency resource information of the random access channel corresponding to each second beam.

[0281] Each second beam corresponds to an SSB index. Each SSB index corresponds to the random access channel (RACH) time-frequency resource information. For example, the RACH time-frequency resource information includes the physical random access channel configuration identifier (prach-ConfigIndex), message 1 frequency division multiplexing (msg1-FDM), and message 1 frequency domain start (msg1-FrequencyStart).

[0282] It should be noted that the resource information may not include the random access channel time-frequency resource information corresponding to each second beam.

[0283] ssb-perRACH-OccasionAndCB-PreamblesPerSSB includes the random access occasion (RACH occasion, RO) corresponding to each second beam. The second network device can determine the preamble index and the corresponding RO corresponding to each second beam managed by the second network device based on the SSB index corresponding to one or more second beams managed by the second network device and ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0284] It should be noted that, during step 302, the first network device also sends at least one of the following to the second network device:

[0285] System information, time-frequency resource information corresponding to the system information, time-frequency resource information corresponding to the demodulation reference signal, time-frequency resource information corresponding to the CSI-RS, cell radio network temporary identifier set, control resource set time-frequency resource information, and scheduling time-frequency resource information.

[0286] The system information is the same as the system information of the physical cell used by the first network device.

[0287] Optionally, the above-mentioned time-frequency resource information includes at least one of a time domain starting position, a time domain period, a frequency domain starting position, a time domain ending position, a frequency domain ending position, a radio bearer (RB) starting number, and an RB ending number.

[0288] It should be noted that the first network device sends the above-mentioned parameters to the second network device via one or more RRC messages; alternatively, the second network device may obtain some of the above-mentioned parameters by reading broadcast messages of the first network device in the physical cell. For example, the system information may be obtained by the second network device by reading broadcast messages of the first network device in the physical cell.

[0289] In case that the beams included in the physical cell change, after the first network device completes the configuration for the second network device, the first network device broadcasts the updated system information block 1 (SIB1).

[0290] For example, Figure 1B As shown, the physical cell has changed from only including beams 1 to 3 to including beams 1 to 4. That is, the physical cell has newly added beam 4. The updated ssb-perRACH-OccasionAndCB-PreamblesPerSSB in SIB1 has been modified from the original correspondence between three SSB indices and RACH resources to the correspondence between four SSB indices and RACH resources. In addition,

[0291] ssb-perRACH-OccasionAndCB-PreamblesPerSSB indicates the RACHoccasion associated with each SSB index and the number of contention-based random access preambles corresponding to each SSB index.

[0292] 303. The second network device provides communication services for the terminal device requesting to access the one or more second beams according to the resource information.

[0293] The relevant introduction of step 303 can be found later. Figure 4A and Figure 5 The illustrated embodiment introduces a process in which the second network device provides access services and resource scheduling for the terminal device, which will not be described in detail here.

[0294] In an embodiment of the present application, a first network device determines that it manages one or more first beams and a second network device manages one or more second beams. The one or more first beams and the one or more second beams belong to the same physical cell. The second network device is a device that accesses the physical cell. The first network device then determines resource information corresponding to the one or more second beams and sends the resource information to the second network device. The resource information is used by the second network device to provide access services and resource scheduling to terminal devices requesting access to the one or more second beams. As can be seen from the technical solution of this embodiment of the present application, the first network device configures the resource information of the one or more second beams for the second network device. This enables the second network device to manage the one or more second beams of the physical cell. The second network device is responsible for providing access services and resource scheduling to terminal devices requesting access to the one or more second beams. Since the one or more second beams managed by the second network device and the one or more first beams managed by the first network device belong to the same physical cell, the second network device is not managing a new physical cell. Therefore, there is no need to allocate a new PCI, thus avoiding the PCI conflict issue that can occur with large-scale deployment sites due to a single PCI being shared by different adjacent cells. Furthermore, compared to the technical solution of adding an IAB node, since the terminal device detects the same PCI from the first and second network devices, it only perceives the physical cell and does not distinguish between the first and second network devices. When the terminal device receives signals from multiple beams in the physical cell, it can select and connect to the beam with the highest signal strength. This avoids switching between the first and second network devices when the terminal device moves, saving network signaling overhead and improving service quality.

[0295] The following combination Figure 4A The embodiment shown shows the process in which the second network device provides access services to the terminal device during the four-step random access process. Figure 4A , Figure 4A This is another embodiment diagram of the communication method of the present application embodiment. Figure 4A , the communication method comprises:

[0296] 401. The second network device sends SSB and system information to the terminal device.

[0297] The SSB is an SSB corresponding to one or more second beams respectively.

[0298] In the above Figure 3 In step 302 of the illustrated embodiment, the second network device obtains system information, time-frequency resources corresponding to the system information, and time-frequency resources corresponding to the SSB from the first network device. The second network device broadcasts the system information on the time-frequency resources corresponding to the system information, and broadcasts the SSB on the time-frequency resources corresponding to the SSB.

[0299] For example, the second network device sends a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a master information block (MIB) on the time-frequency resource corresponding to the SSB index. The second network device broadcasts system information on the time-frequency resource corresponding to the system information. For example, SIBx, x can be an integer greater than 1 or less than or equal to N, where N is the maximum number of SIBs defined in the current protocol.

[0300] In step 401, the second network device may first send an SSB, and then send the system information after a period of time (eg, ten milliseconds).

[0301] above Figure 3 In step 302 of the illustrated embodiment, the second network device obtains the SSB index corresponding to the one or more second beams, and the RACH time-frequency resource corresponding to each SSB index, from the resource information. The second network device monitors the channel on the RACH time-frequency resource corresponding to each SSB index to facilitate receiving information sent by a terminal device requesting access to one or more second beams managed by the second network device, for example, message 1 (Msg1) of the random access process of the terminal device.

[0302] 402. The terminal device sends message 1 to the second network device.

[0303] Message 1 includes a random access preamble.

[0304] The terminal device determines the beams included in the physical cell, the SSB index of each beam, the RACH time-frequency resources corresponding to each SSB index, and the random access preamble code set corresponding to each SSB index through the updated SIB1 broadcast by the first network device or the second network device in the above step 302. The terminal device receives the SSB of one or more second beams sent by the second network device. The terminal device determines that the RSRP (or RSRQ, or SINR) of the SSB of the third beam included in the one or more second beams is higher. Then the terminal device determines the SSB index of the third beam and selects a random access preamble code from the random access preamble code set corresponding to the SSB index. Then, the terminal device sends message 1 to the second network device on the RACH time-frequency resource corresponding to the SSB index. Message 1 is message 1 in the four-step random access process, and message 1 includes the random access preamble code.

[0305] For example, Figure 1B As shown, the second network device is NodeX. The terminal device receives the SSB and system information for beam 4 sent by NodeX. The terminal device determines that beam 4 has the best signal quality. Then, the terminal device determines the SSB index corresponding to beam 4. The terminal device determines the RACH resource and random access preamble set corresponding to the SSB index and selects a random access preamble from the random access preamble set. The terminal device then sends Message 1 to NodeX on the RACH resource corresponding to the SSB index, including the random access preamble.

[0306] 403. The second network device determines, based on the random access preamble and the mapping relationship between the random access preamble and the identifiers of one or more second beams managed by the second network device, that the terminal device requests access to the third beam.

[0307] The third beam is one of the one or more beams. The mapping relationship between the random access preamble and the identifiers of the one or more second beams includes a mapping relationship between the random access preamble and the SSBindex of the one or more second beams.

[0308] Specifically, the second network device receives message 1 from the terminal device on the RACH time-frequency resources corresponding to one or more second beams managed by the second network device. Message 1 includes a random access preamble. Then, the second network device determines whether the random access preamble belongs to the random access preamble corresponding to the one or more second beams based on the mapping relationship between the random access preamble and the SSB index of the one or more second beams. If so, the second network device determines the SSB index of the third beam that the terminal device requests to access based on the random access preamble.

[0309] It should be noted that if the second network device determines that the random access preamble code does not belong to the random access preamble code in the random access preamble code set corresponding to the beam managed by the second network device, the second network device ignores or rejects the access request of the terminal device.

[0310] For example, Figure 1BAs shown, if the first network device configures the SSBindex=3 corresponding to beam 4, the preamble index=4-15 corresponding to the SSB index corresponding to beam 4, and the RACH time-frequency resource information corresponding to beam 4 for the second network device. The second network device receives the preamble index=5 sent by the terminal device on the RACH time-frequency resource corresponding to beam 4, then the second network device can determine that the terminal device requests to access beam 4 corresponding to SSB index=3.

[0311] 404. The second network device sends message 2 to the terminal device.

[0312] If the second network device determines that the terminal device requests access to the third beam managed by the second network device, the second network device sends a message 2 (msg2) to the terminal device. Message 2 includes a temporary cell radio network temporary identifier (T-CRNTI), a time advance (TA), and the time-frequency resources (e.g., uplink grant) configured by the second network device for the terminal device to send message 3.

[0313] From the above Figure 3 As can be seen in step 302 of the illustrated embodiment, the first network device configures scheduled time-frequency resources for the second network device. The time-frequency resources configured by the second network device for the terminal device to transmit message 3 are determined by the second network device from the scheduled time-frequency resources. That is, the second network device allocates the corresponding scheduled time-frequency resources to the terminal device. The second network device selects a C-RNTI from the C-RNTI set included in the resource information allocated by the first network device to the second network device as the T-CRNTI and allocates it to the terminal device.

[0314] 405. The terminal device sends message 3 to the second network device.

[0315] Message 3 includes an RRC message, for example, an RRC setup request (RRCSetupRequest) message.

[0316] 406. The second network device processes the message 3 to obtain a processed message 3, where the processed message 3 includes an RRC establishment request message.

[0317] Before introducing step 406, the protocol stack of the terminal device, the protocol stack of the first network device, and the protocol stack of the second network device are first introduced. Figure 4B , Figure 4BThe control plane protocol stack of the terminal device, the control plane protocol stack of the second network device, and the control plane protocol stack of the first network device are respectively shown.

[0318] The control plane protocol stack of a terminal device includes the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer.

[0319] The RRC layer of the terminal device corresponds to the RRC layer of the first network device, the PDCP layer of the terminal device corresponds to the PDCP layer of the first network device, the RLC layer of the terminal device corresponds to the RLC layer of the second network device, the MAC layer of the terminal device corresponds to the MAC layer of the second network device, and the PHY layer of the terminal device corresponds to the PHY layer of the second network device.

[0320] The second network device includes an RLC layer, a MAC layer, a PHY layer, and an adaptation (Adaptation, Adapt) layer. The Adapt layer is used by the first network device and the second network device to identify the first terminal device. It can also be used to identify the data radio bearer (DRB) or signaling radio bearer (SRB) or logical channel (LCH) of the first terminal device. It can also be used to identify the beam currently accessed by the first terminal device. The name of the Adapt layer is only an example and can also be called other names, which is not limited in this application.

[0321] The Adapt layer of the second network device corresponds to the Adapt layer of the first network device, the RLC layer of the second network device corresponds to the RLC layer of the first network device, the MAC layer of the second network device corresponds to the MAC layer of the first network device, and the PHY layer of the second network device corresponds to the PHY layer of the second network device.

[0322] The first network device includes an RRC layer, a PDCP layer, an Adapt layer, an RLC layer, a MAC layer, and a PHY layer.

[0323] The Adapt layer of the first network device corresponds to the Adapt layer of the second network device. The RLC layer of the first network device corresponds to the RLC layer of the second network device. The MAC layer of the first network device corresponds to the MAC layer of the second network device. The PHY layer of the first network device corresponds to the PHY layer of the second network device.

[0324] The following combination Figure 4B Introduce step 406. After the second network device receives message 3, the second network device removes the PHY layer, MAC layer and RLC layer of message 3. It should be noted that removing a certain layer can be understood as removing the header of the PDU of that layer, thereby obtaining the service data unit (SDU) of that layer, which will not be repeated later. Then, the second network device uses message 3 without the PHY layer, MAC layer and RLC layer as the SDU of the Adapt layer, and encapsulates the Adapt layer outside the SDU, that is, adds the header of the Adapt layer, thereby forming the protocol data unit (PDU) of the Adapt layer. For example, the Adapt layer header encapsulated outside the message 3 without the PHY layer, MAC layer and RLC layer includes the C-RNTI allocated by the second network device to the terminal device (it may also be other identifiers used by the first network device and the second network device to identify the terminal device) and the identifier of the third beam, that is, the SSB index corresponding to the third beam. The third beam is the beam managed by the second network device that the terminal device requests to access. The second network device then encapsulates the RLC layer, MAC layer, and PHY layer outside the Adapt layer to obtain a processed message 3. The identifier of the third beam may also not be included in the header of the Adapt layer, but may be included as an information element (IE) in the RRC establishment request message.

[0325] 407. The second network device sends the processed message 3 to the first network device.

[0326] In order for the first network device to distinguish whether the data (including control plane messages and user plane messages) sent by the second network device comes from the second network device or is data forwarded by the second network device from other terminal devices, two possible implementations are shown below.

[0327] 1. A dedicated logical channel (LCH) is established between the first network device and the second network device. This dedicated LCH is used by the second network device to transmit messages from other terminal devices. For example, the first network device and the second network device pre-agreed that the LCH with a logical channel identifier (LCID) equal to 1 is used to transmit messages from other terminal devices. In other words, the terminal device's message includes the Adapt layer, and the first network device can determine the terminal device's message by reading the C-RNTI in the Adapt layer.

[0328] 2. The second network device adds a first indication in the RLC header, MAC header, or PHY header of the message to indicate whether the message has an Adapt layer. When the first indication indicates that the message has an Adapt layer, the first network device can determine which terminal device the message belongs to by reading the Adapt layer of the message.

[0329] After receiving the processed message 3 , the first network device can identify that the processed message 3 is a message from the terminal device in any of the following ways: Then, the first network device parses the processed message 3 to obtain the RRC establishment request message included in the original message 3 .

[0330] 408. The first network device sends message 4 to the second network device. Message 4 includes an RRC establishment response message sent by the first network device to the terminal device.

[0331] It is understandable that message 4 is an RRC setup response message that encapsulates messages obtained by the PDCP layer, Adapt layer, RLC layer, MAC layer, and PHY layer. The encapsulation of the Adapt layer includes the terminal device's identifier in the Adapt layer header. Optionally, the Adapt layer header also includes: an SRB ID or LCID. The SRB ID or LCID is used by the first network device to indicate to the second network device which channel the RRC setup response message should be sent to the terminal device.

[0332] 409. The second network device processes message 4 to obtain a processed message 4, where the processed message 4 includes an RRC establishment response message.

[0333] After receiving Message 4 sent by the first network device, the second network device removes the PHY layer, MAC layer, and RLC layer encapsulated outside Message 4. The second network device then reads the terminal device identifier, such as the C-RNTI, from the Adapt layer header. Optionally, the second network device reads the SRB ID or LCID from the Adapt layer header. The second network device then removes the Adapt layer from Message 4, removing the encapsulated PHY layer, MAC layer, and RLC layer, and encapsulates the RLC layer, MAC layer, and PHY layer outside, obtaining the processed Message 4.

[0334] 410. The second network device sends the processed message 4 to the terminal device. The processed message 4 includes an RRC establishment response message.

[0335] The first network device forwards the RRC establishment response message to the terminal device via the second network device, thereby enabling the terminal device to establish an RRC connection to the first network device. For example, the second network device sends the processed message 4 to the terminal device via the channel indicated by the SRB ID or LCID.

[0336] In this embodiment, the terminal device may send uplink data to the first network device via the second network device. Optionally, this embodiment further includes steps 411 to 413, and steps 411 to 413 are performed after step 410.

[0337] 411. The terminal device sends the encapsulated first data to the second network device.

[0338] Before introducing step 411, the user plane protocol stack of the terminal device, the user plane protocol stack of the second network device, and the user plane protocol stack of the first network device are introduced. Figure 4C , Figure 4C A schematic diagram of a user plane protocol stack of a terminal device, a user plane protocol stack of a second network device, and a user plane protocol stack of a first network device.

[0339] The terminal device includes a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. The second network device includes a PHY layer, a MAC layer, an RLC layer, and an Adapt layer. The first network device includes a PHY layer, a MAC layer, an RLC layer, an Adapt layer, a PDCP layer, and an SDAP layer. The Adapt layer is used by the first network device and the second network device to identify the first terminal device, and can also be used to identify the data radio bearer (DRB) or signaling radio bearer (SRB) or logical channel (LCH) of the first terminal device, and can also be used to identify the beam currently accessed by the first terminal device.

[0340] The PHY layer of the terminal device corresponds to the PHY layer of the second network device, the MAC layer of the terminal device corresponds to the MAC layer of the second network device, the RLC layer of the terminal device corresponds to the RLC layer of the second network device, the PDCP layer of the terminal device corresponds to the PDCP layer of the first network device, and the SDAP layer of the terminal device corresponds to the SDAP layer of the first network device.

[0341] The PHY layer of the second network device corresponds to the PHY layer of the first network device, the MAC layer of the second network device corresponds to the MAC layer of the first network device, the RLC layer of the second network device corresponds to the RLC layer of the first network device, and the Adapt layer of the second network device corresponds to the Adapt layer of the first network device.

[0342] The encapsulated first data refers to the data obtained by the first terminal device by encapsulating the SDAP layer, PDCP layer, RLC layer, MAC layer and PHY layer outside the first data.

[0343] It should be noted that before step 411, the second network device can configure uplink resources for the first terminal device to send data. The specific configuration method is similar to the method in which existing access network devices configure uplink resources for terminal devices, and will not be described in detail herein.

[0344] 412. The second network device processes the encapsulated first data to obtain processed first data.

[0345] The following combination Figure 4C Introduce step 411. After the second network device receives the encapsulated first data, the second network device removes the PHY layer, MAC layer, and RLC layer of the encapsulated first data. Then, the second network device encapsulates the Adapt layer outside the first data after the PHY layer, MAC layer, and RLC layer are removed. For example, the Adapt layer encapsulated outside the first data after the PHY layer, MAC layer, and RLC layer are removed contains the C-RNTI allocated by the second network device to the terminal device (it may also be other identifiers used by the first network device and the second network device to identify the terminal device). The second network device then encapsulates the RLC layer, MAC layer, and PHY layer outside the Adapt layer to obtain the processed first data.

[0346] 413. The second network device sends the processed first data to the first network device.

[0347] It can be seen from the above steps 411 to 413 that the terminal device forwards the first data to the first network device through the second network device, thereby realizing uplink data transmission between the terminal device and the first network device.

[0348] In this embodiment, the first network device may send downlink data to the terminal device. Optionally, this embodiment further includes steps 414 to 416, and steps 414 to 416 are performed after step 410.

[0349] 414. The first network device sends the encapsulated second data to the second network device.

[0350] The encapsulated second data refers to the data obtained by the first network device by encapsulating the SDAP layer, PDCP layer, Adapt layer, RLC layer, MAC layer, and PHY layer outside the second data. The Adapt layer in the encapsulated second data includes the identifier of the first terminal device. For example, the C-RNTI allocated by the second network device to the terminal device (it may also be other identifiers used by the first network device and the second network device to identify the terminal device).

[0351] 415. The second network device processes the encapsulated second data to obtain processed second data.

[0352] After the second network device receives the encapsulated second data, it removes the PHY layer, MAC layer, and RLC layer of the encapsulated second data. The second network device then reads the terminal device identifier in the Adapt layer of the second data from which the PHY layer, MAC layer, and RLC layer have been removed, thereby determining the terminal device. Optionally, the second network device reads the DRB identifier or LCID from the Adapt layer to determine the DRB or LCH of the terminal device. Next, the second network device removes the Adapt layer of the second data and then externally encapsulates the RLC layer, MAC layer, and PHY layer to obtain the processed second data.

[0353] 416. The second network device sends the processed second data to the terminal device.

[0354] For example, the second network device sends the processed second data to the terminal device through the DRB indicated by the DRB identifier of the Adapt layer; or, the second network device sends the processed second data to the terminal device through the LCH indicated by the LCID of the Adapt layer.

[0355] It can be seen from steps 413 to 416 that the first network device forwards the second data to the terminal device through the second network device, thereby realizing downlink data transmission between the terminal device and the first network device.

[0356] The following combination Figure 5 The embodiment shown shows the process in which the second network device provides access services to the terminal device during the two-step random access process. Figure 5 , Figure 5 This is another embodiment diagram of the communication method of the present application embodiment. Figure 5 , the communication method comprises:

[0357] 501. The second network device sends SSB and system information to the terminal device.

[0358] Step 501 and the aforementioned Figure 4A Step 401 of the embodiment shown is similar, please refer to the aforementioned Figure 4A The relevant introduction of step 401 of the illustrated embodiment will not be repeated here.

[0359] 502. The terminal device sends message A to the second network device.

[0360] Message A includes a random access preamble and an RRC establishment request message.

[0361] 503. The second network device determines, based on the random access preamble and the mapping relationship between the random access preamble and the identifiers of one or more second beams managed by the second network device, that the terminal device requests to access the third beam.

[0362] Step 503 is the same as the above Figure 4A In the embodiment shown, step 403 is similar, please refer to the aforementioned Figure 4A The relevant introduction of step 403 in the illustrated embodiment will not be repeated here.

[0363] 504. The second network device processes the message A to obtain a processed message A, where the processed message A includes an RRC establishment request message.

[0364] Combined with the above Figure 4A Step 406 in the embodiment shown. The second network device removes the PHY layer, MAC layer and RLC layer of the message A. Then, the second network uses the message A with the PHY layer, MAC layer and RLC layer removed as the SDU of the Adapt layer, and encapsulates the Adapt layer outside the SDU, that is, adds the header of the Adapt layer, thereby forming the PDU of the Adapt layer. For example, the Adapt layer header encapsulated outside the message A with the PHY layer, MAC layer and RLC layer removed contains the C-RNTI allocated by the second network device to the terminal device. Optionally, the Adapt layer header encapsulated outside the message A with the PHY layer, MAC layer and RLC layer removed by the second network device also contains the identifier of the third beam. The second network device then encapsulates the RLC layer, MAC layer and PHY layer outside the Adapt layer to obtain the processed message A, and the processed message A includes the RRC establishment request message.

[0365] It should be noted that the first beam identifier may not be included in the header of the Adapt layer, but may be included as an information element in the RRC establishment request message.

[0366] 505. The second network device sends the processed message A to the first network device.

[0367] Step 505 is the same as the above Figure 4A Step 407 in the embodiment shown is similar, please refer to the aforementioned Figure 4A The relevant introduction of step 407 in the illustrated embodiment will not be repeated here.

[0368] 506. The first network device sends a message B to the second network device, where the message B includes an RRC establishment response message.

[0369] It is understood that message B is an RRC setup response message encapsulated with the PDCP layer, Adapt layer, RLC layer, MAC layer, and PHY layer. The Adapt layer includes the terminal device identifier. Optionally, the Adapt layer also includes an SRB ID or LCID.

[0370] 507. The second network device processes message B to obtain a processed message B, where the processed message B includes an RRC establishment response message.

[0371] After receiving message B from the first network device, the second network device removes the PHY layer, MAC layer, and RLC layer encapsulated outside message B. The second network device then reads the terminal device identifier from the Adapt layer header. For example, the C-RNTI. Optionally, the second network device reads the SRB ID or LCID from the Adapt layer header. The second network device then removes the Adapt layer from message B, removing the PHY layer, MAC layer, and RLC layer encapsulation, and encapsulates the RLC layer, MAC layer, and PHY layer outside, obtaining the processed message B.

[0372] 508. The second network device sends the processed message B to the terminal device.

[0373] The first network device sends an RRC establishment response message to the terminal device through the second network device, thereby enabling the terminal device to establish an RRC connection to the first network device.

[0374] It should be noted that in Figure 5 After the two-step random access process shown, data can be transmitted between the first network device and the terminal device. For example, uplink data transmission, or downlink data transmission. The specific process of uplink data transmission between the first network device and the terminal device is the same as that described above. Figure 4A The steps 411 to 413 of the embodiment shown are similar. The process of downlink data transmission between the first network device and the terminal device is the same as the above Figure 4A Steps 414 to 416 of the embodiment shown are similar. Figure 4A The relevant introduction of steps 411 to 416 in the illustrated embodiment will not be repeated here.

[0375] above Figure 4A and Figure 5 The illustrated embodiment shows the process of the second network device providing access services, resource scheduling and data forwarding for the terminal device. Through the technical solution of the embodiment of the present application, it can be known that the resource information of one or more second beams is configured for the second network device by the first network device. Thereby, the second network device manages one or more second beams of the physical cell. The second network device is responsible for providing access services and resource scheduling for the terminal device requesting access to the one or more second beams. Since the one or more second beams managed by the second network device belong to the same physical cell as the one or more first beams managed by the first network device. That is, the second network does not manage a new physical cell. The PCI of the physical cell of the second network device is the same as the PCI of the physical cell of the first network device, so there is no need to allocate a new PCI. This avoids the problem of PCI conflicts caused by a large number of deployed sites being easily caused by one PCI being shared by different adjacent cells.

[0376] The following takes the first terminal device as an example to introduce the process of the first network device performing beam management on the first terminal device.

[0377] 1. Beam measurement configuration and reporting of the first terminal device.

[0378] The first network device sends an RRC reconfiguration message to the first terminal device, where the RRC reconfiguration message includes a CSI measurement configuration CSI-MeasConfig. The CSI measurement configuration includes a CSI resource configuration (CSI-ResourceConfig), a CSI reporting configuration (CSI-ReportConfig), a trigger status, and the like.

[0379] Among them, the CSI resource configuration may include SSB resource information and CSI-RS resource information.

[0380] For example, SSB resource information includes the SSB resource identifier (SS / PBCH Block Resource Indicator, SSBRI) or SSB index, the frequency corresponding to the SSB, the SSB subcarrier spacing, the SSB period, the SSB measurement timing configuration (SSB-MTC), the system frame number (SFN) offset, etc. For example, CSI-RS resource information includes the frequency corresponding to the CSI-RS, the BWP corresponding to the CSI-RS, the CSI-RS resource identifier, the CSI-RS resource mapping, the CSI-RS timing configuration including the slot offset and period, the CSI-RS density, etc.

[0381] The CSI reporting configuration may include an L1-RSRP parameter and an SSB index; or, ReportConfig may include an L1-RSRP parameter and a CSI-RS resource indicator (CSI-RS resource indicator, CRI).

[0382] The CSI measurement configuration mainly includes SSB frequency, SSB subcarrier spacing, SSB measurement time configuration (ie, SSB-MTC), CSI-RS frequency, CSI-RS resource identifier, CSI-RS time slot configuration, and CSI-RS associated SSB identifier.

[0383] Then, the first terminal device reports the CSI measurement report through uplink control information (UCI). For example, the measurement report includes SSBRI, and L1-RSRP corresponding to SSBRI (or, differential RSRP corresponding to SSBRI; or, L1-SINR corresponding to SSBRI); or, includes L1-RSRP or differential RSRP or L1-SINR corresponding to CRI.

[0384] 2. Transmission configuration indicator state (TCIstate) configuration and notification.

[0385] TCI state: In 3GPP Release 15 (R15), for each physical channel or signal, the network can use different signaling to provide beam instructions to the terminal device, instructing the terminal device on how to receive downlink physical channels or signals and how to transmit uplink physical channels or signals. The TCI indication determines the corresponding beam, namely the SSB index or CSI-RS index.

[0386] The first network device configures a TCI state set for the first terminal device via an RRC reconfiguration message. For example, TCI state subset 1 corresponding to the control resource set (CORESET) is provided in ControlResourceSet (CORESET can be understood as part of the PDCCH), and TCI state subset 2 corresponding to the PDSCH is included in PDSCH-Config.

[0387] Each TCI state has a corresponding TCI state ID and Quasi Co-location (QCL) information. The QCL information includes the cell ID, BWP ID, reference signal ID (CSI-RS resource ID or SSB index), and Quasi Co-location (QCL) type. It is important to note that determining the TCI also determines the CSI-RS resource ID or SSB index, which is equivalent to determining the beam.

[0388] Then the first network device notifies the first terminal device of 1 TCIstate ID corresponding to CORESET (the TCI state ID is selected by the first network device from TCI state subset 1) through a MAC layer control instruction (for example, a media access control-control element (MAC CE)), and notifies the first terminal device of up to 8 TCI state IDs corresponding to PDSCH (the TCI state ID is selected by the first network device from TCI state subset 2) through a MAC layer control instruction. Finally, the first network device gives 1 TCI state ID corresponding to PDSCH (the TCI state ID is selected by the first network device from a maximum of 8 TCI state IDs) through downlink control information (DCI). In the case where the first terminal device accesses the second network device, the second network device sends TCI state-related indications to the first terminal device through MAC CE or DCI.

[0389] 3. Management of beam failure of the first terminal device.

[0390] The first network device configures the radio link monitoring configuration (RadioLinkMonitoringConfig) and the beam failure recovery (BFR) configuration (BeamFailureRecoveryConfig) for the first terminal device. When the first terminal device detects a beam failure, the first terminal device initiates BFR based on the parameters in the beam failure recovery configuration configured by the first network device for the first terminal device. The random access process is triggered during the BFR process.

[0391] The beam failure recovery configuration includes the SSB index (or CSI-RS resource index), preamble index, and RACH-ConfigGeneric corresponding to at least one beam in the random access process triggered by BFR. The first terminal device can determine the location information of the RACH time-frequency resource based on RACH-ConfigGeneric.

[0392] For the Contention Free Random Access (CFRA) method, because the network side cannot determine which beam the first terminal device will eventually access to perform beam failure recovery, the beam failure recovery configuration includes at least one beam corresponding identifier, corresponding RACH time-frequency resources, and corresponding preamble index.

[0393] For the contention-based random access (CBRA) method, the network side does not include a random access preamble code dedicated to a certain beam for the first terminal device in the beam failure recovery configuration. For the CBRA method, the first terminal device selects the random access preamble code corresponding to the beam that the first terminal device wants to access based on the mapping relationship between the beam identifier and the random access preamble code. Then, the first terminal device sends the random access preamble code in message 1 of the four-step random access, or the first terminal device sends the random access preamble code in message A of the two-step random access. The mapping relationship between the beam identifier and the random access preamble code can be the broadcast of the network device accessed by the first terminal device before the beam failure recovery occurs. For example, the mapping relationship between the SSB index and the preamble index set.

[0394] For the CFRA method, the first network device can determine which terminal device re-accesses the network through the RACH process based on the location information of the time-frequency resource when the first terminal device initiates the random access process and the random access preamble code sent by the first terminal device on the time-frequency resource.

[0395] For the CBRA mode, the first network device can determine that the first terminal device re-accesses the network through the RACH process based on the identifier of the first terminal device carried by the first terminal device in msgA or msg3.

[0396] In the solution of introducing the second network device in the embodiment of the present application, the aforementioned Figure 3 、 Figure 4A and Figure 5 As can be seen from the illustrated embodiment, when a first terminal device is within the coverage area of ​​a first beam managed by a second network device, the second network device will be responsible for processing the PHY layer, MAC layer, and RLC layer of the first terminal device's data. In other words, the second network device receives uplink control information (UCI) from the first terminal device and determines whether the first terminal device should change beams based on the UCI.

[0397] Then, the second network device should determine which TCI states the first network device has configured for the first terminal device. For example, the first network device will inform the second network device of basic configuration information such as the ControlResourceSet configured for the CORESET of the first terminal device and the PDSCH-Config configured for the PDSCH of the first terminal device. The second network device subsequently determines which TCI state in TCI state set 1 is active (for CORESET), and determines which TCI states in TCI state set 2 are active (for PDSCH), and notifies the first terminal device of the above TCI state through MAC CE. In addition, the second network device can also indicate one or two TCI states for PDSCH to the first terminal device through DCI.

[0398] Alternatively, the second network device configures the ControlResourceSet configured by the CORESET for the first terminal device and the PDSCH-Config for the PDSCH of the first terminal device; then, the second network device sends basic configuration information such as the ControlResourceSet configured by the second network device for the first terminal device and the PDSCH-Config for the PDSCH of the first terminal device to the first network device, and the first network device informs the first terminal device through an RRC message.

[0399] The following describes some possible scenarios of the embodiments of the present application in conjunction with specific embodiments.

[0400] Scenario 1: A first terminal device is within the signal coverage of a third beam managed by a second network device. This is a beam switch scenario in which the first terminal device switches from the third beam to the fourth beam. The third beam is one of one or more second beams managed by the second network device. The fourth beam is one of one or more first beams managed by the first network device.

[0401] The following combination Figure 6A The embodiment scenario shown is 1. Please refer to Figure 6A , Figure 6A This is another embodiment diagram of the communication method of the present application embodiment. Figure 6A , the communication method comprises:

[0402] 601. The first terminal device sends an L1 measurement report to the second network device.

[0403] The L1 measurement report includes: channel quality information (CQI), rank indication (RI), precoding matrix indication (PMI), CRI, SSBRI, layer indication (LI), L1-RSRP or L1-SINR, etc. measured by the first terminal device.

[0404] Specifically, the first terminal device reports the L1 measurement report of the first terminal device to the second network device through uplink control information.

[0405] For example, Figure 6B As shown, the physical cell includes beams 1 to 4. The gNB manages beams 1 to 3, and NodeX manages beam 4. UE1 is within the signal coverage of beam 4 managed by NodeX and accesses beam 4. UE1 measures the signal strength of the beam sent by the gNB and the signal strength of the beam sent by NodeX, generating an L1 measurement report. UE1 then reports the L1 measurement report to NodeX, allowing NodeX to determine which beam has higher signal quality and is more suitable for serving UE1.

[0406] 602. The second network device determines a fourth beam according to the L1 measurement report.

[0407] The fourth beam is one of the one or more first beams managed by the first network device.

[0408] For example, Figure 6BAs shown, NodeX determines based on the L1 measurement report that beam 2 has the best signal quality and is more suitable for serving the first terminal device. NodeX then decides to use beam 2 to serve UE1.

[0409] 603. The second network device sends an identifier of the fourth beam to the first terminal device.

[0410] The identifier of the fourth beam includes the SSB index corresponding to the fourth beam or the CSI-RS index corresponding to the fourth beam.

[0411] Optionally, the identifier of the fourth beam includes a TCI state ID corresponding to the fourth beam. That is, the second network device indicates the TCI through the TCI state ID, and the first terminal device determines the TCI based on the TCI state ID, and the TCI indicates the fourth beam. For example, the TCI includes the SSB index corresponding to the fourth beam or the CSI-RS index corresponding to the fourth beam. For the relevant introduction to TCI, please refer to the previous article, and you will know that the first terminal device can determine which beam to switch to through TCI.

[0412] Specifically, the second network device sends the identifier of the fourth beam to the first terminal device through the downlink control information DCI. For example, the TCI state related to PDSCH. For example, NodeX sends the TCI state or SSB index or CSI-RS index corresponding to beam 2 to UE1 through DCI. Alternatively, the second network device sends the identifier of the fourth beam to the first terminal device through MAC CE. For example, the TCI state related to COREST. For example, NodeX sends the TCI state or SSB index or CSI-RS index corresponding to beam 2 to UE through MAC CE.

[0413] 604. The first terminal device switches from the third beam to the fourth beam.

[0414] The first terminal device determines the fourth beam according to the identifier of the fourth beam; then, the first terminal device switches the beam from the third beam to the fourth beam.

[0415] For example, Figure 6B As shown in the figure, UE1 initially accesses beam 4 managed by NodeX. UE1 performs beam switching, switching from beam 4 to beam 2 managed by gNB.

[0416] 605. The second network device sends the C-RNTI of the first terminal device and the identifier of the fourth beam to the first network device.

[0417] The second network device determines that the fourth beam is used to provide services for the first terminal device. The second network device may send the C-RNTI of the first terminal device and the identifier of the fourth beam to the first network device to notify the first network device to provide services for the first terminal device switched from the third beam to the fourth beam.

[0418] It should be noted that there is no fixed order for executing step 603 and step 605. For example, step 603 may be executed first, and then step 605; or step 605 may be executed first, and then step 603; or, step 603 and step 605 may be executed simultaneously depending on the circumstances, and this application does not limit this.

[0419] For example, Figure 6B As shown, the fourth beam is beam 2. NodeX forwards the C-RNTI allocated by NodeX to the first terminal device, the TCI state ID corresponding to beam 2, the buffer status report (BSR), and other information to the gNB.

[0420] In this embodiment, the second network device further sends data transmission status information of the first terminal device to the first network device. The data transmission status information includes at least one of the following:

[0421] Sequence information of the data units that have been sent but for which no feedback information has been received, data transmission timer, hybrid automatic repeat request HARQ process number, new data indication, transmission block size, redundancy version, process time information corresponding to the HARQ process number, data unit transmission confirmation information of the HARQ process, confirmation information of the data unit, maximum sending state variable, maximum receiving state variable, sending state variable, receiving state variable and transmission window.

[0422] Optionally, the data transmission timer may be a reordering timer of an RLC or MAC, or a HARQ round trip time (RTT) timer, etc., which is not specifically limited in this application. In addition, the data transmission timer also includes some sending variables and receiving variables of the RLC layer. For example, TX_Next_Ack, TX_Next, RX_Next, POLL_SN, RETX_COUNT, etc. For details, please refer to the relevant introduction in Section 7.1 and Section 7.3 of the communication standard 3GPP TS38.322 v16.1.0.

[0423] The first network device can determine the data transmission status information of the first terminal device so that the first network device can provide services to the first terminal device, thereby enabling the first terminal device to continue to transmit data under the scheduling of the first network device in a beam switching scenario of the first terminal device.

[0424] 606. The first network device provides communication services for the first terminal device according to the C-RNTI of the first terminal device and the identifier of the fourth beam.

[0425] In step 604, the first terminal device switches from the third beam to the fourth beam. After receiving the C-RNTI of the first terminal device and the identifier of the fourth beam, the first network device provides communication services to the first terminal device, such as resource scheduling and data transmission. This allows the first terminal device to continue data transmission under the scheduling of the first network device in the beam switching scenario.

[0426] In an embodiment of the present application, when the first terminal device is within the signal coverage of the third beam managed by the second network device, the second network device determines that the fourth beam provides services for the first terminal device based on the L1 measurement report of the first terminal device. The second network device sends the identifier of the fourth beam to the first terminal device so that the first terminal device can switch from the third beam to the fourth beam. Then, the second network device sends the C-RNTI and the identifier of the fourth beam allocated by the second network device to the first terminal device to the first network device. In this way, the first network device can provide scheduling services for the first terminal device, so that in the beam switching scenario of the first terminal device, the first terminal device continues to transmit data under the scheduling of the first network device.

[0427] Scenario 2: The first terminal device originally experienced a beam failure within the signal coverage of the third beam managed by the second network device, and then moved to the signal coverage of the fourth beam managed by the first network device. The first terminal device initiated beam failure recovery (BFR) to the first network device to enable the first network device to continue to provide services to the first terminal device.

[0428] First combine Figure 7A The embodiment shown introduces scenario 2 based on the CFRA method and the four-step random access process. Figure 7B The illustrated embodiment introduces scenario 2 based on the CFRA method and the four-step random access process.

[0429] See also Figure 7A , Figure 7A This is another embodiment diagram of the communication method of the present application embodiment. Figure 7A , the communication method includes:

[0430] 701. The first terminal device sends message 1 to the first network device, where message 1 includes a random access preamble code.

[0431] The first terminal device quickly moves from the signal coverage of the third beam managed by the second network device to the signal coverage of the fourth beam managed by the first network device. The PHY layer of the first terminal device detects the beam failure and indicates a candidate beam to the MAC layer of the first terminal device, which in this embodiment is referred to as the fourth beam.

[0432] Specifically, the PHY layer of the first terminal device performs a beam search process. During the beam search process, the PHY layer of the first terminal device records the signal strength corresponding to the received beams and selects the beam with the largest signal strength as a candidate beam. The PHY layer of the first terminal device then notifies the MAC layer of the first terminal device of the identifier of the candidate beam.

[0433] Then, the MAC layer of the first terminal device determines the RACH time-frequency resources and random access preamble code corresponding to the fourth beam according to the beam failure recovery configuration. For information about the beam failure recovery configuration, please refer to the aforementioned related introduction. The MAC layer of the first terminal device indicates the RACH time-frequency resources and the corresponding random access preamble code corresponding to the fourth beam of the first terminal device to the PHY layer of the first terminal device. The first terminal device sends message 1 to the first network device on the RACH time-frequency resources corresponding to the second fourth beam, and message 1 includes a random access preamble code.

[0434] 702. The first network device determines, based on the random access preamble code of message 1, that the first terminal device requests beam failure recovery in the fourth beam.

[0435] It can be seen from the aforementioned configuration of beam failure recovery and the CFRA method that the first network device can uniquely determine which terminal device is requesting to re-access the network through the RACH process through the random access preamble sent by the first terminal device. First, the first network device determines that the random access preamble of message 1 belongs to the random access preamble for beam failure recovery of the first terminal device based on the relationship between each terminal device and the allocated random access preamble for beam failure recovery, that is, the first terminal device is applying for beam failure recovery. Then, the first network device determines that it is the first terminal device requesting beam failure recovery in the fourth beam based on the mapping relationship between the beam identifier for beam recovery failure of the first terminal device and the random access preamble for beam failure recovery of the first terminal device.

[0436] For example, Figure 7B As shown in the figure, NodeX manages beam 4, and the gNB manages beams 1 through 3. UE1 accesses beam 4 and quickly moves from the signal coverage of beam 4 to the signal coverage of beam 2. UE1 detects a beam failure and requests beam failure recovery from the gNB, allowing the gNB to determine whether UE1 has re-accessed the network through the RACH procedure.

[0437] 703. The first network device sends a message 2 to the first terminal device, where the message 2 includes a random access response message, for example, parameters such as a time advance (TA).

[0438] After the first network device receives message 1 in step 701, the first network device determines, in conjunction with step 702, that the first terminal device requests to re-access the network through a RACH procedure. The first network device may send a random access response message to the first terminal device via message 2 to inform the first terminal device that the beam recovery request is successful, so that the first terminal device can perform data transmission under the scheduling of the first network device.

[0439] 704. The first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0440] From the above Figure 4A As can be seen in the illustrated embodiment, a first terminal device accesses a third beam managed by a second network device. The first network device stores the context of the first terminal device during the first terminal device's random access process. In step 703, the first network device queries the context of the first terminal device and determines that the second network device was originally responsible for scheduling the first terminal device and which beam the first terminal device originally accessed. The first network device notifies the second network device that the first terminal device is being scheduled by the first network device, thereby instructing the second network device to stop scheduling the first terminal device.

[0441] Optionally, the information for instructing the second network device to stop scheduling the first terminal device is a stop transmission user equipment identifier (StopTransmissionUEID), which includes the C-RNTI of the first terminal device. The first network device instructs the second network device to stop scheduling the first terminal device through the StopTransmissionUEID.

[0442] 705. The second network device stops scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0443] For example, NodeX receives the indication information sent by gNB and stops scheduling UE1 according to the indication information.

[0444] For example, NodeX receives the StopTransmissionUEID sent by the gNB, which includes the C-RNTI of the first terminal device; then, NodeX stops scheduling UE1 according to the StopTransmissionUEID.

[0445] See also Figure 7C , Figure 7C This is another embodiment diagram of the communication method of the present application, based on the CBRA method and the four-step random access process. Figure 7C , the communication methods include:

[0446] 706. The first terminal device sends message 1 to the first network device, where message 1 includes a random access preamble code.

[0447] The MAC layer of the first terminal device determines the RACH time-frequency resources corresponding to the fourth beam based on the beam failure recovery configuration. The first terminal device selects the random access preamble based on the mapping relationship between the beam identifier broadcast by the access network device and the random access preamble. The MAC layer of the first terminal device indicates the RACH time-frequency resources and the corresponding random access preamble corresponding to the fourth beam of the first terminal device to the PHY layer of the first terminal device. Then, the first terminal device sends message 1 to the first network device on the RACH time-frequency resources corresponding to the fourth beam, and message 1 includes the random access preamble.

[0448] 707. The first network device determines, based on the random access preamble code, that a terminal device requests to access the fourth beam.

[0449] From the above introduction to the CBRA method, it can be seen that the random access preamble corresponding to the beam is used for random access for multiple terminal devices to compete for access. Therefore, the first network device determines that the terminal device requests access to the second beam based on the random access preamble of message 1 and the mapping relationship between the beam identifier and the random access preamble.

[0450] 708. The first network device sends message 2 to the first terminal device.

[0451] 709. The first terminal device sends message 3 to the first network device. Message 3 includes the identifier of the first terminal device.

[0452] The identifier of the first terminal device is the identifier of the first terminal device to which the first terminal device was assigned before the beam failure occurred.

[0453] 710. The first network device determines, based on the identifier of the first terminal device, that the first terminal device requests access to the second beam.

[0454] Since the random access preamble corresponding to the second beam is used by multiple terminal devices for competition, the first network device can determine that it is the first terminal device that applies to access the fourth beam through the identifier of the first terminal device included in message 3.

[0455] 711. The first network device sends message 4 to the first terminal device.

[0456] The first network device can inform the first terminal device of the success of random access through message 4, so that the first terminal device can perform data transmission under the scheduling of the first network device.

[0457] 712. The first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0458] 713. The second network device stops scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0459] Steps 712 to 713 are the same as those mentioned above. Figure 7A Steps 704 to 705 in the embodiment shown are similar, please refer to the aforementioned Figure 7A The relevant introduction of steps 704 to 705 in the illustrated embodiment will not be repeated here.

[0460] The following combination Figure 8 The illustrated embodiment introduces scenario 2 based on the CBRA method and the two-step random access process.

[0461] See also Figure 8 , Figure 8 This is another embodiment diagram of the communication method of the present application embodiment. Figure 8 , the communication method comprises:

[0462] 801. A first terminal device sends a message A to a first network device. The message A includes a random access request and an identifier of the first terminal device.

[0463] The first terminal device quickly moves from the signal coverage of the third beam managed by the second network device to the signal coverage of the fourth beam managed by the first network device. The PHY layer of the first terminal device detects the beam failure and indicates a candidate beam to the MAC layer of the first terminal device, which in this embodiment is referred to as the fourth beam.

[0464] The MAC layer of the first terminal device determines the RACH time-frequency resources based on the beam failure recovery configuration. For more information about the beam failure recovery configuration, please refer to the aforementioned related introduction. The MAC layer of the first terminal device indicates the RACH time-frequency resources of the first terminal device to the PHY layer. Then, the first terminal device sends message A to the first network device on the RACH resources corresponding to the fourth beam. Message A includes the random access preamble corresponding to the fourth beam and the identifier of the first terminal device.

[0465] For the CBRA method, the random access preamble code corresponding to the fourth beam is not specially configured for the first terminal device in the beam failure configuration, but is shared with other terminal devices. For example, one of the random access preamble code sets corresponding to the fourth beam obtained from the system information. Then the first network device can determine through the identifier of the first terminal device in message A that it is the first terminal device that requests to apply for beam failure recovery in the fourth beam. That is, the first terminal device requests beam failure recovery from the first network device through message A. In this way, the second network device can determine that the first terminal device requests to re-access the network through the RACH process.

[0466] 802. The first network device determines, based on the identifier of the first terminal device and the random access preamble code in message A, that it is the first terminal device that requests to access the fourth beam.

[0467] Specifically, the first network device determines that the first terminal device has re-accessed the network through a RACH process based on the identifier of the first terminal device included in msgA and the absence of any RRC message found in msgA. Furthermore, the first network device determines that the first terminal device requests access to the fourth beam based on a mapping relationship between the beam identifier and the random access preamble.

[0468] 803. The first network device sends a message B to the first terminal device. The message B is a random access response message, for example, parameters such as time advance (TA).

[0469] After the first network device receives message A in step 801, the first network device determines, in conjunction with step 802 above, that the first terminal device requests to re-access the network through the RACH process. The first network device may send a random access response message to the first terminal device via message B to inform the first terminal device that the beam recovery request is successful, so that the first terminal device can perform data transmission under the scheduling of the first network device.

[0470] 804. The first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0471] 805. The second network device stops scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0472] Steps 804 to 805 are the same as those mentioned above. Figure 7A Steps 704 to 705 in the embodiment shown are similar, please refer to the aforementioned Figure 7A The relevant introduction of steps 704 to 705 in the illustrated embodiment will not be repeated here.

[0473] In an embodiment of the present application, the first terminal device moves from the signal coverage of the third beam managed by the second network device to the signal coverage of the fourth beam managed by the first network device. The first terminal device initiates a beam failure recovery request to the first network device to enable the first network device to provide services to the first terminal device, thereby enabling the first terminal device to continue to transmit data under the scheduling of the first network device in the scenario where a beam failure occurs in the first terminal device. In addition, the first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device, so that the second network device can stop scheduling the first terminal device, so that the first network device can provide communication services to the first terminal device.

[0474] Scenario three: The first terminal device is within the signal coverage of the third beam managed by the second network device, and the first terminal device switches from the third beam to the fifth beam, a beam switching scenario.

[0475] Among them, the fifth beam is a beam managed by the third network device. The third network device first accesses the physical cell of the first network device as a terminal device. The third network device is an access point type device. Then, the first network device configures the resource information of the fifth beam of the physical cell for the third network device and sends the resource information of the fifth beam to the third network device. The resource information of the fifth beam is used by the third network device to manage the fifth beam of the physical cell. That is, the fifth beam managed by the third network device and the one or more first beams managed by the first network device belong to the same physical cell. That is, the PCI of the physical cell used by the third network device is the same as the PCI of the physical cell used by the first network device. The system information of the physical cell broadcast by the third network device is the same as the system information of the physical cell broadcast by the first network device.

[0476] The following combination Figure 9A The embodiment shown introduces scenario three. Figure 9A , Figure 9A This is another embodiment diagram of the communication method of the present application embodiment. Figure 9A , the communication method includes:

[0477] 901. The first terminal device sends an L1 measurement report to the second network device.

[0478] 902. The second network device determines a fifth beam according to the L1 measurement report.

[0479] 903. The second network device sends an identifier of the fifth beam to the first terminal device.

[0480] 904. The first terminal device switches from the third beam to the fifth beam.

[0481] Steps 901 to 904 are the same as those mentioned above. Figure 6A Steps 601 to 604 of the embodiment shown are similar, please refer to the aforementioned Figure 6A The relevant introduction of steps 601 to 604 of the illustrated embodiment will not be repeated here.

[0482] 905. The second network device sends the C-RNTI of the first terminal device and the identifier of the fifth beam to the first network device.

[0483] There is no fixed execution order between step 903 and step 905. Step 903 may be executed first, and then step 905; or step 905 may be executed first, and then step 903; or, step 903 and step 905 may be executed simultaneously depending on the situation.

[0484] 906. The first network device sends the C-RNTI of the first terminal device and the identifier of the fifth beam to the third network device.

[0485] In steps 905 and 906 above, the fifth beam is managed by the third network device, which is a device connected to the first network device. The second network device can send the C-RNTI of the first terminal device and the identifier of the fifth beam to the first network device. The first network device then sends the C-RNTI of the first terminal device and the identifier of the fifth beam to the third network device. This allows the third network device to determine that after the first terminal device switches to the fifth beam, the third network device will provide scheduling services for the first terminal device.

[0486] For example, Figure 9BAs shown, UE1 accesses beam 4 of NodeX1. NodeX1 decides to switch the first terminal device to beam 5 managed by NodeX2 based on the L1 measurement report of UE1. NodeX1 indicates the identifier of beam 5 to UE1 so that UE1 can switch from beam 4 to beam 5. NodeX1 sends the C-RNTI of the first terminal device, the identifier of beam 5 (for example, the corresponding TCIstate ID or SSB index or CSI-RS index), and BSR and other information to the gNB. Then, the gNB sends the C-RNTI of the first terminal device, the identifier of beam 5 (for example, the TCI state ID corresponding to beam 5, or the SSBindex corresponding to beam 5, or the CSI-RS index corresponding to beam 5), and BSR and other information to NodeX2 so that NodeX2 can provide scheduling services for UE1.

[0487] In this embodiment, the second network device sends the data transmission status information of the first terminal device to the first network device, and then the first network device sends the data transmission status information to the third network device. In this way, the third network device can determine the data transmission status information of the first terminal device so that the third network device can provide services for the first terminal device. In this way, in the beam switching scenario of the first terminal device, the first terminal device continues to transmit data under the scheduling of the third network device. For relevant introduction to data transmission status information, please refer to the aforementioned Figure 6A The relevant introduction of step 604 of the embodiment shown is not repeated here.

[0488] For example, Figure 9B As shown, NodeX1 sends UE1's data transmission status information to gNB, which then sends it to NodeX2 so that NodeX2 can provide services for UE1. In this way, in the beam switching scenario of UE1, UE1 continues to transmit data under the scheduling of NodeX2.

[0489] 907. The third network device provides communication services for the first terminal device according to the C-RNTI of the first terminal device and the identifier of the fourth beam.

[0490] Step 907 and the above Figure 6A In the embodiment shown, step 606 is similar, please refer to the aforementioned Figure 6A The relevant introduction of step 606 in the illustrated embodiment will not be repeated here.

[0491] In an embodiment of the present application, the first terminal device is within the signal coverage of the first beam managed by the second network device. The second network device determines that the fifth beam managed by the third network device provides services for the first terminal device based on the L1 measurement report of the first terminal device. The second network device sends the identifier of the fifth beam to the first terminal device so that the first terminal device can switch from the third beam to the fifth beam managed by the third network device. Then, the second network device first sends the C-RNTI of the first terminal device and the identifier of the fifth beam to the first network device. Then, the first network device sends the C-RNTI of the first terminal device and the identifier of the fifth beam to the third network device. Thereby, in the beam switching scenario of the first terminal device, the first terminal device continues to transmit data under the scheduling of the third network device.

[0492] Scenario 4: The first terminal device moves from the signal coverage of the third beam managed by the second network device to the signal coverage of the fifth beam managed by the third network device. The first terminal device initiates a beam failure recovery request to the third network device.

[0493] Among them, the fifth beam is a beam managed by the third network device. The third network device first accesses the physical cell of the first network device as a terminal device. The third network device is an access point type device. Then, the first network device configures the resource information of the fifth beam of the physical cell for the third network device and sends the resource information of the fifth beam to the third network device. The resource information of the fifth beam is used by the third network device to manage the fifth beam of the physical cell. That is, the fifth beam managed by the third network device and the one or more first beams managed by the first network device belong to the same physical cell. That is, the PCI of the physical cell used by the third network device is the same as the PCI of the physical cell used by the first network device. The system information of the physical cell broadcast by the third network device is the same as the system information of the physical cell broadcast by the first network device.

[0494] The following combination Figure 10A The embodiment shown introduces scenario 4 based on the CFRA method and the first two steps of the four-step random access. Figure 10A , Figure 10A This is another embodiment diagram of the communication method of the present application embodiment. Figure 10A , the communication method includes:

[0495] 1001. The first terminal device sends message 1 to the third network device, where message 1 includes a random access preamble code.

[0496] 1002. The third network device determines, based on the random access preamble code of message 1, that the first terminal device requests the fifth beam to perform beam failure recovery.

[0497] Before step 1002, the first network device may optionally send an identifier of at least one terminal device and a partial or complete beam failure recovery configuration corresponding to the at least one terminal device to the third network device. For example, the first network device may send a beam failure recovery configuration of at least one terminal device for a beam managed by the third network device to the third network device.

[0498] 1003. The third network device sends message 2 to the first terminal device, where message 2 is a random access response message.

[0499] Steps 1001 to 1003 are the same as those mentioned above. Figure 7A In the embodiment shown, steps 701 to 703 are similar. For details, please refer to the aforementioned Figure 7A The relevant introduction of steps 701 to 703 in the illustrated embodiment will not be repeated here.

[0500] For example, Figure 10B As shown, UE1 initially accesses beam 4 managed by NodeX1. UE1 then moves from the signal coverage of beam 4 managed by NodeX1 to the signal coverage of beam 5 managed by NodeX2. UE1 detects a beam failure and initiates a beam recovery request to NodeX2, requesting access to beam 4 of NodeX2 so that NodeX2 can provide service to the first terminal device.

[0501] 1004. The third network device sends the C-RNTI of the first terminal device to the first network device.

[0502] The first terminal device re-accesses the network through the BFR process. The third network device may send the C-RNTI of the first terminal device to the first network device to inform the first network device that the first terminal device will continue to be served by the third network device.

[0503] 1005. The first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0504] In step 1005, the first network device determines that the third network device provides services for the first terminal device. Then, the first network device sends information to the second network device for instructing the second network device to stop scheduling the first terminal device, so as to notify the second network device to stop scheduling the first terminal device.

[0505] 1006. The second network device stops scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0506] The information for instructing the second network device to stop scheduling the first terminal device is the same as the above Figure 7AThe information used to instruct the second network device to stop scheduling the first terminal device in step 705 in the illustrated embodiment is similar, and details can be found in the aforementioned related introduction.

[0507] In scenario 4, if the CBRA method and the four-step random access process are used, the operations performed between the first terminal device and the third network device are the same as those performed in the example above. Figure 7C In this manner, the third network device instructs the second network device to stop scheduling the first terminal device through the first network device. The specific execution process is similar to the aforementioned steps 1004 to 1006 and will not be repeated here.

[0508] The following combination Figure 11 The embodiment shown is based on CBRA and two-step random access to introduce scenario 4. Figure 11 , Figure 11 This is another embodiment diagram of the communication method of the present application embodiment. Figure 11 , the communication method comprises:

[0509] 1101. A first terminal device sends a message A to a third network device. The message A includes a random access preamble code and an identifier of the first terminal device.

[0510] 1102. The third network device determines, based on the random access preamble code of message A and the identifier of the first terminal device, that the first terminal device requests to access the fifth beam.

[0511] 1103. The third network device sends a message B to the first terminal device, where the message B is a random access response message.

[0512] Steps 1101 to 1103 are the same as those mentioned above. Figure 8 Steps 801 to 803 in the embodiment shown are similar, please refer to the aforementioned Figure 8 The relevant introduction of steps 801 to 803 in the illustrated embodiment will not be repeated here.

[0513] 1104. The third network device sends the C-RNTI of the first terminal device to the first network device.

[0514] 1105. The first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0515] 1106. The second network device stops scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0516] Steps 1104 to 1106 are the same as those described above. Figure 10ASteps 1004 to 1006 of the embodiment shown are similar, please refer to the aforementioned Figure 10A The relevant introduction of steps 1004 to 1006 of the illustrated embodiment will not be repeated here.

[0517] In an embodiment of the present application, the first terminal device moves from the signal coverage of the first beam managed by the second network device to the signal coverage of the fifth beam managed by the third network device. The first terminal device initiates a beam failure recovery request to the third network device to enable the third network device to provide services for the first terminal device. In the scenario where a beam failure occurs in the first terminal device, the first terminal device continues to transmit data under the scheduling of the third network device. The third network device sends the C-RNTI of the first terminal device to the first network device (specifically, it can be obtained during the beam failure recovery process of the first terminal device), then the first network device can instruct the second network device to stop scheduling the first terminal device, so that the first network device can provide communication services for the first terminal device.

[0518] Scenario 5: The first terminal device is within the signal coverage of the fourth beam managed by the first network device, and the first terminal device switches from the fourth beam to the third beam managed by the second network device. This is a beam switching scenario.

[0519] The following combination Figure 12 The embodiment shown introduces scenario 5. Please refer to Figure 12 , Figure 12 This is another embodiment diagram of the communication method of the present application embodiment. Figure 12 , the communication method includes:

[0520] 1201. The first terminal device sends an L1 measurement report to the first network device.

[0521] 1202. The first network device determines a third beam according to the L1 measurement report.

[0522] 1203. The first network device sends an identifier of the third beam to the first terminal device.

[0523] 1204. The first terminal device switches from the fourth beam to the third beam.

[0524] 1205. The first network device sends the C-RNTI of the first terminal device and the identifier of the third beam to the second network device.

[0525] There is no fixed execution order between step 1203 and step 1205. Step 1203 may be executed first, and then step 1205; or step 1205 may be executed first, and then step 1203; or, step 1203 and step 1205 may be executed simultaneously depending on the situation.

[0526] 1206. The second network device provides communication services for the first terminal device according to the C-RNTI of the first terminal device and the identifier of the third beam.

[0527] Steps 1201 to 1206 are the same as those described above. Figure 6A Steps 601 to 606 of the embodiment shown are similar, please refer to the aforementioned Figure 6A The relevant introduction of steps 601 to 606 of the illustrated embodiment will not be repeated here.

[0528] For example, Figure 6B As shown, UE1 accesses beam 2 managed by the gNB and sends an L1 measurement report to the gNB. Based on this L1 measurement report, the gNB determines that beam 4 managed by NodeX has better signal quality and is more suitable for serving UE1. The gNB then sends the identifier of beam 4 to UE1, allowing UE1 to switch from beam 2 to beam 4. Furthermore, the gNB sends the identifier of UE1 to NodeX, enabling NodeX to provide service to UE1.

[0529] In an embodiment of the present application, the first terminal device is within the signal coverage of the fourth beam managed by the first network device. The first network device determines that the third beam managed by the second network device provides services for the first terminal device based on the L1 measurement report of the first terminal device. The first network device sends an identifier of the third beam to the first terminal device so that the first terminal device switches from the fourth beam to the third beam. In addition, the first network device sends the C-RNTI of the first terminal device and the identifier of the third beam to the second network device, thereby realizing that in the beam switching scenario of the first terminal device, the first terminal device continues to transmit data under the scheduling of the second network device.

[0530] Scenario 6: The first terminal device moves from the signal coverage of the fourth beam managed by the first network device to the signal coverage of the third beam managed by the second network device. The first terminal device initiates a beam failure recovery request to the second network device.

[0531] The following combination Figure 13A The embodiment shown introduces scenario 6 based on the CFRA method and the first two steps of the four-step random access. Figure 13A , Figure 13A This is another embodiment diagram of the communication method of the present application embodiment. Figure 13A , the communication method comprises:

[0532] 1301. The first terminal device sends message 1 to the second network device, where message 1 includes a random access preamble code.

[0533] 1302. The second network device determines, based on the random access preamble code of message 1, that the first terminal device requests beam failure recovery in the third beam.

[0534] 1303. The second network device sends message 2 to the first terminal device, where message 2 includes a random access response message.

[0535] 1304. The second network device sends information to the first network device to instruct the first network device to stop scheduling the first terminal device.

[0536] 1305. The first network device stops scheduling the first terminal device according to the information used to instruct the first network device to stop scheduling the first terminal device.

[0537] Steps 1301 to 1305 are the same as those described above. Figure 7A Steps 701 to 705 of the embodiment shown are similar, please refer to the aforementioned Figure 7A The relevant introduction of steps 701 to 705 of the illustrated embodiment will not be repeated here.

[0538] For example, Figure 13B As shown, UE1 initially accesses beam 2 managed by the gNB. UE1 then moves from the signal coverage of beam 2 to the signal coverage of beam 4 managed by NodeX. UE1 detects a beam failure and initiates a beam failure recovery request to NodeX. Specifically, UE1 requests access to beam 4 managed by NodeX, allowing NodeX to provide service to the first terminal device.

[0539] In scenario six, if the CBRA method and the four-step random access process are used, the operations performed between the first terminal device and the second network device are the same as those performed in the example above. Figure 7C In this manner, the specific execution process of the second network device instructing the first network device to stop scheduling the first terminal device is similar to the aforementioned steps 1304 to 1305 and will not be repeated here.

[0540] The following combination Figure 14 The embodiment shown introduces the above scenario 6 based on the CBRA method and the two-step random access process. Figure 14 , Figure 14 This is another embodiment diagram of the communication method of the present application embodiment. Figure 14 , the communication method comprises:

[0541] 1401. The first terminal device sends a message A to the second network device, where the message A includes a random access preamble code and an identifier of the first terminal device.

[0542] 1402. The second network device determines, based on the random access preamble code and the identifier of the first terminal device, that the first terminal device requests to access the third beam.

[0543] 1403. The second network device sends a message B to the first terminal device, where the message B is a random access response message.

[0544] 1404. The second network device sends information to the first network device to instruct the first network device to stop scheduling the first terminal device.

[0545] 1405. The first network device stops scheduling the first terminal device according to the information used to instruct the first network device to stop scheduling the first terminal device.

[0546] Steps 1401 to 1405 are the same as those described above. Figure 8 Steps 801 to 805 of the embodiment shown are similar, please refer to the aforementioned Figure 8 The relevant introduction of steps 801 to 805 of the illustrated embodiment will not be repeated here.

[0547] above Figure 13A and Figure 14 In the embodiment shown, the first terminal device moves from the signal coverage of the fourth beam managed by the first network device to the signal coverage of the third beam managed by the second network device. The first terminal device initiates a beam failure recovery request to the second network device so that the second network device can provide services to the first terminal device. Figure 13A or Figure 14 In the illustrated embodiment, even if a beam failure occurs on a first terminal device, the first terminal device continues to transmit data under the scheduling of a second network device. The second network device sends information to the first network device instructing the first network device to stop scheduling the first terminal device. This allows the first network device to stop scheduling the first terminal device, allowing the second network device to provide communication services to the first terminal device.

[0548] Scenario 7: The first terminal device is within the signal coverage of the third beam managed by the second network device. The first terminal device switches (handover) from the signal coverage of the third beam managed by the second network device to the signal coverage of the sixth beam managed by the fourth network device.

[0549] The fourth network device and the first network device are of the same type. The fourth network device and the second network device are of different types. The PCI of the physical cell used by the fourth network device is different from the PCI of the physical cell used by the second network device. The system information of the fourth network device is different from the system information of the second network device.

[0550] The following combination Figure 15A The embodiment shown introduces the above scenario seven. Figure 15A , Figure 15A This is another embodiment diagram of the communication method of the present application embodiment. Figure 15A , the communication method comprises:

[0551] 1501. The first terminal device sends an L3 measurement report to the first network device.

[0552] The first terminal device sends an L3 measurement report to the first network device through an RRC message. The L3 measurement report includes a reference signal received power (RSRP) or a reference signal received quality (RSRQ) obtained by the first terminal device measuring the signal sent by the gNB and / or the signal sent by NodeX.

[0553] 1502. The first network device switches the first terminal device from the first network device to the fourth network device according to the L3 measurement report.

[0554] In one possible implementation, the first network device determines, based on the L3 measurement report, which beam managed by the fourth network device the first terminal device switches to.

[0555] In another possible implementation, the first network device only determines that the first terminal should switch to the fourth network device, and sends the L3 measurement report to the fourth network device, and the fourth network device determines which beam managed by the fourth network device the first terminal device switches to.

[0556] The third beam is a beam managed by the second network device. The second network device is a device that accesses the physical cell of the first network device, and the second network device is an access point type device.

[0557] For example, Figure 15B As shown, UE1 is within the signal coverage of NodeX's beam 4. gNB1 receives the L3 measurement report sent by UE1. Based on the L3 measurement report, gNB1 decides to handover UE1 from NodeX's beam 4 to the beam managed by gNB2.

[0558] 1503. The first network device sends a handover request message to the fourth network device.

[0559] Optionally, the switching request message includes an L3 measurement report reported by the first terminal device.

[0560] For example, Figure 15BAs shown, gNB1 sends a handover request message to gNB2 via the Xn interface.

[0561] 1504. The fourth network device sends a handover request acknowledgment message to the first network device. The handover request acknowledgment message includes a handover command message sent by the fourth network device to the first terminal device.

[0562] The handover request confirmation message includes a handover command message, the handover command message includes a random access channel dedicated (rach-configDedicated) parameter, and the rach-configDedicated parameter includes the C-RNTI allocated by the fourth network device to the first terminal device, the identifier of the sixth beam, and the random access preamble code sequence number corresponding to the sixth beam. The sixth beam is a beam managed by the fourth network device. That is, the fourth network device determines that the first terminal device should switch to the sixth beam based on the L3 measurement report included in the handover request message of step 1503 above.

[0563] For example, Figure 15B As shown, gNB2 sends a handover request confirmation message to gNB1. The handover request confirmation message includes a handover command message. The handover command message includes a rach-configDedicated parameter. The rach-configDedicated parameter includes the C-RNTI assigned by gNB2 to UE1, the SSB index corresponding to the sixth beam, the random access preamble index (preamble index) corresponding to the sixth beam, and other rach-configGeneric parameters. Alternatively, the rach-configDedicated parameter includes the C-RNTI assigned by gNB2 to UE1, the CSI-RS resource index and preamble index corresponding to the sixth beam, and other rach-configGeneric parameters.

[0564] 1505. The first network device sends a switching command message to the first terminal device.

[0565] 1506. The first terminal device switches from the first network device to the fourth network device.

[0566] In steps 1505 to 1506, the first network device forwards the handover command message sent by the fourth network device to the first terminal device. The first terminal device then determines the sixth beam based on the identifier of the sixth beam included in the handover command message. The terminal device switches from the third beam managed by the second network device to the sixth beam managed by the fourth network device.

[0567] 1507. The first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0568] In a possible implementation, the information for instructing the second network device to stop scheduling the first terminal device is instruction information. The first network device instructs the second network device to stop scheduling the first terminal device through the instruction information.

[0569] In another possible implementation, the information for instructing the second network device to stop scheduling the first terminal device includes StopTransmissionUEID, and StopTransmissionUEID includes the C-RNTI allocated by the first network device or the second network device to the first terminal device.

[0570] 1508. The second network device stops scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0571] Step 1508 and the above Figure 14 Step 1405 of the embodiment shown is similar, please refer to the aforementioned Figure 14 The relevant introduction of step 1405 of the illustrated embodiment will not be repeated here.

[0572] In an embodiment of the present application, a first terminal device is within the signal coverage of a third beam managed by a second network device. Based on the L3 measurement report of the first terminal device, the first network device determines to switch the first terminal device from the third beam to a beam managed by a fourth network device. The first network device then sends a handover request message to the fourth network device and receives a handover request confirmation message from the fourth network device. The handover request confirmation message includes a handover command message. The fourth network device then sends a handover command message to the first terminal device. Based on the information about the third beam carried in the handover command message, the first terminal device switches from the third beam to the sixth beam, thereby enabling the first terminal device to switch between the first and fourth network devices. After the first terminal device switches to the fourth network device, the fourth network device provides scheduling services for the first terminal device. Furthermore, the first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device, thereby instructing the second network device to stop scheduling the first terminal device. In this way, after the first terminal device switches to the sixth beam managed by the fourth network device, the second network device can promptly stop scheduling the first terminal device.

[0573] Scenario 8: The first terminal device is within the signal coverage of the sixth beam managed by the fourth network device. The first terminal device switches (handover) from the signal coverage of the sixth beam managed by the fourth network device to the signal coverage of the third beam managed by the second network device.

[0574] The fourth network device and the first network device are of the same type. The fourth network device and the second network device are of different types. The PCI of the physical cell used by the fourth network device is different from the PCI of the physical cell used by the second network device. The system information of the fourth network device is different from the system information of the second network device.

[0575] The following combination Figure 16A The embodiment shown introduces scenario eight. Figure 16A , Figure 16A This is another embodiment diagram of the communication method of the present application embodiment. Figure 16A , the communication method includes:

[0576] 1601. The first terminal device sends an L3 measurement report to the fourth network device.

[0577] 1602. The fourth network device determines to switch the first terminal device from the fourth network device to the first network device according to the L3 measurement report.

[0578] In one possible implementation, the fourth network device determines, based on the L3 measurement report of the first terminal device, which beam managed by the first network device or the second network device the first terminal device switches to.

[0579] In another possible implementation, the fourth network device only determines that the first terminal should be handed over to the first network device. Simultaneously, the fourth network device sends the L3 measurement report of the first terminal device to the first network device. Based on the L3 measurement report, the first network device determines which beam managed by the first network device or the second network device the first terminal should be handed over to.

[0580] 1603. The fourth network device sends a switching request message to the first network device.

[0581] Steps 1601 to 1603 are the same as those mentioned above. Figure 15A Steps 1501 to 1503 of the embodiment shown are similar, please refer to the aforementioned Figure 15A The relevant introduction of steps 1501 to 1503 of the illustrated embodiment will not be repeated here.

[0582] 1604. The first network device sends a switching request confirmation message to the fourth network device. The switching request confirmation message includes a switching command message sent by the first network device to the first terminal device.

[0583] The switching command message includes a rach-configDedicated parameter, which includes the C-RNTI allocated by the first network device to the first terminal device, the identifier of the third beam, the RACH time-frequency resources corresponding to the third beam, and the random access preamble code sequence number corresponding to the third beam.

[0584] The third beam is managed by the second network device. Based on the handover request message, the first network device determines that the third beam has higher signal quality and is more suitable for serving the first terminal device. Therefore, the first network device decides to handover the first terminal device from the sixth beam to the third beam. The sixth beam is managed by the fourth network device.

[0585] For example, Figure 16B As shown, gNB1 determines that NodeX will serve UE1. That is, it decides to switch the first UE from gNB2's beam to beam 4. The rach-configDedicated parameter includes the C-RNTI assigned by gNB1 to UE1, the SSB index of beam 4, the random access preamble sequence number corresponding to beam 4, and other rach-configGeneric parameters. Alternatively, the rach-configDedicated parameter includes the C-RNTI assigned by gNB1 to UE1, the CSI-RS resource index of beam 4, the random access preamble sequence number corresponding to beam 4, and other rach-configGeneric parameters.

[0586] 1605. The fourth network device sends a switching command message to the first terminal device.

[0587] 1606. The first terminal device switches from the fourth network device to the first network device.

[0588] In steps 1605 to 1606, the first network device forwards the handover command message sent by the fourth network device to the first terminal device. The first terminal device then determines the third beam based on the identifier of the third beam included in the handover command message and switches from the sixth beam of the fourth network device to the third beam managed by the second network device.

[0589] 1607. The first network device sends the C-RNTI of the first terminal device and the random access preamble code corresponding to the third beam to the second network device.

[0590] Specifically, the first network device allocates a C-RNTI to the first terminal device. The first network device sends the C-RNTI of the first terminal device and a random access preamble code (eg, preamble index) corresponding to the third beam to the second network device.

[0591] Optionally, the first network device may also send the RACH time-frequency resources corresponding to the third beam and the identifier of the third beam to the second network device.

[0592] For example, Figure 16B As shown, gNB1 sends the C-RNTI allocated by gNB1 to UE1, the SSB index (or CSI-RS resource index) corresponding to the third beam, the random access preamble code number corresponding to the third beam, and other rach-configGeneric parameters to NodeX.

[0593] 1608. The second network device determines to provide communication services to the first terminal device based on the C-RNTI allocated by the first network device to the first terminal device and the random access preamble code corresponding to the third beam.

[0594] After receiving the random access preamble sent by the first terminal device, the second network device can determine that the first terminal device is a terminal device that has been handed over from the fourth network device to the second network device. The second network device then provides communication services to the first terminal device. For example, the second network device provides resource scheduling, data transmission, and other services to the first terminal device.

[0595] In an embodiment of the present application, the first terminal device is within the signal coverage of the sixth beam managed by the fourth network device. The fourth network device determines to switch the first terminal device from the sixth beam to the beam managed by the first network device or the second network device based on the L3 measurement report of the first terminal device. Then, the fourth network device sends a switching request message to the first network device. The first network device sends a switching request confirmation message to the fourth network device. The switching request confirmation message includes a switching command message. Then, the fourth network device sends a switching command message to the first terminal device. The switching command message includes an identifier of the third beam. In this way, the first terminal device can determine to switch from the sixth beam managed by the fourth network device to the third beam managed by the second network device based on the identifier of the third beam. The first network device sends to the second network device information such as the C-RNTI allocated by the first network device to the first terminal device and the preamble index corresponding to the third beam. In this way, the switching of the first terminal device between the second network device and the fourth network device is realized, so that after the first terminal device switches to the second network device, the second network device provides communication services for the first terminal device.

[0596] Scenario 9: The first terminal device is within the signal coverage of the third beam managed by the second network device. The first terminal device switches (handover) from the signal coverage of the third beam managed by the second network device to the signal coverage of the seventh beam managed by the fifth network device.

[0597] The fifth network device first accesses the physical cell of the fourth network device as a terminal device. The fifth network device is an access point type device. The fourth network device configures resource information for the seventh beam of the physical cell for the fifth network device and sends the resource information for the seventh beam to the fifth network device. The resource information for the seventh beam is used by the fifth network device to manage the seventh beam of the physical cell. In other words, the seventh beam managed by the fifth network device and the beam managed by the fourth network device belong to the same physical cell. In other words, the PCI used by the fifth network device is the same as the PCI used by the fourth network device. The system information broadcast by the fifth network device is the same as the system information broadcast by the fourth network device.

[0598] The first network device and the fourth network device are of the same type, and the first network device and the second network device are of different types. The fifth network device and the second network device are of the same type, but the PCI used by the fifth network device is different from the PCI used by the second network device. The system information of the fifth network device is different from the system information of the second network device.

[0599] The following combination Figure 17A The embodiment shown introduces scenario nine. Figure 17A , Figure 17A This is another embodiment diagram of the communication method of the present application embodiment. Figure 17A , the communication method includes:

[0600] 1701. The first terminal device sends an L3 measurement report to the first network device.

[0601] 1702. The first network device determines to switch the first terminal device from the first network device to the fourth network device based on the L3 measurement report.

[0602] 1703. The first network device sends a switching request message to the fourth network device.

[0603] 1704. The fourth network device sends a switching request confirmation message to the first network device. The switching request confirmation message includes a switching command message sent by the fourth network device to the first terminal device.

[0604] The handover command message includes the C-RNTI allocated by the fourth network device to the first terminal device, the identifier of the seventh beam, the RACH time-frequency resources corresponding to the seventh beam, and the random access preamble code (e.g., preamble index) corresponding to the seventh beam. The seventh beam is a beam managed by the fifth network device, and the fifth network device is an access point device accessing the fourth network device.

[0605] For example, Figure 17B As shown, gNB1 decides to handover UE1 from gNB1 to gNB2 based on UE1's L3 measurement report. gNB1 sends a Handover Request message to gNB2. Based on UE1's L3 measurement report, gNB2 decides that NodeX2 will serve UE1 and connects UE1 to Beam 6 managed by NodeX2. The Handover Request message carries UE1's measurement report, and gNB2 may obtain UE1's L3 measurement report from the Handover Request message. gNB2 then sends a Handover Request Acknowledge message to gNB1, which includes a Handover Command message. The Handover Command message includes the C-RNTI allocated by gNB2 to UE1, the SSB index of Beam 6, the RACH time-frequency resource corresponding to the SSB index, and the random access preamble sequence number corresponding to the SSB index.

[0606] 1705. The first network device sends a switching command message to the first terminal device.

[0607] 1706. The first terminal device switches from the first network device to the fourth network device.

[0608] Specifically, the first terminal device switches from the third beam to the seventh beam managed by the fifth network device.

[0609] Steps 1701 to 1706 are the same as those described above. Figure 15A Steps 1501 to 1506 of the embodiment shown are similar, please refer to Figure 15A The relevant introduction of steps 1501 to 1506 of the illustrated embodiment will not be repeated here.

[0610] 1707. The first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0611] A first terminal device accesses beam 4 of a second network device. The first network device stores the first terminal device's context. Based on the first terminal device's context, the first network device determines that the second network device was originally providing services to the first terminal device. In other words, the first terminal device was originally accessing beam 3, managed by the second network device. The first network device then instructs the second network device to stop scheduling the first terminal device.

[0612] For example, the information used to instruct the second network device to stop scheduling the first terminal device is the indication information, and the first network device instructs the second network device to stop scheduling the first terminal device through the indication information.

[0613] For another example, the information for instructing the second network device to stop scheduling the first terminal device is

[0614] StopTransmissionUEID, StopTransmissionUEID includes the C-RNTI allocated by the second network device to the first terminal device.

[0615] 1708. The second network device stops scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0616] 1709. The fourth network device sends the C-RNTI of the first terminal device and the identifier of the seventh beam to the fifth network device.

[0617] In step 1709, the fourth network device may send the C-RNTI and the identifier of the seventh beam allocated by the fourth network device to the first terminal device to the fifth network device, so that the fifth network device can provide access services and resource scheduling services to the first terminal device.

[0618] In this embodiment, optionally, the fourth network device sends the RACH time-frequency resources corresponding to the seventh beam and the random access preamble code corresponding to the seventh beam to the fifth network device; or, the fourth network device may include the RACH time-frequency resources corresponding to the seventh beam and the random access preamble code corresponding to the seventh beam in the resource information of the beam managed by the fifth network device configured for the fifth network device, so that the fifth network device can provide services for the terminal device.

[0619] In an embodiment of the present application, a first terminal device is within the signal coverage of a third beam managed by a second network device. Based on the L3 measurement report of the first terminal device, the first network device determines to switch the first terminal device from the third beam to a beam managed by a fourth network device. The first network device then sends a handover request message to the fourth network device. The fourth network device sends a handover request confirmation message to the first network device. The handover request confirmation message includes a handover command message. The first network device then sends a handover command message to the first terminal device. In this way, the first terminal device can determine the seventh beam based on the identifier of the seventh beam included in the handover command message. The first terminal device then switches from the third beam to the seventh beam. The fourth network device sends the C-RNTI allocated by the fourth network device to the first terminal device, the identifier of the seventh beam, the RACH time-frequency resources corresponding to the seventh beam, and the random access preamble sequence number corresponding to the seventh beam to the fifth network device. In this way, the fifth network device can provide communication services for the first terminal device. For example, the fifth network device can provide access services, resource scheduling, and data transmission services for the first terminal device, enabling handover of the first terminal device between the second network device and the fifth network device. After the first terminal device switches to the fifth network device, the fifth network device can provide scheduling services for the first terminal device. In addition, the first network device sends information to the second network device to instruct the second network device to stop scheduling the first terminal device, so that the second network device stops scheduling the first terminal device.

[0620] The following describes the first network device provided in the embodiment of the present application. Figure 18 , Figure 18 This is a structural diagram of the first network device 1800 according to an embodiment of the present application. The first network device 1800 can be used to Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A For the steps executed by the first network device in the illustrated embodiment, reference may be made to the relevant descriptions in the above method embodiment.

[0621] The first network device 1800 includes a processing unit 1801 and a transceiver unit 1802 .

[0622] The processing unit 1801 is configured to determine that a first network manages one or more first beams and a second network device manages one or more second beams; wherein the one or more first beams and the one or more second beams belong to the same physical cell; and the second network device is a device accessing the physical cell; and determine resource information corresponding to the one or more second beams.

[0623] The transceiver unit 1802 is used to send resource information to the second network device; the resource information is used by the second network device to provide communication services for terminal devices requesting access to one or more second beams.

[0624] In one possible implementation, the resource information includes at least one of the following: identifiers corresponding to one or more second beams, a set of preamble code numbers corresponding to each second beam, and random access channel time-frequency resource information corresponding to each second beam.

[0625] In another possible implementation, the transceiver unit 1802 is further configured to:

[0626] Send at least one of the following to the second network device:

[0627] System information, time-frequency resource information corresponding to the system information, time-frequency resource information corresponding to the demodulation reference signal, time-frequency resource information corresponding to the CSI-RS, cell radio network temporary identifier set, control resource set time-frequency resource information, and scheduling time-frequency resource information.

[0628] In another possible implementation, the transceiver unit 1802 is further configured to:

[0629] Capability information of the second network device sent by the second network device is received; the capability information includes at least one of the following: information indicating that the second network device is an access point type device, and transmission power of the second network device.

[0630] In another possible implementation, the capability information also includes at least one of the following: the number of transmitting and receiving antennas of the second network device, location information, the number of supported beams, the number of terminal devices supported for access, and the size of the requested time-frequency resources.

[0631] In another possible implementation, the processing unit 1801 is specifically configured to:

[0632] Determine, based on the capability information, that the one or more second beams are managed by the second network device.

[0633] In another possible implementation, the transceiver unit 1802 is further configured to:

[0634] receiving location information and a beam measurement result of a second network device, where the beam measurement result includes a beam measurement result obtained by the second network device measuring a beam of a physical cell;

[0635] The processing unit 1801 is specifically configured to:

[0636] Determine, based on the capability information and the beam measurement result, that the second network device manages the one or more second beams.

[0637] In another possible implementation, when the first terminal device switches from the third beam to the fourth beam, the third beam is one of the one or more second beams, and the fourth beam is one of the one or more first beams; the transceiver unit 1802 is further configured to:

[0638] Receiving the C-RNTI of the first terminal device and the identifier of the fourth beam sent by the second network device;

[0639] The processing unit 1801 is further configured to:

[0640] Communication services are provided to the first terminal device according to the C-RNTI of the first terminal device and the identifier of the fourth beam.

[0641] In another possible implementation, the one or more second beams include a third beam, and the first terminal device accesses the third beam; when the first terminal device moves from the signal coverage of the third beam to the signal coverage of the fourth beam, the fourth beam is one of the one or more first beams managed by the first network device; the transceiver unit 1802 is further configured to:

[0642] Receive a message 1 sent by a first terminal device, where the message 1 includes a random access preamble;

[0643] The processing unit 1801 is further configured to:

[0644] Determining, based on the random access preamble of message 1, that the first terminal device requests beam failure recovery in the fourth beam; the first network device sends message 2 to the first terminal device, where message 2 includes a random access response message;

[0645] The transceiver unit 1802 is further configured to:

[0646] Information is sent to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0647] In another possible implementation, the one or more first beams include a fourth beam, and the first terminal device accesses the fourth beam; and the transceiver unit 1802 is further configured to:

[0648] receiving an L1 measurement report of the first terminal device;

[0649] The processing unit 1801 is further configured to:

[0650] Determining a third beam according to the L1 measurement report; the third beam is one of the one or more second beams managed by the second network device;

[0651] The transceiver unit 1802 is further configured to:

[0652] Sending an identifier of the third beam to the first terminal device, where the identifier of the third beam is used by the first terminal device to switch from the fourth beam to the third beam;

[0653] Send the C-RNTI of the first terminal device and the identifier of the third beam to the second network device.

[0654] In another possible implementation, the one or more first beams include a fourth beam, and the first terminal device accesses the fourth beam; when the first terminal device moves from the signal coverage of the fourth beam to the signal coverage of the third beam, the first terminal device initiates a beam failure recovery request to the first network device, and the third beam is one of the one or more second beams managed by the second network device. The transceiver unit 1802 is further used to:

[0655] receiving information from the second network device for instructing the first network device to stop scheduling the first terminal device;

[0656] The processing unit 1801 is further configured to:

[0657] Stop scheduling the first terminal device according to the information used to instruct the first network device to stop scheduling the first terminal device.

[0658] In another possible implementation, the transceiver unit 1802 is further configured to:

[0659] receiving an L3 measurement report of the first terminal device;

[0660] The processing unit 1801 is further configured to:

[0661] Determining, according to the L3 measurement report, to switch the first terminal device from the first network device to the fourth network device; the first network device sending a switching request message to the fourth network device;

[0662] The transceiver unit 1802 is further configured to:

[0663] Receive a switching request confirmation message from the fourth network device, where the switching request confirmation message includes a switching command message sent by the fourth network device to the first terminal device; the switching command message includes a random access channel dedicated parameter; the random access channel dedicated parameter includes the C-RNTI allocated by the fourth network device to the first terminal device, an identifier of the sixth beam, and a random access preamble corresponding to the sixth beam, where the sixth beam is a beam managed by the fourth network device; and send information to the second network device to instruct the second network device to stop scheduling the first terminal device.

[0664] In another possible implementation, the transceiver unit 1802 is further configured to:

[0665] Receive a handover request message from a fourth network device; send a handover request confirmation message to the fourth network device, where the handover request confirmation message includes a handover command message sent by the first network device to the first terminal device; the handover command message includes a random access channel-specific parameter; the random access channel-specific parameter includes a C-RNTI allocated by the first network device or the second network device to the first terminal device, an identifier of the third beam, and a random access preamble corresponding to the third beam; the third beam is one of one or more second beams managed by the second network device; and send the C-RNTI of the first terminal device and the random access preamble corresponding to the third beam to the second network device.

[0666] In an embodiment of the present application, the processing unit 1801 is configured to determine that a first network manages one or more first beams and a second network device manages one or more second beams; wherein the one or more first beams and the one or more second beams belong to the same physical cell; the second network device is a device that accesses the physical cell; and resource information corresponding to the one or more second beams is determined; the transceiver unit 1802 is configured to send the resource information to the second network device; the resource information is used by the second network device to provide communication services to terminal devices requesting access to the one or more second beams. The first network device configures the resource information of the one or more second beams for the second network device, so that the second network device manages the one or more second beams of the physical cell and is responsible for providing access services and resource scheduling to terminal devices requesting access to the one or more second beams. Since the second network device manages the one or more second beams of the physical cell, not a new physical cell, there is no need to allocate a new PCI, thereby avoiding the PCI conflict problem that is common in a large number of deployed sites due to a PCI being shared by different adjacent physical cells.

[0667] The second network device provided in the embodiment of the present application is described below. Figure 19 , Figure 19This is a structural diagram of the second network device 1900 of the embodiment of the present application. The second network device 1900 can be used Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A For the steps performed by the second network device in the illustrated embodiment, reference may be made to the relevant descriptions in the above method embodiment.

[0668] The second network device 1900 includes a transceiver unit 1901 and a processing unit 1902 .

[0669] The transceiver unit 1901 is configured to receive resource information corresponding to one or more second beams sent by a first network device; the one or more second beams and the one or more first beams managed by the first network device belong to the same physical cell; the second network device is a device accessing the physical cell;

[0670] The processing unit 1902 is configured to provide communication services to a terminal device requesting access to the one or more second beams based on the resource information.

[0671] In one possible implementation, the resource information includes at least one of the following: identifiers corresponding to the one or more second beams, a set of contention-based preamble code numbers corresponding to each second beam, and random access channel time-frequency resource information corresponding to each second beam.

[0672] In another possible implementation, the transceiver unit 1901 is further configured to:

[0673] Receive at least one of the following items sent by the first network device: system information, time-frequency resource information corresponding to the system information, time-frequency resource information corresponding to the demodulation reference signal, time-frequency resource information corresponding to the channel state information reference signal, cell wireless network temporary identifier set, control resource set time-frequency resource information, and scheduling time-frequency resource information.

[0674] In another possible implementation, the processing unit 1902 is further configured to:

[0675] Determine the time-frequency resource corresponding to the system information according to the time-frequency resource information corresponding to the system information;

[0676] The transceiver unit 1901 is further configured to:

[0677] The system information is sent in the time-frequency resources corresponding to the system information.

[0678] In another possible implementation, the transceiver unit 1901 is further configured to:

[0679] Send capability information of the second network device to the first network device; the capability information includes at least one of the following: information indicating that the second network device is an access point type device, and transmission power of the second network device.

[0680] In another possible implementation, the capability information also includes at least one of the following: the number of transmitting and receiving antennas of the second network device, location information, the number of supported beams, the number of terminal devices supported for access, and the size of the requested time-frequency resources.

[0681] In another possible implementation, the transceiver unit 1901 is further configured to:

[0682] The beam measurement result of the second network device is sent to the first network device, where the beam measurement result includes the beam measurement result obtained by the second network device measuring the beam of the physical cell.

[0683] In another possible implementation, the one or more second beams include a third beam, and the first terminal device accesses the third beam; and the transceiver unit 1901 is further configured to:

[0684] Receiving an L1 measurement report sent by the first terminal device;

[0685] The processing unit 1902 is further configured to:

[0686] Determining a fourth beam according to the L1 measurement report; the fourth beam being one of the one or more first beams managed by the first network device;

[0687] The transceiver unit 1901 is further configured to:

[0688] Sending an identifier of the fourth beam to the first terminal device; the identifier of the fourth beam is used by the first terminal device to switch from the third beam to the fourth beam;

[0689] Send the C-RNTI of the first terminal device and the identifier of the fourth beam to the first terminal device.

[0690] In another possible implementation, the one or more second beams include a third beam, and the first terminal device accesses the third beam; when the first terminal device moves from the signal coverage of the third beam to the signal coverage of the fourth beam, the first terminal device initiates a beam failure recovery request to the first network device, and the fourth beam is one of the one or more first beams managed by the first network device. The transceiver unit 1901 is further used to:

[0691] receiving information from the first network device for instructing the second network device to stop scheduling the first terminal device;

[0692] The processing unit 1902 is further configured to:

[0693] Stop scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0694] In another possible implementation, when the first terminal device switches from the fourth beam to the third beam, the third beam is one of the one or more second beams, and the fourth beam is one of the one or more first beams managed by the first network device; the transceiver unit 1901 is further configured to:

[0695] Receiving the C-RNTI of the first terminal device and the identifier of the third beam sent by the first network device;

[0696] The processing unit 1902 is further configured to:

[0697] Communication services are provided to the first terminal device according to the C-RNTI of the first terminal device and the identifier of the third beam.

[0698] In another possible implementation, the one or more first beams include a fourth beam, and the first terminal device accesses the fourth beam; when the first terminal device moves from the signal coverage of the fourth beam to the signal coverage of the third beam, the third beam is one of the one or more second beams managed by the second network device; the transceiver unit 1901 is further configured to:

[0699] Receive a message 1 from a first terminal device, where the message 1 includes a random access preamble;

[0700] The processing unit 1902 is further configured to:

[0701] Determining, according to the random access preamble of message 1, that the first terminal device requests beam failure recovery in the third beam;

[0702] The transceiver unit 1901 is further configured to:

[0703] Sending message 2 to the first network device, where message 2 includes a random access response message;

[0704] Information is sent to the first network device to instruct the first network device to stop scheduling the first terminal device.

[0705] In another possible implementation, when the first terminal device switches from the first network device to the fourth network device, the transceiver unit 1901 is further configured to:

[0706] receiving information sent by the first network device for instructing the second network device to stop scheduling the first terminal device;

[0707] The processing unit 1902 is further configured to:

[0708] Stop scheduling the first terminal device according to the information used to instruct the second network device to stop scheduling the first terminal device.

[0709] In another possible implementation, when the first terminal device switches from the fourth network device to the first network device, the transceiver unit 1901 is further configured to:

[0710] Receive a C-RNTI of the first terminal device and a random access preamble corresponding to the third beam sent by the first network device;

[0711] The processing unit 1902 is further configured to:

[0712] Communication services are provided for the first terminal device according to the C-RNTI of the first terminal device and the random access preamble code corresponding to the third beam.

[0713] In an embodiment of the present application, the transceiver unit 1901 is used to receive resource information corresponding to one or more second beams sent by the first network device; the one or more second beams and the one or more first beams managed by the first network device belong to the same physical cell; the second network device is a device for accessing the physical cell; the processing unit 1902 is used to provide communication services for terminal devices requesting access to the one or more second beams based on the resource information. The first network device configures the resource information of one or more second beams for the second network device, so that the second network device manages the one or more second beams of the physical cell and is responsible for providing access services and resource scheduling for terminal devices requesting access to the one or more second beams. Since the second network device manages one or more second beams of the physical cell, which is not a new physical cell, there is no need to allocate a new PCI, thereby avoiding the problem of PCI conflicts that are prone to occur in a large number of deployed sites due to a PCI being shared by different adjacent physical cells.

[0714] This application also provides a first network device, see Figure 20 , another structural diagram of the first network device 2000 in the embodiment of the present application, the first network device 2000 can be used to perform Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A For the steps executed by the first network device in the illustrated embodiment, reference may be made to the relevant descriptions in the above method embodiment.

[0715] The network device 2000 includes a processor 2001 , a memory 2002 , and a transceiver 2003 .

[0716] In a possible implementation, the processor 2001, the memory 2002, and the transceiver 2003 are connected via buses, and computer instructions are stored in the memory.

[0717] The processing unit 1801 in the aforementioned embodiment may specifically be the processor 2001 in this embodiment, so the specific implementation of the processor 2001 is not repeated. The transceiver unit 1802 in the aforementioned embodiment may specifically be the transceiver 2003 in this embodiment, so the specific implementation of the transceiver 2003 is not repeated.

[0718] This application also provides a second network device, see Figure 21 , another structural diagram of the second network device 2100 in the embodiment of the present application, the second network device 2100 can be used to perform Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A For the steps performed by the second network device in the illustrated embodiment, reference may be made to the relevant descriptions in the above method embodiment.

[0719] The network device 2100 includes a processor 2101 , a memory 2102 , and a transceiver 2103 .

[0720] In a possible implementation, the processor 2101, the memory 2102, and the transceiver 2103 are respectively connected via a bus, and the memory stores computer instructions.

[0721] The processing unit 1902 in the aforementioned embodiment may specifically be the processor 2101 in this embodiment, so the specific implementation of the processor 2101 is not repeated. The transceiver unit 1901 in the aforementioned embodiment may specifically be the transceiver 2103 in this embodiment, so the specific implementation of the transceiver 2103 is not repeated.

[0722] See also Figure 22 The embodiment of the present application also provides a communication system, which includes Figure 18 The first network device shown and Figure 19 The second network device shown. Figure 18 The first network device is used to perform Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A In the illustrated embodiment, all or part of the steps are performed by the first network device. Figure 19 The second network device shown is used to perform Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A In the illustrated embodiment, all or part of the steps are performed by the second network device.

[0723] The embodiment of the present application also provides a computer program product including instructions, which, when executed on a computer, enables the computer to execute the above Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A The communication method of the embodiment shown.

[0724] The embodiment of the present application also provides a computer-readable storage medium, including computer instructions, which, when executed on a computer, causes the computer to execute the above-mentioned Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A The communication method of the embodiment shown.

[0725] The embodiment of the present application also provides a chip device, including a processor, which is connected to a memory and calls a program stored in the memory so that the processor executes the above Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A The communication method of the embodiment shown.

[0726] The processor mentioned in any of the above can be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the above Figure 3 、 Figure 4A 、 Figure 5 、 Figure 6A 、 Figure 7A 、 Figure 7C 、 Figure 8 、 Figure 9A 、 Figure 10A 、 Figure 11 、 Figure 12 、 Figure 13A 、 Figure 14 A. Figure 15A 、 Figure 16A and Figure 17A The integrated circuit for executing the program of the communication method of the embodiment shown. The memory mentioned in any of the above places can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM), etc.

[0727] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0728] In the several embodiments provided in this 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 schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0729] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0730] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0731] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computing device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk.

[0732] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A communication method, characterized in that: The method comprises: The first network device determines that the first network device manages one or more first beams and the second network device manages one or more second beams, wherein the one or more first beams and the one or more second beams belong to the same physical cell, and the second network device is a device accessing the physical cell; Determining, by the first network device, resource information corresponding to the one or more second beams; The first network device sends the resource information to the second network device, and the resource information is used by the second network device to provide communication services for terminal devices requesting access to the one or more second beams.

2. The method according to claim 1, characterized in that The resource information includes at least one of the following: The identifiers corresponding to the one or more second beams, the preamble code sequence number set corresponding to each second beam, and the random access channel time-frequency resource information corresponding to each second beam.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The first network device sends at least one of the following to the second network device: System information SI, time-frequency resource information corresponding to the system information SI, time-frequency resource information corresponding to the demodulation reference signal DMRS, time-frequency resource information corresponding to the channel state information reference signal CSI-RS, cell radio network temporary identifier C-RNTI set, control resource set CORESET time-frequency resource information, and scheduling time-frequency resource information.

4. The method according to any one of claims 1 to 2, characterized in that The method further comprises: The first network device receives capability information of the second network device from the second network device; The capability information includes at least one of the following: Information used to indicate that the second network device is an access point type device, and the transmission power of the second network device.

5. The method according to claim 4, characterized in that The capability information also includes at least one of the following: The number of transmitting and receiving antennas, location information, number of supported beams, number of terminal devices supported for access, and size of the requested time-frequency resources of the second network device.

6. The method according to claim 5, characterized in that The first network device determines that the first network device manages one or more first beams and the second network device manages one or more second beams, including: The first network device determines, according to the capability information, that the one or more second beams are managed by the second network device.

7. The method according to claim 5, characterized in that The method further comprises: The first network device receives the location information and a beam measurement result of the second network device, where the beam measurement result includes a beam measurement result obtained by the second network device measuring the beam of the physical cell; The first network device determines that the first network device manages one or more first beams and the second network device manages one or more second beams, including: The first network device determines, based on the capability information and the beam measurement result, that the second network device manages the one or more second beams.

8. A communication method, characterized in that: The method comprises: The second network device receives resource information corresponding to one or more second beams from the first network device, where the one or more second beams and the one or more first beams managed by the first network device belong to the same physical cell, and the second network device is a device accessing the physical cell; The second network device provides communication services for terminal devices requesting access to the one or more second beams based on the resource information.

9. The method according to claim 8, characterized in that The resource information includes at least one of the following: The identifiers corresponding to the one or more second beams, the contention-based preamble code sequence number set corresponding to each second beam, and the random access channel time-frequency resource information corresponding to each second beam.

10. The method according to claim 8 or 9, characterized in that The method further comprises: The second network device receives at least one of the following from the first network device: System information SI, time-frequency resource information corresponding to the system information SI, time-frequency resource information corresponding to the demodulation reference signal DMRS, time-frequency resource information corresponding to the channel state information reference signal CSI-RS, cell radio network temporary identifier C-RNTI set, control resource set CORESET time-frequency resource information, and scheduling time-frequency resource information.

11. The method according to any one of claims 8 to 9, characterized in that The method further comprises: The second network device sends the capability information of the second network device to the first network device; The capability information includes at least one of the following: Information used to indicate that the second network device is an access point type device, and the transmission power of the second network device.

12. The method according to claim 11, characterized in that The capability information also includes at least one of the following: The number of transmitting and receiving antennas, location information, number of supported beams, number of terminal devices supported for access, and size of the requested time-frequency resources of the second network device.

13. The method according to any one of claims 8 to 9, characterized in that The method further comprises: The second network device sends the location information and beam measurement result of the second network device to the first network device, where the beam measurement result includes a beam measurement result obtained by the second network device measuring the beam of the physical cell.

14. A first network device, characterized in that: The first network device includes: a processing unit, configured to determine that the first network device manages one or more first beams and the second network device manages one or more second beams, wherein the one or more first beams and the one or more second beams belong to the same physical cell, and the second network device is a device accessing the physical cell; and determine resource information corresponding to the one or more second beams; A transceiver unit is used to send the resource information to the second network device, and the resource information is used by the second network device to provide communication services for terminal devices requesting access to the one or more second beams.

15. The first network device according to claim 14, characterized in that: The resource information includes at least one of the following: The identifiers corresponding to the one or more second beams, the preamble code sequence number set corresponding to each second beam, and the random access channel time-frequency resource information corresponding to each second beam.

16. The first network device according to claim 14 or 15, characterized in that: The transceiver unit is further configured to: Send at least one of the following to the second network device: System information SI, time-frequency resource information corresponding to the system information SI, time-frequency resource information corresponding to the demodulation reference signal DMRS, time-frequency resource information corresponding to the channel state information reference signal CSI-RS, cell radio network temporary identifier C-RNTI set, control resource set CORESET time-frequency resource information, and scheduling time-frequency resource information.

17. The first network device according to any one of claims 14 to 15, characterized in that: The transceiver unit is further configured to: receiving capability information of the second network device from the second network device; The capability information includes at least one of the following: Information used to indicate that the second network device is an access point type device, and the transmission power of the second network device.

18. The first network device according to claim 17, characterized in that: The capability information also includes at least one of the following: The number of transmitting and receiving antennas, location information, number of supported beams, number of terminal devices supported for access, and size of the requested time-frequency resources of the second network device.

19. The first network device according to claim 18, characterized in that The processing unit is specifically configured to: Determine, according to the capability information, that the one or more second beams are managed by the second network device.

20. The first network device according to claim 18, wherein: The transceiver unit is further configured to: receiving the location information and a beam measurement result of the second network device, where the beam measurement result includes a beam measurement result obtained by the second network device measuring the beam of the physical cell; The processing unit is specifically configured to: Determine, based on the capability information and the beam measurement result, that the second network device manages the one or more second beams.

21. A second network device, characterized in that: The second network device includes: a transceiver unit, configured to receive resource information corresponding to one or more second beams from a first network device, where the one or more second beams and the one or more first beams managed by the first network device belong to the same physical cell, and the second network device is a device accessing the physical cell; A processing unit is used to provide communication services for terminal devices requesting access to the one or more second beams based on the resource information.

22. The second network device according to claim 21, characterized in that The resource information includes at least one of the following: The identifiers corresponding to the one or more second beams, the contention-based preamble code sequence number set corresponding to each second beam, and the random access channel time-frequency resource information corresponding to each second beam.

23. The second network device according to claim 21 or 22, characterized in that: The transceiver unit is further configured to: Receive at least one of the following from the first network device: System information SI, time-frequency resource information corresponding to the system information SI, time-frequency resource information corresponding to the demodulation reference signal DMRS, time-frequency resource information corresponding to the channel state information reference signal CSI-RS, cell radio network temporary identifier C-RNTI set, control resource set CORESET time-frequency resource information, and scheduling time-frequency resource information.

24. The second network device according to any one of claims 21 to 22, characterized in that: The transceiver unit is further configured to: Sending capability information of the second network device to the first network device; The capability information includes at least one of the following: Information used to indicate that the second network device is an access point type device, and the transmission power of the second network device.

25. The second network device according to claim 24, characterized in that The capability information also includes at least one of the following: The number of transmitting and receiving antennas, location information, number of supported beams, number of terminal devices supported for access, and size of the requested time-frequency resources of the second network device.

26. The second network device according to any one of claims 21 to 22, characterized in that: The transceiver unit is further configured to: Send the location information and beam measurement result of the second network device to the first network device, where the beam measurement result includes the beam measurement result obtained by the second network device measuring the beam of the physical cell.

27. A network device, characterized in that: The network device includes a processor, which is used to call a computer program or computer instruction in a memory, so that the network device executes the method according to any one of claims 1 to 7; or, the network device executes the method according to any one of claims 8 to 13.

28. A computer-readable storage medium, characterized in that The method comprises computer instructions, which, when executed on a computer, cause the computer to execute the method according to any one of claims 1 to 7; or cause the computer to execute the method according to any one of claims 8 to 13.

Images