Patent Description:
In a wireless communications system, a terminal device needs to keep monitoring cells. A component carrier may be divided into a full-capability component carrier and a non-full-capability component carrier based on different manners of monitoring the cell by the terminal device. For a component carrier, how to determine a full-capability component carrier and a non-full-capability component carrier is currently popular research.

<NPL>, describes UE requirements for FR2.

<NPL>, describes UE measurement configuration parameters.

<NPL>, describes restrictions on a number of MOs.

This application provides a communications method and apparatus, to provide a manner of determining a full-capability component carrier or a non-full-capability component carrier.

For ease of understanding, descriptions of concepts related to this application are provided for reference by using examples. Details are as follows:.

The network device and the terminal device may be deployed on land, including an indoor or outdoor device, a handheld device, or a vehicle-mounted device; may be deployed on a water surface; or may be deployed on an aircraft, a balloon, or a satellite in the air. Application scenarios of the network device and the terminal device are not limited in the embodiments of this application.

Communication between the network device and the terminal device and communication between terminal devices may be performed by using a licensed spectrum (licensed spectrum), an unlicensed spectrum (unlicensed spectrum), or both a licensed spectrum and an unlicensed spectrum. A spectrum resource used between the network device and the terminal device is not limited in the embodiments of this application.

(<NUM>) Terminal device: may be a wireless terminal device that can receive scheduling and indication information of a network device. The wireless terminal device may be a device that provides a user with voice and/or data connectivity, a handheld device with a wireless connection function, or another processing device connected to a wireless modem. The wireless terminal device may communicate with one or more core networks or the internet through a radio access network (radio access network, RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or referred to as a "cellular" phone or a mobile phone (mobile phone)), a computer, or a data card, for example, may be a portable, pocket-sized, handheld, computer built-in, or vehicle-mounted mobile apparatus that exchanges language and/or data with the radio access network. For example, the terminal device may be a personal communication service (personal communication service, PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a tablet computer (Pad), a computer with wireless sending and receiving functions, or the like. The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile station), a mobile station (mobile station, MS), a remote station (remote station), an access point (access point, AP), a remote terminal (remote terminal), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), a subscriber station (subscriber station, SS), a customer premises equipment (customer premises equipment, CPE), a terminal (terminal), user equipment (user equipment, UE), a mobile terminal (mobile terminal, MT), or the like. Alternatively, the wireless terminal device may be a wearable device, or a terminal device in a next-generation communications system, for example, a terminal device in a <NUM> network, a terminal device in a future evolved public land mobile network (public land mobile network, PLMN), or a terminal device in an NR communications system.

(<NUM>) Communications system: may use various radio access technologies (radio access technology, RAT), for example, code division multiple access (code division multiple access, CDMA), time division multiple access (time division multiple access, TDMA), frequency division multiple access (frequency division multiple access, FDMA), orthogonal frequency division multiple access (orthogonal frequency division multiple access , OFDMA), and single carrier frequency division multiple access (single carrier FDMA, SC-FDMA). A RAT used in the communications system is not limited in this application. The terms "system" and "network" may be interchangeable in this application. Networks may be classified into a <NUM> (generation) network, a <NUM> network, a <NUM> network, or a future evolved network such as a <NUM> network based on factors such as capacities, rates, or latencies of different networks. A typical <NUM> network includes a global system for mobile communications (global system for mobile communications/general packet radio service, GSM) network or a general packet radio service (general packet radio service, GPRS) network. A typical <NUM> network includes a universal mobile communications system (universal mobile telecommunications system, UMTS) network. A typical <NUM> network includes a long term evolution (long term evolution, LTE) network. A typical <NUM> network includes a new radio access technique (new radio access technique, NR) network. The UMTS network sometimes may also be referred to as a universal terrestrial radio access network (universal terrestrial radio access network, UTRAN), and the LTE network sometimes may also be referred to as an evolved universal terrestrial radio access network (evolved universal terrestrial radio access network, E-UTRAN).

(<NUM>) Full-capacity component carrier (component carrier, CC): The terminal device needs to monitor, on the CC, at least six cells and <NUM> synchronization signal blocks (synchronization signal block, SSB), where the <NUM> SSBs may have different physical cell identifiers (physical cell identifier, PCI) and/or time indexes (time index), the PCIs are used to identify different physical cells, and the time indexes are used to identify different SSBs.

