COMMUNICATION METHOD AND APPARATUS

Abstract

A communication method includes receiving, by a first terminal device, first information sent by a second terminal device. The first information includes information indicating a second beam selected by the second terminal device. The communication method also includes sending, by the first terminal device, (1) identification information of the second terminal device, or (2) identification information and the first information, to a network device. The first terminal device is a cluster head node, and the second terminal device is a member node of a cluster to which the first terminal device belongs.

Claims

1. A communication method, comprising: receiving, by a first terminal device, first information sent by a second terminal device, wherein the first information comprises information indicating a second beam selected by the second terminal device; and sending, by the first terminal device, (1) identification information of the second terminal device, or (2) identification information and the first information, to a network device, wherein the first terminal device is a cluster head node, and the second terminal device is a member node of a cluster to which the first terminal device belongs.

2. The communication method according to claim 1, wherein the sending, by the first terminal device, of the (1) identification information of the second terminal device, or the (2) identification information and the first information, to the network device, comprises: determining, by the first terminal device based on second information, whether (1) to send the identification information to the network device or (2) to send the identification information and the first information to the network device, wherein the second information is information required for determining whether the first terminal device is to forward downlink data that is sent by the network device to the second terminal device.

3. The communication method according to claim 2, further comprising: sending, by the first terminal device, the second information to the network device, and the sending, by the first terminal device, of the (1) identification information of the second terminal device, or the (2) identification information and the first information, to the network device, further comprises: receiving, by the first terminal device, first indication information of the network device.

4. The communication method according to claim 2, wherein the first information further comprises one or more of: a quality of a sidelink channel between the first terminal device and the second terminal device, a quality of a downlink channel between the second terminal device and the network device, or third information of the second terminal device, wherein the third information indicates that the second terminal device expects to receive the downlink data sent by the network device, or that the second terminal device expects to receive the downlink data forwarded by the first terminal device.

5. The communication method according to claim 4, wherein the second information comprises one or more of: the quality of the sidelink channel between the first terminal device and the second terminal device, a quality of a downlink channel between the first terminal device and the network device, the quality of the downlink channel between the second terminal device and the network device, load information of the first terminal device, or the third information.

6. The communication method according to claim 4, wherein the sending, by the first terminal device, of the (1) identification information of the second terminal device, or the (2) identification information and the first information, to the network device, comprises: in response to the third information in the first information indicating that the second terminal device expects to receive the downlink data sent by the network device, sending, by the first terminal device, the identification information of the second terminal device and the first information to the network device; and in response to the third information in the first information indicating that the second terminal device expects to receive the downlink data forwarded by the first terminal device, sending, by the first terminal device, the identification information to the network device.

7. The communication method according to claim 1, wherein the sending, by the first terminal device, of the (2) identification information and the first information to the network device comprises: sending, by the first terminal device, the identification information to the network device on a time-frequency resource associated with the second beam selected by the second terminal device.

8. The communication method according to claim 1, further comprising: sending, by the first terminal device, second indication information to the second terminal device, wherein the second indication information indicates that downlink data of the second terminal device is to be sent by the network device, or the second indication information indicates that the downlink data of the second terminal device is to be forwarded by the first terminal device.

9. A communication method, comprising: sending, by a second terminal device, first information to a first terminal device based on a measurement result of a beam of a network device, wherein the first information indicates information about a second beam selected by the second terminal device; and receiving, by the second terminal device, downlink data sent by the network device or that is from the network device and that is forwarded by the first terminal device, wherein the first terminal device is a cluster head node, and the second terminal device is a member node of a cluster to which the first terminal device belongs.

10. The communication method according to claim 9, further comprising: receiving, by the second terminal device, second indication information, wherein the second indication information indicates whether the first terminal device is to forward the downlink data of the second terminal device; and receiving, by the second terminal device based on the second indication information, the downlink data sent by the network device or that is from the network device and that is forwarded by the first terminal device.

11. The communication method according to claim 9, wherein the first information comprises one or more of: a quality of a sidelink channel between the first terminal device and the second terminal device, a quality of a downlink channel between the second terminal device and the network device, or third information of the second terminal device, wherein the third information indicates that the second terminal device expects to receive the downlink data sent by the network device, or that the second terminal device expects to receive the downlink data forwarded by the first terminal device.

12. The communication method according to claim 11, wherein the method further comprises: in response to the third information in the first information indicating that the second terminal device expects to receive the downlink data sent by the network device, receiving, by the second terminal device, the downlink data sent by the network device; and in response to the third information in the first information indicating that the second terminal device expects to receive the downlink data forwarded by the first terminal device, receiving, by the second terminal device, the downlink data forwarded by the first terminal device.

13. A communication apparatus, comprising: a processor; and a non-transitory computer-readable storage medium having instructions stored thereon that, when executed by the processor, cause the communication apparatus to: receive first information sent by a second terminal device, wherein the first information comprises information indicating a second beam selected by the second terminal device; and send (1) identification information of the second terminal device or (2) identification information and the first information, to a network device, wherein the communication apparatus is a cluster head node, and the second terminal device is a member node in a cluster to which the communication apparatus belongs.

14. The communication apparatus according to claim 13, wherein the communication apparatus is further caused to: determine, based on second information, whether (1) to send the identification information to the network device or (2) to send the identification information and the first information to the network device, wherein the second information is information required for determining whether the communication apparatus is to forward downlink data that is sent by the network device to the second terminal device.

15. The communication apparatus according to claim 14, wherein the communication apparatus is further caused to: send the second information to the network device; and wherein the communication apparatus is further caused to send the (1) identification information to the network or the (2) identification information and the first information to the network device based on received first indication information of the network device.

16. The communication apparatus according to claim 14, wherein the first information further comprises one or more of: a quality of a sidelink channel between the communication apparatus and the second terminal device, a quality of a downlink channel between the second terminal device and the network device, or third information of the second terminal device, wherein the third information indicates that the second terminal device expects to receive the downlink data sent by the network device, or that the second terminal device expects to receive the downlink data forwarded by the communication apparatus.

17. The communication apparatus according to claim 16, wherein the second information comprises one or more of: the quality of the sidelink channel between the communication apparatus and the second terminal device, a quality of a downlink channel between the communication apparatus and the network device, the quality of the downlink channel between the second terminal device and the network device, load information of the communication apparatus, or the third information, wherein the third information.

18. The communication apparatus according to claim 16, wherein the communication apparatus is further caused to: in response to the third information in the first information indicating that the second terminal device expects to receive the downlink data sent by the network device, send the identification information of the second terminal device and the first information to the network device; and in response to the third information in the first information indicating that the second terminal device expects to receive the downlink data forwarded by the communication apparatus, send the identification information to the network device.

19. The communication apparatus according to claim 13, wherein the communication apparatus is further caused to: send the identification information to the network device on a time-frequency resource associated with the second beam selected by the second terminal device.

20. The communication apparatus according to claim 13, wherein the communication apparatus is further caused to: send second indication information to the second terminal device, wherein the second indication information indicates that downlink data of the second terminal device is to be sent by the network device, or the second indication information indicates that the downlink data of the second terminal device is to be forwarded by the communication apparatus.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0038] FIG. 1 is a first schematic diagram of a communication system according to an embodiment of this application;

[0039] FIG. 2 is a second schematic diagram of a communication system according to an embodiment of this application;

[0040] FIG. 3 is a first example flowchart of a communication method according to an embodiment of this application;

[0041] FIG. 4 is a schematic diagram of a second beam according to an embodiment of this application;

[0042] FIG. 5 is a second example flowchart of a communication method according to an embodiment of this application;

[0043] FIG. 6A and FIG. 6B are a third example flowchart of a communication method according to an embodiment of this application;

[0044] FIG. 7A and FIG. 7B are a fourth example flowchart of a communication method according to an embodiment of this application;

[0045] FIG. 8 is a fifth example flowchart of a communication method according to an embodiment of this application;

[0046] FIG. 9A and FIG. 9B are a sixth example flowchart of a communication method according to an embodiment of this application;

[0047] FIG. 10 is a first schematic diagram of a communication apparatus according to an embodiment of this application;

[0048] FIG. 11 is a schematic diagram of a terminal device according to an embodiment of this application;

[0049] FIG. 12 is a second schematic diagram of a communication apparatus according to an embodiment of this application; and

[0050] FIG. 13 is a block diagram of a communication apparatus according to an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

[0051] The following describes some terms in embodiments of this application, to facilitate understanding of a person skilled in the art.

[0052] (1) A cluster is a set including a plurality of terminal devices that have an association relationship. For example, the association relationship between the terminal devices in the cluster may mean that configured control information retrieval resources are the same, configured radio network temporary identifiers (RNTIs) are the same, geographical locations are similar, owners are the same, and service types are the same.

[0053] (2) A cluster head node is a most crucial terminal device in a cluster, and functions of the cluster head node include but are not limited to forwarding data sent by a base station to a cluster member, assisting the cluster member in sending data to the base station, scheduling data receiving and sending of the cluster member terminal, and configuring a data transmission resource for the cluster member terminal.

[0054] (3) A cluster member node is a terminal device other than a cluster head node in a cluster.

