Spectrum aggregation method and apparatus, device, and storage medium

Abstract

A spectrum aggregation method and apparatus, a device, and a storage medium, which relate to the technical field of communications. The method is executed by a terminal device, and comprises: executing a first behavior on the basis of one or more frequency domain units (410). The method can be applied to each spectrum aggregation scenario to achieve spectrum aggregation enhancement, such that a first behavior of a terminal device can adapt to the spectrum aggregation enhancement scenario.

Description

Spectrum aggregation method, apparatus, device, and storage medium TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication technology, in particular to a spectrum aggregation method, apparatus, device, and storage medium. BACKGROUND

[0002] With the development of communication technology, based on the analysis of 6G (Sixth Generation, the sixth generation of mobile communication technology) spectrum demand and 4G / 5G carrier aggregation technology, the 6G control plane needs to continue to evolve on the basis of the traditional spectrum aggregation framework, support efficient and flexible spectrum aggregation, and improve spectrum utilization. From the perspective of sustainability, the carrier aggregation enhancement of 6G needs to consider the terminal and network energy saving under the multi-carrier / bandwidth configuration. From the perspective of scalability, the carrier aggregation enhancement of 6G needs to consider supporting more carrier / bandwidth aggregation, realizing flexible configuration, scheduling and switching of uplink / downlink transmission resources. How to realize spectrum aggregation under multi-carrier / bandwidth needs further discussion and research.

[0003] SUMMARY

[0004] Embodiments of the present application provide a spectrum aggregation method, apparatus, device, and storage medium. The technical solutions provided by the embodiments of the present application are as follows:

[0005] According to an aspect of the embodiments of the present application, a spectrum aggregation method is provided, the method is executed by a terminal device, and the method comprises:

[0006] Performing a first action based on one or more frequency domain units.

[0007] According to an aspect of the embodiments of the present application, a spectrum aggregation method is provided, the method is executed by a network device, and the method comprises:

[0008] Responding to the first action of the terminal device based on one or more frequency domain units.

[0009] According to an aspect of the embodiments of the present application, a spectrum aggregation apparatus is provided, the apparatus comprises:

[0010] A processing module configured to perform a first action based on one or more frequency domain units.

[0011] According to an aspect of the embodiments of the present application, a spectrum aggregation apparatus is provided, the apparatus comprises:

[0012] A processing module configured to respond to the first action of the terminal device based on one or more frequency domain units.

[0013] According to an aspect of an embodiment of the present application, a communication device is provided, which comprises a processor and a memory, the memory storing a computer program, and the processor executes the computer program to implement the above spectrum aggregation method. The communication device is a terminal device, or the communication device is a network device.

[0014] According to an aspect of an embodiment of the present application, a computer readable storage medium is provided, which stores a computer program, and the computer program is used to be executed by a processor to implement the above spectrum aggregation method.

[0015] According to an aspect of an embodiment of the present application, a chip is provided, which comprises a programmable logic circuit and / or program instructions, and when the chip is running, the programmable logic circuit and / or program instructions are used to implement the above spectrum aggregation method.

[0016] According to an aspect of an embodiment of the present application, a computer program product is provided, which comprises computer instructions stored in a computer readable storage medium, and a processor reads and executes the computer instructions from the computer readable storage medium to implement the above spectrum aggregation method.

[0017] The technical scheme provided by the embodiments of the present application can include the following beneficial effects:

[0018] The technical scheme can be applied to various spectrum aggregation scenarios, and the first behavior of the terminal device can be adapted to the spectrum aggregation enhanced scenario. BRIEF DESCRIPTION OF DRAWINGS

[0019] FIG. 1 is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0020] FIG. 2 is a schematic diagram of CA (Carrier Aggregation) provided by an embodiment of the present application;

[0021] FIG. 3 is a schematic diagram of the scheduling relationship between a PCell (Primary Cell) and an SCell (Secondary Cell) provided by an embodiment of the present application;

[0022] FIG. 4 is a flowchart of a spectrum aggregation method provided by an embodiment of the present application;

[0023] FIG. 5 is a block diagram of a spectrum aggregation apparatus provided by an embodiment of the present application;

[0024] FIG. 6 is a block diagram of a spectrum aggregation apparatus provided by another embodiment of the present application;

[0025] FIG. 7 is a structural schematic diagram of a communication device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0026] For the purposes of the present application, the technical solutions and advantages will be more apparent from the following detailed description of the embodiments of the present application, taken in conjunction with the accompanying drawings.

[0027] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, as the network architecture evolves and new service scenarios appear, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0028] Please refer to FIG. 1, which shows a schematic diagram of a network architecture 100 provided by an embodiment of the present application. The network architecture 100 can include a terminal device 10, an access network device 20 and a core network element 30.

[0029] The terminal device 10 can refer to a UE (User Equipment), a STA (Station), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent or a user apparatus. In some embodiments, the terminal device 10 can also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5GS (5th Generation System) or a terminal device in a future evolved PLMN (Public Land Mobile Network), etc., and the embodiments of the present application are not limited thereto. For the convenience of description, the above-mentioned devices are collectively referred to as terminal devices. The number of terminal devices 10 is usually multiple, and one or more terminal devices 10 can be distributed in a cell managed by each access network device 20. The terminal device can also be referred to as a terminal or a UE, and those skilled in the art can understand its meaning.

[0030] The access network device 20 is a device deployed in an access network to provide wireless communication functions for the terminal device 10. The access network device 20 can include various forms of macro base stations, micro base stations, relay stations, APs (Access Points), and the like. In systems using different wireless access technologies, the names of devices with access network device functions can be different, for example, in a 5G NR (New Radio) system, it is called gNodeB or gNB (Next Generation Node B). With the evolution of communication technology, the name of the "access network device" can change. For ease of description, in the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal device 10 are collectively referred to as access network devices. In some embodiments, through the access network device 20, a communication relationship can be established between the terminal device 10 and the core network element 30. Illustratively, in the LTE system, the access network device 20 can be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) or one or more eNodeBs in the EUTRAN; in the 5G NR system, the access network device 20 can be a RAN (Radio Access Network) or one or more gNBs in the RAN. In the embodiments of the present application, the "network device" refers to the access network device 20, such as a base station, unless otherwise specified.

[0031] The core network element 30 is a network element deployed in the core network, and the main functions of the core network element 30 are to provide user connection, manage users, and complete bearer for services, and provide an interface to external networks as a bearer network. For example, the core network element in the 5G NR system can include AMF (Access and Mobility Management Function) entities, UPF (User Plane Function) entities, and SMF (Session Management Function) entities.

[0032] In some embodiments, the access network device 20 and the core network element 30 communicate with each other through some air interface technology, such as the NG interface in the 5G NR system. The access network device 20 and the terminal device 10 communicate with each other through some air interface technology, such as the Uu interface.

[0033] The "5G NR system" in the embodiments of the present application can also be referred to as a 5G system or an NR system, but those skilled in the art can understand its meaning. The technical solutions described in the embodiments of the present application can be applicable to the LTE system, and can also be applicable to the 5G NR system, and can also be applicable to the subsequent evolution system (for example, the B5G (Beyound 5G) system, the 6G system (6th Generation System, the sixth generation mobile communication system)) of the 5G NR system, and can also be applicable to other communication systems such as the NB-IoT (Narrow Band Internet of Things, Narrow Band Internet of Things) system, and the present application does not limit this.

[0034] In the embodiments of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resource (for example, the frequency domain resource, or the spectrum resource) on the carrier used by the cell. The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell (Small cell). The small cell here can include a metro cell, a micro cell, a pico cell, a femto cell, etc., and these small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-speed data transmission services.

[0035] Before introducing the technical solutions of the present application, some related technical knowledge involved in the present application will be introduced and explained. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0036] 1. Carrier aggregation CA technology

[0037] In order to be able to provide greater data transmission rate and improve user experience, the 5G NR further increases the system bandwidth on the basis of the 4G. In the 5G NR, for the frequency band below 6GHz, the maximum bandwidth supported by a single carrier is 100MHz; for the frequency band above 6GHz, the maximum bandwidth supported by a single carrier is 400MHz.

[0038] The same as the LTE system, the carrier aggregation CA technology is also supported in the 5G NR.

[0039] Please combine Figure 2, carrier aggregation, that is, by joint scheduling and using resources on multiple component carriers (CC), the NR system can support a larger bandwidth, so as to realize higher system peak rate. According to the continuity of the aggregated carrier in the frequency spectrum, it can be divided into continuous carrier aggregation and discontinuous carrier aggregation; according to whether the bands where the aggregated carriers are located are the same, it can be divided into intra-band carrier aggregation and inter-band carrier aggregation.

[0040] The PCC (Primary Cell Component) is called the primary carrier, and in a cell group, there is only one PCC, which provides RRC (Radio Resource Control) signaling connection, NAS (Non-Access Stratum) function, security, etc. The SCC (Secondary Cell Component) is called the secondary carrier, which provides additional radio resources. The PCC and the SCC are collectively referred to as serving cells, and the PCC corresponds to the primary serving cell PCell, and the SCC corresponds to the secondary serving cell SCell. For terminal devices supporting CA features, in addition to having a PCell, the network device RRC can also configure one or more SCells for the terminal device. The standard also stipulates that the aggregated carriers belong to the same base station. All aggregated carriers use the same C-RNTI (Cell Radio Network Temporary Identifier), and the base station ensures that the C-RNTI does not conflict in each carrier cell. Since both asymmetric carrier aggregation and symmetric carrier aggregation are supported, it is required that the aggregated carriers must have downlink, and can have no uplink.

[0041] The SCell has two states of activation and inactivation. Only when the SCell is in the activated state, the terminal device can transmit and receive data on this SCell. The SCell is configured by RRC dedicated signaling, and the initial configuration state is the deactivated state, in which data transmission and reception cannot be performed. Then the SCell is activated by the MAC CE to perform data transmission and reception. From the perspective of the delay of SCell configuration and activation, this architecture is not an optimal architecture. This delay also reduces the efficiency of CA use and radio resources, especially in small cell deployment scenarios. In the dense small cell deployment scenario, the signaling load of each SCell is also large, especially in the case of separate configuration of each SCell. Therefore, the current CA architecture introduces additional delay, limits the use of CA, and reduces the gain of CA load sharing.

[0042] 2. Beam failure recovery (BFR)

[0043] An important use scenario of analog beams is in high frequency bands, such as millimeter wave bands. Due to high frequency band electromagnetic wave penetration loss and analog beam narrowing, a communication link is easily blocked, resulting in poor communication quality and even communication interruption.

[0044] To improve the robustness of high frequency band analog beam transmission, when the current beam transmission quality is found to be poor to a certain extent, the terminal device actively finds a new beam with good link quality and notifies the network device, so as to reestablish a high-quality reliable communication link through the new beam. This processing method is called beam failure recovery (BFR) mechanism, which is referred to as beam recovery mechanism.

[0045] In the NR system, the beam failure recovery procedure is designed for downlink transmission beams and does not consider the problem of blocked uplink transmission beams. The main reason is that if the downlink communication quality is good, the network device can instruct the terminal device to switch to a better uplink transmission beam for transmission; if the downlink communication quality is poor, the terminal device may not be able to receive the network device instructions, so it cannot effectively communicate with the terminal device to determine the new beam pairing.

[0046] For beam failure detection (BFD), the gNB configures the beam failure detection reference signal (BFD-RS, including SSB (Synchronization Signal Block) or CSI-RS (Channel State Information Reference Signal)) for the UE, and when the number of physical layer beam failure instances reaches the configured threshold before the configured timer expires, the UE declares beam failure.

[0047] SSB-based beam failure detection is based on CD-SSB related to the initial downlink BWP (Bandwidth Part), and can be configured for the following BWPs: initial downlink BWPs (initial DL BWPs); downlink BWPs containing CD-SSB associated with the initial DL BWP; and if supported, downlink BWPs not containing cell defining SSB (CD-SSB) associated with the initial DL BWP.

[0048] In addition, if a non-cell defining SSB (NCD-SSB) is configured for the active DL BWP, SSB-based beam failure detection can also be performed based on this SSB.

[0049] If a CSI-RS is configured for the active DL BWP, beam failure detection can also be performed based on the CSI-RS.

[0050] After detecting a beam failure on the PCell, the UE's behavior includes:

[0051] • Triggering beam failure recovery by initiating a random access procedure on the PCell;

[0052] • Selecting a suitable beam to perform beam failure recovery (if the gNB provides dedicated random access resources for certain beams, the UE will prefer to use these resources).

[0053] • If it is a contention-based random access, including an indication of the beam failure on the PCell in the BFR MAC CE (Medium Access Control Control Element).