(<NUM>) Non-full-capability CC: The terminal device needs to monitor, on the CC, only at least two SSBs with different SSB time indexes in a serving cell.

(<NUM>) Measurement object (measurement object, MO): includes various configurations related to a reference signal used for measurement, for example, a time-frequency location and a subcarrier spacing indication of the reference signal.

(<NUM>) Reporting configuration (report configuration, RC): includes a specific parameter used by the terminal device to perform measurement. For example, the RC may include a reporting criterion, a type of a reference signal used for measurement, a reporting format, a measurement quantity type, a quantity of reported cell-level measurement quantities, and a quantity of reported beam (beam)-level (beam) measurement quantities. The reporting criterion may be specifically event-based triggering or periodic triggering, the type of the reference signal used for the measurement may be specifically an SSB or a channel state information reference signal (channel state information reference signal, CSI-RS), and the reporting format may specifically report only a cell-level measurement quantity, report only a beam-level measurement quantity, or report both a cell-level measurement quantity and a beam-level measurement quantity.

(<NUM>) Measurement identifier (measure ID, MI): A measurement object is associated with a reporting configuration by using the measurement identifier. The measurement object may notify a terminal device of a configuration for measuring a reference signal, and the reporting configuration notifies the terminal device of a type of measurement performed based on the reference signal. The measurement object is associated with the reporting configuration by using the measurement identifier, so that the terminal device can obtain a complete description of a measurement. One measurement object MO may be associated with one or more reporting configurations RCs, or one reporting configuration RC may be associated with one or more measurement objects MOs. For example, as shown in <FIG>, a measurement object MO <NUM> may be associated with a reporting configuration RC <NUM> by using a measurement identifier MI <NUM>, and a reporting configuration RC <NUM> is associated with a measurement object MO <NUM> by using a measurement identifier MI <NUM>.

(<NUM>) At least one of a or b: may specifically include a, b, and a and b, where a and b each may be in single or plural form.

It may be understood that, in descriptions of this application, words such as "first" and "second" are merely used for distinction and description, and cannot be understood as an indication or implication of relative importance, or an indication or implication of an order.

In the embodiments of this application, the word "example" or "for example" is used to represent giving an example, an illustration, or a description. Any embodiment or design scheme described as an "example" or "for example" in the embodiments of this application shall not be explained as being more preferred or having more advantages than another embodiment or design scheme. Exactly, use of the word such as "example" or "for example" is intended to present a relative concept in a specific manner.

As shown in <FIG>, an embodiment of this application provides a communications system <NUM>. The communications system <NUM> may include a network device <NUM> and a terminal device <NUM>.

In a new radio access technology (new radio access technique, NR), because the terminal device <NUM> moves, the terminal device <NUM> needs to support mobility processes such as cell selection, cell reselection, and a cell handover. In this case, the terminal device <NUM> needs to monitor a cell.

Specifically, a downlink frequency band in which the terminal device <NUM> communicates with the network device <NUM> may include a plurality of component carriers (component carrier, CC). Further, 3GPP defines two parts: a frequency range <NUM> below <NUM> (frequency range <NUM>, FR <NUM>) and a frequency range <NUM> above <NUM> (frequency range <NUM>, FR <NUM>) for a spectrum. A frequency range of the FR <NUM> ranges from <NUM> to <NUM>, and a frequency range of the frequency range <NUM> ranges from <NUM> to <NUM>. The CC may be within the frequency range of the FR <NUM> or the frequency range of the frequency range <NUM>.

For each CC, the terminal device <NUM> needs to monitor at least several cells and synchronization signal blocks (synchronization signal block, SSB). Specifically, when the CC is within the frequency range of the FR <NUM>, 3GPP specifies that the terminal device <NUM> shall monitor at least eight cells and <NUM> SSBs with different physical cell identifiers (physical cell identity, PCI) and/or SSB time indexes (time index) on the CC. When the CC is within the frequency range of the frequency range <NUM>, 3GPP specifies that the terminal device <NUM> needs to monitor, on only one CC, at least six cells and <NUM> SSBs with different PCIs and/or SSB time indexes in each frequency band (band) of the frequency range <NUM>. On another CC in the frequency band belongs to the frequency range <NUM>, only at least two SSBs with different SSB time indexes are monitored in the serving cell.