[0055] (4) The terms “system” and “network” may be used interchangeably in embodiments of this application. The term “a plurality of” means two or more, and another quantifier is similar to this. The term “and/or” describes an association relationship between associated objects and indicates that three relationships may exist. For example, A and/or B may indicate the following three cases: Only A exists, both A and B exist, and only B exists. In addition, an element that appears in singular forms “a”, “an”, and “the” does not mean “one or only one” unless otherwise specified in the context, but means “one or more”. For example, “a device” means one or more such devices. Further, “at least one of . . . ” means one or any combination of subsequent associated objects. For example, “at least one of A, B, and C” includes A, B, C, AB, AC, BC, or ABC.

[0056] Technical solutions in embodiments of this application may be applied to various communication systems, for example, a long term evolution (LTE) system, a worldwide interoperability for microwave access (WiMAX) communication system, a future 5th generation (5G) system such as a new radio access technology (NR), and a future communication system such as a 6G system.

[0057] All aspects, embodiments, or features are presented in this application by describing a system that may include a plurality of devices, components, modules, and the like. It should be appreciated and understood that, each system may include another device, component, module, and the like, and/or may not include all devices, components, modules, and the like discussed with reference to the accompanying drawings. In addition, a combination of these solutions may be used.

[0058] A network architecture and a service scenario described in embodiments of this application are intended to describe the technical solutions in embodiments of this application more clearly, and do not constitute a limitation on the technical solutions provided in embodiments of this application. A person of ordinary skill in the art may know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided in embodiments of this application are also applicable to similar technical problems.

[0059] Embodiments of this application may be applied in a conventional typical network or a future UE-centric network. A non-cell network architecture is introduced to the UE-centric network. In some embodiments, a large quantity of small cells are deployed in a specific area to form a hyper cell. Each small cell is a transmission point (TP) or a transmission reception point (TRP) of the hyper cell, and is connected to a centralized controller. When UE moves in the hyper cell, a network side device selects a new sub-cluster for the UE to serve the UE, to avoid real cell handover, and implement UE service continuity. The network side device includes a wireless network device. Alternatively, in the UE-centric network, a plurality of network side devices such as small cells may have independent controllers such as distributed controllers. Each small cell can independently schedule a user, and information is exchanged between small cells for a long time, so that the small cell can provide a coordinated service for the UE flexibly to some extent.

[0060] In embodiments of this application, different base stations may be base stations having different identifiers, or may be base stations that have a same identifier and that are deployed at different geographical locations. Before a base station is deployed, the base station does not know whether the base station is related to the scenario to which embodiments of this application are applied. Therefore, before deployment, the base station or a baseband chip supports a method provided in embodiments of this application. It may be understood that the foregoing base stations having the different identifiers may be base station identifiers, or may be cell identifiers or other identifiers.

[0061] In embodiments of this application, an NR network scenario in a wireless communication network is used as an example to describe some scenarios. It should be noted that the solutions in embodiments of this application may alternatively be applied to another wireless communication network, and a corresponding name may be replaced with a name of a corresponding function in the another wireless communication network.

[0062] The technical solutions provided in embodiments of this application may be applied to wireless communication between communication devices. The wireless communication between communication devices may include wireless communication between a network device and a terminal device, wireless communication between network devices, and wireless communication between terminal devices. In embodiments of this application, the term “wireless communication” may be referred to as “communication” for short, and the term “communication” may also be described as “data transmission”, “information transmission”, or “transmission”.

[0063] For ease of understanding embodiments of this application, a communication system shown in FIG. 1 is first used as an example to describe in detail a communication system applicable to embodiments of this application. FIG. 1 is a schematic diagram of a communication system applicable to a communication method according to an embodiment of this application. As shown in FIG. 1, the communication system 100 includes a terminal device 101 and a terminal device 103. A plurality of antennas may be configured for the terminal device 101 and the terminal device 103. Optionally, the communication system may further include a terminal device 105, and a plurality of antennas may be configured for the terminal device 105.

[0064] The terminal device in this application includes a device that provides a voice and/or data connectivity for a user. The terminal device includes a device that provides a voice for the user, includes a device that provides data connectivity for the user, or includes a device that provides a voice and data connectivity for the user. For example, the terminal device may include a handheld device having a wireless connection function, or a processing device connected to a wireless modem. The terminal may communicate with a core network through a radio access network (RAN), and exchange a voice or data with the RAN, or exchange a voice and data with the RAN. The terminal may include user equipment ( ) a wireless terminal, a mobile terminal, a device-to-device communication (D2D) terminal, a vehicle-to-everything (V2X) terminal, a machine-to-machine/machine type communication (M2M/MTC) terminal, an internet of things (IoT) terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, an access point (AP), a remote terminal, an access terminal, a user terminal, a user agent, a user device, or the like. For example, the terminal may include a mobile phone (or referred to as a “cellular” phone), a computer with a mobile terminal, or a portable, pocket-sized, handheld, or computer built-in mobile apparatus. For example, the terminal may be a device such as a personal communications service (PCS) phone, a cordless telephone set, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, or a personal digital assistant (PDA). The terminal may alternatively include a limited device, for example, a device with low power consumption, a device with a limited storage capability, or a device with a limited computing capability. For example, the terminal includes an information sensing device such as a barcode, radio frequency identification (RFID), a sensor, a global positioning system (GPS), or a laser scanner.

[0065] By way of example and not limitation, in embodiments of this application, the terminal may alternatively be a wearable device. The wearable device may also be referred to as a wearable intelligent device, an intelligent wearable device, or the like, and is a general term of wearable devices that are intelligently designed and developed for daily wear by using a wearable technology, for example, glasses, gloves, watches, clothes, and shoes. The wearable device is a portable device that can be directly worn on the body or integrated into clothes or an accessory of a user. The wearable device is not only a hardware device, but also implements a powerful function through software support, data exchange, and cloud interaction. In a broad sense, wearable intelligent devices include full-featured and large-sized devices that can implement all or a part of functions without depending on smartphones, for example, smart watches or smart glasses, and include devices that are dedicated to only one type of application function and collaboratively work with other devices such as smartphones, for example, various smart bands, smart helmets, or smart jewelry for monitoring physical signs.

[0066] If the various terminals described above are located on a vehicle (for example, placed in the vehicle or installed in the vehicle), the terminals may be considered as vehicle-mounted terminals. For example, the vehicle-mounted terminals are also referred to as on board units (OBUs).

[0067] In embodiments of this application, an apparatus configured to implement a function of a terminal may be a terminal, or may be an apparatus, for example, a chip system, that can support the terminal in implementing the function. The apparatus may be installed in the terminal. In embodiments of this application, the chip system may include a chip, or may include a chip and another discrete component. In the technical solutions provided in embodiments of this application, the technical solutions provided in embodiments of this application are described by using an example in which the apparatus configured to implement the function of the terminal is the terminal

[0068] In this embodiment of this application, the terminal device 101, the terminal device 103, and the terminal device 105 may form a cluster, the terminal device 101 may be a cluster head node, and the terminal device 103 and the terminal device 105 may be cluster member nodes. In the communication system 100, the terminal device 101 may perform data transmission with the terminal device 103 and the terminal device 105. For example, the terminal device 101 may send data to the terminal device 103 and the terminal device 105, and the terminal device 103 and the terminal device 105 may send data to the terminal device 101.

[0069] As shown in FIG. 2, the communication system may further include a network device 102. The network device in this application includes, for example, an access network (AN) device such as a base station (for example, an access point), and may be a device that communicates with a wireless terminal over an air interface through one or more cells in an access network. Alternatively, for example, a network device in a vehicle-to-everything (V2X) technology is a road side unit (RSU). The base station may be configured to mutually convert a received over-the-air frame and an IP packet, and serve as a router between the terminal and a remaining part of the access network. The remaining part of the access network may include an IP network. The RSU may be a fixed infrastructure entity supporting a V2X application, and may exchange a message with another entity supporting the V2X application. The network device may further coordinate attribute management of the air interface. For example, the network device may include an evolved NodeB (NodeB, eNB, or e-NodeB, evolved NodeB) in a long term evolution (LTE) system or a long term evolution-advanced (LTE-A) system, may include a next generation NodeB (gNB) in an evolved packet core (EPC) network, a 5th generation (5G) mobile communication technology, or a new radio (new radio, NR) system (referred to as an NR system for short), or may include a central unit (CU) and a distributed unit (DU) in a cloud access network (Cloud RAN) system. This is not limited in embodiments of this application.

[0070] The network device may further include a core network device, and the core network device includes, for example, an access and mobility management function (AMF).

[0071] In embodiments of this application, an apparatus configured to implement a function of the network device may be a network device, or may be an apparatus, for example, a chip system, that can support the network device in implementing the function. The apparatus may be installed in the network device. In the technical solutions provided in embodiments of this application, the technical solutions provided in embodiments of this application are described by using an example in which the apparatus configured to implement the function of the network device is the network device.

[0072] The network device 102 may send data to a terminal device 101, a terminal device 103, or a terminal device 105 in a cluster. When sending the data, the network device 102 may send the data to a cluster head node (terminal device 101), and the cluster head node (terminal device 101) forwards, to cluster member nodes (terminal device 103 and the terminal device 105), the data sent by the network device. Alternatively, when sending the data, the network device 102 may separately send the data to the terminal device 101, the terminal device 103, and the terminal device 105.