[0054] • After the random access procedure is completed, the beam failure recovery for the PCell is considered complete.

[0055] After detecting a beam failure on the SCell, the UE's behavior includes:

[0056] • Triggering beam failure recovery by initiating transmission of a BFR MAC CE for this SCell;

[0057] • Selecting a suitable beam (if any) for this SCell and indicating it in the BFR MAC CE along with the beam failure information.

[0058] • When the UE receives a PDCCH (Physical Downlink Control Channel) indicating an UL grant (uplink grant) and a new transmission for the HARQ (Hybrid Automatic Repeat Request) process of the BFR MAC CE transmission, the beam failure recovery for this SCell is considered complete.

[0059] When beam failure detection is performed in multi-TRP (Transmit Receive Point) operation, gNB configures two sets of beam failure detection reference signals for a UE, and the UE declares beam failure for a TRP / BFD-RS set when the number of beam failure instances related to the corresponding set of beam failure detection reference signals at the physical layer reaches a configured threshold before the expiry of a configured timer.

[0060] Upon detecting beam failure on a BFD-RS set of a serving cell, the UE:

[0061] • triggers beam failure recovery by initiating transmission of a BFR MAC CE for this BFD-RS set;

[0062] • selects a suitable beam (if any) for this BFD-RS set and indicates in the BFR MAC CE whether a suitable (new) beam was found and information about the beam failure. Beam failure recovery for this BFD-RS set is considered complete upon reception of an uplink grant indicating a new transmission of the HARQ process for the BFR MAC CE transmission indicating this BFD-RS set.

[0063] When two BFD-RS sets of a PCell detect beam failure simultaneously, the UE:

[0064] • triggers beam failure recovery by initiating a random access procedure on the PCell;

[0065] • selects a suitable beam (if any) for each failed BFD-RS set and indicates in the BFR MAC CE for each failed BFD-RS set whether a suitable (new) beam was found and information about the beam failure;

[0066] • considers beam failure recovery for both BFD-RS sets of the PCell complete upon completion of the random access procedure.

[0067] 3. Timing Advance

[0068] In RRC_CONNECTED (RRC Connected) state, gNB is responsible for maintaining the timing advance (TA) to maintain L1 synchronization. Cells using the same timing advance TA and using the same timing reference cell are grouped in a TAG (Timing Advance Group). Each TAG contains at least one serving cell configured with uplink, and the mapping of each serving cell to a TAG is configured by RRC.

[0069] For primary TAG (P-TAG), UE uses PCell as time reference, unless in shared spectrum channel access, in which case SCell can also be used in some cases. In secondary TAG (S-TAG), UE can use any activated SCell of that TAG as timing reference cell, but should not change unless necessary.

[0070] The update of timing advance is signaled by gNB to UE through a MAC CE command. Such a command restarts a TAG-specific timer TimeAlignmentTimer (TAT) that indicates whether L1 can be considered synchronized: when the timer is running, L1 is considered synchronized, otherwise, L1 is considered not synchronized (in which case uplink transmission can only be done through MSG1 / MSGA).

[0071] When two TAG IDs are configured for PCell, both TAGs are considered as primary TAG.

[0072] For P-TAG and S-TAG, the behavior related to TAT timer expiry is different:

[0073] - If TAT of P-TAG expires, UE considers that TAT of all TAGs expires, and thus needs to release resources of all Serving Cells of UE, including clearing HARQ buffer, informing RRC to release PUCCH / SRS, clearing configured DL assignment / configured UL grant, etc. In this case, due to uplink out-of-sync, UE has no UL resource available, when UL data arrives, it needs to trigger RACH procedure.

[0074] - If TAT of S-TAG expires, UE only releases related resources for all SCells under this S-TAG, including clearing HARQ buffer, informing RRC to release PUCCH / SRS, clearing configured DL assignment / configured UL grant, etc. In this case, UE does not trigger RACH by itself, but the network device triggers RACH through PDCCH order to solve the timing synchronization of S-TAG.

[0075] 4. Cross-carrier scheduling

[0076] In NR multi-carrier scenario, a base station can semi-statically configure each carrier to support self-scheduling or cross-carrier scheduling by RRC higher layer signaling (CrossCarrierSchedulingConfig). Self-scheduling means that the PDCCH scheduling the carrier is carried on the carrier, and cross-carrier scheduling means that the PDCCH scheduling the carrier is carried on another carrier.

[0077] Cross-carrier scheduling using the carrier indicator field (CIF) allows the PDCCH of one serving cell to schedule the resources of another serving cell, but with the following restrictions:

[0078] - When cross-carrier scheduling from SCell to PCell is not configured, the PCell can only be scheduled by its PDCCH;

[0079] - When cross-carrier scheduling from SCell to PCell is configured:

[0080] The PDCCH of the SCell can schedule the PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel) of the PCell;

[0081] The PDCCH of the PCell can schedule the PDSCH and PUSCH of the PCell, but cannot schedule the PDSCH and PUSCH of any other cell;

[0082] Only one SCell can be configured for cross-carrier scheduling to the PCell.

[0083] - When the SCell is configured with PDCCH, the PDSCH and PUSCH of the cell are always scheduled by the PDCCH of the SCell;

[0084] - When the SCell is not configured with PDCCH, the PDSCH and PUSCH of the cell are always scheduled by the PDCCH of another serving cell;

[0085] - The scheduling PDCCH and the scheduled PDSCH / PUSCH can use the same or different subcarrier spacing.

[0086] In R15, for each carrier, the high layer signaling indicates whether the scheduling carrier is the carrier itself or other carriers, and the carrier identity used for scheduling is also configured. And, the scheduling carrier for other carriers is only allowed to be configured for SCell. Before R17, in multi-carrier scenario, each carrier can only be scheduled by one carrier, and PCell cannot be scheduled by other carriers, and PCell can schedule SCell, and the scheduling relationship is shown in Figure 3.

[0087] After R17 supports flexible cross-carrier scheduling, the scheduling carrier configured for PCell is allowed to be other carriers. In this configuration condition, the PDCCH scheduling PCell can be on PCell or configured scheduling carrier (sSCell). The new scheduling relationship is defined as follows:

[0088] -PCell can be scheduled by itself (PCell) and one SCell, which is called sSCell.

[0089] -PCell cannot schedule any carrier except itself.

[0090] -sSCell can be scheduled by itself and cannot be scheduled by other carriers.

[0091] -Non-sSCell can be scheduled by itself and can be scheduled by other SCells (including sSCell).

[0092] -Only one sSCell can be configured.

[0093] 5, PUCCH: SpCell, PUCCH Scell, PUCCH switching SCell

[0094] In order to reduce the HARQ-ACK feedback delay of URLLC service in TDD operation, PUCCH cell switching is supported for TDD cells. In addition to PCell / PSCell / PUCCH SCell, each PUCCH group can be configured for the UE PUCCH switching SCell (PUCCH sSCell) for PUCCH transmission. PUCCH transmission on PCell / PSCell / PUCCH SCell or PUCCH sSCell is defined by the following methods:

[0095] -Semi-static: PUCCH transmission is applicable to cells defined by high layer semi-static configuration time-domain pattern, and PUCCH cell switching is applicable to all UCI types;

[0096] - Dynamic: PUCCH (Physical Uplink Control Channel) transmission is scheduled by PDCCH, dynamically indicates the cell of PUCCH transmission, only applies to HARQ feedback.

[0097] 6. Power headroom reporting

[0098] Power headroom reporting (PHR) is provided to support power-aware packet scheduling. In NR, three types of reporting are supported: the first is for PUSCH transmission, the second is for PUSCH and PUCCH transmission in LTE cell group in EN-DC (see TS 37.340

[0021] ), and the third is for SRS transmission on SCells configured with SRS only. In the case of CA (Carrier Aggregation), when no transmission occurs on an activated SCell, a virtual report is provided using a reference power. To allow the network equipment to detect uplink power reduction, the PHR report can also contain power management maximum power reduction information, which is used by the UE to ensure that the UE complies with the Maximum Permissible Exposure (MPE) exposure regulations for FR2, which is set to limit human exposure to radio frequency exposure. The power headroom report is transmitted through MAC signaling.

[0099] The power headroom reporting procedure is used to provide the following information to the serving gNB:

[0100] - Type 1 power headroom: the difference between the UE nominal maximum transmit power and the estimated power for UL-SCH transmission for each activated serving cell;

[0101] - Type 2 power headroom: the difference between the UE nominal maximum transmit power and the estimated power for UL-SCH and PUCCH transmission on the SpCell of the other MAC entity (i.e. E-UTRA MAC entity in the case of EN-DC, NE-DC and NGEN-DC);

[0102] - Type 3 power headroom: the difference between the UE nominal maximum transmit power and the estimated power for SRS transmission for each activated serving cell;

[0103] - MPE P-MPR (Power Management Power Reduction): power backoff made to meet MPE requirements for serving cells on FR2;

[0104] - DPC: maximum output power adjustment for a given power class for serving cells on FR1;

[0105] - DPCBC: maximum output power adjustment for a given power class for band combinations on FR1.

[0106] A power headroom report (PHR) shall be triggered if any of the following events occur:

[0107] - phr-ProhibitTimer expires or has expired and the path loss of at least one RS used as path loss reference has changed by more than phr-Tx-PowerFactorChange dB;

[0108] - phr-PeriodicTimer expires;

[0109] - the power headroom reporting function is configured or reconfigured by higher layers, except to disable the function;

[0110] - an SCell configured with UL of any MAC entity is activated;

[0111] - the SCG (Secondary Cell Group) is activated;

[0112] - a PSCell is added, except when the SCG is deactivated (i.e. the PSCell is newly added or changed);

[0113] - phr-ProhibitTimer expires or has expired, when the MAC entity has uplink resources for new transmission, for any activated serving cell of any MAC entity configured with uplink, one of the following is true: uplink resources are allocated for transmission, or there is PUCCH transmission on this cell and the required power back-off due to power management has changed by more than phr-Tx-PowerFactorChange dB since the last transmission of PHR on this cell;

[0114] - activated BWP switch from dormant BWP to non-dormant DL BWP for any SCell of any MAC entity configured with UL;

[0115] - If dpc-Reporting-FR1 is configured, the ΔPPowerClass / ΔPPowerClass, CA / ΔPPowerClass, EN-DC / ΔPPowerClass, NR-DC reporting is triggered when the uplink duty cycle exceeds or returns to the power class after the duty cycle exceeds.

[0116] - If mpe-Reporting-FR2 is configured and mpe-ProhibitTimer is not running:

[0117] - The measured P-MPR applied to meet FR2 MPE requirements is equal to or greater than mpe-Threshold since the last transmission of PHR in this MAC entity for at least one activated FR2 serving cell; or,

[0118] - The measured P-MPR applied to meet FR2 MPE requirements has changed by more than phr-Tx-PowerFactorChange dB since the last transmission of PHR in this MAC entity for at least one activated FR2 serving cell, due to the measured P-MPR applied to meet MPE requirements being equal to or greater than mpe-Threshold.

[0119] 7. Tracking Area Update / Mobility Update

[0120] Tracking Area update is an important NAS layer mobility management procedure, which allows the UE to update the network device with the Tracking Area identifying its location information, so that the network device can find the UE when needed (such as data transmission or service request). The purpose of this process design is to reduce signaling overhead and improve network device efficiency, while maintaining the reachability of the UE.

[0121] In LTE, this process is called TAU (Tracking Area Update). In 5G, this process is implemented through Mobility Registration Update.

[0122] The triggers of TAU procedure include the following:

[0123] 1 / UE movement triggers update: When the UE camps on a new cell, the Tracking Area Code (TAC) broadcast by the cell is not in the TAC list stored by the UE, which will trigger the TAU NAS layer procedure, and the UE will inform the network device to update the tracking area where the UE is located through NAS layer signaling.

[0124] 2 / Periodic update: UE triggers TAU procedure periodically according to pre-set timer.

[0125] In NTN, multiple TAIs (Tracking Area Identity) are configured for each PLMN per cell. As long as the UE registered TAI is contained in the multiple TAIs broadcasted by the cell, TAU does not need to be performed, which can avoid the number of UEs in the TA boundary area initiating TAU, but the more TAIs broadcasted by the cell, the heavier the paging load, which will lead to obvious imbalance in the inter-cell paging load distribution.

[0126] In 5G, the existing carrier aggregation (CA) technology usually relies on the concept of primary serving cell (PCell) and secondary serving cell (SCell). For terminal devices configured with CA, a Cell Group contains one PCell and multiple SCells. Under this 5G CA framework, many processes are limited to the roles of PCell and SCell, which are limited by the roles of the cells, such as BFR, TA reference cell, cross-carrier scheduling, PUCCH, PHR, and NAS Mobility Information (TAI).