Based on this, a concept of a full-capability CC and a concept of a non-full-capability CC are defined for the CC within the frequency range of the frequency range <NUM>. For the concept of the full-capability CC, refer to the foregoing concept description (<NUM>). For the concept of the non-full-capability CC, refer to the foregoing concept description (<NUM>).

It is specified in the 3GPP protocol that the terminal device <NUM> may determine, in either one of the following manners, a full-capability CC and a non-full-capability CC from the plurality of CCs included in the downlink frequency band.

Manner <NUM>: If there is a primary component carrier (primary component carrier, PCC) or a primary secondary component carrier (primary secondary component carrier, PSCC) in the CC in the downlink frequency band, it is determined that the PCC or the PSCC is a full-capability CC, and a remaining CC in the downlink frequency band is a non-full-capability CC.

Manner <NUM>: If the downlink frequency band includes only one secondary component carrier (secondary component carrier, SCC), it is determined that the SCC is a full-capability CC.

If the downlink frequency band includes a plurality of SCCs, how to determine a full-capability CC and a non-full-capability CC from the plurality of SCCs is not specified in the 3GPP protocol.

Solution <NUM>: The terminal device <NUM> determines the full-capability CC and the non-full-capability CC by itself.

Because the terminal device measures only the serving cell on the non-full-capability CC, and does not measure a neighboring cell; and cannot support the mobility process such as a handover on the non-full-capability CC. If the terminal device determines the full-capability CC and the non-full-capability CC by itself, the network device <NUM> cannot learn which CC is set by the terminal device <NUM> to the full-capability CC and which CC is set by the terminal device <NUM> to the non-full-capability CC. Further, the network device <NUM> cannot know a specific CC on which the terminal device <NUM> measures a neighboring cell, either, and consequently cannot instruct the terminal device to perform an operation such as cell handover, affecting network scheduling.

Solution <NUM>: The terminal device <NUM> uses a first activated SCC as the full-capability CC. To be specific, when a downlink frequency band belongs to the frequency range <NUM> includes a plurality of SCCs, the terminal device <NUM> uses the first activated SCC as the full-capability SCC.

First, in the NR, the network device may activate a plurality of SCCs at a time. If the network device activates a plurality of SCCs at a time, in other words, the plurality of SCCs are activated at a same time, there is no related solution to how to determine a full-capability CC from the plurality of SCCs.

For example, it is specified in 3GPP that an SCC may be activated in the following manner: The network device <NUM> sends a bit mapping table to the terminal device <NUM>, where in the bit mapping table, a bit whose value is <NUM> corresponds to activation of an SCC, and a bit whose value is <NUM> corresponds to no activation of an SCC. For the bit mapping table, refer to <FIG>. It can be learned from <FIG> that the bit mapping table may include seven bits and one reserved (reserve, R) bit. The seven bits are sequentially C<NUM> to C<NUM>. Values of C<NUM> to C<NUM> may be <NUM> or <NUM>, where a value <NUM> may represent activation of a corresponding SCC, and a value <NUM> may represent no activation of a corresponding SCC.

Further, even if the network device <NUM> activates only one SCC at a time, to determine an SCC activation sequence, the terminal device <NUM> needs to record an SCC activation time, increasing costs of the terminal device <NUM>.

Solution <NUM>: The network device <NUM> configures an MO only for a full-capability CC, but not for a non-full-capability CC. The terminal device <NUM> may determine, based on whether an MO is configured for an SCC, whether the SCC is the full-capability CC or the non-full-capability CC.

Because it is specified in 3GPP that, a network shall ensure that, in a measurement configuration, a measurement object is configured for a SpCell and each SCell that needs to be measured, provided that UE is configured with the measurement configuration. It can be learned that, it is specified in 3GPP that an MO needs to be configured for each SCC. The foregoing solution in which the MO is configured only for the full-capability CC, but not for the non-full-capability CC is in conflict with that specified in 3GPP above.