[0073] However, in a random access process, the cluster member nodes such as the terminal device 103 and the terminal device 105 do not directly communicate with the network device 102, but form the cluster with the terminal device 101 to implement communication with the network device 102. As a result, the network device 102 cannot learn of beams selected by the cluster member nodes such as the terminal device 103 and the terminal device 105. Consequently, the network device 102 does not know how to communicate with the cluster member nodes.

[0074] Based on the foregoing problem, an embodiment of this application provides a communication method. The communication method in this application may be applied to a wireless communication system, for example, the communication system shown in FIG. 1 or FIG. 2. The communication system may include at least two terminal devices, or may further include at least one network device. The terminal devices may communicate with each other over a wireless air interface, and the network device may also communicate with a communication device over a wireless air interface. For example, the terminal devices may correspond to the terminal device 101 and the terminal device 103 shown in FIG. 1 or FIG. 2, and the network device may correspond to the network device 102 shown in FIG. 2.

[0075] FIG. 3 is an example flowchart of a communication method according to an embodiment of this application from a perspective of device interaction. A first terminal device may be a cluster head node, and a second terminal device may be a cluster member node of a cluster to which the first terminal device belongs. The method may include the following steps.

[0076] Step 301: The second terminal device sends first information to the first terminal device.

[0077] The second terminal device may send the first information to the first terminal device based on measurement results of beam reference signals of beams of a network device. The first terminal device and the second terminal device may separately measure the beam reference signals sent by the network device. The beam reference signal is a reference signal used for beam management, and each beam reference signal corresponds to a beam for sending the beam reference signal. For example, the first terminal device and the second terminal device may separately measure synchronization signal blocks (SSBs) sent by the network device. The first terminal device and the second terminal device may measure one or more of reference signal received power (RSRP), reference signal received quality (RSRQ), or a signal to interference plus noise ratio (SINR) of the beam reference signal. The measurement result of the beam reference signal of the beam may be one or more of the RSRP, the RSRQ, and the SINR that are obtained through measurement, or may be representations of the RSRP, the RSRQ, and the SINR that are obtained through measurement. The first terminal device and the second terminal device may separately select, based on the measurement results, beams from the beams sent by the network device. The beam selected by the first terminal device may be referred to as a first beam, and the beam selected by the second terminal device may be referred to as a second beam. For example, the first terminal device and the second terminal device may separately select beams whose RSRP measurement results are greater than a specified threshold, or separately select beams whose RSRP is the largest.

[0078] In an embodiment, the first information may include information about the second beam selected by the second terminal device. For example, the first information may include an SSB index of an SSB selected by the second terminal device or indication information of the SSB index. The SSB index may be an index of the selected SSB in an SSB set. For example, NR supports a maximum of 64 SSBs, and the first information may include an index of the SSB selected by the second terminal device in the 64 SSBs or indication information of the index of the selected SSB in the 64 SSBs. Alternatively, the SSB index may be an index in a set including a maximum supported quantity of SSBs in a current frequency range or indication information of the index. For example, in a frequency range (FR) 1, when a carrier frequency is less than or equal to X, a maximum supported quantity of SSBs is 4. In this case, the first information may include an index of the SSB selected by the second terminal device in the four SSBs or indication information of the index of the selected SSB in the four SSBs. For another example, in an FR1, when a carrier frequency is greater than X, a maximum supported quantity of SSBs is 8. In this case, the first information may include an index of the SSB selected by the second terminal device in the eight SSBs or indication information of the index of the selected SSB in the eight SSBs. For still another example, in a frequency range FR2, if a maximum supported quantity of SSBs is 64, the first information may include an index of the SSB selected by the second terminal device in the 64 SSBs or indication information of the index of the selected SSB in the 64 SSBs. X herein may be an integer greater than 0. Alternatively, the SSB index may be an index in an SSB set sent by the network device. For example, the network device may use signaling to indicate the sent SSB set. The SSB set may include K SSBs. The first information may include an index of the SSB selected by the second terminal device in the K SSBs or indication information of the index of the selected SSB in the K SSBs. K herein may be an integer greater than 0.

[0079] In another embodiment, the first information may alternatively include a measurement result of a beam reference signal of the second beam selected by the second terminal device, or measurement results of beam reference signals of a plurality of beams selected by the second terminal device. The measurement result may be a quantized measurement result. For example, the measurement result may be identification information of the measurement result, and identification information of each measurement result may correspond to one measurement result range. Alternatively, in the measurement results of the beam reference signals of the plurality of beams included in the first information, a largest or smallest measurement result is an absolute measurement result, and measurement results of beam reference signals of the remaining beams may be differences relative to the largest or smallest measurement result.

[0080] In addition, it should be noted that, if the network device directly sends downlink data to the second terminal device, at least one of a physical downlink shared channel (PDSCH) that carries the downlink data of the second terminal device and a physical downlink control channel (PDCCH) that schedules the PDSCH may have a same quasi co-location (QCL) property of a demodulation reference signal (DMRS) antenna port as one or more beam reference signals of the second beam selected by the second terminal device.

[0081] In this application, the downlink data of the second terminal device may be service data sent by a base station to the second terminal device, or a downlink feedback that is sent by the base station to the second terminal device and that is for uplink transmission or random access of the second terminal device.

[0082] Optionally, the first information may further include at least one of the following:

[0083] Item 1: Quality of a Sidelink Channel Between the First Terminal Device and the Second Terminal Device

[0084] The quality of the sidelink channel herein may be a representation of a measurement result of the sidelink channel measured by the second terminal device. For example, the second terminal device may measure RSRP, RSRQ, or an SINR of the sidelink channel.

[0085] Item 2: Quality of a Downlink Channel Between the Second Terminal Device and the Network Device

[0086] The quality of the downlink channel between the second terminal device and the network device may be a representation of a measurement result of the downlink channel measured by the second terminal device. For example, the second terminal device may measure RSRP, RSRQ, or an SINR of the downlink channel.

[0087] Item 3: Third Information of the Second Terminal Device

[0088] The third information herein may indicate that the second terminal device expects to receive the downlink data sent by the network device, or may indicate that the second terminal device expects to receive the downlink data forwarded by the first terminal device. For example, if the second terminal device expects to communicate with the network device, the third information may indicate that the second terminal device expects to receive the downlink data sent by the network device. If the second terminal device does not expect to communicate with the network device, the third information may indicate that the second terminal device expects to receive the downlink data forwarded by the first terminal device.

[0089] The first information may be carried on a physical sidelink control channel (PSCCH) or a physical sidelink shared channel (PSSCH). The first information may be sent in a form of sideline control information (SCI), or may be sent in a form of a media access control (MAC) control element (CE), or may be sent in a form of a radio resource control (RRC) message.

[0090] Step 302: The first terminal device sends identification information of the second terminal device to the network device, or the first terminal device sends identification information and the first information to the network device.

[0091] If the first terminal device is to forward the downlink data from the network device for the second terminal device, the first terminal device may send the identification information of the second terminal device to the network device, or the first terminal device may send uplink data of the second terminal device to the network device, where the uplink data may include the identification information of the second terminal device. If the network device is to send the downlink data to the second terminal device, the first terminal device may send the identification information of the second terminal device and the first information to the network device, or the first terminal device may send uplink data of the second terminal device and the first information to the network device, where the uplink data may include the identification information of the second terminal device. The identification information of the second terminal device herein may be sent by the second terminal device to the first terminal device. For example, when sending a random access request or the uplink data to the first terminal device, the second terminal device may send the identification information of the second terminal device to the first terminal device.

[0092] In addition, it should be noted that the first terminal device may send the identification information of the second terminal device and the first information to the network device in the following two manners.

[0093] Manner 1: The first terminal device sends the identification information of the second terminal device and the first information to the network device.

[0094] The first information may include an identifier that is reported by the second terminal device and that is of the beam reference signal of the selected second beam. Optionally, the first information may further include the measurement result of the beam reference signal of the second beam selected by the second terminal device. The first terminal device may send the identification information and the first information to the network device on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). For example, the first terminal device may send the first information and the uplink data of the second terminal device to the network device, where the uplink data may carry the identification information of the second terminal device.

[0095] Manner 2: The first terminal device sends the identification information to the network device on a time-frequency resource associated with the second beam selected by the second terminal device. For example, the first terminal device may send the uplink data of the second terminal device to the network device on the time-frequency resource associated with the second beam, where the uplink data includes the identification information of the second terminal device.

[0096] (1) The first terminal device may send the identification information of the second terminal device and the first information to the network device through two-step random access. As shown in FIG. 4, a part of second terminal devices select an SSB 1, and the other part of second terminal devices select an SSB 2. Therefore, when performing random access by using physical random access channels (PRACHs) and preambles that are associated with the SSB 1, the first terminal device may send, to the network device on PUCCHs or PUSCHs that are associated with the PRACHs and the preambles, identification information of one or more second terminal devices that select the SSB 1. One PRACH and one preamble may be selected from the PRACHs and the preambles that are associated with the SSB 1, and the identification information of the second terminal device is sent on a PUCCH or a PUSCH that is associated with the PRACH and the preamble. When performing random access by using PRACHs and preambles that are associated with the SSB 2, the first terminal device may send, to the network device on PUCCHs or PUSCHs that are associated with the PRACHs and the preambles, identification information of one or more second terminal devices that select the SSB 2. One PRACH and one preamble may be selected from the PRACHs and the preambles that are associated with the SSB 2, and the identification information of the second terminal device is sent on a PUCCH or a PUSCH that is associated with the PRACH and the preamble.