[0127] Based on the analysis of the spectrum demand of 6G and the existing 4G / 5G carrier aggregation technology, the control plane of 6G needs to continue to evolve on the basis of the traditional spectrum aggregation framework, support efficient and flexible spectrum aggregation, and improve spectrum utilization. From the perspective of sustainability, the carrier aggregation enhancement of 6G needs to consider the energy saving of terminal devices and network devices under multi-carrier / bandwidth configuration. From the perspective of scalability, the carrier aggregation enhancement of 6G needs to consider supporting aggregation of more carriers / bandwidth, realizing flexible configuration, scheduling and switching of uplink / downlink transmission resources.

[0128] In the carrier aggregation enhancement of 6G, in order to realize flexible carrier resource scheduling mode and configuration (e.g. flexible association of carriers and related control channels), it can be considered to support uplink / downlink decoupling in spectrum aggregation (e.g. support aggregation of UL only carrier); consider weakening the concept of PCell and SCell, support dynamic conversion of “PCell” and “SCell”; further, it can also be considered to unbind the current cell and carrier, i.e. no longer limit each carrier to be modeled as a cell.

[0129] Please refer to FIG. 4, which shows a flowchart of a spectrum aggregation method provided by an embodiment of the present application. The method is executed by a terminal device, and the method includes the following step 410.

[0130] At step 410, the terminal device performs a first action based on one or more frequency domain units.

[0131] Correspondingly, the network device responds to the first action of the terminal device based on one or more frequency domain units.

[0132] The frequency domain unit is used to describe the range of cells and / or frequency bands. Optionally, the frequency domain unit is any of the following: cell, carrier, frequency band, sub-band, bandwidth, frequency range. Exemplarily, the first frequency domain unit can be implemented as a cell, or a BW (Bandwidth), or a CC.

[0133] Optionally, the one or more frequency domain units are configured by the network device. Optionally, the network device configures identification information of the one or more frequency domain units. Exemplarily, the network device configures the ID of the one or more frequency domain units.

[0134] Optionally, the first action can be related to any of the following aspects: BFR, TA (Timing Advance), cross-carrier scheduling, PUCCH, PHR, TAU (Tracking Area Update).

[0135] BFR, Beam Failure Recovery, is used to handle the case of beamforming failure in 5G NR.

[0136] TA, Timing Advance, is used to adjust the uplink transmission time of the terminal device (UE) to ensure that the signal arrives at the network device synchronously.

[0137] Cross-carrier scheduling refers to scheduling data transmission on multiple carriers to improve transmission efficiency and reliability.

[0138] PHR, Tracking Area Update, is the process by which the UE reports its location change to the core network when moving to a new tracking area.

[0139] PUCCH, Physical Uplink Control Channel, is used to transmit uplink control information such as HARQ-ACK, CQI, SR, etc.

[0140] TAU, Tracking Area Update, is the process by which the UE reports its location change to the core network when moving to a new tracking area.

[0141] The technical solutions provided by the embodiments of the present application can also be applied to other spectrum aggregation scenarios, which are not listed one by one in the present application.

[0142] The technical solutions provided by the embodiments of the present application can be applied to various spectrum aggregation scenarios, and can realize the enhancement of spectrum aggregation, so that the first action of the terminal device can adapt to the scenario of spectrum aggregation enhancement.

[0143] Next, the first action of each of the above aspects will be described.

[0144] I. BFR

[0145] Optionally, after determining that the beam failure occurs, the first behavior is to start BFR on the frequency domain unit where the beam failure occurs.

[0146] Optionally, the network device configures, for each frequency domain unit of the terminal device, a reference signal BFD-RS (including SSB or CSI-RS) for beam failure detection, a beam failure detection timer (beamFailureDetectionTimer), and a maximum number of beam failure instances (beamFailureInstanceMaxCount).

[0147] Optionally, the terminal device determines that the beam failure occurs. Illustratively, it is determined whether to send a beam failure on this cell / BW / CC based on the physical layer BFI reporting and the beam failure detection timer (beamFailureDetectionTimer) and the beam failure counter (BFI_COUNTER) maintained by the MAC layer, that is, before the beamFailureDetectionTimer expires, the BFI_COUNTER reaches the configured threshold beamFailureInstanceMaxCount, and the terminal device declares a beam failure.

[0148] Optionally, performing the first behavior includes at least one of the following:

[0149] In the case that there is UL-SCH resource available for new transmission on at least one frequency domain unit, and the UL-SCH resource supports containing BFR MAC CE and its subheader, generating BFR MAC CE, the BFR MAC CE being used to indicate the new beam information and / or BFR information selected by the terminal device;

[0150] In the case that there is no UL-SCH resource available for transmitting BFR MAC CE on at least one frequency domain unit, or at least one frequency domain unit occurs beam failure, triggering SR for BFR;

[0151] In the case that there is no UL-SCH resource available for transmitting BFR MAC CE on at least one frequency domain unit, or there is no frequency domain unit where the beam failure does not occur, triggering a random access procedure.

[0152] Optionally, after the terminal device detects the beam failure on one frequency domain unit, the terminal device triggers the beam failure recovery by starting the BFR MAC CE transmission for the frequency domain unit.

[0153] 1. There is a resource available for sending BFR MAC CE

[0154] Optionally, if the terminal device has one or more frequency domain units with UL-SCH resources available for new transmission, and the UL-SCH resources can accommodate the BFR MAC CE and the corresponding subheader based on the LCP result, the terminal device generates the BFR MAC CE and indicates the UE-selected new beam information and / or BFR information in the BFR MAC CE.

[0155] Optionally, after the beam failure occurs in the first frequency domain unit in the one or more frequency domain units, the terminal device determines that the beam failure occurs in one or more second frequency domain units, and the first frequency domain unit has an association relationship with the one or more second frequency domain units. Optionally, the association relationship is configured by the network device. Illustratively, the network device configures the association relationship based on the identification information of the first frequency domain unit and the second frequency domain unit. Optionally, for the available UL-SCH resources, the network device can not configure BFD-RS on all frequency domain units, but indicate that there is an association relationship between different frequency domain units. If the beam failure occurs in one of the frequency domain units, it is considered that the associated frequency domain units are also unavailable. For example, the network device indicates that carrier 1 has an association relationship with carrier 2, and if the beam failure occurs on carrier 1, it is considered that the beam failure also occurs on carrier 2. The frequency domain units with the association relationship may have a correlation, such as being located on the same frequency band or having the same beam direction, and they may simultaneously have beam failure, so excluding these associated frequency domain units can ensure that the terminal device successfully sends the BFR MAC CE.

[0156] Optionally, the new beam is determined based on the measurement result of at least one candidate beam, each candidate beam corresponds to a reference signal, and the reference signal is used to determine the measurement result of the candidate beam, and the new beam is used to establish a new link.

[0157] The measurement result of the candidate beam is used to reflect the channel quality of the frequency domain unit. Illustratively, the measurement result of the candidate beam can be RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality), SINR (Signal to Interference plus Noise Ratio), etc. Optionally, the terminal device selects the new beam from the candidate beams based on the measurement result threshold. Illustratively, the terminal device determines the candidate beam whose measurement result exceeds the measurement result threshold as the new beam. Optionally, the measurement result threshold is configured by the network device.

[0158] If the terminal device only knows that beam failure occurs, it cannot quickly reestablish a new link with the network device. The terminal device also needs to know which other beam has good quality, so as to quickly reestablish the link using the beam with good quality. In order to assist the terminal device to save time and effort to find a good quality downlink transmission beam, the network device configures a set of reference signals (such as CSI-RS signals and / or SSBs) for the terminal device in advance. In fact, each reference signal corresponds to a candidate downlink transmission beam, that is, the network device configures a set of candidate downlink transmission beams for the terminal device. The terminal device determines a new beam by measuring the L1-RSRP of these candidate beams. The network device will pre-configure an RSRP threshold value, and the terminal device selects a beam from the candidate beams with L1-RSRP measurement value greater than the RSRP threshold as a usable new beam.

[0159] Optionally, after the terminal device transmits the HARQ new transmission carrying the BFR MAC CE on a frequency domain unit, it considers that the beam failure recovery on the frequency domain unit is completed.

[0160] 2. No resource available for BFR MAC CE

[0161] Optionally, if there is no UL-SCH resource available for transmitting the BFR MAC CE on each frequency domain unit, or there is no frequency domain unit without beam failure, the terminal device first triggers an SR for BFR. In the case that there is no available PUCCH resource to transmit the SR, the terminal device triggers a random access procedure to obtain the UL-SCH resource for BFR MAC CE transmission. First triggering the SR can effectively save the RACH resource in the case that there is a PUCCH resource for transmitting the SR.

[0162] Optionally, if there is no UL-SCH resource available for transmitting the BFR MAC CE on each frequency domain unit, or there is no frequency domain unit without beam failure, the terminal device directly triggers a random access procedure. Directly triggering a random access procedure without triggering an SR can reduce the latency and improve the transmission reliability.

[0163] Optionally, triggering the random access procedure includes at least one of the following:

[0164] In the case that there is a reference signal corresponding to the candidate beam and there is a candidate beam with dedicated RACH resource, a CFRA procedure is triggered;

[0165] In the case that there is no reference signal corresponding to the candidate beam, and / or there is no candidate beam with dedicated RACH resource, a CBRA procedure is triggered;

[0166] In a case where the measurement results of the alternative beams are all lower than the first threshold, the CBRA procedure is triggered.

[0167] Optionally, the first threshold is configured by the network device. The first threshold is used to represent the channel quality of the alternative beam. For example, the first threshold can be an RSRP threshold, an RSRQ threshold, an SINR threshold, etc.

[0168] If the network device configures the terminal device with reference signals of the alternative beams and provides dedicated RACH resources for some alternative beams, the terminal device will preferentially use these resources to trigger CFRA, which can indicate the new beam selected by the terminal device. Optionally, the dedicated RACH resource is used to indicate the new beam determined by the terminal device.

[0169] Optionally, in the CBRA procedure, Msg3 or MsgA is used to carry the BFR MAC CE. If the network device does not configure the terminal device with reference signals of the alternative beams and / or dedicated RACH resources for the alternative beams, or the L1-RSRP measurement values of all the alternative beams are lower than the threshold configured by the network device, CBRA is triggered. Since the network device does not know that the purpose of the RACH is BFR, it is still necessary to carry the BFR MAC CE through Msg3 or MsgA, which is used to indicate the BFR information and / or the new beam information selected by the UE to the network device.

[0170] Optionally, the above method can also be applied to a multi-TRP scenario, in which the network device configures a BFD-RS set consisting of at least one BFD-RS for a frequency domain unit.

[0171] Through the above method, the triggering and recovery process of BFR is no longer limited by the role of the cell, which is more flexible, thereby improving the robustness and transmission efficiency of the communication system.

[0172] II. TA

[0173] TAT timeout refers to a timer allocated by the network device (such as gNodeB in 5G NR) for the terminal device (UE) in the random access process. If the UE does not receive the timing advance (Timing Advance) command from the network device before the TAT timeout, the UE may consider that the uplink is out of synchronization, which will affect the synchronization and transmission efficiency of data.

[0174] 1. TAT timeout of one TAG

[0175] Optionally, in a case where the TAT of the first TAG times out, the first behavior includes releasing the transmission resources of all frequency domain units in the first TAG; and / or, triggering a random access procedure.

[0176] Optionally, the releasing the transmission resource of all frequency domain units in the first TAG includes, but is not limited to, emptying the HARQ buffer, notifying the RRC to release the PUCCH or SRS, clearing the configured DL assignment or the configured UL grant.

[0177] Optionally, the terminal device triggers a random access procedure based on the reason of the TAT timeout of the first TAG to solve the timing synchronization problem of the first TAG. Optionally, in the case that the first TAG is configured with a dedicated RACH resource, the CFRA procedure is triggered preferentially. Optionally, in the case that the first TAG is not configured with a dedicated RACH resource, the CBRA procedure is triggered.

[0178] 2. The TAT of all TAGs is timed out

[0179] Optionally, in the case that the TAT of all TAGs of the terminal device is timed out, the first behavior includes triggering a random access procedure. Optionally, in the case that the TAT of a TAG of the terminal device is not timed out, the terminal device does not trigger a random access procedure.

[0180] In this case, the condition of triggering the random access procedure can include at least one of the following:

[0181] In the case that the TAT of all TAGs of the terminal device is timed out, the random access procedure is triggered based on a RACH trigger condition, and the RACH trigger condition includes that the TAT of all TAGs of the terminal device is timed out.