Based on the foregoing description, as shown in <FIG>, a procedure of a communications method is provided. In the procedure, a terminal device may be the terminal device <NUM> in <FIG>, and a network device may be the network device <NUM> in <FIG>. It may be understood that a function of the terminal device may also be implemented by using a chip applied to the terminal device, and a function of the network device may also be implemented by using a chip applied to the network device. The procedure may include the following steps.

The network device sends first configuration information to the terminal device.

In this embodiment of this application, it may be set that the terminal device needs to measure N SCCs in a downlink frequency band belongs to the frequency range <NUM>, where N is a positive integer greater than or equal to <NUM>, and the first configuration information is used to configure an MO for each of the N SCCs. Based on the first configuration information, a total of NMOs need to be configured for the terminal device.

The terminal device receives the first configuration information, and configures, based on the first configuration information, an MO for each SCC on which measurement needs to be performed.

The network device sends second configuration information to the terminal device, where the second configuration information is used to configure M RCs for the terminal device.

Optionally, the second configuration information may be further used to configure reporting types of the M RCs. For example, the network device may configure a reporting type of any one of the M RCs as an SSB, a CSI-RS, or the like.

The terminal device receives the second configuration information, and configures, based on the second configuration information, the M RCs for the terminal device.

The network device sends third configuration information to the terminal device, where the third configuration information is used to establish an association relationship between an MO and an RC.

The terminal device receives the third configuration information, and establishes, based on the third configuration information, the association relationship between the MO and the RC.

For example, in this embodiment of this application, the association relationship between the MO and the RC may be established by using a measurement identifier list. As shown in <FIG>, an association relationship between an MO <NUM> and an RC <NUM> may be established by using an MI <NUM>, an association relationship between an MO <NUM> and an RC <NUM> may be established by using an MI <NUM>, and the like.

In this embodiment of this application, any of the N MOs may be referred to as a first MO for convenience. The first MO may have an association relationship with one or more of the M RCs, or the first MO may have no association relationship with an RC. For example, as shown in <FIG>, an MO <NUM> has no association relationship with the RC. Any one of the M RCs may be referred to as a first RC for convenience. The first RC may have an association relationship one or more of the NMOs, or the first RC may have no association relationship with an MO. For example, as shown in <FIG>, an RC <NUM> has no association relationship with any MO.

In this embodiment of this application, in a frequency band of the frequency range <NUM>, based on the third configuration information, only one MO may be configured to be associated with an RC whose reporting type is a first type, or at least two MOs may be configured to be associated with an RC whose reporting type is a first type.

As shown in <FIG>, this application provides a procedure of a communications method of the claimed invention. The procedure may be applicable to a scenario in which only one MO is associated with an RC whose reporting type is a first type. Specifically, a terminal device in the procedure may be the terminal device <NUM> in <FIG>. The procedure includes the following steps:.

As shown in <FIG>, this application further provides a procedure of a communications method of the claimed invention. The procedure may also be applicable to a scenario in which only one MO is associated with an RC whose reporting type is a first type. Specifically, a terminal device in the procedure may be the terminal device <NUM> in <FIG>. The procedure includes the following steps:.

As shown in <FIG>, this application further provides a procedure of a communications method. The procedure may also be applicable to a scenario in which only one MO is associated with an RC whose reporting type is a first type. Specifically, a terminal device in the procedure may be the terminal device <NUM> in <FIG>. The procedure may include the following steps:.