[0097] (2) The first terminal device may send the identification information of the second terminal device and the first information to the network device through four-step random access. As shown in FIG. 4, a part of second terminal devices select an SSB 1, and the other part of second terminal devices select an SSB 2. Therefore, the first terminal device may perform random access by using PRACHs and preambles that are associated with the SSB 1. The first terminal device may send, to the network device on a time-frequency resource that is used for scheduling for the first terminal device and that is in a random access response fed back by the network device, identification information of one or more second terminal devices that select the SSB 1. The first terminal device may perform random access by using PRACHs and preambles that are associated with the SSB 2. The first terminal device may send, to the network device on a time-frequency resource that is used for scheduling for the first terminal device and that is in a random access response fed back by the network device, identification information of one or more second terminal devices that select the SSB 2.

[0098] (2) The first terminal device may send the identification information of the second terminal device and the first information to the network device through preconfigured grant transmission. As shown in FIG. 4, a part of second terminal devices select an SSB 1, and the other part of second terminal devices select an SSB 2. The first terminal device may send, to the network device by using PUSCHs and DMRSs that are associated with the SSB 1, identification information of one or more second terminal devices that select the SSB 1. One PUSCH and one DMRS may be selected from the PUSCHs and the DMRSs that are associated with the SSB 1. The first terminal device may send, to the network device by using PUSCHs and DMRSs that are associated with the SSB 2, identification information of one or more second terminal devices that select the SSB 2. One PUSCH and one DMRS may be selected from the PUSCHs and the DMRSs that are associated with the SSB 2. The preconfigured grant transmission means that the network device preconfigures, for a terminal device, a time-frequency resource that can be used for uplink transmission. When the terminal device performs uplink transmission, the terminal device uses the time-frequency resource, and may perform uplink transmission without using a dynamic grant of the network device.

[0099] It should be understood that the identification information of the second terminal device may be a unique identifier of the second terminal device, for example, an international mobile equipment identity (IMEI), a radio network temporary identifier (RNTI), or a temporary mobile subscriber identity (TMSI). Alternatively, the identification information may be identification information of the second terminal device in the cluster. After receiving the identification information of the second terminal device, the network device may determine the time-frequency resource for receiving the identification information of the second terminal device, to further determine the second beam selected by the second terminal device. Based on the foregoing solution, the first terminal device may send the identification information of the second terminal device to the network device on the time-frequency resource associated with the second beam, to save transmission resources.

[0100] Step 303: The network device sends the downlink data of the second terminal device to the second terminal device by using the second beam selected by the second terminal device; or the network device sends the downlink data of the second terminal device to the first terminal device by using a first beam selected by the first terminal device.

[0101] If the downlink data of the second terminal device is to be forwarded by the first terminal device, the network device may send the downlink data of the second terminal device to the first terminal device by using the first beam selected by the first terminal device. The downlink data herein may include the identification information of the second terminal device. The first terminal device may send the downlink data to the corresponding second terminal device.

[0102] If the downlink data of the second terminal device is to be sent by the network device, the network device sends the downlink data of the second terminal device to the second terminal device by using the second beam selected by the second terminal device.

[0103] The foregoing describes the communication method in this embodiment of this application, and the following describes communication apparatuses in this embodiment of this application. The method and the apparatus are based on a same technical concept. The method and the apparatus have similar principles for resolving problems. Therefore, for implementations of the apparatus and the method, refer to each other. Details are not repeated.

[0104] In this embodiment of this application, the cluster head node (for example, the first terminal device), the cluster member node (for example, the second terminal device), or the network device may determine a communication mode between the cluster member node and the network device. In some embodiments, the cluster head node, the cluster member node, or the network device may determine whether the cluster member node is to receive the downlink data sent by the network device or receive downlink data forwarded by the cluster head node. The following separately describes the foregoing three cases.

[0105] Embodiment 1: The cluster head node determines the communication mode between the cluster member node and the network device.

[0106] The first terminal device may determine, based on second information, whether to forward the downlink data from the network device for the second terminal device. The second information herein is information required for determining whether the first terminal device is to forward the downlink data of the second terminal device that is from the network device, and may include at least one of the following:

[0107] Item 1: Quality of the Sidelink Channel Between the First Terminal Device and the Second Terminal Device

[0108] The quality of the sidelink channel herein may be a representation of a measurement result of the sidelink channel that is between the first terminal device and the second terminal device and that is measured by the first terminal device, or may be a representation of a measurement result of the sidelink channel that is between the first terminal device and the second terminal device and that is measured by the second terminal device, where the measurement result is sent by the second terminal device. The measurement result may be at least one of RSRP, RSRQ, or an SINR.

[0109] For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to a first threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device.

[0110] Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to a second threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. The first threshold and the second threshold herein may be determined based on empirical values, or may be preset. The first threshold and the second threshold may be the same or different. This is not specifically limited in this application.

[0111] Item 2: Quality of a Downlink Channel Between the First Terminal Device and the Network Device

[0112] The quality of the downlink channel herein may be represented by a measurement result of the downlink channel that is between the first terminal device and the network device and that is measured by the first terminal device. The measurement result may be at least one of RSRP, RSRQ, or an SINR.

[0113] For example, if the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device.

[0114] Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. The first threshold and the second threshold herein may be determined based on empirical values. The first threshold and the second threshold may be the same or different. This is not specifically limited in this application.

[0115] In an embodiment, the first terminal device may determine, based on the item 1 and the item 2, whether the first terminal device is to forward the downlink data from the network device. For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, and the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, the first terminal device may determine that the first terminal device is to forward the downlink data of the second terminal device that is from the network device.

[0116] Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, and the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data of the second terminal device that is from the network device, or the first terminal device may determine to forward the downlink data of the second terminal device that is from the network device.

[0117] Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, and the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data of the second terminal device that is from the network device, or the first terminal device may determine not to forward the downlink data of the second terminal device that is from the network device.

[0118] Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, and the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, the first terminal device may determine not to forward the downlink data of the second terminal device that is from the network device.

[0119] Item 3: Quality of the Downlink Channel Between the Second Terminal Device and the Network Device

[0120] The quality of the downlink channel herein may be a representation of a measurement result of the downlink channel that is between the second terminal device and the network device and that is measured by the second terminal device, where the measurement result is sent by the second terminal device. The measurement result may be at least one of RSRP, RSRQ, or an SINR.

[0121] For example, if the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. If the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. The first threshold and the second threshold herein may be determined based on empirical values. The first threshold and the second threshold may be the same or different. This is not specifically limited in this application.

[0122] In an embodiment, the first terminal device may determine, based on at least one of the item 1, the item 2, and the item 3, whether to forward the downlink data from the network device for the second terminal device.

[0123] For example, the first terminal device may determine, based on the item 1 and the item 3, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, and the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, and the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, and the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device. Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, and the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device.

[0124] Alternatively, the first terminal device may determine, based on the item 2 and the item 3, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, and the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. Alternatively, if the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, and the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the second threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. Alternatively, if the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the second threshold, and the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device. Alternatively, if the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, and the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device.

[0125] The first terminal device may determine, based on the item 1, the item 2, and the item 3, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, and the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. For another example, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, and the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device.

[0126] Item 4: Load Information of the First Terminal Device

[0127] The load information of the first terminal device herein may refer to a quantity of second terminal devices for which the first terminal device forwards the downlink data from the network device. If load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. If load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. The first threshold and the second threshold herein may be determined based on empirical values. The first threshold and the second threshold may be the same or different. This is not specifically limited in this application.

[0128] In an embodiment, the first terminal device may determine, based on at least one of the item 1 to the item 4, whether to forward the downlink data from the network device for the second terminal device. For example, the first terminal device may determine, based on the quality of the sidelink channel between the first terminal device and the second terminal device and the load information of the first terminal device, whether to forward the downlink data from the network device for the second terminal device. If the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, and the load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. If the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, and the load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device. If the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device.

[0129] The first terminal device may determine, based on the item 2 and the item 4, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. If the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, and the load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. If the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, and the load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device. If the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device.

[0130] The first terminal device may determine, based on the item 3 and the item 4, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. If the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the second threshold, and the load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. For another example, if the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device. For another example, if the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, and the load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device, or may determine not to forward the downlink data from the network device for the second terminal device.

[0131] Alternatively, the first terminal device may determine, based on the item 1, the item 2, and the item 4, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. For another example, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, and the load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device.

[0132] Alternatively, the first terminal device may determine, based on the item 1, the item 3, and the item 4, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. For another example, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the first threshold, the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, and the load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device.

[0133] Alternatively, the first terminal device may determine, based on the item 2, the item 3, and the item 4, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device. For another example, if the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, and the load of the first terminal device is greater than or equal to the first threshold, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device.

[0134] Alternatively, the first terminal device may determine, based on the item 1, the item 2, the item 3, and the item 4, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, and the load of the first terminal device is less than or equal to the second threshold, the first terminal device may determine to forward the downlink data from the network device for the second terminal device.

[0135] Item 5: Third Information

