It should be further understood that the terms “first”, “second”, and “third” in the embodiments of this application are used for distinguishing purposes only, and should not be construed as any limitation on this application. For example, a “first control resource set” in the embodiments of this application represents a set of downlink control channels.

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

It should be noted that, in the embodiments of this application, “preset” or “preconfiguration” may be implemented by pre-storing corresponding code or a corresponding table in a device (for example, the terminal device or the network device) or in another manner that can be used to indicate related information. A specific implementation of “preset” or “preconfiguration” is not limited in this application.

It should be further noted that the term “and/or” describes an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. The character “/” usually indicates an “or” relationship between the associated objects.