As shown in <FIG>, it is specified that a network device configures, for the terminal device in a frequency band of an frequency range <NUM>, three SCCs on which measurement needs to be performed: an SCC <NUM>, an SCC <NUM>, and an SCC <NUM>, and that there is no PCC or PSCC in the frequency band of the frequency range <NUM>. If the network device expects the terminal device to use the SCC <NUM> as a full-capability CC, the network device associates, in a measurement configuration by using a measurement identifier MI <NUM>, an MO <NUM> corresponding to the SCC <NUM> with a reporting configuration RC <NUM>, where a reporting type of the reporting configuration <NUM> is a first type. An MO <NUM> corresponding to the SCC <NUM> is associated with a reporting configuration RC <NUM> by using a measurement identifier MI <NUM>, a reporting type of the reporting configuration RC <NUM> is a second type, and an MO <NUM> corresponding to the SCC <NUM> is not associated with any reporting configuration. In this embodiment of this application, after receiving the measurement configuration, the terminal device may traverse an entire measurement identifier list (MI list). It may be found that, the MO <NUM> corresponding to the SCC <NUM> is not associated with any RC, and in this case, it may be determined that the SCC <NUM> is a non-full-capability CC; and the MO <NUM> corresponding to the SCC <NUM> is associated with the RC <NUM>, the reporting type of the RC <NUM> is the second type, and in this case, it may be determined that the SCC <NUM> is a non-full-capability CC. Only the MO <NUM> corresponding to the SCC <NUM> is associated with the RC <NUM>, and the reporting type of the RC <NUM> is the first type. In this case, it may be determined that the SCC <NUM> is a full-capability CC.

As shown in <FIG>, this application provides a procedure of a communications method. The procedure may be applicable to a scenario in which at least two MOs are associated with an RC whose reporting type is a first type. Specifically, a terminal device in the procedure may be the terminal device <NUM> in <FIG>. The procedure may include the following steps.

The terminal device determines NMOs that correspond to N SCCs and that need to be measured, where the NMOs one-to-one correspond to the N SCCs, and N is a positive integer greater than <NUM>.

The terminal device determines, from the N MOs, at least two MOs that have an association relationship with an RC and for which a reporting type of the RC is a first type.

The terminal device determines a first MO from the at least two MOs.

In this embodiment of this application, the terminal device may select, according to a specific rule, one MO from the at least two MOs as the first MO, or the terminal device may randomly select one MO from the at least two MOs as the first MO.

The terminal device uses an SCC corresponding to the first MO as a full-capability CC.

In this embodiment of this application, if the network device may indicate a range of a full-capability CC to the terminal device, the terminal device may select by itself, within the range, an SCC as the full-capability CC.

It should be noted that the procedures shown in <FIG>, <FIG>, and <FIG> may be used separately or may be used in combination. For example, a terminal device may establish an association relationship between an MO and an RC by using the procedure shown in <FIG>. In addition, after the association relationship between the MO and the RC is established, the terminal device may determine a full-capability CC and a non-full-capability CC by using the procedure shown in <FIG>, <FIG>, <FIG>, or <FIG>.

As shown in <FIG>, it is specified that a network device configures, for a terminal device in a frequency band belongs to an frequency range <NUM>, three SCCs on which measurement needs to be performed: an SCC <NUM>, an SCC <NUM>, and an SCC <NUM>, and there is no PCC or PSCC in the frequency band belongs to the frequency range <NUM>, but the network device expects the terminal device to use the SCC <NUM> or the SCC <NUM> as a full-capability CC. In this case, the network device associates, in a measurement configuration by using a measurement identifier MI <NUM>, an MO <NUM> corresponding to the SCC <NUM> with a reporting configuration RC <NUM>, where a reporting type of the reporting configuration <NUM> is a first type. An MO <NUM> corresponding to the SCC <NUM> is associated with a reporting configuration RC <NUM> by using a measurement identifier MI <NUM>, and a reporting type of the reporting configuration <NUM> is the first type. An MO <NUM> corresponding to the SS <NUM> is not associated with any reporting configuration, or an MO <NUM> corresponding to the SS <NUM> is associated with an RC <NUM> by using an MI <NUM>, where a reporting type of the RC <NUM> is a second type. In an example shown in <FIG>, an example in which no RC is configured for the MO <NUM> corresponding to the SCC <NUM> is used for description. After receiving the measurement configuration, the terminal device may traverse an entire measurement identifier list. It may be found that the MO <NUM> corresponding to the SCC <NUM> is not associated with any RC. It may be determined that the SCC <NUM> is a non-full-capability CC, the MO <NUM> corresponding to the SCC <NUM> and the MO <NUM> corresponding to the SCC <NUM> each are associated with the RC, and a reporting type of the associated RC is the first type. In this case, in this embodiment of this application, the terminal device may select, from the SCC <NUM> and the SCC <NUM>, one SCC as a full-capacity CC. For example, the terminal device may use the SCC <NUM> as a full-capability CC, or use the SCC <NUM> as a full-capability CC. This is not limited in this application.