[0136] The third information herein may indicate that the second terminal device expects to receive the downlink data sent by the network device, or may indicate that the second terminal device expects to receive the downlink data forwarded by the first terminal device. For example, if the third information indicates that the second terminal device expects to receive the downlink data sent by the network device, the first terminal device may determine not to forward the downlink data from the network device for the second terminal device. If the third information indicates that the second terminal device expects to receive the downlink data forwarded by the first terminal device, the first terminal device may determine to forward the downlink data from the network device for the second terminal device.

[0137] In an embodiment, the first terminal device may determine, based on at least one of the item 1 to the item 5, whether to forward the downlink data from the network device for the second terminal device. For example, the first terminal device may determine, based on the item 1 and the item 5, the item 2 and the item 5, the item 3 and the item 5, or the item 4 and the item 5, whether to forward the downlink data from the network device for the second terminal device. Alternatively, the first terminal device may determine, based on the item 1, the item 2, and the item 5, or the item 1, the item 2, the item 3, and the item 5, or the item 1, the item 2, the item 3, the item 4, and the item 5, whether to forward the downlink data from the network device for the second terminal device. For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the load of the first terminal device is less than or equal to the second threshold, and the third information indicates that the second terminal device expects to receive the downlink data forwarded by the first terminal device, the second terminal device may determine to forward the downlink data from the network device for the second terminal device.

[0138] In another embodiment, if the first terminal device receives the information about the second beam selected by the second terminal device, or any one of the item 1 to the item 5, the first terminal device may consider by default that the first terminal device is to forward the downlink data from the network device for the second terminal device.

[0139] FIG. 5 is an example flowchart of a communication method according to an embodiment of this application from a perspective of device interaction. The method may include the following steps.

[0140] Step 501: A second terminal device sends first information to a first terminal device.

[0141] The second terminal device may send the first information to the first terminal device based on measurement results of beam reference signals of beams of a network device. Optionally, the second terminal device may further send uplink data to the first terminal device.

[0142] For descriptions of the first information, refer to related descriptions shown in FIG. 3. Details are not described herein again.

[0143] Step 502: The first terminal device sends identification information of the second terminal device to the network device.

[0144] Optionally, the first terminal device may send the uplink data of the second terminal device to the network device.

[0145] In this case, the first terminal device determines to forward downlink data from the network device for the second terminal device. Therefore, the first terminal device may send the identification information of the second terminal device to the network device on an uplink resource corresponding to a first beam selected by the first terminal device.

[0146] Optionally, the first terminal device may send the uplink data of the second terminal device to the network device on the uplink resource corresponding to the first beam selected by the first terminal device.

[0147] Step 503: The network device sends the downlink data of the second terminal device to the first terminal device.

[0148] The downlink data herein may include the identification information of the second terminal device or indication information of the identification information. The first terminal device may determine, based on the identification information or the indication information that is included in the downlink data, a terminal device to which the downlink data belongs. The network device may send the downlink data of the second terminal device to the first terminal device by using the first beam selected by the first terminal device.

[0149] Step 504: The first terminal device detects DCI within a time range T1.

[0150] The time range T1 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application. When detecting the DCI, the first terminal device may search in a detection window based on identification information of the first terminal device and/or cluster identification information. The DCI herein is for scheduling a PDSCH carrying the downlink data of the second terminal device.

[0151] Step 505: The first terminal device sends the downlink data of the second terminal device to the second terminal device within a time range T2.

[0152] The time range T2 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application. The first terminal device may include the downlink data in a PSSCH or a PSCCH.

[0153] Step 502 to step 505 are an example flowchart in which the first terminal device determines to forward the downlink data from the network device for the second terminal device.

[0154] The following step 506 and step 507 are an example flowchart in which the first terminal device determines not to forward downlink data from the network device for the second terminal device.

[0155] Step 506: The first terminal device sends identification information of the second terminal device and the first information to the network device.

[0156] Optionally, the first terminal device may send the uplink data of the second terminal device to the network device.

[0157] The first terminal device may include the identification information and the first information in a PUSCH or a PUCCH. Alternatively, the first terminal device may send the identification information to the network device on a time-frequency resource that is in the first information and that is associated with a second beam selected by the second terminal device.

[0158] Step 507: The network device sends the downlink data to the second terminal device within a time range T3 by using the second beam selected by the second terminal device.

[0159] Optionally, the network device may include the identification information of the second terminal device in the downlink data. For example, the identification information may be carried in a header of a data packet of the downlink data.

[0160] The time range T3 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application.

[0161] Step 508: The second terminal device detects the DCI within the time range T3, and detects SCI within the time range T2.

[0162] Because the second terminal device does not know whether the first terminal device is to forward the downlink data from the network device or the network device is to send the downlink data, the second terminal device detects the DCI and the SCI, to receive the downlink data. The second terminal device may detect the DCI and the SCI in the detection window based on the identification information of the second terminal device and/or the cluster identification information. The DCI is for scheduling the PDSCH carrying the downlink data, and the SCI is for scheduling the PSSCH carrying the downlink data.

[0163] In addition, it should be noted that the first terminal device may send second indication information to the second terminal device. The second indication information herein may indicate that the downlink data of the second terminal device is to be sent by the network device, or the second indication information may indicate that the downlink data of the second terminal device may be forwarded by the first terminal device. If the first terminal device determines to forward the downlink data from the network device for the second terminal device, the second indication information indicates that the downlink data of the second terminal device is to be forwarded by the first terminal device. If the first terminal device determines not to forward the downlink data from the network device for the second terminal device, the second indication information indicates that the downlink data of the second terminal device is to be sent by the network device.

[0164] If the second indication information indicates that the downlink data of the second terminal device is to be forwarded by the first terminal device, the second terminal device may detect the sidelink control information (SCI) within a predefined or preconfigured time range. The SCI is for scheduling the physical sidelink shared channel (PSSCH) carrying the downlink data. If the second indication information indicates that the downlink data of the second terminal device is to be sent by the network device, the second terminal device may detect, within a predefined or preconfigured time range, the DCI including the cluster identification information or the identification information of the second terminal device. The DCI is applicable to scheduling the PDSCH carrying the downlink data.

[0165] FIG. 6A and FIG. 6B are an example flowchart of a communication method according to an embodiment of this application from a perspective of device interaction. The method may include the following steps.

[0166] Step 601 and step 602 may be the same as step 501 and step 502 shown in FIG. 5.

[0167] Step 603: The first terminal device sends second indication information to the second terminal device.

[0168] The second indication information herein may indicate that the downlink data of the second terminal device is to be forwarded by the first terminal device. An execution sequence of step 602 and step 603 is not limited to the sequence shown in FIG. 6A. For example, step 602 and step 603 may be performed simultaneously, or step 603 may be performed before step 602. This is not specifically limited in this application.

[0169] Step 604 to step 606 may be the same as step 503 to step 505 shown in FIG. 5.

[0170] Step 607: The second terminal device detects SCI within the time range T2.

[0171] The time range T2 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application. The second terminal device may search for the SCI in the detection window based on the identification information of the second terminal device and/or cluster identification information. The SCI is for scheduling a PSSCH carrying the downlink data.

[0172] Step 602 to step 607 are an example flowchart in which the first terminal device determines to forward the downlink data from the network device for the second terminal device, and sends the second indication information to the second terminal device.

[0173] The following step 608 to step 610 are an example flowchart in which the first terminal device determines not to forward downlink data from the network device for the second terminal device, and sends second indication information to the second terminal device.

[0174] Step 608: The first terminal device sends identification information of the second terminal device and the first information to the network device.

[0175] The first terminal device may include the identification information and the first information in a PUSCH or a PUCCH. Alternatively, the first terminal device may send the identification information to the network device on a time-frequency resource that is in the first information and that is associated with a second beam selected by the second terminal device.

[0176] Step 609: The first terminal device sends the second indication information to the second terminal device.

[0177] The second indication information herein may indicate that the downlink data of the second terminal device is to be sent by the network device. It should be understood that an execution sequence of step 608 and step 609 is not limited to the sequence shown in FIG. 6B. Step 608 and step 609 may be performed simultaneously, or step 609 may be performed before step 608.

[0178] Step 610: The network device sends the downlink data to the second terminal device within a time range T3 by using the second beam selected by the second terminal device.

[0179] The time range T3 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application.

[0180] Step 611: The second terminal device detects DCI within the time range T3.

[0181] The second terminal device may search for the DCI in a detection window based on the identification information of the second terminal device and/or cluster identification information. The DCI is for scheduling a PDSCH carrying the downlink data.

[0182] Embodiment 2: The second terminal device determines whether the first terminal device is to forward the downlink data from the network device.

[0183] The second terminal device may determine, based on second information, whether the first terminal device is to forward the downlink data from the network device. The second information herein may include the item 1 to the item 4 described in case 1. The second terminal device may determine, based on any one or more of the item 1 to the item 4, whether the downlink data is to be forwarded by the first terminal device.

[0184] For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, the second terminal device may determine that the downlink data is to be forwarded by the first terminal device. Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, the second terminal device may determine that the downlink data is to be sent by the network device. The first threshold and the second threshold herein may be determined based on empirical values. The first threshold and the second threshold may be the same or different. This is not specifically limited in this application.

[0185] For another example, if the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, the second terminal device may determine that the downlink data is to be sent by the network device. If the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the second terminal device may determine that the downlink data is to be forwarded by the first terminal device. The first threshold and the second threshold herein may be determined based on empirical values. The first threshold and the second threshold may be the same or different. This is not specifically limited in this application.

