Apparatus and method for communication

Abstract

Embodiments of the present disclosure provide a solution for secondary cell (Scell) configuration in a non-terrestrial network (NTN). In one solution, a terminal device receives configuration information from a network device, the configuration information comprising at least one of: a first list comprising at least one Scell condition configuration for addition or modification of at least one Scell in an NTN; or a second list comprising at least one Scell condition configuration for release of at least one Scell in the NTN, where the Scell condition configuration in the first list or the second list at least comprises an execution condition for addition, modification or release of the Scell. And according to a determination that at least one execution condition in the at least one Scell condition configuration is satisfied, the terminal device executes addition, modification and / or release of the at least one Scell according to the at least one Scell condition configuration.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein relate generally to the field of communication technology, and more particularly to devices and methods for configuring secondary cells (Scells) in non-terrestrial networks (NTNs). Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) is also collaborating with the satellite communications industry to develop integrated satellite and terrestrial network infrastructure specifications within the context of fifth-generation (5G) technology. This is known as Non-Terrestrial Network (NTN), a term referring to networks or network segments that use airborne or spacecraft for transmission. Satellites refer to spacecraft in Low Earth Orbit (LEO), Medium Earth Orbit (MEO), and Geostationary Earth Orbit (GEO) (also known as Geostationary Stationary Orbit (GSO)). Airborne vehicles refer to High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) (including tethered UAS, lighter-than-air UAS, and heavier-than-air UAS, all of which operate quasi-stationarily at altitudes typically between 8 km and 50 km). Satellites in GEO have an exact 24-hour cycle. Satellites in MEO take approximately 12 hours to complete the same orbit, with a speed of about 3.13 km / s. Satellites in LEO, such as the International Space Station, take approximately 1.5 hours to orbit the Earth, with a speed of about 7.56 km / s. Summary of the Invention

[0003] Overall, the embodiments disclosed herein provide a solution for secondary cell (Scell) configuration in non-terrestrial networks (NTN).

[0004] In a first aspect, a terminal device is provided, the terminal device comprising: a processor configured to cause the terminal device to: receive configuration information from a network device, the configuration information including at least one of: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN), or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN, wherein the Scell ​​condition configuration in the first list or the second list includes at least execution conditions for adding, modifying, or releasing a secondary cell; and, based on determining that at least one execution condition in the at least one Scell ​​condition configuration is satisfied, perform the addition, modification, and / or release of at least one secondary cell according to the at least one Scell ​​condition configuration.

[0005] In a second aspect, a network device is provided, the network device comprising: a processor configured to cause the network device to: determine configuration information for a terminal device, the configuration information including at least one of: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN), or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN, wherein the Scell ​​condition configuration in the first list or the second list includes at least execution conditions for adding, modifying, or releasing a secondary cell; and send the configuration information to the terminal device.

[0006] In a third aspect, a communication method performed by a terminal device is provided. The method includes: receiving configuration information from a network device, the configuration information including at least one of the following: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN); or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN, wherein the Scell ​​condition configuration in the first list or the second list includes at least execution conditions for adding, modifying, or releasing a secondary cell; and performing the addition, modification, and / or release of at least one secondary cell according to the at least one Scell ​​condition configuration based on determining that at least one execution condition in the at least one Scell ​​condition configuration is satisfied.

[0007] In a fourth aspect, a communication method performed by a network device is provided. The method includes: determining configuration information for a terminal device, the configuration information including at least one of the following: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN); or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN, wherein the Scell ​​condition configuration in the first list or the second list at least includes execution conditions for adding, modifying, or releasing a secondary cell; and sending the configuration information to the terminal device.

[0008] In a fifth aspect, a computer-readable medium is provided that stores instructions which, when executed on at least one processor, cause the at least one processor to perform the method according to the third or fourth aspect.

[0009] Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The above and other objects, features, and advantages of this disclosure will become more apparent from a more detailed description of some exemplary embodiments thereof in the accompanying drawings, wherein: Figure 1 An example communication environment in which an example implementation of the present disclosure can be carried out is illustrated; Figures 2A to 2D This illustrates a possible specific implementation of a radio access network (RAN) that can be used in an NTN environment; Figure 3 Example communication modes supported in an NTN environment are illustrated; Figure 4 Signaling flows configured in an Scell ​​within an NTN according to some embodiments of this disclosure are illustrated; Figure 5 Flowcharts illustrating methods implemented at a terminal device according to some example embodiments of this disclosure are shown; Figure 6 Flowcharts illustrating methods implemented at a network device according to some example embodiments of this disclosure are shown; and Figure 7 A simplified block diagram of an apparatus suitable for implementing an example embodiment of the present disclosure is shown.

[0011] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0012] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art to understand and implement this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.

[0013] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0014] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to: user equipment (UE); personal computers; desktop computers; mobile phones; cellular phones; smartphones; personal digital assistants (PDAs); portable computers; tablets; wearable devices; Internet of Things (IoT) devices; Ultra-reliable and Low-Latency Communication (URLLC) devices; Internet of Everything (IoE) devices; machine-type communication (MTC) devices; devices on vehicles for V2X communication, where X refers to pedestrians, vehicles, or infrastructure / networks; devices for Integrated Access and Backhaul (IAB); spacecraft or aerospace vehicles in non-terrestrial networks (NTNs), including satellites and high-altitude platforms (HAPs) covering Unmanned Aircraft Systems (UAS); and different types of reality (such as Augmented Reality (AR), Mixed Reality (MR)). Extended Reality (XR) devices, including those for Virtual Reality (VR) and Virtual Reality (VR); unmanned aerial vehicles (UAVs), often referred to as drones (aircraft without human pilots); devices on high-speed trains (HSTs); or image capture devices such as digital cameras and sensors; gaming devices; music storage and playback equipment; or internet devices enabling wireless or wired internet access and browsing. "Terminal devices" may further possess "multicast / broadcast" characteristics to support public safety and mission-critical applications, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, wireless software delivery, group communications, and IoT applications. "Terminal devices" may also incorporate one or more Subscriber Identity Modules (SIMs), the latter being referred to as multi-SIMs.The term "terminal equipment" is used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless equipment.

[0015] The term "network device" refers to a device that provides or hosts a cell or coverage area for terminal devices to communicate. Examples of network devices include, but are not limited to, NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), next-generation NodeBs (gNBs), transmission reception points (TRPs), remote radio units (RRUs), radioheads (RHs), remote radio heads (RRHs), IAB nodes, low-power nodes (such as femtonodes and piconodes), reconfigurable intelligent surfaces (RISs), etc.

[0016] Terminal devices or network devices may have artificial intelligence (AI) or machine learning capabilities. Terminal devices or network devices typically include models that have been trained on specific functions based on a large amount of collected data and can be used to predict some information.

[0017] Terminal or network devices can operate within several frequency ranges, such as FR1 (e.g., 450MHz to 6000MHz), FR2 (e.g., 24.25GHz to 52.6GHz), bands greater than 100GHz, and terahertz (THz), and can also operate on licensed / unlicensed / shared spectrum. In Multi-Radio Dual Connectivity (MR-DC) applications, terminal devices can be connected to more than one network device. Terminal or network devices can operate in full-duplex, flexible-duplex, and cross-division duplex modes.

[0018] The embodiments of this disclosure can be executed in test equipment (e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal equipment, test network equipment, channel simulator). In some embodiments, the terminal equipment can be connected to a first network equipment and a second network equipment. One of the first network equipment and the second network equipment can be a master node, and the other can be a slave node. The first network equipment and the second network equipment can use different radio access technologies (RATs). In some embodiments, the first network equipment can be a first RAT device, and the second network equipment can be a second RAT device. In some embodiments, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs can be sent to the terminal equipment from at least one of the first network equipment or the second network equipment. In some embodiments, first information can be sent from the first network equipment to the terminal equipment, and second information can be sent from the second network equipment directly or via the first network equipment to the terminal equipment. In some embodiments, information configured by the second network equipment and related to the configuration of the terminal equipment can be sent from the second network equipment via the first network equipment. Information configured by the second network device and related to the reconfiguration of the terminal device can be sent directly from the second network device or via the first network device to the terminal device.

[0019] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one implementation” and “implementation” should be understood as “at least one implementation.” The term “another implementation” should be understood as “at least one other implementation.” The terms “first,” “second,” etc., may refer to different or the same objects. Other explicit and implicit definitions are given below.

[0020] In some examples, values, programs, or devices are described as “best,” “lowest,” “highest,” “smallest,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a choice can be made among many alternative functionalities used, and that such a choice is not necessarily better, smaller, higher, or otherwise preferred than other choices.

[0021] As used herein, the terms “resource,” “transmission resource,” “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as a resource in the time domain, a resource in the frequency domain, a resource in the spatial domain, a resource in the code domain, or any other resource used to implement communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources to describe some exemplary embodiments of this disclosure. It should be noted that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.