[0182] In the case that the TAT of all TAGs of the terminal device is timed out, the random access procedure is triggered in the case that uplink data arrives and there is no available uplink resource.

[0183] In one example, a trigger condition of the random access procedure is added, and the added condition is that the TAT of all TAGs of the terminal device is timed out, in which case the terminal device does not need to wait for uplink data to arrive, and can trigger the random access procedure.

[0184] In another example, the trigger condition of the random access procedure is not added, and then the terminal device triggers the random access procedure when uplink data arrives.

[0185] Exemplarily, the TAT timeout includes the following key steps:

[0186] If the TAT of a TAG (including multiple Cells / BWs / CCs) is timed out, the behavior of the UE includes:

[0187] Only release the transmission resource of all Cells / BWs / CCs under this TAG, including clearing HARQ buffer, notifying RRC to release PUCCH / SRS, clearing configured DL assignment / configured UL grant, etc.

[0188] Optionally, the UE triggers RACH by itself based on the reason of the TAG timeout, solving the timing synchronization of the TAG.

[0189] Optionally, if the dedicated RACH resource is configured for the TAG timeout, the UE can prefer to use CFRA, otherwise, CBRA is executed

[0190] Optionally, only when the TAT of all TAGs of the UE is timed out, the UE triggers RACH (as long as the TAT of one TAG is not timed out, the RACH is not triggered). The UE triggers RACH includes one of the two possible ways:

[0191] 1 / Add a new RACH trigger condition "establish TA due to all TAGs of the UE being timed out", in which case there is no need to wait for the arrival of UL data;

[0192] 2 / Due to uplink out-of-sync, the UE has no available UL resource, and when the UL data arrives, the RACH process needs to be triggered.

[0193] Through the above method, the TAT timeout behavior of the TAG is no longer limited by the role of the cell, and there is no difference between P-TAG and S-TAG. The method for the TAT of a TAG to be timed out is beneficial to the UE to recover the uplink synchronization of the TAG as soon as possible, but the RACH overhead is large. The method for the TAT of all TAGs to be timed out can avoid the RACH overhead, and only when the UE has UL data to send, the RACH is initiated as needed to recover the uplink synchronization.

[0194] 3, TA reference frequency domain unit

[0195] Optionally, the TA corresponding to the frequency domain unit in one TAG is the same, and the TA corresponding to the frequency domain unit in one TAG is the same. The TA reference frequency domain unit is the same. Illustratively, the cells in one TAG use the same TA, and use the same TA reference cell. Illustratively, the carriers in one TAG use the same TA, and use the same TA reference carrier.

[0196] Optionally, the TA reference frequency domain unit is semi-statically configured by the network device. Optionally, the network device semi-statically configures the TA reference frequency domain unit through RRC signaling. Optionally, the network device semi-statically configures the identification information of the TA reference frequency domain unit. Illustratively, the network device semi-statically configures the ID of the TA reference frequency domain unit. For example, the network device configures the ID of the TA reference frequency domain unit through RRC signaling. Illustratively, the network device semi-statically indicates the PCI of the TA reference cell.

[0197] Optionally, the TA reference frequency domain unit is a frequency domain unit in the TAG that supports downlink transmission. Illustratively, the TA reference frequency domain unit can be any frequency domain unit in the TAG that is configured with DL, i.e., not an UL-only frequency domain unit.

[0198] Optionally, each TAG includes at least one frequency domain unit that supports uplink transmission. The TA is used for the transmission of uplink data, and the presence of a frequency domain unit that supports uplink transmission in the TAG makes it meaningful to configure the TA for the TAG.

[0199] Optionally, each TAG includes at least one frequency domain unit that supports downlink transmission. This is because a frequency domain unit that supports downlink transmission is needed as a TA reference frequency domain unit.

[0200] Illustratively, the frequency domain unit is a cell.

[0201] The network device semi-statically configures the mapping relationship between the cell and the TAG for the UE through RRC signaling, and indicates the timing reference cell for each TAG.

[0202] All cells in the TAG use the same timing advance TA, and use the same timing reference cell indicated by the network device as the TA reference.

[0203] The timing reference cell is any cell in the TAG that is configured with DL, i.e., not an UL-only cell, and can be indicated by a Cell ID (such as a PCI).

[0204] A TAG contains at least one cell configured with UL (the TA is used for UL transmission, and it is meaningful to have UL).

[0205] A TAG contains at least one cell configured with DL (a DL is needed as a TA reference).

[0206] The UE uses the timing reference cell as the TA reference for the TAG according to the indication of the network device.

[0207] Exemplarily, the frequency domain unit is a BW or a CC:

[0208] The network device semi-statically configures the UE with the mapping relationship between the uplink and downlink BW / CC and the TAG through RRC signaling, and indicates the timing reference BW / CC for each TAG.

[0209] All the UL BW / CCs in the TAG use the same timing advance TA, and use the same timing reference BW / CC indicated by the network device as the TA reference.

[0210] The timing reference DL BW / CC is any one of the DL BW / CCs in the TAG, which can be indicated by the BW / CC ID.

[0211] Each TAG contains at least one UL BW / CC (TA is used for UL transmission, and it is meaningful to have UL).

[0212] Each TAG contains at least one DL BW / CC (DL is needed as the TA reference).

[0213] The UE uses the timing reference BW / CC as the TA reference of the TAG according to the indication of the network device.

[0214] Through the above method, the configuration of the TA reference frequency domain unit becomes more flexible, and is no longer limited by the role of the cell, thereby improving the synchronization performance of the system.

[0215] Three, scheduling channel PDCCH and feedback channel PUCCH

[0216] Optionally, the first behavior is to transmit and / or receive data based on the PDCCH on one or more frequency domain units.

[0217] Optionally, the PDCCH and / or PUCCH corresponding to the one or more frequency domain units are configured by the network device. Optionally, the network device configures the PDCCH and / or PUCCH on one or more frequency domain units of the terminal device. Optionally, there can be one or more PDCCHs and / or PUCCHs on a frequency domain unit, or there can be no PDCCH and / or PUCCH. For example, a frequency domain unit can transmit PDCCH+PUCCH, or only transmit PDCCH or PUCCH, or not transmit PDCCH and PUCCH.

[0218] Optionally, the network device semi-statically configures the corresponding PDCCH and / or PUCCH on one or more frequency domain units. For example, the network device configures the corresponding PDCCH and / or PUCCH on one or more frequency domain units through RRC signaling.

[0219] Optionally, one frequency domain unit of the one or more frequency domain units corresponds to one or more PDCCHs, and the plurality of PDCCHs are located on the same or different frequency domain units. For the transmission resource on one frequency domain unit, one or more PDCCHs can be configured, and the one or more PDCCHs can be located on the same frequency domain unit or transmitted on different frequency domain units. For example, the PDCCH corresponding to the transmission resource on the first frequency domain unit can be transmitted on the second frequency domain unit.

[0220] Optionally, one frequency domain unit corresponds to one or more PUCCHs, and the plurality of PUCCHs are located on the same or different frequency domain units. For the transmission resource on one frequency domain unit, one or more PUCCHs can be configured, and the one or more PUCCHs can be located on the same frequency domain unit or transmitted on different frequency domain units. For example, the PUCCH corresponding to the transmission resource on the first frequency domain unit can be transmitted on the second frequency domain unit.

[0221] Optionally, the correspondence between the plurality of PUCCHs and the transmission resource on the frequency domain unit is semi-statically configured by using a time domain pattern. For example, the network device indicates the time domain pattern through RRC signaling.

[0222] Optionally, the PDCCH is also used to indicate the identification information of the one or more frequency domain units. Since one PDCCH can be associated with multiple frequency domain units, the identification information of the frequency domain unit scheduling PUSCH and / or PDSCH transmission needs to be dynamically indicated in the PDCCH DCI format to support scheduling PUSCH and / or PDSCH transmission of different frequency domain units, support frequency domain unit self-scheduling or flexible cross-frequency domain unit scheduling. For example, the PDCCH is also used to indicate the ID of the one or more frequency domain units.

[0223] Optionally, the PDCCH is also used to indicate the identification information of the frequency domain unit where the PUCCH for HARQ feedback is located. For example, the identification information of the frequency domain unit where the PUCCH for HARQ feedback is located is indicated through the PDCCH DCI format.

[0224] For example, the frequency domain unit can be implemented as a cell or a bandwidth or a carrier.

[0225] Network equipment configures PDCCH and / or PUCCH for each cell / BW / CC for UE by RRC signaling (i.e. optional presence as well).

[0226] For each cell / BW / CC, one or more PDCCHs can be configured for scheduling transmission, which can be located on the same cell / BW / CC or different PDCCHs.

[0227] For each cell / BW / CC, one or more PUCCHs can be configured for HARQ feedback, which can be located on the same cell / BW / CC or different PUCCHs.

[0228] Optionally, for multiple PUCCHs, further semi-statically configure time-domain pattern to determine cell / BW / CC for PUCCH transmission at different time.

[0229] UE transmits / receives on transmission resource on different cell / BW / CC according to scheduling channel PDCCH indication.

[0230] Since one PDCCH can be associated with multiple cell / BW / CCs, cell / BW / CC ID for scheduling PUSCH and / or PDSCH transmission needs to be dynamically indicated in PDCCH DCI Format to support scheduling PUSCH and / or PDSCH transmission on different cell / BW / CCs, support cell / BW / CC self-scheduling or flexible cross-cell / BW / CC scheduling.

[0231] Optionally, further indicate cell / BW / CC ID by PDCCH DCI Format to determine PUCCH for HARQ feedback

[0232] For downlink reception, the UE determines the cell / BW / CC to send PUCCH HARQ Feedback according to the time-domain pattern configured by the network semi-statically, or the UE determines the cell / BW / CC to send PUCCH HARQ Feedback based on the cell / BW / CC ID indicated by PDCCH DCI Format dynamically.

[0233] Through the above method, cross-carrier scheduling and feedback become more flexible and are no longer limited by the role of the cell, thereby improving the transmission efficiency and resource utilization of the system.

[0234] Four, PHR

[0235] Optionally, the first behavior is to send a PHR MAC CE, and the PHR MAC CE is used to report PHR information based on a frequency domain unit granularity. If the decoupling of the cell and the carrier is considered, the UE needs to support a BW / CC-based triggering condition and a BW / CC-granularity-based PHR MAC CE report, and the frequency domain unit in the embodiment can be implemented as a BW or a CC.

[0236] Optionally, the PHR information includes at least one of the following:

[0237] The first type of power margin is the difference between the nominal maximum transmit power of the terminal device for the activated uplink frequency domain unit and the estimated power of UL-SCH transmission;

[0238] The second type of power margin is the difference between the nominal maximum transmit power of the terminal device for the uplink frequency domain unit of other MAC entities and the estimated power of UL-SCH and PUCCH transmission;

[0239] The third type of power margin is the difference between the nominal maximum transmit power of the terminal device for the activated uplink frequency domain unit and the estimated power of sounding reference signal SRS transmission;

[0240] The maximum allowed exposure power plus maximum power reduction MPE P-MPR is the power backoff performed to meet the MPR requirement of the uplink frequency domain unit on the frequency range FR2;

[0241] The DPC is the maximum output power adjustment of a given power class for the uplink frequency domain unit on FR1.

[0242] The DPCBC is the maximum output power adjustment of a given power class for the frequency band combination on FR1.

[0243] Optionally, the first behavior is triggered based on at least one of the following conditions:

[0244] activating one or more uplink frequency domain units;

[0245] deactivating one or more uplink frequency domain units;

[0246] adding one or more uplink frequency domain units;

[0247] deleting one or more uplink frequency domain units.

[0248] Optionally, the triggering conditions for other first behaviors mentioned in the related art, such as the triggering conditions of phr-ProhibitTimer or phr-PeriodicTimer, can also be combined into the embodiments of the present application, for example, by configuring or reconfiguring the PHR function through a higher layer.

[0249] Exemplarily, the frequency domain unit can be implemented as a BW or a CC.

[0250] The PHR triggering condition based on BW / CC includes at least one of the following:

[0251] activating one or more UL BW / CCs;

[0252] deactivating one or more UL BW / CCs;

[0253] adding one or more UL BW / CCs;

[0254] deleting one or more UL BW / CCs;

[0255] For other PHR triggering conditions in the related art, the triggering conditions based on phr-ProhibitTimer or phr-PeriodicTimer remain unchanged, such as by configuring or reconfiguring the PHR function through a higher layer.

[0256] When the UE triggers PHR, the UE generates a PHR MAC CE, and reports the PHR information based on the BW / CC granularity to the network through the PHR MAC CE, including at least one of the following:

[0257] Type 1 power headroom: the difference between the nominal maximum transmit power of each activated UL BW / CC and the estimated power of UL-SCH transmission;

[0258] Type 2 power headroom: the difference between the UE nominal maximum transmit power and the estimated power of UL-SCH and PUCCH transmission on the UL BW / CC of other MAC entities (i.e. E-UTRA MAC entity in EN-DC, NE-DC and NGEN-DC cases);

[0259] Type 3 power headroom: the difference between the UE nominal maximum transmit power and the estimated power of SRS transmission on each activated UL BW / CC;

[0260] MPE P-MPR: power backoff made to meet the MPE requirement on UL BW / CC on FR2;

[0261] DPC: the maximum output power adjustment of a given power class for UL BW / CC on FR1;

[0262] DPCBC: the maximum output power adjustment of a given power class for band combination on FR1.

[0263] By the above method, based on the decoupling concept of cell and carrier, the PHR is adaptively modified, which can be applied to the 6G cell and carrier decoupling carrier aggregation enhancement scenario.

[0264] V. TAU

[0265] Optionally, the first behavior is triggering a tracking area update (TAU).

[0266] 1. New cell addition

[0267] Optionally, the method further includes the following step 420 (not shown in the figure).

[0268] Step 420: The terminal device receives first signaling, and the first signaling includes configuration information of the new cell, and the first signaling is used to add the new cell for the terminal device.

[0269] Correspondingly, the network device sends the first signaling. Optionally, the first signaling is a dedicated signaling. Illustratively, the first signaling is an RRC reconfiguration message.

[0270] Optionally, the first signaling includes first information for the new cell, the first information being a serving TAI, or the first information being indication information of not performing TAU. Optionally, the TAI can also be referred to as a TAC (Tracking Area Code). Optionally, the network device semi-statically configures the serving TAI of the cell.

[0271] Optionally, the serving TAI is different from the TAI broadcast by the new cell. Optionally, if a cell is configured with both a serving TAI and a broadcast TAI, the terminal device takes the serving TAI as the criterion.

[0272] Optionally, the serving TAI belongs to a TAI list of the terminal device; and / or, the serving TAI is one of TAI of one or more cells already configured by the terminal device.

[0273] Optionally, the indication information of not performing TAU is carried in configuration information of the new cell. Exemplarily, the indication information of not performing TAU can be 1-bit indication information. For example, the value of the indication information is 1, indicating not performing TAU. Exemplarily, the indication information of not performing TAU can be a bitmap for all new cells, wherein one bit corresponds to one new cell. Exemplarily, the indication information of not performing TAU can be list information, wherein identification information of a new cell indicated in the list information indicates that the new cell does not perform TAU. Optionally, the list information can indicate the PCI of the new cell.

[0274] Exemplarily, the network device adds a new cell for the UE through dedicated signaling (for example, RRCReconfiguration), and provides configuration information of the new cell for the UE. Optionally, the gNB indicates first information for the new cell in the dedicated signaling, the first information being a serving TAI or indication information of not performing TAU.

[0275] The serving TAI is different from the TAI broadcast by the new cell.

[0276] The serving TAI is one of a TAI list of the UE, and / or the serving TAI is one of TAI of one or more cells already configured by the UE (if there is a cell in the already configured cells, the cell broadcasts a TAI and the dedicated signaling configures a serving TAI, and the serving TAI configured in the dedicated signaling is taken as the criterion).

[0277] The indication information of not performing TAU can be configured in configuration information of each new cell, being 1-bit indication information, or being a bitmap for all added new cells, or being a PCI list, etc.

[0278] 2. The first information is used to indicate a serving TAI

[0279] Optionally, the first behavior comprises at least one of the following:

[0280] If the serving TAI is not in the TAI list of the terminal device, triggering a TAU;

[0281] If the serving TAI is in the TAI list of the terminal device, not triggering a TAU;

[0282] If all the cells configured by the terminal device use the serving TAI, or if all the TAIs broadcast by the cells currently configured by the terminal device are not in the TAI list of the terminal device, triggering a TAU.

[0283] Optionally, if the terminal device receives first signaling for adding a new cell to the terminal device, and the serving TAI is indicated, the terminal device takes the serving TAI as the TAI of the newly configured cell. If the serving TAI is not in the TAI list of the terminal device, triggering a TAU, if the serving TAI is in the TAI list of the terminal device, not triggering a TAU.

[0284] If all the cells configured by the terminal device use the serving TAI, or if all the TAIs broadcast by the cells currently configured by the terminal device are not in the TAI list of the terminal device, triggering a TAU. This situation is usually caused by the network device releasing part of the configured cells of the terminal device through dedicated signaling.

[0285] Illustratively, when the UE receives dedicated signaling for adding a new cell to the UE, and the serving TAI is indicated. The UE takes the serving TAI configured in the dedicated signaling as the TAI of this cell (i.e., the serving TAI indicated in the dedicated signaling overrides the TAI broadcast by the cell), and performs at least one of the following behaviors:

[0286] If the TAI of this new cell (i.e., the serving TAI) is not in the TAI list of the UE, the UE triggers a TAU procedure;

[0287] If the TAI of this new cell (i.e., the serving TAI) is in the TAI list of the UE, the UE does not trigger a TAU procedure;

[0288] If all the cells configured for the UE are serving TAI indicated by dedicated signaling, or, further, if all the TAI broadcasted by the currently configured cells of the UE are not in the TAI list of the UE, the UE needs to trigger the TAU procedure (this situation is usually caused by the network releasing some already configured cells of the UE by dedicated signaling).

[0289] 3、The first information is the indication information of not performing TAU

[0290] Optionally, the first behavior includes at least one of the following:

[0291] In the case of receiving the indication information of not performing TAU for the first cell, the TAU caused by the TAI of the first cell is not performed;

[0292] In the case of receiving the indication information of not performing TAU for all the cells configured for the terminal device, the TAU is performed.

[0293] Optionally, if the terminal device receives the first signaling of adding a new cell for the terminal device, and the indication information of not performing TAU is indicated, in the case of receiving the indication information of not performing TAU for the first cell, the TAU caused by the TAI of the first cell is not performed. If all the cells configured for the terminal device indicate the indication information of not performing TAU, the terminal device performs the TAU.

[0294] Exemplarily, when the UE receives the dedicated signaling of adding a new cell for the UE, and the indication information of not performing TAU is indicated, the UE performs at least one of the following behaviors:

[0295] The UE ignores the TAI of the cell according to the indication information of not performing TAU, and does not perform the TAU procedure caused by the TAI of the cell;

[0296] If all the currently configured cells of the UE indicate the indication information of not performing TAU, the UE needs to perform the TAU.

[0297] 4、Adding a new cell or deleting an already configured cell

[0298] Optionally, in the case of receiving the signaling of adding a new cell or deleting an already configured cell, or receiving the system message change notification of the broadcasted TAI change for the already configured cell, the first behavior is performed, including at least one of the following:

[0299] If the broadcasted TAI of at least one of the already configured cells belongs to the TAI list of the terminal device, the TAU is not triggered;

[0300] If all the broadcast TAIs of the configured cells do not belong to the TAI list of the terminal device, the TAU is triggered.

[0301] Optionally, the terminal device receives dedicated signaling to add a new cell for the terminal device, or delete a configured cell, or the broadcast TAI of the currently configured cell of the terminal device changes, the terminal device receives a system message change notification, and the terminal device determines whether to trigger the TAU based on whether the broadcast TAI of the configured cell belongs to the TAI list of the terminal device. Illustratively, if at least one configured cell has a broadcast TAI that belongs to the TAI list of the terminal device, the TAU is not triggered. If all the broadcast TAIs of the configured cells do not belong to the TAI list of the terminal device, the TAU is triggered.

[0302] Illustratively, when the network adds a new cell or deletes a configured cell for the UE through dedicated signaling (e.g., RRCReconfiguration), or when the UE receives a system message change notification when the broadcast TAI of the currently configured cell changes, the behavior of the UE includes at least one of the following:

[0303] If at least one configured cell has a broadcast TAI in the TAI list of the UE, the UE does not trigger the TAU procedure;

[0304] If all the broadcast TAIs of the configured cells do not belong to the TAI list of the UE, the UE triggers the TAU procedure.

[0305] By the above method, unnecessary TAU initiated by the terminal device is effectively avoided, thereby saving the power consumption of the terminal device.

[0306] In the above method embodiments, the technical solutions of the present application are introduced and described only from the perspective of interaction between the terminal device and the network device. The steps performed by the terminal device described above can be implemented alone to become a spectrum aggregation method on the terminal device side, and the steps performed by the network device described above can be implemented alone to become a spectrum aggregation method on the network device side. In addition, the embodiments provided herein can be combined arbitrarily to form new embodiments, which are all within the protection scope of the present application.

[0307] The following is an apparatus embodiment of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the apparatus embodiments of the present application, please refer to the method embodiments of the present application.

[0308] Please refer to FIG. 5, which shows a block diagram of a spectrum aggregation apparatus according to an embodiment of the present application. The apparatus has the functions of implementing the spectrum aggregation method examples described above, which can be implemented by hardware or by executing corresponding software by hardware. The apparatus can be the terminal device described above or can be arranged in the terminal device. As shown in FIG. 5, the apparatus 500 can include a processing module 510.

[0309] The processing module 510 is configured to perform a first action based on one or more frequency domain units.

[0310] In some embodiments, after determining that beam failure occurs, the first action is to start a beam failure recovery (BFR) on the frequency domain unit where the beam failure occurs.

[0311] In some embodiments, the performing the first action includes at least one of the following:

[0312] In the case that there is an uplink shared channel (UL-SCH) resource available for new transmission on the one or more frequency domain units, and the UL-SCH resource supports containing the BFR medium access control (MAC) control element (CE) and its subheader, the BFR MAC CE is generated, which is used to indicate new beam information and / or BFR information selected by the terminal device;

[0313] In the case that there is no UL-SCH resource available for transmitting the BFR MAC CE on the one or more frequency domain units, or beam failure occurs on the one or more frequency domain units, a scheduling request (SR) for BFR is triggered.

[0314] In the case that there is no UL-SCH resource available for transmitting the BFR MAC CE on the one or more frequency domain units, or there is no frequency domain unit where beam failure does not occur, a random access procedure is triggered.

[0315] In some embodiments, the processing module 510 is further configured to determine that one or more second frequency domain units have beam failure after a first frequency domain unit of the one or more frequency domain units has beam failure, the first frequency domain unit and the one or more second frequency domain units having an association relationship.

[0316] In some embodiments, the association relationship is configured by a network device.

[0317] In some embodiments, the new beam is determined based on measurement results of at least one candidate beam, each candidate beam corresponding to a reference signal used to determine the measurement result of the candidate beam, and the new beam is used to establish a new link.

[0318] In some embodiments, the triggering the random access procedure comprises at least one of:

[0319] In a case that there is a reference signal corresponding to an alternative beam and there is an alternative beam with dedicated RACH resource, triggering a CFRA procedure based on non-contention-based random access;

[0320] In a case that there is no reference signal corresponding to an alternative beam and / or there is no alternative beam with dedicated RACH resource, triggering a CBRA procedure based on contention-based random access;

[0321] In a case that measurement results of alternative beams are all lower than a first threshold, triggering the CBRA procedure.

[0322] In some embodiments, the dedicated RACH resource is used to indicate a new beam determined by the terminal device.

[0323] In some embodiments, in the CBRA procedure, Msg3 or MsgA is used to carry the BFR MAC CE.

[0324] In some embodiments, in a case that a timing advance timer TAT of a first timing advance group TAG times out, the first behavior comprises:

[0325] releasing transmission resources of all frequency domain units in the first TAG; and / or,

[0326] triggering a random access procedure.

[0327] In some embodiments, in a case that TATs of all TAGs of the terminal device time out, the first behavior comprises triggering a random access procedure.

[0328] In some embodiments, the triggering the random access procedure comprises:

[0329] In a case that the first TAG is configured with dedicated RACH resource, preferentially triggering a CFRA procedure; or,

[0330] In a case that the first TAG is not configured with dedicated RACH resource, triggering a CBRA procedure.

[0331] In some embodiments, in a case that TATs of all TAGs of the terminal device time out,

[0332] the random access procedure is triggered based on a RACH triggering condition, the RACH triggering condition comprising that TATs of all TAGs of the terminal device time out; or,

[0333] the random access procedure is triggered in a case that uplink data arrives and there is no available uplink resource.

[0334] In some embodiments, the TAs corresponding to the frequency domain units in one TAG are the same, and the TAs corresponding to the frequency domain units in one TAG refer to the same frequency domain unit.