[0186] For another example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, and the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the second terminal device may determine that the downlink data is to be forwarded by the first terminal device. Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, and the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, the second terminal device may determine that the downlink data is to be sent by the network device. Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, and the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, the first terminal device may determine that the downlink data is to be sent by the network device or forwarded by the first terminal device. Alternatively, if the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to a second threshold, and the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the second terminal device may determine that the downlink data is to be sent by the network device or forwarded by the first terminal device.

[0187] In this embodiment of this application, the second terminal device may send third information to the first terminal device. The third information may indicate that the second terminal device expects to receive the downlink data sent by the network device, or the third information may indicate that the second terminal device expects to receive the downlink data forwarded by the first terminal device. Alternatively, if the second terminal device does not send third information to the first terminal device, the first terminal device may consider by default that the first terminal device is to forward the downlink data from the network device for the second terminal device. Alternatively, if the second terminal device does not send third information to the first terminal device, the first terminal device may consider by default that the first terminal device is not to forward the downlink data from the network device for the first terminal device. For example, the third information may be carried in the first information.

[0188] FIG. 7A and FIG. 7B are an example flowchart of a communication method according to an embodiment of this application from a perspective of device interaction. The method may include the following steps.

[0189] Step 701: A second terminal device sends first information to a first terminal device.

[0190] The second terminal device may send the first information to the first terminal device based on measurement results of beam reference signals of beams of a network device. Optionally, the second terminal device may send uplink data to the first terminal device.

[0191] For descriptions of the first information, refer to related descriptions shown in FIG. 3. Details are not described herein again. The second terminal device may determine, based on the measurement results, whether the first terminal device is to forward downlink data from the network device. The following step 702 to step 706 are a procedure of determining that the first terminal device is to forward the downlink data from the network device.

[0192] Step 702: The first terminal device sends identification information of the second terminal device to the network device.

[0193] Optionally, the first terminal device may send the uplink data of the second terminal device to the network device.

[0194] Because the first terminal device does not receive third information that is sent by the second terminal device and that indicates whether the first terminal device is to forward the downlink data from the network device, the first terminal device may consider by default that the second terminal device expects the first terminal device to forward the downlink data from the network device. Alternatively, the first information includes third information, and the third information indicates that the second terminal device expects to receive the downlink data that is from the network device and that is forwarded by the first terminal device. The first terminal device may send the identification information of the second terminal device to the network device by using a first beam selected by the first terminal device.

[0195] Step 703: The network device sends the downlink data of the second terminal device to the first terminal device.

[0196] The downlink data herein may include the identification information of the second terminal device or indication information of the identification information. The first terminal device may determine, based on the identification information or the indication information that is included in the downlink data, a terminal device to which the downlink data belongs.

[0197] Step 704: The first terminal device detects DCI within a time range T1.

[0198] The time range T1 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application. When detecting the DCI, the first terminal device may search in a detection window based on identification information of the first terminal device and/or cluster identification information. The DCI herein is for scheduling a PDSCH carrying the downlink data of the second terminal device.

[0199] Step 705: The first terminal device sends the downlink data of the second terminal device to the second terminal device within a time range T2.

[0200] The time range T2 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application. The first terminal device may include the downlink data in a PSSCH or a PSCCH.

[0201] Step 706: The second terminal device detects SCI within the time range T2.

[0202] The second terminal device may search for the SCI in the detection window based on the identification information of the second terminal device and/or the cluster identification information. The SCI is for scheduling the PSSCH carrying the downlink data.

[0203] The following step 707 to step 709 are an example procedure in which the second terminal device determines that the downlink data is to be sent by the network device.

[0204] Step 707: The first terminal device sends identification information of the second terminal device and the first information to the network device.

[0205] Optionally, the first terminal device may send the uplink data of the second terminal device to the network device.

[0206] Because the first terminal device does not receive third information that is sent by the second terminal device and that indicates whether the first terminal device is to forward the downlink data from the network device, the first terminal device may consider by default that the second terminal device expects to receive the downlink data sent by the network device. Alternatively, the first information includes third information, and the third information indicates that the second terminal device expects to receive the downlink data sent by the network device. The first terminal device may include the identification information and the first information in a PUSCH or a PUCCH. Alternatively, the first terminal device may send the identification information to the network device on a time-frequency resource that is in the first information and that is associated with a second beam selected by the second terminal device.

[0207] Step 708: The network device sends the downlink data to the second terminal device within a time range T3 by using the second beam selected by the second terminal device.

[0208] The time range T3 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application.

[0209] Step 709: The second terminal device detects DCI within the time range T3.

[0210] The second terminal device may search for the DCI in a detection window based on the identification information of the second terminal device and/or cluster identification information. The DCI is for scheduling a PDSCH carrying the downlink data.

[0211] Embodiment 3: The network device determines whether the first terminal device is to forward the downlink data of the second terminal device.

[0212] The network device may receive second information sent by the first terminal device. The second information herein is information required for determining whether the first terminal device is to forward the downlink data of the second terminal device that is from the network device, and may include the item 1 to the item 5 described in case 1. The network device may determine, based on any one or more of the item 1 to the item 5, whether the downlink data of the second terminal device is to be forwarded by the first terminal device.

[0213] For example, if the quality of the sidelink channel between the first terminal device and the second terminal device is greater than or equal to the first threshold, the network device may determine that the downlink data of the second terminal device is to be forwarded by the first terminal device. If the quality of the sidelink channel between the first terminal device and the second terminal device is less than or equal to the second threshold, the network device may determine that the downlink data of the second terminal device is not to be forwarded by the first terminal device.

[0214] For another example, if the quality of the downlink channel between the first terminal device and the network device is greater than or equal to the first threshold, the network device may determine that the downlink data of the second terminal device is to be forwarded by the first terminal device. If the quality of the downlink channel between the first terminal device and the network device is less than or equal to the second threshold, the downlink data of the second terminal device is not to be forwarded by the first terminal device.

[0215] For another example, if the quality of the downlink channel between the second terminal device and the network device is greater than or equal to the first threshold, the network device may determine that the downlink data of the second terminal device is not to be forwarded by the first terminal device. If the quality of the downlink channel between the second terminal device and the network device is less than or equal to the second threshold, the network device may determine that the downlink data of the second terminal device is to be forwarded by the first terminal device.

[0216] FIG. 8 is an example flowchart of a communication method according to an embodiment of this application from a perspective of device interaction. The method may include the following steps.

[0217] Step 801: A second terminal device sends first information to a first terminal device.

[0218] The second terminal device may send the first information to the first terminal device based on measurement results of beam reference signals of beams of a network device. Optionally, the second terminal device may further send uplink data to the first terminal device.

[0219] For descriptions of the first information, refer to related descriptions shown in FIG. 3. Details are not described herein again.

[0220] Step 802: The first terminal device sends identification information of the second terminal device, the first information, and second information to the network device.

[0221] Optionally, the first terminal device may send the uplink data of the second terminal device to the network device.

[0222] The first terminal device may send the identification information, the first information, and the second information to the network device by using a first beam selected by the first terminal device.

[0223] The network device may determine, based on the second information, whether downlink data of the second terminal device is to be forwarded by the first terminal device. The following step 803 to step 805 are an example procedure in which the network device determines that the downlink data of the second terminal device is to be forwarded by the first terminal device.

[0224] Step 803: The network device sends the downlink data of the second terminal device to the first terminal device.

[0225] The network device may send the downlink data of the second terminal device to the first terminal device by using the first beam. The downlink data herein may include the identification information of the second terminal device or indication information of the identification information.

[0226] Step 804: The first terminal device detects DCI within a time range T1.

[0227] The time range T1 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application. When detecting the DCI, the first terminal device may search in a detection window based on identification information of the first terminal device and/or cluster identification information. The DCI herein is for scheduling a PDSCH carrying the downlink data of the second terminal device.

[0228] Step 805: The first terminal device sends the downlink data of the second terminal device to the second terminal device within a time range T2.

[0229] The time range T2 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application. The first terminal device may include the downlink data in a PSSCH or a PSCCH.

[0230] The following step 806 and step 807 are an example flowchart in which the network device determines that the downlink data of the second terminal device is not to be forwarded by the first terminal device.

[0231] Step 806: The network device sends the downlink data to the second terminal device within a time range T3 by using a second beam selected by the second terminal device.

[0232] The time range T3 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application.

[0233] Step 807: The first terminal device detects DCI within the time range T3.

[0234] Because the first terminal device does not know the decision of the network device, in other words, the first terminal device does not know whether the downlink data of the second terminal device is to be forwarded by the first terminal device, the first terminal device still detects the DCI. When detecting the DCI, the first terminal device may search in a detection window based on identification information of the first terminal device and/or cluster identification information. The DCI herein is for scheduling a PDSCH carrying the downlink data of the second terminal device.

[0235] Step 808: The second terminal device detects the DCI within the time range T3, and detects SCI within the time range T2.

[0236] Because the second terminal device does not know whether the first terminal device is to forward the downlink data from the network device or the network device is to send the downlink data, the second terminal device detects the DCI and the SCI, to receive the downlink data. The second terminal device may search for the DCI and the SCI in the detection window based on the identification information of the second terminal device and/or the cluster identification information. The DCI is for scheduling the PDSCH carrying the downlink data, and the SCI is for scheduling the PSSCH or the PSCCH carrying the downlink data.