[0022] Communication in the communication environment may conform to any suitable standard, including but not limited to Global System for Mobile Communication (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Embodiments of this disclosure may be implemented according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, 5G-Advanced Networks, or sixth-generation (6G) networks.

[0023] Figure 1 A schematic diagram of an example communication environment 100 in which an example embodiment of the present disclosure may be implemented is illustrated. Environment 100 involves one or more satellite or UAS platforms 130-1, 130-2, NTN gateway 140, data network 150, one or more terminal devices 110 and one or more network devices 120.

[0024] NTN Gateway 140 is an earth station or gateway located on the Earth's surface, providing sufficient radio frequency (RF) power and RF sensitivity for access to satellites (HAPS, high altitude platform stations). NTN Gateway 140 can be considered a transport network layer (TNL) node. A feeder link or radio link is a wireless link between the NTN gateway and the satellites (or UAS platforms). These satellites or UAS platforms 130-1, 130-2 (collectively or individually referred to as satellites or UAS platforms 130) can establish feeder links with NTN Gateway 140, and such links are necessary if there is no inter-satellite link (ISL) between different satellites 130.

[0025] A service link or radio link is the wireless link between terminal device 110 and satellite (or UAS platform) 130. Beam coverage area 112 is the area of ​​Earth visible to the satellite. From the field of view of the satellite (or UAS platform) 130, more than one coverage area 112 can be covered. Typically, determining whether a terminal device can communicate with a satellite depends on whether and when the satellite's signal coverage area will cover the terminal device.

[0026] Subsequent connections are supported by NTN payloads. In one example, an NTN gateway can serve multiple NTN payloads. In another example, an NTN payload can be served by multiple NTN gateways.

[0027] Three types of service links are supported in NTN. In the Earth-fixed type, the service link is provided by a beam that continuously covers the same geographic area (e.g., in the case of GSO satellites). In the Quasi-Earth-fixed type, the service link is provided by a beam that covers one geographic area for a limited time period and a different geographic area for another time period (e.g., in the case of non-GSO (NGSO) satellites generating steerable beams). In the Earth-moving type, the service link is provided by a beam whose coverage area slides across the Earth's surface (e.g., in the case of NGSO satellites generating fixed or unsteerable beams).

[0028] Figures 2A to 2D Examples 200, 201, 202, and 203 illustrate possible specific implementations of a radio access network (RAN) that can be used in an NTN environment. For example... Figures 2A to 2D As seen, new radio (NR) - RAN can be implemented in a variety of different ways in an NTN environment, and therefore the interface between different entities can vary in different specific implementations. Figure 2AThe specific implementation 200 illustrates a networked RAN architecture with transparent satellites, where satellites and NTN gateways are considered remote radio units. Figure 2B The specific implementation 201 illustrates a regenerable satellite with payloads processed by ISL and network devices (e.g., gNB). Figure 2C Specific implementation 202 shows a regenerated satellite with a payload that does not have ISL (e.g., gNB) processing. Figure 2D Specific implementation 203 illustrates an NG-RAN with regenerative satellites based on a distributed unit (DU) of a network device, the DU being connected to a central unit (CU) of the same network device within the NG-RAN. The regenerative payload is a payload that transforms and amplifies the uplink RF signal before transmission on the downlink. Signal transformation refers to digital processing that may include demodulation, decoding, recoding, remodulation, and / or filtering. The transparent payload is a payload that changes the frequency carrier of the uplink RF signal, filters, and amplifies it before transmission on the downlink.

[0029] Figure 3 Example 300 illustrates the communication modes supported in an NTN environment. As shown, terminal device 110-1 supports aggregation type of Multiple Radio Access Technology (RAT) dual connectivity (MR-DC) and also supports aggregation type of E-UTRAN New Radio Dual Connectivity (EN-DC) with network device 120 and satellite 130-1. Terminal device 110-2 supports aggregation type of MR-DC with satellites 130-1 and 130-2. Terminal device 110-3 supports aggregation type of carrier aggregation (CA) with satellite 130-2. It should be understood that MR-DC is applicable to inter-satellite / intra-satellite scenarios and NTN-TN inter-scenario scenarios, EN-DC is applicable to NTN-TN inter-scenario scenarios, and CA is applicable to intra-satellite scenarios.

[0030] It should be understood that Figures 1 to 3 The number of devices and their connections are given for illustrative purposes and do not imply any limitation on this disclosure. These environments may include any suitable number of devices appropriate for a particular implementation of this disclosure.

[0031] In a traditional TN (Network Transmission Network), the terminal device reports Scell ​​measurements to the network device. Based on this measurement report, the network device decides to add, modify, or release Scell ​​configurations and transmits these configurations to the terminal device. In this scenario, the latency of adding / modifying / releasing Scells is significant. In NTN (Network Transmission Network), due to long propagation delays and rapid satellite movement, the traditional methods for adding, modifying, or releasing Scell ​​configurations used in TN may not perform well. Sometimes, in CA (Cybernetic Application) scenarios, the configurations for adding, modifying, and / or releasing secondary cells (SCells) may be outdated by the time they reach the terminal device.

[0032] According to an example embodiment of this disclosure, conditional Scell ​​addition, modification, and / or release are proposed in an NTN. A network device sends at least one Scell ​​conditional configuration for adding, modifying, and / or releasing at least one Scell ​​to an end device. The end device evaluates the execution conditions in at least one received Scell ​​conditional configuration. If one or more execution conditions are met, the end device can perform the addition, modification, and / or release of the Scell. In this way, the end device can successfully add, modify, or release an Scell ​​when the evaluation conditions are appropriate, without worrying about Scell ​​configurations becoming outdated due to long propagation delays and rapid satellite movement in an NTN.

[0033] Figure 4 Signaling flow 400 configured in an Scell ​​within an NTN according to some embodiments of this disclosure is illustrated. For discussion purposes, reference will be made to... Figure 1 Discuss signaling flow 400. This signaling flow involves terminal device 110 and network device 120.

[0034] In signaling flow 400, network device 120 sends (405) and terminal device 110 receives (410) configuration information related to at least one Scell ​​condition configuration. This configuration information includes a first list containing at least one secondary cell (Scell) condition configuration for adding or modifying at least one Scell ​​in a non-terrestrial network (NTN). Alternatively or additionally, the configuration information includes a second list containing at least one Scell ​​condition configuration for releasing at least one Scell ​​in the NTN. The Scell ​​condition configurations in the first or second list at least include execution conditions for adding, modifying, or releasing an Scell. In some embodiments, the configuration information may include multiple Scell ​​condition configurations.

[0035] In some implementations, the Scell ​​condition configuration may also include a configuration identifier (ID), the cell ID of the Scell, and / or cell configuration information for that Scell. In some implementations, a timer may be included in the Scell ​​condition configuration to indicate verification of the condition configuration. In some implementations, conditional Scell ​​release may be configured to release one or more Scells. Details of the Scell ​​condition configuration will be further described below.

[0036] In some implementations, terminal device 110 may send (415) capability information to network device 120. This capability information may indicate whether terminal device 110 supports condition addition, condition modification, and / or condition release for Scells. In some implementations, the capability information may include: a first parameter indicating whether the terminal device supports condition addition for Scells, a second parameter indicating whether the terminal device supports condition modification for Scells, and / or a third parameter indicating whether the terminal device supports condition release for Scells. In some implementations, support for condition addition, condition modification, and / or condition release may be indicated by frequency band.

[0037] Table 1 is an example of parameter definitions used in the capability information to support condition addition, condition modification, and / or condition release.

[0038] Table 1

[0039] In Table 1, " ConditionalScellAddition "This indicates the first parameter added to indicate whether the terminal device supports Scell." ConditionalScellModification "This indicates the second parameter used to indicate whether the terminal device supports Scell ​​condition modification." ConditionalScellRelease This indicates the third parameter used to indicate whether the terminal device supports conditional release of Scell. The parameter " nonTerrestrialNetwork-r17 "This is used to indicate whether the terminal device supports operation in NTN. In Table 1, "M" in the column name indicates whether the corresponding parameter is required; "FDD-TDD DIFF" indicates whether the corresponding parameter is different in Frequency Division Duplexing (FDD) mode and Time Division Duplexing (TDD) mode; "FR1-FR2 DIFF" indicates whether the corresponding parameter is different in FR1 and FR2."

[0040] Network device 120 can receive (420) capability information and prepare configuration information related to Scell ​​condition configuration based on the capability information of terminal device 110. For example, if terminal device 110 supports adding, modifying, and / or releasing Scell ​​conditions, network device 120 can include Scell ​​condition configurations for adding, modifying, and / or releasing Scells in the configuration information. Otherwise, if terminal device 110 does not support adding, modifying, and / or releasing Scell ​​conditions, network device 120 can configure terminal device 110 to add, modify, and / or release Scells using non-Scell ​​condition configurations for adding, modifying, and / or releasing.

[0041] In some implementations, network device 120 may receive Scell ​​measurements reported from terminal device 110, and the measurement reports may trigger network device 120 to prepare Scell ​​condition configuration.

[0042] In some implementations, terminal device 110 may send (425) feedback information to network device 120 to indicate receipt of configuration information. By receiving (430) this feedback information, network device 120 can determine that terminal device 110 has successfully received the Scell ​​condition (add, modify, or release) configuration. In some implementations, this feedback information may be sent via Layer 1 or higher-layer signaling such as acknowledgment (ACK) or RRC reconfiguration signaling.

[0043] After successfully receiving at least one Scell ​​condition configuration from the configuration information, terminal device 110 evaluates (435) whether the execution conditions in the received Scell ​​condition configuration are met. In some embodiments, the execution conditions may be related to a measurement of the corresponding Scell. Terminal device 110 may use the measurement of the Scell ​​to determine whether the execution conditions are met. Based on the determination that at least one execution condition in the at least one Scell ​​condition configuration is met, terminal device 110 performs (440) the addition, modification, and / or release of at least one Scell ​​according to the at least one Scell ​​condition configuration. In some cases, the Scell ​​identified in the received Scell ​​condition configuration may be referred to as a "candidate" Scell, and the Scell ​​determined to be added, modified, or released may be referred to as a "target" Scell.

[0044] In some implementations, after successfully adding, modifying, and / or releasing at least one Scell, the terminal device 110 may not release other Scell ​​conditional configurations used for adding, modifying, and / or releasing. That is, the terminal device 110 may perform the addition, modification, and / or release of at least one Scell ​​based on the at least one Scell ​​conditional configuration, without releasing one or more other Scell ​​conditional configurations included in the configuration information. This differs from the Conditional Handover (CHO) scenario, where the terminal device 110 discards the conditional configurations used for handover to other target cells if the execution conditions of the target cell in the conditional configuration for handover are met.

[0045] In some implementations, if multiple execution conditions in multiple Scell ​​condition configurations are met, the terminal device 110 can perform the addition, modification, and / or release of multiple Scells according to the multiple Scell ​​condition configurations. That is, if multiple execution conditions are met, the addition, modification, and / or release of multiple Scells can be performed. This differs from the CHO scenario, where only one target cell is selected for handover when the execution conditions are met.

[0046] In some implementations, if terminal device 110 receives an unconditional Scell ​​add / modify / release configuration before executing the condition, terminal device 110 can directly perform Scell ​​add / modify / release based on the received configuration, regardless of the Scell ​​condition configuration used for adding, modifying, or releasing.

[0047] In some implementations, terminal device 110 may send (445) indication information to network device 120 indicating the addition, modification, and / or release of at least one Scell. This indication information may include the Scell ​​ID of the Scell ​​being added, modified, and / or released. By receiving (450) this indication information, network device 120 can determine which Scell ​​was added, modified, and / or released, and thus determine the operation associated with terminal device 110 within the corresponding Scell.

[0048] In some implementations, the first Scell ​​condition configuration in the first list may also include at least one of the following: configuration identifier (ID), cell ID of the Scell, or cell configuration information for the Scell.

[0049] In some implementations, at least one of the first list and the second list is also used to include at least one conditional configuration for Conditional Handover (CHO). Therefore, the Scell ​​conditional configuration reuses the traditional conditional reconfiguration used for CHO. In one example, the conditional configurations used for adding or modifying in the CHO and the Scell ​​conditional configurations used for adding or modifying in the first list may be included together with the conditional configurations used for CHO in the list of conditional configurations used for adding or modifying (denoted as ""). CondReconfigToAddModList-r16 Included in the list " CondReconfigToAddModList-r16 The conditional configuration in "" can be represented as " CondReconfigToAddMod-r16 Its information element (IE) is defined in Table 2.

[0050] Table 2

[0051] In Table 2, IE "condReconfigId-r16" represents the configuration ID of the conditional configuration, and IE "condExecutionCond-r16" represents the execution condition. MeasId The relevant execution conditions can be found in the report configuration within the measurement configuration of the RRC reconfiguration information, i.e. RRCReconfiguration -> MeasConfig -> ReportConfigNR The IE command "condRRCReconfig-r16" indicates the cell configuration information used for Scells, which can be found in the Scell ​​configuration information within the RRC reconfiguration information. RRCReconfiguration -> SCellConfig The Scell's cell ID can be found in the physical cell ID within the Scell ​​configuration information in the RRC reconfiguration information, i.e. RRCReconfiguration -> SCellConfig->PhysCellId .

[0052] List CondReconfigToAddModList-r16 The maximum number of conditional configurations in the "" section is now set to the maximum number of target cells for CHO, which is 8 in one example. However, the maximum number of Scells (32 in one example, referencing the Scell ​​index range from 1 to 32) is typically much larger than the maximum number of target cells for CHO. Therefore, the traditional configuration ID is not applicable to adding, modifying, or releasing conditional Scells.

[0053] In some implementations, the maximum value of the IE (e.g., "condReconfigId-r16", sometimes referred to as the first IE), which is configured to indicate a conditional configuration for an Scell ​​or a CHO, can be amplified to identify Scell ​​conditional configurations for all possible Scells. In some implementations, the maximum value of the IE "condReconfigId-r16" can be set based on the maximum number of Scells; for example, it can be set to 32 by referring to an Scell ​​index range from 1 to 32. For example, the definition of the IE "condReconfigId-r16" can be described as follows: Table 3

[0054] In some implementations, the maximum value of IE "condReconfigId-r16" can be set based on the sum of the maximum number of Scells and the maximum number of target cells for CHO; for example, it can be set to 40 (the sum of 8 and 32). In this example, the definition of IE "condReconfigId-r16" can be described as follows: Table 4

[0055] In some example implementations, conditional configurations that can be used as Scell ​​conditional configurations or as CHO conditional configurations (e.g., " CondReconfigToAddMod-r16 In this context, a new conditional configuration ID can be introduced to indicate the configuration ID used for Scell ​​conditional configuration. Therefore, the first IE, configured to indicate the configuration ID used for Scell ​​conditional configuration, is separate from the second IE, configured to indicate the configuration ID used for CHO conditional configuration. The maximum value of the first IE is set independently based on the maximum number of Scells, for example, it can be set to 32.

[0056] In one example, conditional configuration is included. CondReconfigToAddMod-r16 "list" CondReconfigToAddModList-r16 "Can be defined as the maximum number of Scell ​​condition configurations (e.g., 32), or the maximum number of Scell ​​condition configurations and the sum of condition configurations used for CHO (e.g., 40). For example, " CondReconfigToAddModList-r16 "It can be defined in Table 5."

[0057] Table 5

[0058] The definition of the condition configuration in Table 2 can be changed to the following Table 6.

[0059] Table 6

[0060] In Table 6, the IE "condReconfigId-r16" is configured to indicate the configuration ID for conditional configuration used in a CHO, therefore it is defined as an optional IE and is included when "CondReconfigToAddMod-r16" is used for conditional configuration of a CHO (e.g., condReconfig). The IE "ScellCondReconfigId" is used to indicate the configuration ID for conditional configuration of an Scell, therefore it is defined as an optional IE and is included when "CondReconfigToAddMod-r16" is used for conditional configuration of an Scell ​​(e.g., ScellcondReconfig). The conditions for the existence of the IEs "condReconfigId-r16" and "ScellCondReconfigId" are defined in Table 7 below.

[0061] Table 7

[0062] In one example, the IE “ScellCondReconfigId” can be defined as in Table 8, with a value range from 1 to 32.

[0063] Table 8

[0064] In some implementations, the configuration information related to condition configuration includes one or more lists of condition configurations for CHO (e.g., a list of cells added or modified for CHO). condReconfigToAddModList- r16 "and the list of communities released for CHO" condReconfigToRemoveList-r16 ") can be used with the first list for Scell ​​condition configuration (represented as " ScellcondReconfigToAddModList ) and / or the second list (represented as " ScellcondReconfigToRemoveList This means that the CHO's conditional configuration can be separated from the Scell ​​conditional configuration used for adding, modifying, and releasing. For example, an IE carrying configuration information related to conditional configurations can be defined as follows: Table 9

[0065] In Table 9, lists “condReconfigToRemoveList-r16” and “condReconfigToAddModList-r16” are defined to include conditional configurations for CHOs, and lists “ScellcondReconfigToRemoveList” and “ScellcondReconfigToAddModList” are defined to include Scell ​​conditional configurations. The list “ScellcondReconfigToAddModList” is defined to include multiple (e.g., ranging from 1 to 32) Scell ​​conditional configurations for adding or modifying, identified by the configuration ID “ScellCondReconfigId”. The list “ScellcondReconfigToAddModList” can be defined as follows: Table 10

[0066] In Table 10, the Scell ​​condition configuration "ScellCondReconfigToAddMod" included in the list "ScellcondReconfigToAddModList" for adding or modifying Scells may include: IE "ScellcondReconfigId-r16" to indicate the configuration ID, IE "ScellcondExecutionCond-r16" to indicate the execution condition, and IE "ScellcondRRCReconfig-r16" to indicate the cell configuration information used for the Scell, which can be found in the Scell ​​configuration in the RRC reconfiguration information. RRCReconfiguration -> SCellConfig The Scell's cell ID can be found in the physical cell ID within the Scell ​​configuration in the RRC reconfiguration information, i.e. RRCReconfiguration -> SCellConfig->PhysCellId .

[0067] In some implementations, terminal device 110 may store at least one Scell ​​condition configuration along with at least one condition configuration for CHO in the first list in association with a condition configuration variable. For example, terminal device 110 may be specifically associated with the variable " VarConditionalReconfig "The associated conditional configurations for CHOs are stored, and this variable is defined as a cumulative configuration including conditional handover, conditional PSCell addition, conditional PSCell change, or Scell ​​conditional addition / modification configurations. In some implementations, the variable " VarConditionalReconfig "Can be defined as including a list for storing conditional configurations for CHOs (represented as " condReconfigList") and another list (denoted as "") for storing Scell ​​condition configurations used for adding or modifying Scells. SCellcondReconfigList In one example, the variable " VarConditionalReconfig It can be defined as follows: Table 11

[0068] In some implementations, the conditional configuration for CHOs can be separated from the Scell ​​conditional configuration. For example, configuration information including at least one of a first or second list of Scell ​​conditional configurations is separate from configuration information including one or more lists of conditional configurations for CHOs. Therefore, a new IE (Information Interface) can be introduced for configuration information related to Scell ​​conditional configurations, denoted as " ScellConditionalReconfiguration This is defined as the configuration used to add, modify, and release Scell ​​condition reconfigurations. This configuration information... ScellConditionalReconfiguration The definition of "" can be as follows: Table 12

[0069] In the configuration information ScellConditionalReconfiguration In this context, the list "ScellcondReconfigToRemoveList" is defined to include Scell ​​conditional configurations used for releasing Scells, and the list "ScellcondReconfigToAddModList" is defined to include Scell ​​conditional configurations used for adding or modifying Scells. The list "ScellcondReconfigToAddModList" is defined to include multiple (e.g., ranging from 1 to 32) Scell ​​conditional configurations for adding or modifying Scells, identified by the configuration ID "ScellCondReconfigId". The list "ScellcondReconfigToAddModList" can be defined as shown in Table 10.

[0070] When separating the configuration information for CHO and the configuration information for adding, modifying, and releasing conditional Scells, the terminal device 110 may store at least one Scell ​​condition configuration in the first list in association with a first variable of the Scell ​​condition configuration, wherein the first variable is different from the second variable of the condition configuration for CHO (e.g., " VarConditionalReconfig The first variable configured in the Scell ​​condition (represented as ""). VarScellConditionalReconfig ) can be introduced to include cumulative configurations that add / modify configurations based on Scell ​​conditions. In some implementations, variables VarScellConditionalReconfigIt can be defined as a list that includes Scell ​​condition configurations for storing additions or modifications to Scells (represented as ""). SCellcondReconfigList In one example, the variable " VarScellConditionalReconfig It can be defined as follows: Table 13

[0071] In some implementations, the Scell ​​condition configurations in the first or second list may further include a configuration release timer. This configuration release timer may be included in the condition configuration to indicate verification of the condition configuration. In some implementations, the configuration release timer may be configured by network device 120 for each terminal device 110. The configuration release timer starts upon receiving the corresponding Scell ​​condition configuration and stops when the execution condition in the Scell ​​condition configuration is met. That is, if the timer expires but the corresponding execution condition is not met, the terminal device 110 will release the corresponding Scell ​​condition configuration.

[0072] In some implementations, if the first Scell ​​condition configuration in the first list includes a first configuration release timer, the terminal device 110 may start the first configuration release timer upon receiving the first Scell ​​condition configuration. Based on the determination that the first configuration release timer has expired and the execution conditions in the first Scell ​​condition configuration in the first list are not met, the terminal device 110 may determine that the first Scell ​​condition configuration is invalid.

[0073] In a TN network, it can be difficult to estimate a good value for the validity timer because network devices are unaware of the speed and orientation of the end devices. However, this is not a problem in an NTN network because the location, speed, and orientation of the NTN payload are known to both the network devices and the end devices, and given the high speed of the NTN payload, the speed of the end devices can be ignored.

[0074] On the other hand, setting a validity timer for CHO in the TN is inappropriate because the validity timer value needs to be set by the target network device to which the terminal device is handed over (or using input from that target network device), but the processing of the validity timer needs to be done by the source network device of the terminal device. Since resources are reserved in the target cell, the processing (start / run / expiration) of the validity timer needs to be done by the source network device because the terminal device is still connected to the source network device, and the source network device needs to know which potential target cells are currently configured for conditional handover. However, due to the significant transmission delay between NTN gNBs, intra-gNB CA is applied in the NTN, so the terminal device will not switch between network devices after Scell ​​addition, modification, or release. Therefore, the conflict in the above CHO scenario will not occur.

[0075] In some implementations, configuring a release timer can be included in the conditional configuration for reuse. CondReconfigToAddMod-r16 As discussed above, the configuration release timer can be defined in conjunction with the configuration ID. condReconfigId-r16 "Implementation conditions" condExecutionCond-r16 "and community configuration information" condRRCReconfig-r16 The IE is separate from the IE. Therefore, it includes " CondReconfigToAddMod-r16 The condition configuration for "" can be defined as follows: Table 14

[0076] In some implementations, the configuration release timer may be included in a separate Scell ​​condition configuration independent of the condition configuration used for CHO. ScellCondReconfigToAddMod As discussed above, the configuration release timer can be defined in conjunction with the configuration ID. ScellcondReconfigId-r16 "Implementation conditions" ScellcondExecutionCond-r16 "and community configuration information" ScellcondRRCReconfig-r16 The IE is separate from the IE. Therefore, it includes " ScellCondReconfigToAddMod The condition configuration for "" can be defined as follows: Table 15

[0077] In Tables 14 and 15, IE "T_new" represents the configuration release timer configured for conditional configuration. The value of the configuration release timer T_new can be selected from a list of 200 milliseconds (ms200), 400 milliseconds (ms400), 600 milliseconds (ms600), 800 milliseconds (ms800), 1000 milliseconds (ms1000), and 1200 milliseconds (ms1200). Note that the values ​​of "T_new" provided here are only examples, but the range of "T_new" can be from hundreds to thousands of milliseconds.

[0078] In the above implementation, the configuration release timer "T_new" is defined separately from the cell configuration information for the Scell ​​in the Scell ​​condition configuration. Alternatively, in some implementations, the configuration release timer may be included in the cell configuration information in the Scell ​​condition configuration, for example, in the RRC configuration information "RRCReconfiguration", or more specifically, in the Scell ​​configuration information in the RRC reconfiguration information. CondReconfigToAddMod or ScellCondReconfigToAddMod -> RRCReconfiguration -> SCellConfig The Scell ​​condition configuration, including the configuration of the release timer, can be defined as follows: Table 16

[0079] In one example, the definition of IE "T_new" can be provided in Table 17 or Table 18 below, depending on the conditional configuration for application reuse. CondReconfigToAddMod-r16 "Still using Scell ​​conditional configuration" ScellCondReconfigToAddMod ".

[0080] Table 17

[0081] Table 18

[0082] In some implementations, the configuration release timer "T_new" is included in the trigger configuration for the execution condition within the Scell ​​condition configuration. This trigger configuration is used to configure the parameters of the execution condition to trigger the execution of Scell ​​addition, modification, or release. This trigger configuration can be found in the condition trigger configuration information included in the RRC reconfiguration information, i.e. CondRec onfigToAddMod or ScellCondReconfigToAddMod -> RRCReconfiguration -> CondTriggerConfig-r16 Conditional trigger configuration information CondTriggerConfig-r16 This can include multiple condition-triggered events, and the configuration release timer "T_new" can be included in each condition-triggered event. In one example, the condition-triggered configuration information " CondTriggerConfig-r16 "It can be defined as follows (note that Scell ​​conditional configuration is used here)" ScellcondReconfig (As an example).

[0083] Table 19

[0084] Table 19 shows a set of parameters “a3-Offset”, “hysteresis”, and “timeToTrigger” from the conditional triggering event “condEventA3”, as well as similar parameters from other conditional triggering events, applied in the execution conditions.

[0085] In some implementations, a configuration release timer may be included in the Scell ​​condition configuration used for Scell ​​release. Accordingly, the second Scell ​​condition configuration in the second list includes a second configuration release timer and a configuration ID included in the first Scell ​​condition configuration in the first list. In this case, if the second configuration release timer in the second Scell ​​condition configuration in the second list expires, the terminal device 110 may release the first Scell ​​condition configuration identified by the second Scell ​​condition configuration. Therefore, outdated (received at the time defined by the configuration release timer) Scell ​​condition configurations used for addition or modification can be released, so that the terminal device 110 may not need to evaluate the execution conditions in the outdated Scell ​​condition configurations used for addition or modification.

[0086] In some implementations, a condition release condition is proposed. If the measurement of the Scell ​​satisfies the leave condition of the condition triggering event included in the Scell ​​condition configuration, the terminal device 110 may release the corresponding Scell ​​condition configuration used for adding or modifying.

[0087] In a traditional TN, terminal devices can be configured based on Scell ​​settings used for additions or modifications (e.g., ...). CondReconfigToAddMod The Scell ​​configuration is released by the departure condition of the measurement configured in the conditional Scell ​​configuration. This measurement is reported by the terminal device, therefore the delay in releasing the conditional Scell ​​is also significant, similar to the case of Scell ​​addition. In NTN CA, due to long propagation delays and rapid satellite movement, traditional methods may not perform well. When conditional Scell ​​addition / modification is configured, the entry and departure conditions triggered by the measurement report are simultaneously in the conditional trigger configuration information (e.g., ...). CondTriggerConfig It is configured in ). However, if the UE receives condition-triggered configuration information (e.g., CondTriggerConfig If the leave condition is evaluated, the Scell ​​condition configuration can be released directly. Therefore, the leave condition cannot be used directly when the Scell ​​condition configuration is received.

[0088] In some implementations, network device 120 may set time-related parameters in the Scell ​​condition configuration associated with the Scell ​​to indicate when to measure the Scell ​​used for conditional Scell ​​release. In some implementations, network device 120 may be configured such that terminal device 110 should release the corresponding Scell ​​condition configuration if the departure condition is cumulatively met for a period of time or continuously met for a period of time.

[0089] More specifically, in some implementations, the first Scell ​​condition configuration in the first list may include a first execution condition for adding or modifying the Scell, and a second execution condition for releasing the first Scell ​​condition configuration, and a first time-related condition for the second execution condition. The first execution condition may be considered an "entry condition" for adding or modifying the Scell, and the second execution may be considered a "departure condition" for releasing the corresponding Scell ​​condition configuration. The first time-related condition for the second execution condition is included to indicate when the terminal device 110 begins evaluating the second execution (i.e., the departure condition).

[0090] In some implementation schemes, the first-time relevant conditions (referred to as " ConditionalReleaseTime ) may include one or more of the following: The second execution condition is applied after the first time point; A first timer is started when the first Scell ​​condition configuration is received, and the second execution condition is applied when the first timer expires. A first consecutive time interval, wherein after the second execution condition is continuously satisfied for the first consecutive time interval, the first Scell ​​condition configuration is released; or The first cumulative time, wherein the first Scell ​​condition configuration is released after the second execution condition is satisfied.

[0091] In some implementations, the first execution condition and the second execution condition share a set of parameters included in the trigger configuration for the execution condition within the first Scell ​​condition configuration, and therefore the first time-related condition " ConditionalReleaseTime "Included in the trigger configuration as IE" CondTriggerConfig In, for example, it can be configured in the trigger settings. CondTriggerConfig A new IE has been introduced to indicate when to start evaluating leave conditions. In one example, the configuration is triggered. CondTriggerConfig It can be defined as follows: Table 20

[0092] In Table 20, the IE “ConditionalReleaseTime” indicates when the UE begins to evaluate the departure conditions.

[0093] In some implementations, it is assumed that the execution conditions for Scell ​​addition / modification and the execution conditions for Scell ​​release are configured separately. The release condition can be configured in a second list. condReconfigToRemoveList "or" ScellcondReconfigToRemoveList The second Scell ​​condition configuration for releasing the Scell ​​is in the first list. Accordingly, the second Scell ​​condition configuration in the second list includes: the configuration ID of the first Scell ​​condition configuration in the first list, the third execution condition for releasing the Scell ​​in the first Scell ​​condition configuration, and the second time-related condition for the third execution condition. The third execution condition can also be considered as the departure condition for releasing the Scell.

[0094] In some implementations, the second time-related conditions include one or more of the following: The third execution condition is applied after the second time point; A second timer is started when the second Scell ​​condition configuration is received, and the third execution condition is applied when the second timer expires. The second consecutive time period, after the third execution condition is continuously satisfied for the second consecutive time period, releases the second Scell ​​condition configuration; or The second cumulative time is after the third execution condition is satisfied, and the second Scell ​​condition configuration is released.

[0095] In one example, the Scell ​​condition configuration for releasing Scell ​​in the second list can be defined as follows (the " " applies here). condReconfigToRemoveList (As an example).

[0096] Table 21

[0097] In Table 21, “CondReconfigToRemoveList” includes one or more Scell ​​condition configurations used to release “CondReconfigToRemove”. The Scell ​​condition configurations used for release include: “condReconfigId” to indicate the configuration ID of the Scell ​​condition configuration used for adding or modifying, “condExecutionCond” to indicate the execution condition for releasing the Scell ​​in the first Scell ​​condition configuration, and “ConditionalReleaseTime” to indicate the time-related condition used for the execution condition so as to indicate when the terminal device 110 begins to evaluate the release condition.

[0098] According to Table 21, if a Sell release can be configured with separate execution conditions (“ condExecutionCond For adding / modifying an Scell, the Scell ​​entry condition is configured in the Scell ​​condition configuration for adding or modifying the Scell, while the Scell ​​exit condition is configured in the Scell ​​exit condition configuration for releasing the Scell. The Scell ​​exit condition configuration is configured in the Scell ​​condition configuration for releasing the Scell. CondReconfigToRemove Configuration ID in "" condReconfigId "and Scell ​​conditional configurations for adding or modifying" CondReconfigToAddMod Configuration ID in "" condReconfigId "The same and corresponding to one Scell. In some implementations, if the condition Scell ​​addition or modification is not configured, only the Scell ​​condition configuration for release is available." CondReconfigToRemove Configuration ID in "" condReconfigId ".

[0099] In some implementations, as described above, the IE "ConditionalReleaseTime" used for determining when the UE begins evaluating the leave condition can be defined as a specific time or point in time. When using a point in time, this point in time can be Universal Time Code (UTC), such as IE t-Service-r17 defined in SIB19-r17 or t1-Threshold-r17 in condEventT1-r17. UTC is defined as indicating when to begin measuring the candidate Scell. If the leave condition is met, the terminal device 110 can release the corresponding Scell ​​condition configuration. The point in time used for the IE "ConditionalReleaseTime" can be defined as follows: Table 22

[0100] When a timer is applied to IE's "ConditionalReleaseTime", when terminal device 110 receives the Scell ​​condition configuration (e.g., ConditioanlReconfig When the timer expires, the terminal device 110 starts measuring the candidate Scell. If the departure condition is met, the terminal device 110 releases the corresponding Scell ​​condition configuration. The timer used for IE "ConditionalReleaseTime" can be defined as follows: Table 23

[0101] Note that Table 23 provides only examples, and the timer can be set to any other value.

[0102] In some implementations, the IE "ConditionalReleaseTime" can be set to an accumulated time or a continuous time, such that if the release condition is met for an accumulated period of time or continuously for a period of time, the terminal device 110 can release the corresponding Scell ​​condition configuration. In this case, the terminal device 110 can start timing upon receiving the Scell ​​condition configuration.

[0103] The definition of continuous time for IE's "ConditionalReleaseTime" can be as follows: Table 24

[0104] The cumulative time used for IE's "ConditionalReleaseTime" can be defined as follows: Table 25

[0105] Figure 5 A flowchart illustrating a communication method 500 implemented at a terminal device according to some embodiments of the present disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 500 is described from the perspective of terminal device 110.

[0106] At box 510, terminal device 110 receives configuration information from network device, the configuration information including at least one of the following: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN); or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN. The Scell ​​condition configuration in the first list or the second list at least includes execution conditions for adding, modifying, or releasing a secondary cell; and At box 520, based on determining that at least one execution condition in at least one Scell ​​condition configuration is met, terminal device 110 performs the addition, modification, and / or release of at least one secondary cell according to the at least one Scell ​​condition configuration.

[0107] In some example implementations, terminal device 110 may also send capability information to the network device, indicating whether the terminal device supports at least one of the conditions for adding, modifying, or releasing conditions for a secondary cell.

[0108] In some example implementations, the capability information includes at least one of the following: a first parameter indicating whether the terminal device supports adding conditions for a secondary cell, a second parameter indicating whether the terminal device supports modifying conditions for a secondary cell, or a third parameter indicating whether the terminal device supports releasing conditions for a secondary cell.

[0109] In some example implementations, terminal device 110 may also send feedback information to the network device indicating that the configuration information has been received.

[0110] In some example implementations, the terminal device 110 may perform the addition, modification, and / or release of multiple secondary cells based on multiple execution conditions determined to be met in multiple Scell ​​condition configurations.

[0111] In some example implementations, terminal device 110 may perform the addition, modification, and / or release of at least one secondary cell based on the at least one Scell ​​condition configuration, without releasing one or more other Scell ​​condition configurations included in the configuration information.

[0112] In some example implementations, the first Scell ​​condition configuration in the first list may also include at least one of the following: configuration identifier (ID), cell ID of the secondary cell, or cell configuration information for the secondary cell.

[0113] In some example implementations, at least one of the first list and the second list is used to include at least one conditional configuration for Conditional Handover (CHO), wherein a first information element is configured to indicate a configuration ID for a conditional configuration for Scell ​​or for CHO, and the maximum value of the first information element is set based on the maximum number of secondary cells, or based on the sum of the maximum number of secondary cells and the maximum number of target cells for CHO, or wherein the first information element configured to indicate a configuration ID for a conditional configuration for Scell ​​is separate from a second information element configured to indicate a configuration ID for a conditional configuration for CHO, and the maximum value of the first information element is set based on the maximum number of secondary cells.

[0114] In some example implementations, the configuration information also includes at least one list containing at least one conditional configuration for CHO, and the at least one list is separate from at least one of the first list or the second list.

[0115] In some example implementations, the terminal device 110 may also store the at least one Scell ​​condition configuration along with at least one condition configuration for CHO in the first list in association with the condition configuration variable.

[0116] In some example implementations, the configuration information including at least one of the first list or the second list is separate from the configuration information including at least one list, which includes at least one conditional configuration for CHO.

[0117] In some example implementations, the terminal device 110 may also store at least one Scell ​​condition configuration in the first list in association with a first variable of the Scell ​​condition configuration, wherein the first variable is different from the second variable of the condition configuration used for CHO.

[0118] In some example implementations, the Scell ​​condition configuration in the first list or the second list also includes a configuration release timer, wherein the configuration release timer is started when the Scell ​​condition configuration is received and stopped when the execution condition in the Scell ​​condition configuration is met.

[0119] In some example implementations, the first Scell ​​condition configuration in the first list includes a first configuration release timer, and the processor is further configured to cause the terminal device to: determine that the first Scell ​​condition configuration is invalid based on the determination that the first configuration release timer has expired and the execution condition in the first Scell ​​condition configuration in the first list is not met.

[0120] In some example implementations, the configuration release timer is separate from the cell configuration information for the secondary cell in the Scell ​​condition configuration, or the configuration release timer is included in the cell configuration information in the Scell ​​condition configuration, or the configuration release timer is included in the trigger configuration for executing the condition in the Scell ​​condition configuration.

[0121] In some example implementations, the second Scell ​​condition configuration in the second list includes a second configuration release timer and a configuration ID included in the first Scell ​​condition configuration in the first list, wherein the processor is further configured to cause the terminal device to: release the first Scell ​​condition configuration identified by the second Scell ​​condition configuration upon determining that the second configuration release timer in the second Scell ​​condition configuration in the second list has expired.

[0122] In some example implementations, the first Scell ​​condition configuration in the first list includes a first execution condition for adding or modifying a secondary cell, and also includes a second execution condition for releasing the first Scell ​​condition configuration and a first time-related condition for the second execution condition, wherein the first time-related condition includes at least one of the following: a first time point after which the second execution condition is applied; a first timer that starts when the first Scell ​​condition configuration is received and applies the second execution condition when the first timer expires; a first continuous time, wherein the first Scell ​​condition configuration is released after the second execution condition has continuously satisfied the first continuous time; or a first cumulative time, wherein the first Scell ​​condition configuration is released after the second execution condition has satisfied the first cumulative time.

[0123] In some example implementations, the first execution condition and the second execution condition share a set of parameters included in the trigger configuration for the execution condition in the first Scell ​​condition configuration, and wherein the first time-related condition is included as an information element in the trigger configuration.

[0124] In some example implementations, the second Scell ​​condition configuration in the second list includes: a configuration ID of the first Scell ​​condition configuration in the first list, a third execution condition for the release of the secondary cell in the first Scell ​​condition configuration, and a second time-related condition for the third execution condition; wherein the second time-related condition includes at least one of the following: a second time point after which the third execution condition is applied; a second timer that starts when the second Scell ​​condition configuration is received and applies the third execution condition when the second timer expires; a second consecutive time after which the second Scell ​​condition configuration is released after the third execution condition is continuously satisfied for the second consecutive time; or a second cumulative time after which the second Scell ​​condition configuration is released after the third execution condition is satisfied for the second cumulative time.

[0125] In some example implementations, terminal device 110 may also send instruction information to the network device indicating the addition, modification, and / or release of the at least one secondary cell.

[0126] Figure 6 A flowchart illustrating a communication method 600 implemented at a network device according to some embodiments of this disclosure is shown. For discussion purposes, [the following will be discussed]. Figure 1 Method 600 describes the network device 120 from the perspective of network device 120.

[0127] At box 610, network device 120 determines configuration information for terminal devices, the configuration information including at least one of the following: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN), or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN. The Scell ​​condition configuration in either the first or second list includes at least the execution conditions for adding, modifying, or releasing a secondary cell.

[0128] At frame 620, network device 120 sends the configuration information to the terminal device.

[0129] In some example implementations, network device 120 may also receive capability information from the terminal device, which indicates whether the terminal device supports at least one of adding, modifying, or releasing conditions for a secondary cell; and determine the configuration information based on the capability information.

[0130] In some example implementations, the capability information includes at least one of the following: a first parameter indicating whether the terminal device supports adding conditions for a secondary cell, a second parameter indicating whether the terminal device supports modifying conditions for a secondary cell, or a third parameter indicating whether the terminal device supports releasing conditions for a secondary cell. Network device 120 can determine the configuration information for the terminal device based on this capability information.

[0131] In some example implementations, network device 120 may also receive feedback information from the terminal device indicating the receipt of the configuration information.

[0132] In some example implementations, network device 120 may also receive instruction information from the terminal device indicating the addition, modification, and / or release of the at least one secondary cell.

[0133] Figure 7 This is a simplified block diagram of device 700 suitable for implementing embodiments of the present disclosure. Device 700 can be considered as follows: Figure 1 Another example implementation of any of the devices shown. Therefore, device 700 may be implemented at or be at least a part of terminal device 110 or network device 120.

[0134] As shown in the figure, device 700 includes a processor 710, a memory 720 coupled to the processor 710, a suitable transceiver 740 coupled to the processor 710, and a communication interface coupled to the transceiver 740. The memory 720 stores at least a portion of a program 730. Depending on requirements, the transceiver 740 can be used for bidirectional or unidirectional communication. The transceiver 740 may include at least one of a transmitter 742 and a receiver 744. The transmitter 742 and receiver 744 may be functional modules or physical entities. The transceiver 740 has at least one antenna to facilitate communication; however, in practice, the access node mentioned in this application may have several antennas. The communication interface can represent any interface necessary for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between the Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and eNBs / gNBs, the Un interface for communication between eNBs / gNBs and relay nodes (RNs), or the Uu interface for communication between eNBs / gNBs and terminal equipment.

[0135] Assume that program 730 includes program instructions that, when executed by the associated processor 710, enable device 700 to operate according to embodiments of this disclosure, as referenced herein. Figures 1 to 6 The embodiments described herein may be implemented by computer software executable by the processor 710 of device 700, or by hardware, or by a combination of software and hardware. The processor 710 may be configured to implement various embodiments of this disclosure. Furthermore, a combination of the processor 710 and the memory 720 may form a processing unit 750 suitable for implementing various embodiments of this disclosure.

[0136] Memory 720 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 720 is shown in device 700, several physically different memory modules may exist in device 700. Processor 710 can be of any type suitable for a local technology network and may include one or more of the following: as non-limiting examples, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Device 700 may have multiple processors, such as application-specific integrated circuit chips, which are time-dependent on a clock that synchronizes the main processor.

[0137] According to embodiments of this disclosure, a terminal device including circuitry is provided. The circuitry is configured to: receive configuration information from a network device, the configuration information including at least one of the following: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN); or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN, wherein the Scell ​​condition configuration in the first list or the second list includes at least execution conditions for adding, modifying, or releasing a secondary cell; and, based on determining that at least one execution condition in the at least one Scell ​​condition configuration is satisfied, perform the addition, modification, and / or release of at least one secondary cell according to the at least one Scell ​​condition configuration. According to embodiments of this disclosure, the circuitry can be configured to perform any method implemented by the terminal device as discussed above.

[0138] According to embodiments of this disclosure, a network device including circuitry is provided. The circuitry is configured to: determine configuration information for a terminal device, the configuration information including at least one of the following: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN); or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN, wherein the Scell ​​condition configuration in the first list or the second list at least includes execution conditions for adding, modifying, or releasing a secondary cell; and send the configuration information to the terminal device. According to embodiments of this disclosure, the circuitry can be configured to perform any of the methods implemented by the network device as discussed above.

[0139] As used herein, the term "circuit" can refer to hardware circuitry and / or a combination of hardware and software circuitry. For example, a circuit can be a combination of analog and / or digital hardware circuitry with software / firmware. As another example, a circuit can be any part of a hardware processor with software, including digital signal processors, software, and memory, which work together to enable a device (such as a terminal device or network device) to perform various functions. In yet another example, a circuit can be hardware circuitry and / or a processor (such as a microprocessor or a portion thereof) that requires software / firmware to operate, but which may be absent when operation is not required. As used herein, the term "circuit" also encompasses a specific implementation of hardware circuitry or a processor alone, or a portion thereof, and its accompanying software and / or firmware.

[0140] According to embodiments of this disclosure, a first apparatus is provided. The first apparatus includes: components for receiving configuration information from a network device, the configuration information including at least one of the following: components for a first list, the first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN); components for a second list, the second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN; components for: wherein the Scell ​​condition configuration in the first list or the second list includes at least execution conditions for adding, modifying, or releasing a secondary cell; and components for: performing the addition, modification, and / or release of at least one secondary cell according to the at least one Scell ​​condition configuration based on determining that at least one execution condition in the at least one Scell ​​condition configuration is satisfied. In some embodiments, the first apparatus may include components for performing corresponding operations of method 500. In some example embodiments, the first apparatus may also include components for performing other operations of some example embodiments of method 500. The components may be implemented in any suitable form. For example, the components may be implemented as circuits or software modules.