In this embodiment of this application, an indication method is provided for indicating a full-capability CC based on whether a measurement object and a reporting configuration are associated or not. The indication method resolves a problem in an existing protocol that a specific SCC cannot be determined as a full-capability CC when there is no PCC or PSCC in a frequency band and there are at least two SCCs. In addition, the indication method is compatible with the existing protocol and has few changes to the existing protocol.

It should be noted that, in the procedure shown in <FIG>, <FIG>, or <FIG>, the first type may be but is not limited to an SSB, and the second type may be but is not limited to a CSI-RS.

In this embodiment of this application, the procedure shown in <FIG>, <FIG>, or <FIG> may be specifically based on the following principles.

A measurement procedure is specified in 3GPP as follows:
"Provided that a network configures a measurement configuration for UE, the UE shall measure, according to following procedures, RSRP and RSRQ of each serving cell configured with a measurement object.

Provided that at least one of measurement identifiers configured by the network for the UE uses an SINR as a reporting measurement quantity or trigger measurement quantity, the UE further needs to measure a SINR of each serving cell configured with a measurement object.

For each measurement identifier in the measurement configuration, the UE performs, according to the following processes, measurement for each cell (including a neighboring cell and a serving cell) on a carrier frequency corresponding to the measurement identifier.

It is specified in 3GPP that, measurement performed by the terminal device for the serving cell does not necessarily require association between an MO and an RC, and measurement performed on the neighboring cell requires association between the MO and the RC. For a full-capability CC, measurement needs to be performed for the serving cell and the neighboring cell. For a non-full-capability CC, measurement needs to be performed only for the serving cell. Therefore, it may be determined, based on an association relationship between the MO and a reporting configuration, that an SCC is a full-capability CC or a non-full-capability CC. In other words, when an MO corresponding to an SCC has an association relationship with a reporting configuration, it may be determined that the SCC is a full-capability CC; or when an MO corresponding to an SCC has no association relationship with a reporting configuration, it may be determined that the SCC is a non-full-capability CC. In actual application, there may be different types of cell measurements performed by the terminal device, for example, an SSB type and a channel state information reference signal CSI-RS type. However, a focus in this embodiment of this application is to improve SSB reporting. Therefore, in this embodiment of this application, for example, when an MO has an association relationship with an RC, and a reporting type of the RC is an SSB type, it is determined that an SCC corresponding to the MO is a full-capability CC.

Based on the foregoing concept, as shown in <FIG>, an embodiment of this application provides a communications apparatus <NUM>. The communications apparatus <NUM> may be configured to implement a function of the terminal device in the procedure shown in <FIG>, <FIG>, or <FIG>. The communications apparatus <NUM> may be applied to a terminal device or a chip in a terminal device. The communications apparatus <NUM> may include a processing module <NUM> and a storage module <NUM>. Optionally, the communications apparatus <NUM> may further include a receiving module <NUM> and a sending module <NUM>.

In an example, the storage module <NUM> may be configured to store a program instruction. The processing module <NUM> may be configured to read the instruction stored in the storage module <NUM>, to perform the following processes: determining a first measurement object corresponding to a secondary component carrier; and when there is an association relationship between the first measurement object and a first reporting configuration, and a reporting type of the first reporting configuration is a first type, determining that the secondary component carrier is a full-capability component carrier; or when there is an association relationship between the first measurement object and a first reporting configuration, and a reporting type of the first reporting configuration is a second type, determining that the secondary component carrier is a non-full-capability component carrier, where the first type is different from the second type.

In an example, the storage module <NUM> may be configured to store a program instruction. The processing module <NUM> may be configured to read the instruction stored in the storage module <NUM>, to perform the following processes: determining a first measurement object corresponding to a secondary component carrier; and when there is no association relationship between the first measurement object and a first reporting configuration, determining that the secondary component carrier is a non-full-capacity component carrier.