[0335] In some embodiments, the frequency domain unit to which the TAs refer is configured semi-statically by the network device.

[0336] In some embodiments, the network device semi-statically configures the identification information of the frequency domain unit to which the TAs refer.

[0337] In some embodiments, the frequency domain unit to which the TAs refer is a frequency domain unit in the TAG that supports downlink transmission.

[0338] In some embodiments, one TAG includes at least one frequency domain unit that supports uplink transmission; and / or,

[0339] One TAG includes at least one frequency domain unit that supports downlink transmission.

[0340] In some embodiments, the first behavior is to send and / or receive data on the one or more frequency domain units based on a physical downlink control channel (PDCCH).

[0341] In some embodiments, the PDCCH and / or physical uplink control channel (PUCCH) corresponding to the one or more frequency domain units are configured by the network device.

[0342] In some embodiments, one frequency domain unit in the one or more frequency domain units corresponds to one or more PDCCHs, and the PDCCHs are located on the same or different frequency domain units; or,

[0343] One frequency domain unit corresponds to one or more PUCCHs, and the PUCCHs are located on the same or different frequency domain units.

[0344] In some embodiments, the correspondence between the PUCCHs and the transmission resources on the frequency domain units is semi-statically configured using a time domain pattern.

[0345] In some embodiments, the PDCCH is further used to indicate the identification information of the one or more frequency domain units.

[0346] In some embodiments, the PDCCH is further used to indicate the identification information of the frequency domain unit in which the PUCCH for hybrid automatic repeat request (HARQ) feedback is located.

[0347] In some embodiments, the first behavior is to send a power headroom report (PHR) MAC CE, and the PHR MAC CE is used to report PHR information based on frequency domain unit granularity.

[0348] In some embodiments, the PHR information comprises at least one of:

[0349] a first type of power headroom, the first type of power headroom being a difference between the nominal maximum transmit power of the terminal device for the activated uplink frequency domain unit and an estimated power of UL-SCH transmission;

[0350] a second type of power headroom, the second type of power headroom being a difference between the nominal maximum transmit power of the terminal device for the uplink frequency domain unit of other MAC entities and an estimated power of the UL-SCH and PUCCH transmission;

[0351] a third type of power headroom, the third type of power headroom being a difference between the nominal maximum transmit power of the terminal device for the activated uplink frequency domain unit and an estimated power of sounding reference signal (SRS) transmission;

[0352] a maximum permissible exposure power additional maximum power reduction (MPE P-MPR) being a power back-off made to meet the MPR requirement for the uplink frequency domain unit on frequency range (FR) 2;

[0353] a DPC being a maximum output power adjustment for a given power class for the uplink frequency domain unit on FR1;

[0354] a DPCBC being a maximum output power adjustment for a given power class for a band combination on FR1.

[0355] In some embodiments, the first behavior is triggered based on at least one of the following conditions:

[0356] activating one or more uplink frequency domain units;

[0357] deactivating one or more uplink frequency domain units;

[0358] adding one or more uplink frequency domain units;

[0359] deleting one or more uplink frequency domain units.

[0360] In some embodiments, the first behavior is triggering a tracking area update (TAU).

[0361] In some embodiments, the apparatus 500 further comprises a receiving module (not shown in the figure).

[0362] The receiving module is configured to receive first signaling, the first signaling comprising configuration information of a new cell, the first signaling being used to add a new cell for the terminal device.

[0363] In some embodiments, the first signaling comprises first information for the new cell, the first information being a serving TAI, or the first information being indication information of not performing TAU.

[0364] In some embodiments, the serving TAI is different from a TAI broadcast by the new cell.

[0365] In some embodiments, the serving TAI belongs to a TAI list of the terminal device; and / or,

[0366] The serving TAI is one of TAIs of one or more cells configured for the terminal device.

[0367] In some embodiments, the indication information of not performing TAU is carried in configuration information of the new cell.

[0368] In some embodiments, the performing the first behavior comprises at least one of:

[0369] If the serving TAI does not belong to the TAI list of the terminal device, triggering TAU;

[0370] If the serving TAI belongs to the TAI list of the terminal device, not triggering TAU;

[0371] If all cells configured for the terminal device adopt the serving TAI, or if TAIs broadcast by all cells configured for the terminal device do not belong to the TAI list of the terminal device, triggering TAU.

[0372] In some embodiments, the performing the first behavior comprises at least one of:

[0373] In a case where indication information of not performing TAU for a first cell is received, not performing TAU caused by a TAI of the first cell;

[0374] In a case where indication information of not performing TAU for all cells configured for the terminal device is received, performing TAU.

[0375] In some embodiments, in a case where signaling of adding a new cell or deleting a configured cell is received, or in a case where system message change notification of a change of a broadcast TAI of a configured cell is received, the performing the first behavior comprises at least one of:

[0376] If a broadcast TAI of at least one configured cell belongs to the TAI list of the terminal device, not triggering TAU;

[0377] If broadcast TAIs of all configured cells do not belong to the TAI list of the terminal device, triggering TAU.

[0378] In some embodiments, the frequency domain unit is any one of the following: a cell, a carrier, a frequency band, a sub-band, a bandwidth, a frequency range.

[0379] The embodiments of the present application provide technical solutions, which can be applied to various spectrum aggregation scenarios, and realize spectrum aggregation enhancement, so that the first behavior of the terminal device can adapt to the spectrum aggregation enhancement scenario.

[0380] Please refer to FIG. 6, which shows a block diagram of a spectrum aggregation device provided by an embodiment of the present application. The device has the functions of realizing the above-mentioned spectrum aggregation method examples, which can be realized by hardware or by executing corresponding software by hardware. The device can be the network device introduced above or can be arranged in the network device. As shown in FIG. 6, the device 600 can include a processing module 610.

[0381] The processing module 610 is configured to respond to the first behavior of the terminal device based on one or more frequency domain units.

[0382] In some embodiments, after it is determined that the beam failure occurs, the first behavior is to start a beam failure recovery (BFR) on the frequency domain unit where the beam failure occurs.

[0383] In some embodiments, the first behavior includes at least one of the following:

[0384] In the case where there is an uplink shared channel (UL-SCH) resource available for new transmission on the one or more frequency domain units, and the UL-SCH resource supports containing the BFR medium access control (MAC) CE and its subheader, the terminal device generates the BFR MAC CE, which is used to indicate the new beam information and / or BFR information selected by the terminal device;

[0385] In the case where there is no UL-SCH resource available for transmitting the BFR MAC CE on the one or more frequency domain units, or the one or more frequency domain units all have beam failure, the terminal device triggers a scheduling request (SR) for BFR.

[0386] In the case where there is no UL-SCH resource available for transmitting the BFR MAC CE on the one or more frequency domain units, or there is no frequency domain unit that does not have beam failure, the terminal device triggers a random access procedure.

[0387] In some embodiments, one or more second frequency domain units are determined by the terminal device to have beam failure after a first frequency domain unit in the one or more frequency domain units has beam failure, the first frequency domain unit having an association relationship with the one or more second frequency domain units.

[0388] In some embodiments, the association relationship is configured by a network device.

[0389] In some embodiments, the new beam is determined based on measurement results of at least one candidate beam, each candidate beam corresponding to a reference signal used to determine the measurement result of the candidate beam, the new beam being used to establish a new link.

[0390] In some embodiments, the terminal device triggers a random access procedure, including at least one of:

[0391] In a case where there is a reference signal corresponding to a candidate beam and there is a candidate beam having a dedicated RACH resource, the terminal device triggers a contention-free random access (CFRA) procedure;

[0392] In a case where there is no reference signal corresponding to a candidate beam and / or there is no candidate beam having a dedicated RACH resource, the terminal device triggers a contention-based random access (CBRA) procedure;

[0393] In a case where the measurement results of the candidate beams are all below a first threshold, the terminal device triggers a CBRA procedure.

[0394] In some embodiments, the dedicated RACH resource is used to indicate a new beam determined by the terminal device.

[0395] In some embodiments, in the CBRA procedure, a Msg3 or a MsgA is used to carry the BFR MAC CE.

[0396] In some embodiments, in a case where a timing advance timer (TAT) of a first timing advance group (TAG) times out, the first behavior includes:

[0397] releasing transmission resources of all frequency domain units in the first TAG; and / or,

[0398] triggering a random access procedure.

[0399] In some embodiments, in a case where TATs of all TAGs of the terminal device time out, the first behavior includes triggering a random access procedure.

[0400] In some embodiments, the terminal device triggers a random access procedure, including:

[0401] In a case where the first TAG is configured with the dedicated RACH resource, the terminal device preferentially triggers the CFRA procedure; or

[0402] In a case where the first TAG is not configured with the dedicated RACH resource, the terminal device triggers the CBRA procedure.

[0403] In some embodiments, in a case where the TAT of all TAGs of the terminal device expires,

[0404] The random access procedure is triggered based on a RACH triggering condition, and the RACH triggering condition includes expiration of the TAT of all TAGs of the terminal device; or

[0405] The random access procedure is triggered in a case where uplink data arrives and there is no available uplink resource.

[0406] In some embodiments, the TAs corresponding to the frequency domain units in one TAG are the same, and the TAs corresponding to the frequency domain units in one TAG refer to the frequency domain units.

[0407] In some embodiments, the TA reference frequency domain unit is semi-statically configured by a network device.

[0408] In some embodiments, the network device semi-statically configures identification information of the TA reference frequency domain unit.

[0409] In some embodiments, the TA reference frequency domain unit is a frequency domain unit supporting downlink transmission in the TAG.

[0410] In some embodiments, one TAG includes at least one frequency domain unit supporting uplink transmission; and / or,

[0411] One TAG includes at least one frequency domain unit supporting downlink transmission.

[0412] In some embodiments, the first behavior is based on sending and / or receiving data by a physical downlink control channel (PDCCH) on the one or more frequency domain units.

[0413] In some embodiments, the PDCCH and / or physical uplink control channel (PUCCH) corresponding to the one or more frequency domain units are configured by a network device.

[0414] In some embodiments, one frequency domain unit of the one or more frequency domain units corresponds to one or more PDCCHs, and the plurality of PDCCHs are located on the same or different frequency domain units; or,

[0415] One frequency domain unit corresponds to one or more PUCCHs, and the plurality of PUCCHs are located on the same or different frequency domain units.

[0416] In some embodiments, the correspondence between the plurality of PUCCHs and the transmission resources on the frequency domain units is semi-statically configured with a time domain pattern.

[0417] In some embodiments, the PDCCH is further used to indicate identification information of the one or more frequency domain units.

[0418] In some embodiments, the PDCCH is further used to indicate identification information of the frequency domain unit where a PUCCH for hybrid automatic repeat request (HARQ) feedback is located.

[0419] In some embodiments, the first behavior is to send a power headroom report (PHR) MAC CE, and the PHR MAC CE is used to report PHR information based on frequency domain unit granularity.

[0420] In some embodiments, the PHR information includes at least one of the following:

[0421] a first type of power headroom, which is a difference between a nominal maximum transmit power of the terminal device and an estimated power of UL-SCH transmission for an activated uplink frequency domain unit;

[0422] a second type of power headroom, which is a difference between the nominal maximum transmit power of the terminal device and an estimated power of the UL-SCH and PUCCH transmission for an uplink frequency domain unit of other MAC entities;

[0423] a third type of power headroom, which is a difference between the nominal maximum transmit power of the terminal device and an estimated power of sounding reference signal (SRS) transmission for an activated uplink frequency domain unit;

[0424] a maximum permissible exposure (MPE) P-MPR, which is a power backoff made to meet the MPR requirement of an uplink frequency domain unit on a frequency range (FR) 2;

[0425] a DPC for a given power class for an uplink frequency domain unit on FR1;

[0426] a DPCBC for a given power class for a frequency band combination on FR1.

[0427] In some embodiments, the first behavior is triggered based on at least one of the following conditions:

[0428] one or more uplink frequency domain units are activated;

[0429] deactivating one or more uplink frequency domain units;

[0430] adding one or more uplink frequency domain units;

[0431] deleting one or more uplink frequency domain units.

[0432] In some embodiments, the first behavior is triggering a tracking area update (TAU).

[0433] In some embodiments, the apparatus 600 further includes a sending module (not shown in the figure).

[0434] The sending module is configured to send first signaling, the first signaling including configuration information of a new cell, and the first signaling being used to add the new cell for the terminal device.

[0435] In some embodiments, the first signaling includes first information for the new cell, the first information being a serving TAI, or the first information being indication information of not performing TAU.