[0141] According to embodiments of this disclosure, a second apparatus is provided. The second apparatus includes: components for determining configuration information for a terminal device, the configuration information including at least one of the following: components for a first list, the first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN); or components for a second list, the second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN; components for: wherein the Scell ​​condition configuration in the first list or the second list includes at least execution conditions for adding, modifying, or releasing a secondary cell; and components for sending the configuration information to the terminal device. In some embodiments, the second apparatus may include components for performing corresponding operations of method 600. In some example embodiments, the second apparatus may also include components for performing other operations of some example embodiments of method 600. The components may be implemented in any suitable form. For example, the components may be implemented as circuits or software modules.

[0142] In summary, the implementation scheme disclosed herein provides the following aspects.

[0143] In one aspect, a terminal device is proposed, comprising: a processor configured to cause the terminal device to: receive configuration information from a network device, the configuration information including at least one of: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN), or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN, wherein the Scell ​​condition configuration in the first list or the second list includes at least execution conditions for adding, modifying, or releasing a secondary cell; and, based on determining that at least one execution condition in the at least one Scell ​​condition configuration is satisfied, perform the addition, modification, and / or release of at least one secondary cell according to the at least one Scell ​​condition configuration.

[0144] In some implementations, the processor is further configured to cause the terminal device to send capability information to the network device, the capability information indicating whether the terminal device supports at least one of condition addition, condition modification, or condition release for a secondary cell.