In an example, the storage module <NUM> may be configured to store a program instruction. The processing module <NUM> may be configured to read the instruction stored in the storage module <NUM>, to perform the following processes: determining N measurement objects corresponding to N secondary component carriers on which measurement needs to be performed, where the N secondary component carriers one-to-one correspond to the N measurement objects, and N is a positive integer greater than <NUM>; determining, from the N measurement objects in a frequency band belongs to a frequency range <NUM>, at least two measurement objects that have an association relationship with a reporting configuration and for which a reporting type of the reporting configuration is a first type; determining a first measurement object from the at least two measurement objects; and using a secondary component carrier corresponding to the first measurement object as a full-capacity carrier unit.

Optionally, the receiving module <NUM> may be configured to receive first configuration information, second configuration information, and third configuration information that are sent by the network device. For the first configuration information, the second configuration information, and the third configuration information, refer to the description in the foregoing method embodiments.

In this embodiment of this application, for descriptions of the processing module <NUM> and the receiving module <NUM>, refer to the descriptions of the procedures shown in <FIG>, <FIG>, or <FIG>.

It should be specially noted that, in this communications apparatus, an entity apparatus corresponding to the processing module may be a processor, an entity device corresponding to the receiving module may be a receiver. Further, an entity apparatus corresponding to the sending module is a transmitter, and an entity device corresponding to the storage module is a memory.

Based on the foregoing concept, as shown in <FIG>, an embodiment of this application provides a communications apparatus <NUM>. The communications apparatus <NUM> may be configured to implement a function of the network device in the procedure shown in <FIG>. The communications apparatus <NUM> may be applied to a network device or a chip in a network device. The communications apparatus <NUM> may include a sending module <NUM> and a processing module <NUM>. Optionally, the communications apparatus <NUM> may further include a storage module <NUM> and a receiving module <NUM>.

In an example of this application, the processing module <NUM> is configured to generate first configuration information, second configuration information, and third configuration information. The sending module <NUM> may send the first configuration information, the second configuration information, and the third configuration information that are determined by the processing module <NUM>.

In this embodiment of this application, for specific descriptions of the sending module <NUM> and the processing module <NUM>, refer to records in the foregoing method embodiments.

In this embodiment of this application, in the communications apparatus <NUM>, an entity apparatus corresponding to the processing module may be a processor, an entity device corresponding to the receiving module may be a receiver, an entity apparatus corresponding to the sending module is a transmitter, and an entity device corresponding to the storage module is a memory.

<FIG> is a simplified schematic diagram of a possible design structure of the terminal device in the foregoing embodiments. The terminal device <NUM> includes a transmitter <NUM>, a receiver <NUM>, a controller/processor <NUM>, a memory <NUM>, and a modem processor <NUM>.

The transmitter <NUM> adjusts (for example, performs analog conversion, filtering, amplification, and up-conversion on) an output sample and generates an uplink signal. The uplink signal is transmitted to the network device in the foregoing embodiments by using an antenna. In a downlink, an antenna receives a downlink signal transmitted by the network device in the foregoing embodiments. The receiver <NUM> adjusts (for example, performs filtering, amplification, down-conversion, and digitalization on) the signal received from the antenna and provides an input sample. In the modem processor <NUM>, an encoder <NUM> receives service data and a signaling message that are to be sent on an uplink, and processes (for example, formats, encodes, and interleaves) the service data and the signaling message. A modulator <NUM> further processes (for example, performs symbol mapping and modulation) encoded service data and an encoded signaling message, and provides an output sample. The demodulator <NUM> processes (for example, demodulates) the input sample and provides a symbol estimate. A decoder <NUM> processes (for example, de-interleaves and decodes) the symbol estimate and provides the decoded data and signaling message that are to be sent to UE. The encoder <NUM>, the modulator <NUM>, the demodulator <NUM>, and the decoder <NUM> may be implemented by an integrated modem processor <NUM>. These units perform processing based on a radio access technology (for example, an access technology of an NR system or another evolution system) used by a radio access network.

The controller/processor <NUM> controls and manages an action of the terminal device and is configured to perform processes performed by the terminal device in the foregoing embodiments. For example, the processes may be: determining a first measurement object corresponding to a secondary component carrier; and when there is an association relationship between the first measurement object and a first reporting configuration, and a reporting type of the first reporting configuration is a first type, determining that the secondary component carrier is a full-capability component carrier; or when there is an association relationship between the first measurement object and a first reporting configuration, and a reporting type of the first reporting configuration is a second type, determining that the secondary component carrier is a non-full-capability component carrier; and/or performing another process of the technologies described in the embodiments of this application. For example, the controller/processor <NUM> is configured to support the terminal device in performing the steps shown in <FIG>, <FIG>, or <FIG>. The memory <NUM> is configured to store program code and data that are related to the terminal device <NUM>.