[0436] In some embodiments, the serving TAI is different from a TAI broadcast by the new cell.

[0437] In some embodiments, the serving TAI belongs to a TAI list of the terminal device; and / or,

[0438] The serving TAI is one of TAIs of one or more cells configured for the terminal device.

[0439] In some embodiments, the indication information of not performing TAU is carried in the configuration information of the new cell.

[0440] In some embodiments, the performing the first behavior includes at least one of the following:

[0441] If the serving TAI does not belong to the TAI list of the terminal device, the terminal device triggers TAU;

[0442] If the serving TAI belongs to the TAI list of the terminal device, the terminal device does not trigger TAU;

[0443] All cells configured for the terminal device use the serving TAI, or TAIs broadcast by all cells configured for the terminal device do not belong to the TAI list of the terminal device, and the terminal device triggers TAU.

[0444] In some embodiments, the performing the first behavior includes at least one of the following:

[0445] In a case where the indication information not to perform the TAU for the first cell is received, the terminal device does not perform the TAU caused by the TAI of the first cell.

[0446] In a case where the indication information not to perform the TAU for all the cells configured for the terminal device is received, the terminal device performs the TAU.

[0447] In some embodiments, in a case where signaling of adding a new cell or deleting a configured cell is received, or, system message change notification of broadcasted TAI change for a configured cell is received, the performing the first behavior includes at least one of the following:

[0448] If the broadcasted TAI of at least one configured cell belongs to the TAI list of the terminal device, the terminal device does not trigger the TAU;

[0449] If the broadcasted TAI of all the configured cells does not belong to the TAI list of the terminal device, the terminal device triggers the TAU.

[0450] In some embodiments, the frequency domain unit is any one of the following: a cell, a carrier, a frequency band, a sub-band, a bandwidth, and a frequency segment.

[0451] The technical scheme provided by the embodiments of the present application can be applied to various spectrum aggregation scenarios, and realizes enhancement of spectrum aggregation, so that the first behavior of the terminal device can adapt to the scenario of spectrum aggregation enhancement.

[0452] It should be noted that, when the apparatuses provided in the above embodiments implement their functions, only the division of the above various functional modules is taken as an example for illustration, and in actual application, the above functions can be completed by different functional modules according to actual needs, that is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0453] As to the apparatuses in the above embodiments, the specific manners in which the various modules perform operations have been described in detail in the embodiments of the method, and will not be described in detail here.

[0454] Please refer to FIG. 7, which shows a structural schematic diagram of a communication device provided by an embodiment of the present application. The communication device can be the terminal device or the first radio access device or the network device introduced above. The communication device 700 can include a processor 701, a transceiver 702, and a memory 703. The transceiver 702 is configured to implement the sending or receiving function, and the processor 701 can be configured to implement other processing functions or control the sending and / or receiving, such as being configured to implement the functions of the processing module 510 or the functions of the processing module 610.

[0455] The processor 701 comprises one or more processing cores, and performs various function applications and information processing by running software programs and modules.

[0456] The transceiver 702 can comprise a receiver and a transmitter, which can be implemented as the same wireless communication component, and can comprise a wireless communication chip and a radio frequency antenna.

[0457] The memory 703 can be connected to the processor 701 and the transceiver 702.

[0458] The memory 703 can be used to store computer programs executed by the processor 701, and the processor 701 is configured to execute the computer programs to implement various steps in the above method embodiments.

[0459] In some embodiments, when the communication device 700 is a terminal device, the processor 701 is configured to perform the first action based on one or more frequency domain units.

[0460] In some embodiments, when the communication device 700 is a network device, the processor 701 is configured to respond to the first action of the terminal device based on one or more frequency domain units.

[0461] For details not described in the present embodiment, reference can be made to the above embodiments, which will not be repeated here.

[0462] In addition, the memory can be implemented by any type of volatile or non-volatile storage devices or a combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only memories, erasable programmable read-only memories, static random access memories, read-only memories, magnetic memories, flash memories, programmable read-only memories.

[0463] The embodiment of the present application further provides a computer readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to be executed by a processor to implement the spectrum aggregation method on the terminal device side or implement the spectrum aggregation method on the network device side. Optionally, the computer readable storage medium can include a ROM (Read-Only Memory), a RAM (Random-Access Memory), a SSD (Solid State Drives) or an optical disc, and the like. The RAM can include a ReRAM (Resistance Random Access Memory) and a DRAM (Dynamic Random Access Memory).

[0464] The embodiment of the present application further provides a chip, wherein the chip includes a programmable logic circuit and / or program instructions, and when the chip is running, the chip is used to implement the spectrum aggregation method on the terminal device side or implement the spectrum aggregation method on the network device side.

[0465] The embodiment of the present application further provides a computer program product, wherein the computer program product includes a computer program, the computer program is stored in a computer readable storage medium, and a processor reads and executes the computer program from the computer readable storage medium, and the computer program is used to implement the spectrum aggregation method on the terminal device side or implement the spectrum aggregation method on the network device side.

[0466] It should be understood that the "indication" mentioned in the embodiments of the present application can be direct indication, or indirect indication, or can be an indication having a correlation relationship. For example, A indicates B, which can mean that B can be obtained by A; or A indirectly indicates B, for example, A indicates C, and B can be obtained by C; or A and B have a correlation relationship.

[0467] In the description of the embodiments of the present application, the term "corresponding" can mean that there is a direct or indirect corresponding relationship between the two, or can mean that there is a correlation relationship between the two, or can mean an indication and being indicated, configuration and being configured, and the like.

[0468] In some embodiments of the present application, "predefined" can be implemented by pre-storing corresponding codes, tables or other information indicating manners in devices (for example, including terminal devices and APs), and the specific implementation manners of the present application are not limited. For example, the pre-defined can mean defined in a protocol.

[0469] In some embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, which can include the LTE protocol, the NR protocol, and related protocols applied in future communication systems, and the present application is not limited thereto.

[0470] "Multiple" mentioned in the present application refers to two or more. "And / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent three cases: A exists alone, A and B exist together, and B exists alone. The character " / " generally represents that the associated objects before and after it are in an "or" relationship.

[0471] "Greater than or equal to" mentioned in the present application can mean greater than or equal to, and "less than or equal to" can mean less than or equal to.

[0472] In addition, the step numbers described in the present application only exemplarily show a possible execution order between steps, and in some other embodiments, the above steps can also be executed in a sequence different from the number, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in an order opposite to the illustration, and the embodiments of the present application are not limited thereto.

[0473] Those skilled in the art should realize that in one or more of the above examples, the functions described in the embodiments of the present application can be realized by hardware, software, firmware or any combination thereof. When realized by software, these functions can be stored in a computer readable medium or transmitted as one or more instructions or codes on a computer readable medium. The computer readable medium includes computer storage medium and communication medium, wherein the communication medium includes any medium facilitating the transmission of computer programs from one place to another. The storage medium can be any available medium accessible by a general or special purpose computer.

[0474] The above only describes exemplary embodiments of the present application, and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method of spectrum aggregation, comprising: The method is performed by a terminal device, and the method comprises: performing a first action based on one or more frequency domain units.

2. The method of claim 1, wherein, After determining that beam failure occurs, the first action is to initiate a beam failure recovery (BFR) on the frequency domain unit where the beam failure occurs.

3. The method of claim 2, wherein, The performing of the first action comprises at least one of the following: in a case where there is an uplink shared channel (UL-SCH) resource available for new transmission on the one or more frequency domain units, and the UL-SCH resource supports containing a BFR medium access control (MAC) control element (CE) and a subheader thereof, generating the BFR MAC CE, the BFR MAC CE being used to indicate new beam information and / or BFR information selected by the terminal device; in a case where there is no UL-SCH resource available for transmitting the BFR MAC CE on the one or more frequency domain units, or the one or more frequency domain units all have beam failure, triggering a scheduling request (SR) for BFR; in a case where there is no UL-SCH resource available for transmitting the BFR MAC CE on the one or more frequency domain units, or there is no frequency domain unit that does not have beam failure, triggering a random access procedure.

4. The method of claim 3, wherein, The method further comprises: after beam failure occurs in a first frequency domain unit of the one or more frequency domain units, determining that beam failure occurs in one or more second frequency domain units, the first frequency domain unit having an association relationship with the one or more second frequency domain units.

5. The method of claim 4, wherein, The association relationship is configured by a network device.

6. The method according to any one of claims 3 to 5, characterized in that, The new beam is determined based on measurement results of at least one candidate beam, each candidate beam corresponding to a reference signal used to determine the measurement result of the candidate beam, and the new beam being used to establish a new link.

7. The method according to any one of claims 3 to 6, characterized in that, The triggering of the random access procedure comprises at least one of the following: in a case where there is a reference signal corresponding to a candidate beam, and there is a candidate beam having a dedicated RACH resource, triggering a contention-free random access (CFRA) procedure; in a case where there is no reference signal corresponding to a candidate beam, and / or, there is no candidate beam having a dedicated RACH resource, triggering a contention-based random access (CBRA) procedure; in a case where the measurement results of the candidate beams are all lower than a first threshold, triggering the CBRA procedure.

8. The method of claim 7, wherein, The dedicated RACH resource is used to indicate a new beam determined by the terminal device.

9. The method of claim 7, wherein, In the CBRA procedure, Msg3 or MsgA is used to carry the BFR MAC CE.

10. The method of claim 1, wherein, In a case where a timing advance timer (TAT) of a first timing advance group (TAG) times out, the first action comprises: releasing transmission resources of all frequency domain units in the first TAG; and / or, triggering a random access procedure.

11. The method according to claim 1 or 10, characterized in that, In a case where TATs of all TAGs of the terminal device time out, the first action comprises triggering a random access procedure.

12. The method according to claim 10 or 11, characterized in that, The triggering of the random access procedure comprises: in a case where the first TAG is configured with a dedicated RACH resource, preferentially triggering a CFRA procedure; or, in a case where the first TAG is not configured with a dedicated RACH resource, triggering a CBRA procedure.

13. The method of claim 11, wherein, In a case that TATs of all TAGs of the terminal device are expired, The random access procedure is triggered based on a RACH trigger condition, and the RACH trigger condition includes that TATs of all TAGs of the terminal device are expired; or The random access procedure is triggered in a case that uplink data arrives and no available uplink resource exists.

14. The method according to any one of claims 10 to 13, characterized in that, TA of a frequency domain unit in one TAG is the same, and TA of the frequency domain unit in one TAG refers to a reference frequency domain unit.

15. The method of claim 14, wherein, The TA reference frequency domain unit is semi-statically configured by a network device.

16. The method of claim 15, wherein, The network device semi-statically configures identification information of the TA reference frequency domain unit.

17. The method according to any one of claims 14 to 16, characterized in that, The TA reference frequency domain unit is a frequency domain unit supporting downlink transmission in the TAG.

18. The method of any one of claims 14 to 17, wherein, At least one frequency domain unit supporting uplink transmission is included in one TAG; and / or At least one frequency domain unit supporting downlink transmission is included in one TAG.

19. The method of claim 1, wherein, The first behavior is based on sending and / or receiving data on the one or more frequency domain units by a physical downlink control channel (PDCCH).

20. The method of claim 14, wherein, The PDCCH and / or a physical uplink control channel (PUCCH) corresponding to the one or more frequency domain units is configured by a network device.

21. The method of claim 19 or 20, wherein, One frequency domain unit in the one or more frequency domain units corresponds to one or more PDCCHs, and the plurality of PDCCHs are located on the same or different frequency domain units; or One frequency domain unit corresponds to one or more PUCCHs, and the plurality of PUCCHs are located on the same or different frequency domain units.

22. The method of claim 21, wherein, A correspondence relationship between the plurality of PUCCHs and transmission resources on the frequency domain units is semi-statically configured by using a time domain pattern.

23. The method according to any one of claims 19 to 22, characterized in that, The PDCCH is further used to indicate identification information of the one or more frequency domain units.

24. The method according to any one of claims 19 to 23, characterized in that, The PDCCH is further used to indicate identification information of a frequency domain unit in which a PUCCH for hybrid automatic repeat request (HARQ) feedback is located.

25. The method of claim 1, wherein, The first behavior is sending a power headroom report (PHR) MAC CE, and the PHR MAC CE is used to report PHR information based on frequency domain unit granularity.