[0145] In some implementations, the capability information includes at least one of the following: a first parameter indicating whether the terminal device supports adding conditions for a secondary cell, a second parameter indicating whether the terminal device supports modifying conditions for a secondary cell, or a third parameter indicating whether the terminal device supports releasing conditions for a secondary cell.

[0146] In some implementations, the processor is further configured to cause the terminal device to send feedback information to the network device indicating the receipt of the configuration information.

[0147] In some implementations, the processor is configured to cause the terminal device to: perform the addition, modification, and / or release of multiple secondary cells according to the multiple Scell ​​condition configurations, based on the determination that multiple execution conditions among multiple Scell ​​condition configurations are satisfied.

[0148] In some implementations, the processor is configured to cause the terminal device to add, modify, and / or release at least one secondary cell based on the at least one Scell ​​condition configuration, without releasing one or more other Scell ​​condition configurations included in the configuration information.

[0149] In some implementations, the first Scell ​​condition configuration in the first list may also include at least one of the following: configuration identifier (ID), cell ID of the secondary cell, or cell configuration information for the secondary cell.

[0150] In some implementations, at least one of the first list and the second list is used to include at least one conditional configuration for conditional handover (CHO), wherein a first information element is configured to indicate a configuration ID for a conditional configuration for Scell ​​or for CHO, and the maximum value of the first information element is set based on the maximum number of secondary cells, or based on the sum of the maximum number of secondary cells and the maximum number of target cells for CHO, or wherein the first information element configured to indicate a configuration ID for a conditional configuration for Scell ​​is separate from a second information element configured to indicate a configuration ID for a conditional configuration for CHO, and the maximum value of the first information element is set based on the maximum number of secondary cells.