It should be noted that the terminal device <NUM> provided in this embodiment of this application is configured to implement the communications method shown in <FIG>, <FIG>, or <FIG>, or a function of the terminal device in the communications method shown in <FIG>, <FIG>, or <FIG>. Only a connection relationship between modules of the terminal device <NUM> is described herein. For a specific solution of processing the communications method by the terminal device <NUM> and a specific action performed by the terminal device <NUM>, refer to related descriptions in the foregoing method embodiments.

<FIG> is a schematic diagram of a possible structure of the network device in the foregoing embodiments. The network device <NUM> includes a transmitter/receiver <NUM>, a controller/processor <NUM>, and a memory <NUM>.

The transmitter/receiver <NUM> is configured to support information receiving and sending between the network device and the terminal device in the foregoing embodiments, and support radio communication between the network device and another terminal device. The controller/processor <NUM> performs various functions for communicating with the terminal device. In an uplink, an uplink signal from the terminal device is received by using an antenna, is demodulated by the receiver <NUM>, and is further processed by the controller/processor <NUM> to restore service data and signaling information that are sent by the terminal device. In a downlink, service data and a signaling message are processed by the controller/processor <NUM> and are demodulated by the transmitter <NUM> to generate a downlink signal, and the downlink signal is transmitted to the terminal device by using an antenna. The controller/processor <NUM> further performs a processing process that relates to the network device in <FIG> and/or another process of the technologies described in this application.

The memory <NUM> is configured to store program code and data of the network device. The network device <NUM> may further include a communications unit <NUM>, and the communications unit <NUM> is configured to support the network device in communicating with another network entity.

It should be noted that the network device <NUM> provided in this embodiment of this application is configured to implement a function of the network device in the communications method shown in <FIG>. Only a connection relationship between modules of the network device <NUM> is described herein. For a specific solution of processing the communications method by the network device <NUM> and a specific action to be performed by the network device <NUM>, refer to related descriptions in the foregoing method embodiments.

According to the method in the embodiments of this application, an embodiment of this application further provides a communications system, including the network device and the terminal device described above.

Based on the foregoing embodiments, an embodiment of this application further provides a computer storage medium. The storage medium stores a software program, and when read and executed by one or more processors, the software program may implement the method provided in any one or more of the foregoing embodiments. The computer storage medium may include any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disc.

Based on the foregoing embodiments, an embodiment of this application further provides a chip. The chip includes a processor, configured to implement a function in any one or more of the foregoing embodiments, for example, obtaining or processing information or a message in the foregoing methods. Optionally, the chip further includes a memory. The memory is configured to store a program instruction and data that are executed by the processor. The chip may also include a chip and another discrete device.

It should be understood that, the processor in the embodiments of this application may be a central processing unit (Central Processing Unit, CPU), or may be another general purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or another programmable logical device, a transistor logical device, a discrete hardware component, or the like. The general purpose processor may be a microprocessor or any conventional processor or the like.

The memory may include a read-only memory and a random access memory, and provide an instruction and data to the processor. A part of the memory may further include a non-volatile random access memory.

Claim 1:
A communications method, performed by a terminal device or a chip for the terminal device, the method comprising:
determining (S501a)
a first measurement object corresponding to a first secondary component carrier, SCC;
determining (S502a),
that the first SCC is a CC where at least <NUM> cells and <NUM> SSB are required to be monitored, when there is an association relationship between the first measurement object and a first reporting configuration for the first SCC, and a reporting type of the first reporting configuration is a synchronization signal block, SSB, type;
performing measurement on the first SCC; wherein the <NUM> SSBs have different physical cell identifiers and/or time indexes;
wherein the first SCC is within a frequency band that belongs to frequency range <NUM>; wherein a frequency range of the frequency range <NUM> ranges from <NUM> to <NUM>.