[0237] In an embodiment, the network device may send third indication information to the first terminal device. The third indication information herein may indicate that the downlink data of the second terminal device is to be forwarded by the first terminal device, or the third indication information may indicate that the downlink data of the second terminal device is to be sent by the network device. Therefore, the first terminal device may further send second indication information to the second terminal device based on the third indication information. If the third indication information indicates that the downlink data of the second terminal device is to be forwarded by the first terminal device, the second indication information indicates that the downlink data of the second terminal device is to be forwarded by the first terminal device. If the third indication information indicates that the downlink data of the second terminal device is to be sent by the network device, the second indication information indicates that the downlink data of the second terminal device is to be sent by the network device.

[0238] Optionally, the network device may send fourth indication information to the second terminal device. The fourth indication information herein may indicate that the downlink data of the second terminal device is to be sent by the network device. For example, if the downlink data of the second terminal device is to be sent by the network device, the network device may send the fourth indication information to the second terminal device. The second terminal device may search for the DCI in the detection window based on the fourth indication information. If the second terminal device does not receive the fourth indication information, the second terminal device may consider by default that the downlink data is to be forwarded by the first terminal device. Therefore, the second terminal device may search for the SCI in the detection window.

[0239] FIG. 9A and FIG. 9B are an example flowchart of a communication method according to an embodiment of this application from a perspective of device interaction. The method may include the following steps.

[0240] Step 901 to step 903 may be the same as step 801 to step 803 shown in FIG. 8.

[0241] Step 904: The network device sends third indication information to the first terminal device.

[0242] The third indication information herein indicates that the downlink data of the second terminal device is to be forwarded by the first terminal device. It should be understood that an execution sequence of step 903 and step 904 is not limited to the sequence shown in FIG. 9A. Step 904 may be performed before step 903, or step 903 and step 904 may be performed simultaneously.

[0243] Step 905 and step 906 may be the same as step 804 and step 805 shown in FIG. 8.

[0244] Step 907: The first terminal device sends second indication information to the second terminal device.

[0245] The second indication information herein may indicate that the downlink data of the second terminal device is to be forwarded by the first terminal device. It should be understood that an execution sequence of step 906 and step 907 is not limited to the sequence shown in FIG. 9A. Step 907 may be performed before step 906, or step 906 and step 907 may be performed simultaneously.

[0246] Step 908: The second terminal device detects SCI within the time range T2.

[0247] The second terminal device may search for the SCI in the detection window based on the identification information of the second terminal device and/or the cluster identification information. The SCI is for scheduling a PSSCH or a PSCCH carrying the downlink data.

[0248] The foregoing step 904 to step 908 are an example procedure in which the network device determines that the first terminal device is to forward the downlink data of the second terminal device, and sends the third indication information to the first terminal device.

[0249] The following step 909 to step 912 are an example procedure in which the network device determines to send the downlink data to the second terminal device, and sends third indication information to the first terminal device.

[0250] Step 909: The network device sends the third indication information to the first terminal device.

[0251] The third indication information herein indicates that the downlink data of the second terminal device is to be sent by the network device. It should be understood that an execution sequence of step 903 and step 909 is not limited to the sequence shown in FIG. 9A and FIG. 9B. Step 909 may be performed before step 903, or step 903 and step 909 may be performed simultaneously.

[0252] Step 910: The network device sends the downlink data to the second terminal device within a time range T3 by using a second beam selected by the second terminal device.

[0253] Step 911: The first terminal device sends second indication information to the second terminal device.

[0254] The second indication information herein may indicate that the downlink data of the second terminal device is to be sent by the network device.

[0255] Step 912: The second terminal device detects DCI within the time range T3.

[0256] The time range T3 herein may be predefined in a protocol, or may be preset. This is not specifically limited in this application. The second terminal device may search for the DCI in a detection window based on the identification information of the second terminal device and/or cluster identification information. The DCI is for scheduling a PDSCH or a PDSCH carrying the downlink data.

[0257] Based on a same technical concept as the foregoing communication method, as shown in FIG. 10, an apparatus 1000 having a communication function is provided. The apparatus 1000 can perform the steps performed by the first terminal device or the second terminal device in the foregoing method. To avoid repetition, details are not described herein again. The apparatus 1000 includes a communication unit 1010 and a processing unit 1020, and optionally, further includes a storage unit 1030. The processing unit 1020 may be separately connected to the storage unit 1030 and the communication unit 1010, or the storage unit 1030 may be connected to the communication unit 1010. The processing unit 1020 may be integrated with the storage unit 1030.

[0258] The storage unit 1030 is configured to store a computer program.

[0259] For example, when the communication apparatus 1000 performs the steps performed by the first terminal device, the communication unit 1010 is configured to receive first information sent by the second terminal device. For descriptions of the first information herein, refer to related descriptions shown in FIG. 3. Details are not described herein again. The communication unit 1010 may send identification information of the second terminal device to a network device, or may send identification information and the first information to a network device.

[0260] In a design, the processing unit 1020 may be configured to determine, based on second information, whether to send the identification information to the network device through the communication unit 1010 or send the identification information and the first information to the network device through the communication unit 1010. For descriptions of the second information, refer to related descriptions shown in FIG. 3. Details are not described herein again.

[0261] In a design, the communication unit 1010 may be configured to send the second information to the network device. The communication unit 1010 may further be configured to receive first indication information of the network device.

[0262] In a design, if third information indicates that the second terminal device expects to receive downlink data sent by the network device, the processing unit 1020 may be configured to send the identification information of the second terminal device and the first information to the network device through the communication unit 1010. If third information indicates that the second terminal device expects to receive downlink data forwarded by the first terminal device, the processing unit 1020 may be configured to send the identification information to the network device through the communication unit 1010.

[0263] In a design, the communication unit 1010 may be configured to: when sending the identification information and the first information to the network device, send the identification information to the network device on a time-frequency resource associated with a second beam selected by the second terminal device.

[0264] In a design, the communication unit 1010 may be configured to send second indication information to the second terminal device. For descriptions of the second indication information, refer to related descriptions shown in FIG. 3.

[0265] For example, when the apparatus 1000 performs the steps performed by the second terminal device, the processing unit 1020 may send first information to the first terminal device based on a measurement result of a beam reference signal of a beam of a network device through the communication unit 1010. For descriptions of the first information, refer to related descriptions in the method embodiment shown in FIG. 3. The communication unit 1010 may receive data. The data is downlink data sent by the network device, or the data is downlink data that is from the network device and that is forwarded by the first terminal device.

[0266] In a design, the communication unit 1010 may be configured to receive second indication information. For descriptions of the second indication information herein, refer to related descriptions shown in FIG. 3. The processing unit 1020 may be configured to receive, through the communication unit 1010 based on the second indication information, the downlink data sent by the network device or the downlink data that is from the network device and that is forwarded by the first terminal device.

[0267] In a design, if third information indicates that the second terminal device expects to receive the downlink data sent by the network device, the communication unit 1010 is configured to receive the downlink data sent by the network device. If third information indicates that the second terminal device expects to receive the downlink data forwarded by the first terminal device, the communication unit 1010 is configured to receive the downlink data forwarded by the first terminal device.

[0268] The apparatus may alternatively be a chip. The communication unit may be an input/output circuit or an interface of the chip. The processing unit may be a logic circuit. The logic circuit may process to-be-processed data based on the steps described in the foregoing method aspects, to obtain processed data. The output circuit/interface is configured to output the processed data.

[0269] An embodiment of this application further provides a terminal device. The terminal device may be a terminal device or a circuit. The terminal device may be configured to perform the actions performed by the first terminal device and the second terminal device in the foregoing method embodiments.

[0270] FIG. 11 is a simplified schematic diagram of a structure of a terminal device. For ease of understanding and ease of illustration, in FIG. 11, an example in which the terminal device is a mobile phone is used. As shown in FIG. 11, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input/output apparatus. The processor is mainly configured to: process a communications protocol and communications data, control the terminal device, execute a software program, process data of the software program, and the like. The memory is mainly configured to store the software program and data. The radio frequency circuit is mainly configured to: perform conversion between a baseband signal and a radio frequency signal, and process the radio frequency signal. The antenna is mainly configured to receive and send a radio frequency signal in a form of an electromagnetic wave. The input/output apparatus, for example, a touchscreen, a display, or a keyboard, is mainly configured to: receive data input by a user and output data to the user. It should be noted that some types of terminal devices may have no input/output apparatus.

[0271] When sending data, after performing baseband processing on the to-be-sent data, the processor outputs a baseband signal to the radio frequency circuit; and the radio frequency circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal to the outside in a form of an electromagnetic wave through the antenna. When data is sent to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data, and processes the data. For ease of description, FIG. 11 shows only one memory and one processor. In an actual terminal device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium, a storage device, or the like. The memory may be disposed independent of the processor, or may be integrated with the processor. This is not limited in embodiments of this application.