[0151] In some implementations, the configuration information also includes at least one list that includes at least one condition configuration for CHO, and the at least one list is separate from at least one of the first list or the second list.

[0152] In some implementations, the processor is further configured such that the terminal device: stores the at least one Scell ​​condition configuration along with at least one condition configuration for CHO in the first list in association with the condition configuration variable.

[0153] In some implementations, the configuration information including at least one of the first list or the second list is separate from the configuration information including at least one list, which includes at least one conditional configuration for CHO.

[0154] In some implementations, the processor is further configured such that the terminal device: stores at least one Scell ​​condition configuration in the first list in association with a first variable of the Scell ​​condition configuration, wherein the first variable is different from a second variable of the condition configuration used for CHO.

[0155] In some implementations, the Scell ​​condition configuration in the first list or the second list further includes a configuration release timer, wherein the configuration release timer is started when the Scell ​​condition configuration is received and stopped when the execution condition in the Scell ​​condition configuration is met.

[0156] In some implementations, the first Scell ​​condition configuration in the first list includes a first configuration release timer, and the processor is further configured to cause the terminal device to: determine that the first Scell ​​condition configuration is invalid based on the determination that the first configuration release timer has expired and the execution condition in the first Scell ​​condition configuration in the first list is not met.

[0157] In some implementations, the configuration release timer is separate from the cell configuration information for the secondary cell in the Scell ​​condition configuration, or the configuration release timer is included in the cell configuration information in the Scell ​​condition configuration, or the configuration release timer is included in the trigger configuration for executing the condition in the Scell ​​condition configuration.