26. The method of claim 25, wherein, The PHR information includes at least one of: A first type of power headroom, which is a difference between a nominal maximum transmit power of the terminal device and estimated power of UL-SCH transmission for an activated uplink frequency domain unit; A second type of power headroom, which is a difference between the nominal maximum transmit power of the terminal device and estimated power of the UL-SCH and PUCCH transmission on an uplink frequency domain unit of another MAC entity; A third type of power headroom, which is a difference between the nominal maximum transmit power of the terminal device and estimated power of sounding reference signal (SRS) transmission for an activated uplink frequency domain unit; A maximum permissible exposure power additional maximum power reduction (MPE P-MPR), which is a power backoff performed to meet an MPR requirement of an uplink frequency domain unit on a frequency range (FR2); and A fourth type of power headroom, which is a difference between the nominal maximum transmit power of the terminal device and estimated power of PUCCH transmission for an activated uplink frequency domain unit. DPC, the DPC being a maximum output power adjustment for a given power class for an uplink frequency domain unit on FR1; DPCBC, the DPCBC being a maximum output power adjustment for a given power class for a frequency range combination on FR1.

27. The method of claim 25 or 26, wherein, The first behavior is triggered based on at least one of the following conditions: activating one or more uplink frequency domain units; deactivating one or more uplink frequency domain units; adding one or more uplink frequency domain units; deleting one or more uplink frequency domain units.

28. The method of claim 1, wherein, The first behavior is triggering a tracking area update (TAU).

29. The method of claim 28, wherein, The method further comprises: receiving first signaling including configuration information of a new cell, the first signaling being used to add the new cell for the terminal device.

30. The method of claim 29, wherein, The first signaling includes first information for the new cell, the first information being a serving TAI, or the first information being indication information of not performing TAU.

31. The method of claim 30, wherein, The serving TAI is different from a TAI broadcast by the new cell.

32. The method of claim 30 or 31, wherein: The serving TAI belongs to a TAI list of the terminal device; and / or, The serving TAI is one of TAIs of one or more cells configured for the terminal device.

33. The method of claim 30, wherein, The indication information of not performing TAU is carried in the configuration information of the new cell.

34. The method according to any one of claims 30 to 33, characterized in that, The performing the first behavior comprises at least one of: triggering TAU if the serving TAI does not belong to the TAI list of the terminal device; not triggering TAU if the serving TAI belongs to the TAI list of the terminal device; triggering TAU if all cells configured for the terminal device use the serving TAI, or if TAIs broadcast by all cells configured for the terminal device do not belong to the TAI list of the terminal device.

35. The method of any one of claims 30 to 33, wherein, The performing the first behavior comprises at least one of: not performing TAU caused by a TAI of a first cell if indication information of not performing TAU for the first cell is received; performing TAU if indication information of not performing TAU for all cells configured for the terminal device is received.

36. The method of any one of claims 28 to 35, wherein, The performing the first behavior comprises at least one of: not triggering TAU if a broadcast TAI of at least one configured cell belongs to the TAI list of the terminal device; triggering TAU if broadcast TAIs of all configured cells do not belong to the TAI list of the terminal device.

37. The method of any one of claims 1 to 36, wherein, The frequency domain unit is any of the following: a cell, a carrier, a frequency band, a sub-band, a bandwidth, a frequency range.

38. A method of spectrum aggregation, comprising: The method is performed by a network device, and the method comprises: responding to a first behavior of a terminal device based on one or more frequency domain units.

39. The method of claim 38, wherein, After determining that a beam failure occurs, the first behavior is to start a beam failure recovery (BFR) on the frequency domain unit where the beam failure occurs.

40. The method of claim 39, wherein, The first behavior comprises at least one of: In a case where there is an uplink shared channel (UL-SCH) resource available for new transmission on the one or more frequency domain units, and the UL-SCH resource supports containing the BFR medium access control (MAC) control element (CE) and a subheader thereof, the terminal device generates the BFR MAC CE, which is used to indicate new beam information and / or BFR information selected by the terminal device; In a case where there is no UL-SCH resource available for transmitting the BFR MAC CE on the one or more frequency domain units, or beam failure occurs on the one or more frequency domain units, the terminal device triggers a scheduling request (SR) for BFR; In a case where there is no UL-SCH resource available for transmitting the BFR MAC CE on the one or more frequency domain units, or no frequency domain unit on which no beam failure occurs, the terminal device triggers a random access procedure.

41. The method of claim 40, wherein, After beam failure occurs on a first frequency domain unit of the one or more frequency domain units, one or more second frequency domain units are determined by the terminal device to have beam failure, and the first frequency domain unit has an association relationship with the one or more second frequency domain units.

42. The method of claim 41, wherein, The association relationship is configured by a network device.

43. The method of any one of claims 40 to 42, wherein, The new beam is determined based on measurement results of at least one candidate beam, each candidate beam corresponding to a reference signal used to determine the measurement result of the candidate beam, and the new beam is used to establish a new link.

44. The method of any one of claims 40 to 43, wherein, The terminal device triggers a random access procedure, including at least one of the following: In a case where there is a reference signal corresponding to a candidate beam, and there is a candidate beam having a dedicated RACH resource, the terminal device triggers a contention-free random access (CFRA) procedure; In a case where there is no reference signal corresponding to a candidate beam, and / or, there is no candidate beam having a dedicated RACH resource, the terminal device triggers a contention-based random access (CBRA) procedure; In a case where the measurement results of the candidate beams are all lower than a first threshold, the terminal device triggers a CBRA procedure.

45. The method of claim 44, wherein, The dedicated RACH resource is used to indicate a new beam determined by the terminal device.

46. The method of claim 44, wherein, In the CBRA procedure, Msg3 or MsgA is used to carry the BFR MAC CE.

47. The method of claim 38, wherein, In a case where a timing advance timer (TAT) of a first timing advance group (TAG) times out, the first behavior includes: releasing transmission resources of all frequency domain units in the first TAG; and / or triggering a random access procedure.

48. The method of claim 38 or 47, wherein, In a case where TATs of all TAGs of the terminal device time out, the first behavior includes triggering a random access procedure.

49. The method of claim 47 or 48, wherein, The terminal device triggers a random access procedure, including: In a case where the first TAG is configured with a dedicated RACH resource, the terminal device preferentially triggers a CFRA procedure; or In a case where the first TAG is not configured with a dedicated RACH resource, the terminal device triggers a CBRA procedure.

50. The method of claim 48, wherein, In a case where TATs of all TAGs of the terminal device time out, The random access procedure is triggered based on a RACH trigger condition, and the RACH trigger condition includes that TAT of all TAGs of the terminal device is expired. The random access procedure is triggered in a case that uplink data arrives and no available uplink resource exists.

51. The method of any one of claims 47-50, wherein, TA of a frequency domain unit in one TAG is the same, and TA of the frequency domain unit in one TAG refers to a frequency domain unit.

52. The method of claim 51, wherein, The TA reference frequency domain unit is semi-statically configured by the network device.

53. The method of claim 52, wherein, The network device semi-statically configures identification information of the TA reference frequency domain unit.

54. The method of any one of claims 51 to 53, wherein, The TA reference frequency domain unit is a frequency domain unit supporting downlink transmission in the TAG.

55. The method of any one of claims 51 to 54, wherein, one TAG includes at least one frequency domain unit supporting uplink transmission; and / or, one TAG includes at least one frequency domain unit supporting downlink transmission.

56. The method of claim 38, wherein, The first behavior is based on sending and / or receiving data on the one or more frequency domain units by a physical downlink control channel (PDCCH).

57. The method of claim 56, wherein, The one or more frequency domain units correspond to a PDCCH and / or a physical uplink control channel (PUCCH) configured by the network device.

58. The method of claim 56 or 57, wherein, One frequency domain unit in the one or more frequency domain units corresponds to one or more PDCCHs, and the plurality of PDCCHs are located on the same or different frequency domain units; or, One frequency domain unit corresponds to one or more PUCCHs, and the plurality of PUCCHs are located on the same or different frequency domain units.

59. The method of claim 58, wherein, A correspondence between the plurality of PUCCHs and transmission resources on the frequency domain units is semi-statically configured by using a time domain pattern.

60. The method of any one of claims 56 to 59, wherein, The PDCCH is further used to indicate identification information of the one or more frequency domain units.

61. The method of any one of claims 56 to 60, wherein, The PDCCH is further used to indicate identification information of a frequency domain unit where a PUCCH for hybrid automatic repeat request (HARQ) feedback is located.

62. The method of claim 38, wherein, The first behavior is sending a power headroom report (PHR) MAC CE, and the PHR MAC CE is used to report PHR information based on frequency domain unit granularity.

63. The method of claim 62, wherein, The PHR information includes at least one of: a first type of power headroom, which is a difference between a nominal maximum transmit power of the terminal device on an activated uplink frequency domain unit and estimated power of UL-SCH transmission; a second type of power headroom, which is a difference between the nominal maximum transmit power of the terminal device on an uplink frequency domain unit of another MAC entity and estimated power of the UL-SCH and PUCCH transmission; a third type of power headroom, which is a difference between the nominal maximum transmit power of the terminal device on the activated uplink frequency domain unit and estimated power of sounding reference signal (SRS) transmission; a maximum permissible exposure power additional maximum power reduction (MPE P-MPR), which is a power backoff for meeting an MPR requirement of an uplink frequency domain unit on a frequency range (FR2); a DPC, which is a maximum output power adjustment of a given power class for an uplink frequency domain unit on FR1; and a DPC, which is a maximum output power adjustment of a given power class for an uplink frequency domain unit on FR1. DPCBC, the DPCBC being a maximum output power adjustment for a band combination on FR1 for a given power class.

64. The method of claim 62 or 63, wherein, The first behavior is triggered based on at least one of the following conditions: activating one or more uplink frequency domain units; deactivating one or more uplink frequency domain units; adding one or more uplink frequency domain units; deleting one or more uplink frequency domain units.

65. The method of claim 38, wherein, The first behavior is triggering a tracking area update (TAU).

66. The method of claim 65, wherein, The method further comprises: sending first signaling including configuration information of a new cell, the first signaling being used for adding the new cell for the terminal device. The first signaling includes first information for the new cell, the first information being a serving TAI, or the first information being indication information of not performing TAU.

67. The method of claim 66, wherein, The serving TAI is different from a TAI broadcast by the new cell.

68. The method of claim 67, wherein, 69. The method of claim 67 or 68, wherein: the serving TAI belongs to a TAI list of the terminal device; and / or the serving TAI is one of TAIs of one or more cells configured for the terminal device. The indication information of not performing TAU is carried in the configuration information of the new cell.

70. The method of claim 67, wherein, The performing the first behavior includes at least one of:

71. The method of any one of claims 67-70, wherein, the terminal device triggering TAU if the serving TAI does not belong to the TAI list of the terminal device; the terminal device not triggering TAU if the serving TAI belongs to the TAI list of the terminal device; the terminal device triggering TAU if all cells configured for the terminal device use the serving TAI or TAIs broadcast by all cells configured for the terminal device do not belong to the TAI list of the terminal device. The performing the first behavior includes at least one of:

72. The method of any one of claims 67-70, wherein, the terminal device not performing TAU caused by a TAI of a first cell if the terminal device receives indication information of not performing TAU for the first cell; the terminal device performing TAU if the terminal device receives indication information of not performing TAU for all cells configured for the terminal device. The performing the first behavior includes at least one of:

73. The method of any one of claims 65 to 72, wherein, the terminal device not triggering TAU if at least one TAI broadcast by at least one configured cell belongs to the TAI list of the terminal device; the terminal device triggering TAU if all TAIs broadcast by all configured cells do not belong to the TAI list of the terminal device. The frequency domain unit is any of the following: a cell, a carrier, a frequency band, a subband, a bandwidth, a band.

74. The method of any one of claims 38 to 73, wherein, The apparatus comprises:

75. An apparatus for spectrum aggregation, comprising: a processing module configured to perform a first behavior based on one or more frequency domain units. The apparatus comprises:

76. A spectrum aggregating apparatus, comprising: a processing module configured to perform a first behavior based on one or more frequency domain units in response to a terminal device. ​ 77. A communications device, comprising: The communication device comprises a processor and a memory, the memory storing a computer program, the processor executing the computer program to implement the method of any one of claims 1 to 37, or to implement the method of any one of claims 38 to 74.

78. A computer-readable storage medium, comprising: The storage medium stores a computer program, the computer program being configured to be executed by a processor to implement the method of any one of claims 1 to 37, or to implement the method of any one of claims 38 to 74.

79. A chip, comprising: The chip comprises programmable logic circuitry and / or program instructions, which when executed by the chip, are configured to implement the method of any one of claims 1 to 37, or to implement the method of any one of claims 38 to 74.

80. A computer program product, characterised in that, The computer program product comprises computer instructions stored in a computer-readable storage medium, the computer instructions being read and executed by a processor to implement the method of any one of claims 1 to 37, or to implement the method of any one of claims 38 to 74.

Images