[0272] In this embodiment of this application, an antenna and a radio frequency circuit that have sending and receiving functions may be considered as a communication unit of the terminal device, and a processor that has a processing function may be considered as a processing unit of the terminal device. As shown in FIG. 11, the terminal device includes a communication unit 1110 and a processing unit 1120. The communication unit may also be referred to as a transceiver, a transceiver apparatus, or the like. The processing unit may also be referred to as a processor, a processing board, a processing module, a processing apparatus, or the like. Optionally, a component that is in the communication unit 1110 and that is configured to implement the receiving function may be considered as a receiving unit, and a component that is in the communication unit 1110 and that is configured to implement the sending function may be considered as a sending unit. That is, the communication unit 1110 includes the receiving unit and the sending unit. The communication unit sometimes may also be referred to as a transceiver, a transceiver circuit, or the like. The receiving unit sometimes may also be referred to as a receiver, a receive circuit, or the like. The sending unit sometimes may also be referred to as a transmitter, a transmit circuit, or the like.

[0273] It should be understood that the communication unit 1110 is configured to perform a sending operation and a receiving operation on the first terminal device side and the second terminal device side in the foregoing method embodiments, and the processing unit 1120 is configured to perform an operation other than the sending operation and the receiving operation on the first terminal device and the second terminal device in the foregoing method embodiments.

[0274] For example, in an implementation, the communication unit 1110 is configured to perform the sending operation and/or the receiving operation on the first terminal device side and the second terminal device side in step 301 to step 303 in FIG. 3, and/or the communication unit 1110 is further configured to perform other sending and receiving steps on the first terminal device side and the second terminal device side in embodiments of this application. The processing unit 1120 is configured to perform other processing steps on the first terminal device side and the second terminal device side in embodiments of this application.

[0275] When the terminal device is a chip apparatus or circuit, the apparatus may include a communication unit and a processing unit. The communication unit may be an input/output circuit and/or a communication interface. The processing unit is an integrated processor, a microprocessor, or an integrated circuit.

[0276] Based on a same technical concept as the foregoing communication method, as shown in FIG. 12, an apparatus 1200 having a communication function is provided. The apparatus 1200 can perform the steps performed by the network device in the foregoing method. To avoid repetition, details are not described herein again. The apparatus 1200 includes a communication unit 1210 and a processing unit 1220, and optionally, further includes a storage unit 1230. The processing unit 1220 may be separately connected to the storage unit 1230 and the communication unit 1210, or the storage unit 1230 may be connected to the communication unit 1210. The processing unit 1220 may be integrated with the storage unit 1230.

[0277] The storage unit 1230 is configured to store a computer program.

[0278] For example, the communication unit 1210 is configured to receive identification information of a second terminal device that is sent by a first terminal device. For the identification information herein, refer to related descriptions in the method embodiment shown in FIG. 3. Details are not described herein again. The communication unit 1210 is further configured to send downlink data of the second terminal device to the second terminal device by using a second beam selected by the second terminal device, or send, for the network device, downlink data of the second terminal device to the first terminal device by using a first beam selected by the first terminal device.

[0279] In a design, the processing unit 1220 is configured to determine, based on second information, to send the downlink data of the second terminal device to the second terminal device through the communication unit 1210 by using the second beam selected by the second terminal device, or send the downlink data of the second terminal device to the first terminal device through the communication unit 1210 by using the first beam selected by the first terminal device. For the second information herein, refer to related descriptions in the method embodiment shown in FIG. 3. Details are not described herein again.

[0280] In a design, if third information indicates that the second terminal device expects to receive the downlink data sent by the network device, the communication unit 1210 may be configured to send the downlink data of the second terminal device to the second terminal device by using the second beam selected by the second terminal device. If third information indicates that the second terminal device expects to receive the downlink data forwarded by the first terminal device, the communication unit 1210 may be configured to send the downlink data of the second terminal device to the first terminal device by using the first beam selected by the first terminal device.

[0281] In a design, the communication unit 1210 may be configured to receive information about the first beam that is sent by the first terminal device. For the first beam herein, refer to related descriptions in the method embodiment shown in FIG. 3. The processing unit 1220 may be configured to determine, based on the information about the first beam, to send the downlink data of the second terminal device to the first terminal device through the communication unit 1210 by using the first beam selected by the first terminal device.

[0282] In a design, the communication unit 1210 may be configured to receive first information of the second terminal device that is sent by the first terminal device. The first information indicates information about the second beam selected by the second terminal device. For the second beam herein, refer to related descriptions in the method embodiment shown in FIG. 3.

[0283] The processing unit 1220 may be configured to determine, based on the information about the second beam, to send the downlink data of the second terminal device to the second terminal device through the communication unit 1210 by using the second beam selected by the second terminal device.

[0284] The apparatus may alternatively be a chip. The communication unit may be an input/output circuit or an interface of the chip. The processing unit may be a logic circuit. The logic circuit may process to-be-processed data based on the steps described in the foregoing method aspects, to obtain processed data. The to-be-processed data may be data received by the input circuit/interface. The output circuit/interface is configured to output the processed data.

[0285] FIG. 13 shows an apparatus 1300 having a communication function according to an embodiment of this application. The apparatus 1300 is configured to implement functions of the first terminal device, the second terminal device, and the network device in the foregoing methods.

[0286] The apparatus may be the first terminal device, the second terminal device, or the network device, or may be a chip with a function similar to that of the first terminal device, the second terminal device, or the network device, or may be an apparatus that can be used with the first terminal device, the second terminal device, or the network device.

[0287] The apparatus 1300 includes at least one processor 1320, configured to implement the functions of the first terminal device, the second terminal device, and the network device in the methods provided in embodiments of this application. The apparatus 1300 may further include a communication interface 1310. In embodiments of this application, the communication interface may be a transceiver, a circuit, a bus, a module, or a communication interface of another type, and is configured to communicate with another device through a transmission medium. For example, the communication interface 1310 is used by an apparatus in the apparatus 1300 to communicate with another device. When the apparatus 1300 is the first terminal device and the second terminal device, the processor 1320 may complete a function of the processing unit 1020 shown in FIG. 10, and the communication interface 1310 may complete a function of the communication unit 1010 shown in FIG. 10. When the apparatus 1300 is the network device, the processor 1320 may complete a function of the processing unit 1220 shown in FIG. 12, and the communication interface 1310 may complete a function of the communication unit 1210 shown in FIG. 12.

[0288] The apparatus 1300 may further include at least one memory 1330, configured to store program instructions and/or data. The memory 1330 is coupled to the processor 1320. The coupling in this embodiment of this application may be an indirect coupling or a communication connection between apparatuses, units, or modules in an electrical form, a mechanical form, or another form, and is used for information exchange between the apparatuses, the units, or the modules. The processor 1320 may operate in collaboration with the memory 1330. The processor 1320 may execute the program instructions stored in the memory 1330. At least one of the at least one memory may be included in the processor.

[0289] In this embodiment of this application, a specific connection medium between the communication interface 1310, the processor 1320, and the memory 1330 is not limited. In this embodiment of this application, in FIG. 13, the memory 1330, the processor 1320, and the communication interface 1310 are connected through a bus 1340. The bus is represented by a bold line in FIG. 13. A connection manner between other components is merely an example for description, and is not limited thereto. The bus may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one bold line is used to represent the bus in FIG. 13, but this does not mean that there is only one bus or only one type of bus.

[0290] In another form of this embodiment, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions. When the instructions are executed, the method on the network device side, the first terminal device side, or the second terminal device side in the foregoing method embodiments is performed.

[0291] In another form of this embodiment, a computer program product including instructions is provided. When the instructions are executed, the method on the first terminal device side, the second terminal device side, or the network device side in the foregoing method embodiments is performed.

[0292] In another form of this embodiment, a communication system is provided. The system may include the at least one first terminal device, the at least one second terminal device, and the at least one network device.

[0293] It should be understood that the processor may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or a transistor logic device, a discrete hardware component, or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

[0294] It may be understood that the memory may be a volatile memory or a nonvolatile memory, or may include a volatile memory and a nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), used as an external cache. By way of example and not limitation, many forms of RAMs may be used, for example, a static random access memory (Static RAM, SRAM), a dynamic random access memory (Dynamic RAM, DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (Synchlink DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DR RAM).

[0295] It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or another programmable logic device, a discrete gate or a transistor logic device, or a discrete hardware component, the memory (a storage module) is integrated into the processor.

[0296] It should be noted that the memory described in this specification aims to include but is not limited to these memories and any memory of another proper type.

[0297] It should be understood that sequence numbers of the foregoing processes do not mean execution sequences in various embodiments of this application. The execution sequences of the processes should be determined according to functions and internal logic of the processes, and should not be construed as any limitation on the implementation processes of the discusses embodiments.

[0298] A person of ordinary skill in the art may be aware that, in combination with the examples described in embodiments disclosed in this specification, units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraint conditions of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this application.

[0299] It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, refer to a corresponding process in the foregoing method embodiments. Details are not described herein again.

[0300] In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the described apparatus embodiment is merely an example. For example, division into the units is merely logical function division, and there may be other division during actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms.

[0301] The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one location, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual requirements to achieve the objectives of the solutions of embodiments.

[0302] In addition, functional units in embodiments of this application may be integrated into one processing unit, each of the units may exist independently physically, or two or more units may be integrated into one unit.

[0303] When the functions are implemented in a form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the prior art, or some of the technical solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or some of the steps of the methods described in embodiments of this application. The foregoing storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc.

[0304] The foregoing descriptions are merely specific implementations of this application, but are not intended to limit the protection scope of this application. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.