[0158] In some implementations, the second Scell ​​condition configuration in the second list includes a second configuration release timer and a configuration ID included in the first Scell ​​condition configuration in the first list, wherein the processor is further configured to cause the terminal device to: release the first Scell ​​condition configuration identified by the second Scell ​​condition configuration upon determining that the second configuration release timer in the second Scell ​​condition configuration in the second list has expired.

[0159] In some implementations, the first Scell ​​condition configuration in the first list includes a first execution condition for adding or modifying a secondary cell, and also includes a second execution condition for releasing the first Scell ​​condition configuration and a first time-related condition for the second execution condition, wherein the first time-related condition includes at least one of the following: a first time point after which the second execution condition is applied; a first timer that starts when the first Scell ​​condition configuration is received and applies the second execution condition when the first timer expires; a first continuous time, wherein the first Scell ​​condition configuration is released after the second execution condition has continuously satisfied the first continuous time; or a first cumulative time, wherein the first Scell ​​condition configuration is released after the second execution condition has satisfied the first cumulative time.

[0160] In some implementations, the first execution condition and the second execution condition share a set of parameters included in the trigger configuration for the execution condition in the first Scell ​​condition configuration, and wherein the first time-related condition is included as an information element in the trigger configuration.

[0161] In some implementations, the second Scell ​​condition configuration in the second list includes: a configuration ID of the first Scell ​​condition configuration in the first list, a third execution condition for releasing the secondary cell in the first Scell ​​condition configuration, and a second time-related condition for the third execution condition; wherein the second time-related condition includes at least one of the following: a second time point after which the third execution condition is applied; a second timer that starts when the second Scell ​​condition configuration is received and applies the third execution condition when the second timer expires; a second consecutive time after which the second Scell ​​condition configuration is released after the third execution condition is continuously satisfied for the second consecutive time; or a second cumulative time after which the second Scell ​​condition configuration is released after the third execution condition is satisfied for the second cumulative time.

[0162] In some implementations, the processor is further configured to cause the terminal device to send indication information to the network device indicating the addition, modification, and / or release of the at least one secondary cell.

[0163] In one aspect, a network device is proposed, comprising: a processor configured to cause the network device to: determine configuration information for a terminal device, the configuration information including at least one of: a first list including at least one secondary cell (Scell) condition configuration for adding or modifying at least one secondary cell in a non-terrestrial network (NTN), or a second list including at least one Scell ​​condition configuration for releasing at least one secondary cell in the NTN, wherein the Scell ​​condition configuration in the first list or the second list includes at least execution conditions for adding, modifying, or releasing a secondary cell; and send the configuration information to the terminal device.

[0164] In some implementations, the processor is further configured to cause the network device to: receive capability information from the terminal device, the capability information indicating whether the terminal device supports at least one of condition addition, condition modification, or condition release for a secondary cell; and determine the configuration information based on the capability information.

[0165] In some implementations, the capability information includes at least one of the following: a first parameter indicating whether the terminal device supports adding conditions for a secondary cell, a second parameter indicating whether the terminal device supports modifying conditions for a secondary cell, or a third parameter indicating whether the terminal device supports releasing conditions for a secondary cell.

[0166] In some implementations, the processor is further configured to cause the network device to receive feedback information from the terminal device indicating the receipt of the configuration information.

[0167] In some implementations, the processor is further configured to cause the network device to receive from the terminal device indication information indicating the addition, modification, and / or release of the at least one secondary cell.

[0168] In one aspect, a terminal device includes: at least one processor; and at least one memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, cause the device to perform the methods implemented by the terminal device as discussed above.

[0169] In one aspect, a network device includes: at least one processor; and at least one memory coupled to the at least one processor and storing instructions that, when executed by the at least one processor, cause the device to perform the methods implemented by the network device as discussed above.

[0170] In one aspect, a computer-readable medium storing instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the terminal device discussed above.

[0171] In one aspect, a computer-readable medium stores instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the network device discussed above.

[0172] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the methods discussed above and implemented by the terminal device.

[0173] In one aspect, a computer program includes instructions that, when executed on at least one processor, cause the at least one processor to perform the methods implemented by the network device discussed above.

[0174] Generally, various embodiments of this disclosure can be implemented in hardware or special-purpose circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software executable by a controller, microprocessor, or other computing device. Although various aspects of embodiments of this disclosure are illustrated and described using block diagrams, flowcharts, or other illustrations, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0175] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions (such as those included in program modules) that execute on a target real or virtual processor in a device to perform the functions described above. Figures 1 to 7 The described process or method. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. The functionality of a program module can be combined in various implementation schemes or split among program modules as needed. The machine-executable instructions used for a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0176] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0177] The aforementioned program code may be embodied on a machine-readable medium, which may be any tangible medium that can contain or store a program used by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Further specific examples of machine-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0178] Furthermore, although the operations are described in a specific order, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all the illustrated operations to achieve the desired result. In some environments, multitasking and parallel processing can be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of individual embodiments may also be implemented in a single embodiment in combination. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0179] Although this disclosure has been described using language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.

[0180] Some of the abbreviations used in this disclosure and their full forms are shown below. It should be noted that it may be assumed that widely established and distinctive abbreviations are known.

[0181] Abbreviation List

Claims

1. A terminal device, the terminal device comprising: Processor, the processor being configured to cause the terminal device to: Receive configuration information from a network device, the configuration information including at least one of the following: A first list, comprising at least one secondary cell condition configuration for adding or modifying at least one secondary cell (Scell) in a non-terrestrial network (NTN), or The second list includes at least one Scell ​​condition configuration for the release of at least one secondary cell in the NTN. The Scell ​​condition configuration in the first list or the second list includes at least the execution conditions for adding, modifying or releasing secondary cells; as well as Based on determining that at least one execution condition in at least one Scell ​​condition configuration is met, at least one secondary cell is added, modified, and / or released according to the at least one Scell ​​condition configuration.

2. The device of claim 1, wherein the processor is further configured to cause the terminal device to: Send capability information to the network device, the capability information indicating whether the terminal device supports at least one of the conditions for adding, modifying, or releasing conditions for secondary cells.

3. The device according to claim 2, wherein the capability information includes at least one of the following: The first parameter indicates whether the terminal device supports conditional addition of secondary cells. The second parameter indicates whether the terminal device supports condition modification of the secondary cell, or The third parameter indicates whether the terminal device supports conditional release of the secondary cell.

4. The device according to any one of claims 1 to 3, wherein the processor is configured to cause the terminal device to: Based on the determination that multiple execution conditions in multiple Scell ​​condition configurations are met, multiple secondary cells are added, modified, and / or released according to the multiple Scell ​​condition configurations.

5. The device according to any one of claims 1 to 4, wherein the processor is configured to cause the terminal device to: The addition, modification, and / or release of at least one secondary cell is performed based on the at least one Scell ​​condition configuration, without releasing one or more other Scell ​​condition configurations included in the configuration information.

6. The device according to any one of claims 1 to 5, wherein the first Scell ​​condition configuration in the first list further includes at least one of the following: Configure identifier (ID, identity). The auxiliary community's community ID, or Cell configuration information for the secondary cell.

7. The device of claim 6, wherein at least one of the first list and the second list is used to include at least one conditional configuration for conditional handover (CHO). The first information element is configured to indicate a configuration ID for Scell ​​conditional configuration or CHO conditional configuration, and the maximum value of the first information element is set based on the maximum number of secondary cells, or based on the sum of the maximum number of secondary cells and the maximum number of target cells for CHO, or... The first information element, configured to indicate the configuration ID for Scell ​​conditional configuration, is separated from the second information element, configured to indicate the configuration ID for CHO conditional configuration, and the maximum value of the first information element is set based on the maximum number of secondary cells.

8. The device of claim 6, wherein the configuration information further comprises at least one list, the at least one list including at least one conditional configuration for CHO, and the at least one list is separate from the at least one of the first list or the second list.

9. The device of claim 8, wherein the processor is further configured to cause the terminal device to: In association with the variables configured for the conditions, the at least one Scell ​​condition configuration is stored together with at least one condition configuration for the CHO in the first list.

10. The device of claim 6, wherein the configuration information of at least one of the first list or the second list is separate from the configuration information comprising at least one list, the at least one list comprising at least one conditional configuration for CHO.

11. The device of claim 10, wherein the processor is further configured to cause the terminal device to: The at least one Scell ​​condition configuration is stored in the first list in association with a first variable configured for the Scell ​​condition. The first variable is different from the second variable used for the conditional configuration of CHO.

12. The device according to any one of claims 1 to 11, wherein the Scell ​​condition configuration in the first list or the second list further includes configuring a release timer, and The configuration release timer is started when the Scell ​​condition configuration is received and stopped when the execution condition in the Scell ​​condition configuration is met.

13. The device of claim 12, wherein the first Scell ​​condition configuration in the first list includes a first configuration release timer, and wherein the processor is further configured to cause the terminal device to: Based on the determination that the first configuration release timer has expired and the execution condition in the first Scell ​​condition configuration in the first list is not met, the first Scell ​​condition configuration is determined to be invalid.

14. The device of claim 13, wherein the configuration release timer is included in the cell configuration information in the Scell ​​condition configuration, or The configuration release timer is included in the trigger configuration for executing the condition in the Scell ​​condition configuration.

15. The device of claim 12, wherein the second Scell ​​condition configuration in the second list includes a second configuration release timer and a configuration ID included in the first Scell ​​condition configuration in the first list, wherein the processor is further configured to cause the terminal device to: Upon determining that the second configuration release timer in the second Scell ​​condition configuration in the second list has expired, the first Scell ​​condition configuration identified by the second Scell ​​condition configuration is released.

16. The device according to any one of claims 1 to 15, wherein the first Scell ​​condition configuration in the first list includes a first execution condition for adding or modifying a secondary cell, and further includes a second execution condition for releasing the first Scell ​​condition configuration and a first time-related condition for the second execution condition, and The first time-related condition includes at least one of the following: The second execution condition is applied after the first time point. A first timer is started upon receiving the first Scell ​​condition configuration, and the second execution condition is applied when the first timer expires. The first consecutive time, wherein after the second execution condition is continuously satisfied for the first consecutive time, the first Scell ​​condition configuration is released, or A first cumulative time, wherein the first Scell ​​condition configuration is released after the second execution condition satisfies the first cumulative time.

17. The device of claim 16, wherein the first execution condition and the second execution condition share a set of parameters included in the trigger configuration for the execution condition in the first Scell ​​condition configuration, and The first time-related condition is included as an information element in the trigger configuration.

18. The device according to any one of claims 1 to 17, wherein the second Scell ​​condition configuration in the second list comprises: The configuration ID included in the first Scell ​​condition configuration in the first list. The third execution condition for releasing the secondary cell in the first Scell ​​condition configuration, and The second time-related condition used for the third execution condition; The second time-related condition includes at least one of the following: The third execution condition is applied after the second time point. The second timer starts upon receiving the second Scell ​​condition configuration and applies the third execution condition upon expiration of the second timer. The second consecutive time, wherein after the third execution condition is continuously satisfied for the second consecutive time, the second Scell ​​condition configuration is released, or The second cumulative time, wherein the second Scell ​​condition configuration is released after the third execution condition is satisfied.

19. The device according to any one of claims 1 to 18, wherein the processor is further configured to cause the terminal device to: Send instruction information to the network device indicating the addition, modification, and / or release of the at least one secondary cell.

20. A network device, the network device comprising: Processor, the processor being configured to cause the network device to: Determine configuration information for the terminal device, the configuration information including at least one of the following: A first list, comprising at least one secondary cell condition configuration for adding or modifying at least one secondary cell (Scell) in a non-terrestrial network (NTN), or The second list includes at least one Scell ​​condition configuration for the release of at least one secondary cell in the NTN. The Scell ​​condition configuration in the first or second list includes at least the execution conditions for adding, modifying, or releasing secondary cells; and The configuration information is sent to the terminal device.

Images