Method for determining distribution time domain position, terminal, network equipment and storage medium

Abstract

The invention relates to a method for determining an allocation time domain position, a terminal, network equipment and a storage medium. The method comprises: determining an allocation time domain position of a scheduled physical shared channel (PSCH) according to a timing offset, the timing offset being used for representing an offset of a scheduling timing sequence in carrier aggregation (CA) of a non-terrestrial network (NTN). According to the method disclosed by the invention, the terminal can more accurately determine the distribution time domain position of the PSCH based on the scheduling time sequence difference between different cells in the NTN CA scene, and the scheduling accuracy is improved.

Description

Methods, terminals, network devices, and storage media for determining time-domain location allocation Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method, terminal, network device, and storage medium for determining and allocating time-domain locations. Background Technology

[0002] In non-terrestrial networks (NTNs), the distance between satellites and ground stations is relatively large, resulting in a significant round-trip time (RTT) and excessive timing advance (TA) for terminals. Furthermore, to further improve data rates to support video streaming services, NTNs can also utilize carrier aggregation (CA). CA involves different cells or carriers from different satellites, resulting in significant differences in transmission paths.

[0003] Summary of the Invention

[0004] In the CA scenario of NTN, due to the long satellite-to-ground link, there are significant differences in scheduling timing between different cells.

[0005] This disclosure provides a method, terminal, network device, and storage medium for determining the allocated time domain location.

[0006] In a first aspect, embodiments of this disclosure provide a method for determining the allocated time-domain location, executed by a terminal, the method comprising:

[0007] The timing offset determines the allocation time-domain position of the scheduled Physical Shared Channel (PSCH), where the timing offset is used to represent the offset of the scheduling timing in the Carrier Aggregation (CA) of the Non-Terrestrial Network (NTN).

[0008] Secondly, embodiments of this disclosure provide a method for determining the allocated time-domain location, executed by a network device, the method comprising:

[0009] The first cell sends a downlink control channel (PDCCH) to the terminal. The PDCCH is used to schedule the physical shared channel (PSCH) on the second cell. The first cell and the second cell correspond to different component carriers in the CA.

[0010] The time domain position of the PSCH allocation is determined based on the timing offset, which is used to represent the offset of the scheduling timing in the carrier aggregation (CA) of the non-terrestrial network (NTN).

[0011] Thirdly, embodiments of this disclosure provide a terminal, including:

[0012] The processing module is used to determine the allocation time domain position of the scheduled physical shared channel (PSCH) based on the timing offset, wherein the timing offset is used to represent the offset of the scheduling timing in the carrier aggregation (CA) of the non-terrestrial network (NTN).

[0013] Fourthly, embodiments of this disclosure provide a network device, including:

[0014] The transceiver module is used to send a downlink control channel (PDCCH) to a terminal in a first cell. The PDCCH is used to schedule a physical shared channel (PSCH) in a second cell. The first cell and the second cell correspond to different component carriers in the CA.

[0015] The time domain position of the PSCH allocation is determined based on the timing offset, which is used to represent the offset of the scheduling timing in the carrier aggregation (CA) of the non-terrestrial network (NTN).

[0016] Fifthly, embodiments of this disclosure provide a communication device, including:

[0017] One or more processors;

[0018] The communication device is configured to implement the method described in the first aspect or the second aspect.

[0019] Sixthly, embodiments of this disclosure provide a communication system, including a terminal and a network device, wherein,

[0020] The terminal is configured to implement the method as described in the first aspect;

[0021] The network device is configured to implement the method as described in the second aspect.

[0022] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0023] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0024] Eighthly, embodiments of this disclosure provide a program product, wherein,

[0025] When the program product is executed by a communication device, the communication device performs the method as described in the first aspect or the second aspect.

[0026] In this embodiment of the disclosure, a timing offset is introduced to express the scheduling timing in the CA of NTN, so that the terminal can more accurately determine the allocation time domain position of PSCH based on the scheduling timing differences between different cells in the NTN CA scenario, thereby improving the scheduling accuracy. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0028] Figure 1a is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0029] Figures 1b to 1d are schematic diagrams of scheduling timing provided according to embodiments of the present disclosure;

[0030] Figures 2a and 2b are exemplary interactive schematic diagrams of a method provided according to an embodiment of the present disclosure;

[0031] Figures 3a to 3c are exemplary flowcharts of a method provided according to embodiments of the present disclosure;

[0032] Figures 4a to 4c are exemplary flowcharts of a method provided according to embodiments of the present disclosure;

[0033] Figure 5a is a schematic diagram of the structure of a device according to an embodiment of the present disclosure;

[0034] Figure 5b is a schematic diagram of the structure of a device according to an embodiment of the present disclosure;

[0035] Figure 6a is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0036] Figure 6b is a schematic diagram of a communication device according to an embodiment of the present disclosure. Detailed Implementation

[0037] This disclosure provides a method, terminal, network device, and storage medium for determining the allocated time domain location.

[0038] In a first aspect, embodiments of this disclosure provide a method for determining the allocated time-domain location, executed by a terminal, the method comprising:

[0039] The timing offset determines the allocation time-domain position of the scheduled Physical Shared Channel (PSCH), where the timing offset is used to represent the offset of the scheduling timing in the Carrier Aggregation (CA) of the Non-Terrestrial Network (NTN).

[0040] In the above embodiments, a timing offset is introduced to express the scheduling timing in the CA of NTN, so that the terminal can more accurately determine the allocation time domain position of PSCH based on the scheduling timing differences between different cells in the NTN CA scenario, thereby improving the scheduling accuracy.

[0041] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0042] The receiving network device transmits the Physical Downlink Control Channel (PDCCH) in the first cell. The PDCCH is used to schedule the PSCH in the second cell. The first cell and the second cell correspond to different component carriers in the CA.

[0043] In the above embodiments, in the cross-carrier scheduling scenario, the terminal can more accurately determine the allocation time domain position of the scheduled PSCH based on the introduced timing offset and the scheduling timing offset involved in the CA adapted to NTN.

[0044] In conjunction with the embodiments of the first aspect, in some embodiments, at least one of the first cell and the second cell is configured with a corresponding timing offset.

[0045] In the above embodiments, different cells in the CA of NTN can be configured with corresponding timing offsets, which improves the flexibility of determining the time domain position of PSCH allocation.

[0046] In conjunction with the embodiments of the first aspect, in some embodiments, determining the allocation time-domain position of the scheduled Physical Shared Channel (PSCH) based on the timing offset includes:

[0047] The time domain location of the PSCH allocation is determined based on the timing offset corresponding to the first cell and / or the timing offset corresponding to the second cell.

[0048] In the above embodiments, the terminal can process the timing offsets corresponding to some or all cells when determining the time domain location of the PSCH, which ensures scheduling accuracy while providing a certain degree of flexibility.

[0049] In conjunction with the embodiments of the first aspect, in some embodiments, when determining the time domain location of the PSCH allocation, the timing offset corresponding to the first cell or the timing offset corresponding to the second cell is selected by means of the protocol definition, wherein the PSCH is the Physical Uplink Shared Channel (PUSCH).

[0050] In the above embodiments, based on the protocol definition, the terminal 101 can select the timing offset of which cell during the process of determining the allocation time domain position of the PSCH, thereby saving terminal operations.

[0051] In conjunction with the embodiments of the first aspect, in some embodiments, the PSCH is the Physical Downlink Shared Channel (PDSCH) or the PUSCH.

[0052] In the above embodiments, the cross-carrier scheduling scenario of this disclosure can be applied to uplink scheduling or downlink scheduling. The terminal can accurately determine the allocation time domain position of the scheduled PDSCH or PUSCH based on the timing offset of different cells, thereby improving the accuracy of uplink or downlink scheduling.

[0053] In conjunction with the embodiments of the first aspect, in some embodiments, when configuring frame offsets corresponding to different carriers in the CA, the allocation of time-domain positions is determined based on timing offsets and frame offsets.

[0054] In the above embodiments, the terminal can determine the allocation time domain position of PSCH based on both the frame offset and the timing offset of this embodiment, thereby further improving the accuracy of determining the allocation time domain position in the CA scenario of NTN.

[0055] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0056] Receive the first RRC message sent by the network device. The first RRC message is used to configure the first offset at the cell level.

[0057] Receive the Media Access Control Layer Control Unit (MAC CE) sent by the network device. The MAC CE is used to indicate the second offset at the terminal level.

[0058] The timing offset includes a first offset and a second offset.

[0059] In the above embodiments, the timing offset of the present disclosure embodiments can be defined or configured by reusing related protocols, thereby reducing the introduced parameters and simplifying the processing behavior of the terminal.

[0060] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0061] Receive a second RRC message sent by the network device. The second RRC message is used to configure the timing offset.

[0062] In conjunction with the embodiments of the first aspect, in some embodiments, the second RRC message configures a timing offset on a cell-by-cell basis; or,

[0063] The second RRC message is a terminal-specific signaling message used to configure the timing offset corresponding to the secondary cell.

[0064] In the above embodiments, a timing offset of the present disclosure can be introduced based on a new configuration method, so that the allocation time domain position in the CA scenario of NTN can be determined more specifically.

[0065] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0066] Receive indication information sent by network devices, which is used to indicate the adjustment of timing offset.

[0067] In the above embodiments, the configured timing offset value can be dynamically adjusted based on the indication information of the network device, improving flexibility and making it suitable for different scenarios.

[0068] In conjunction with the embodiments of the first aspect, in some embodiments, the indication information is sent via MAC CE or downlink control information DCI.

[0069] In the above embodiments, the network device can adjust the timing offset of the RRC configuration based on MAC CE or DCI, thereby reducing the latency of adjusting the timing offset and improving the efficiency of determining the PSCH allocation time domain position.

[0070] In conjunction with the embodiments of the first aspect, in some embodiments, the time-domain position is allocated according to the offset. Determined; where K offset #1 represents the timing offset corresponding to the first cell, K offset #2 indicates the timing offset corresponding to the second cell, 2 μPSCH Indicates the subcarrier spacing SCS of the PSCH. K represents offset SCS #1 K represents offset SCS #2; or,

[0071] Assign time domain position based on offset Determined; where K offset_CA #1 represents the timing offset corresponding to the first cell, K offset _CA#2 represents the timing offset corresponding to the second cell, 2 μPSCH Indicates the subcarrier spacing SCS of the PSCH. K represents offset SCS #1 K represents offset SCS #2.

[0072] In the above embodiments, in the scenario of reusing the relevant protocol Koffset and in the scenario of introducing timing offset in a new way, the terminal can apply timing offset in the corresponding way to improve the accuracy of scheduling.

[0073] Secondly, embodiments of this disclosure provide a method for determining the allocated time-domain location, executed by a network device, the method comprising:

[0074] The first cell sends a downlink control channel PDCCH to the terminal. The PDCCH is used to schedule the physical shared channel PSCH on the second cell. The first cell and the second cell correspond to different component carriers in the CA.

[0075] The time domain position of the PSCH allocation is determined based on the timing offset, which is used to represent the offset of the scheduling timing in the carrier aggregation (CA) of the non-terrestrial network (NTN).

[0076] In the above embodiments, a timing offset is introduced to express the scheduling timing in the CA of NTN, so that the terminal can more accurately determine the allocation time domain position of PSCH based on the scheduling timing differences between different cells in the NTN CA scenario, thereby improving the scheduling accuracy.

[0077] In conjunction with the embodiments of the second aspect, in some embodiments, at least one of the first cell and the second cell is configured with a corresponding timing offset.

[0078] In conjunction with the embodiments of the second aspect, in some embodiments, the time domain location of the PSCH allocation is determined based on the timing offset corresponding to the first cell and / or the timing offset corresponding to the second cell.

[0079] In conjunction with the embodiments of the second aspect, in some embodiments, when determining the time domain location of the PSCH allocation, the timing offset corresponding to the first cell or the timing offset corresponding to the second cell is selected by means of the protocol definition, wherein the PSCH is the Physical Uplink Shared Channel (PUSCH).

[0080] In conjunction with the embodiments of the second aspect, in some embodiments, the PSCH is the Physical Downlink Shared Channel (PDSCH) or the PUSCH.

[0081] In conjunction with the embodiments of the second aspect, in some embodiments, when configuring frame offsets corresponding to different carriers in CA, the allocation of time-domain positions is determined based on timing offsets and frame offsets.

[0082] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0083] Send a first RRC message to the terminal. The first RRC message is used to configure the first offset at the cell level.

[0084] Send a Media Access Control Layer Control Unit (MAC CE) to the terminal. The MAC CE is used to indicate the second offset at the terminal level.

[0085] The timing offset includes a first offset and a second offset.

[0086] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0087] A second RRC message is sent to the terminal. The second RRC message is used to configure the timing offset.

[0088] In conjunction with the embodiments of the second aspect, in some embodiments, the second RRC message configures a timing offset on a cell-by-cell basis; or,

[0089] The second RRC message is a terminal-specific signaling message used to configure the timing offset corresponding to the secondary cell.

[0090] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0091] Send an instruction message to the terminal, which is used to instruct on adjusting the timing offset.

[0092] In conjunction with the embodiments of the second aspect, in some embodiments, the indication information is sent via MAC CE or downlink control information DCI.

[0093] In conjunction with the embodiments of the second aspect, in some embodiments, the time-domain position is allocated according to the offset. Determined; where K offset #1 represents the timing offset corresponding to the first cell, K offset #2 indicates the timing offset corresponding to the second cell, 2 μPSCH Indicates the subcarrier spacing SCS of the PSCH. K represents offset SCS #1 K represents offset SCS #2; or,

[0094] Assign time domain position based on offset Determined; where K offset_CA #1 represents the timing offset corresponding to the first cell, K offset _CA#2 represents the timing offset corresponding to the second cell, 2 μPSCH Indicates the subcarrier spacing SCS of the PSCH. K represents offset SCS #1 K represents offset SCS #2.

[0095] Thirdly, embodiments of this disclosure provide a terminal, including:

[0096] The processing module is used to determine the allocation time domain position of the scheduled physical shared channel (PSCH) based on the timing offset, wherein the timing offset is used to represent the offset of the scheduling timing in the carrier aggregation (CA) of the non-terrestrial network (NTN).

[0097] Fourthly, embodiments of this disclosure provide a network device, including:

[0098] The transceiver module is used to send the downlink control channel PDCCH to the terminal in the first cell. The PDCCH is used to schedule the physical shared channel PSCH in the second cell. The first cell and the second cell correspond to different component carriers in the CA.

[0099] The time domain position of the PSCH allocation is determined based on the timing offset, which is used to represent the offset of the scheduling timing in the carrier aggregation (CA) of the non-terrestrial network (NTN).

[0100] Fifthly, embodiments of this disclosure provide a communication device, including:

[0101] One or more processors;

[0102] The communication device is configured to implement the method described in the first aspect or the second aspect.

[0103] Sixthly, embodiments of this disclosure provide a communication system, including a terminal and a network device, wherein,

[0104] The terminal is configured to implement the method as described in the first aspect;

[0105] The network device is configured to implement the method as described in the second aspect.

[0106] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0107] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0108] Eighthly, embodiments of this disclosure provide a program product, wherein,

[0109] When the program product is executed by a communication device, the communication device performs the method as described in the first aspect or the second aspect.

[0110] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in alternative implementations of the first and second aspects.

[0111] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0112] It is understood that the aforementioned terminals, network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0113] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0114] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0115] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0116] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0117] In the embodiments disclosed herein, "multiple" refers to two or more.

[0118] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0119] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0120] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0121] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0122] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0123] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0124] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0125] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "body", etc.

[0126] In some embodiments, "network" can be interpreted as devices included in the network, such as access network devices, core network devices, etc.

[0127] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)," "base station (BS)," "radio base station," or "fixed station." In some embodiments, it may also be understood as "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," or "bandwidth part (BWP)."

[0128] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," etc.

[0129] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0130] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0131] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0132] Figure 1a is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0133] As shown in Figure 1a, the communication system 100 includes a terminal 101 and a network device 102. In a TN network, the network device 102 may include at least one of an access network device and a core network device. In an NTN network, the network device 102 may include one or more of a satellite, a base station (such as a gNB), and a core network device. A base station may include one or more terrestrial base stations, or earth base stations. A satellite can forward information sent by the base station to the terminal 101. The communication link between the satellite and the base station is a feedback link, and the communication link between the satellite and the terminal 101 is a service link. In an NTN, a satellite can establish communication links with multiple terrestrial base stations, and a terrestrial base station can establish communication links with multiple satellites.

[0134] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0135] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a wireless fidelity (WiFi) system.

[0136] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0137] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0138] In some embodiments, a core network device can be a single device comprising one or more network elements, or it can be multiple devices or a group of devices, each comprising all or part of one or more network elements. Network elements can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC). Alternatively, a core network device refers to a network element with a specific function, such as an Access Management Function (AMF) or a Service Management Function (SMF).

[0139] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.

[0140] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1a, or to a part thereof, but are not limited thereto.

[0141] The entities shown in Figure 1a are illustrative. The communication system may include all or some of the entities in Figure 1a, or it may include other entities besides those in Figure 1a. The number and form of each entity are arbitrary. The connection relationship between the entities is illustrative. The entities may not be connected to each other or may be connected in any way. The connection may be direct or indirect, wired or wireless.

[0142] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication processing methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0143] Referring to Figure 1b, in NTN, due to the large RTT of the satellite network, terminal 101 needs a large TA, and the original offset value K2 in the uplink scheduling no longer meets the scheduling requirements. Here, K2 represents the slot difference between the Physical Downlink Control Channel (PDCCH) and the Physical Uplink Shared Channel (PUSCH).

[0144] When network device 102 sends a PDCCH for scheduling PUSCH in slot n, as shown in Figure 1b, due to the excessively large TA, the time slots when K2 = 0, 1, or 2 cannot be used by terminal 101 to send uplink channels. That is, K2 = 0, 1, or 2 are unavailable; only K2 = 3 is available. The problem caused by excessively long RTT during uplink scheduling is solved by introducing an offset Koffset. Koffset can be approximately equal to the TA value. Introducing Koffset will make the aforementioned K2 value available; for example, if the terminal receives Downlink Control Information (DCI) scheduling in slot n, then the terminal in… Send PUSCH.

[0145] Referring to Figure 1c, when multiple cells corresponding to a CA come from different satellites, scheduling discrepancies exist in downlink scheduling. For example, as shown in Figure 1c, when different component carriers (CCs) in the CA of an NTN correspond to cell#1 and cell#2, and cell#1 and cell#2 come from different satellites, such as cell#1 coming from a satellite in Low Earth Orbit (LEO) at 600km and cell#2 coming from a satellite in LEO at 2000km.

[0146] When network device 102, such as a gNB, sends a PDCCH on cell #1 to schedule the PDSCH on cell #2, the original offset K0 no longer meets the scheduling requirements. Here, K0 represents the slot difference between the PDCCH and PDSCH. For example, if K0 = 0, although terminal 101 can receive the PDCCH on cell #1, due to the difference between the two cells, terminal 101 has not yet received the PDSCH on cell #2. That is, K0 = 0 will result in terminal 101 not receiving the downlink signal on cell #2 at this time, therefore K0 = 0 is unusable. A new offset needs to be introduced to compensate for the scheduling difference between the two cells. At the same time, to facilitate scheduling by network device 102, it is necessary to consider adjusting the offset value of the time difference between the two cells.

[0147] Referring to Figure 1d, when multiple cells corresponding to a CA come from different satellites, scheduling discrepancies also exist in uplink scheduling. For example, as shown in Figure 1d, for cells #1 and #2 from different satellites, they can be configured with different Koffsets: for cell #1, Koffset #1 = 2; for cell #2, Koffset #2 = 4. In NTN, K2 + Koffset can be used to represent the slot difference between downlink scheduling PDCCH and PUSCH.

[0148] When network device 102, such as a gNB, sends a PDCCH on cell #1 to schedule the PUSCH on cell #1, then K2 can be equal to 0. That is, terminal 101 can send the PUSCH on cell #1 according to Koffset #1 = 2. However, when the PDCCH sent by the gNB on cell #1 is used to schedule the PUSCH on cell #2, it may use the Koffset corresponding to any cell. If Koffset #1 = 2 is used, then K2 cannot be equal to 0. As shown in Figure 1d, after receiving the PDCCH on cell #1, terminal 101 needs to send the PUSCH on cell #2 according to (K2 + Koffset #1) = 3. In this case, K2 can be 1. If Koffset #2 = 4 is used, after receiving the PDCCH on cell #1, terminal 101 needs to send the PUSCH on cell #2 according to (K2 + Koffset #1) = 3. However, the minimum value of K2 in the current related protocols is 0, which cannot support the scheduling of PUSCH in the same slot as the slot where the PDCCH received by terminal 101 is located. A new offset needs to be introduced to compensate for the scheduling difference between the two cells. At the same time, in order to facilitate the scheduling of network device 102, it is necessary to consider adjusting the offset value of the time difference between the two cells.

[0149] In 3GPP Release 15 (R15), system frames and slot boundaries between different carriers in inter-band CA (Cellular Array) need to be aligned, which places strict requirements on network deployment. R16 introduced the feature of non-aligned NR inter-band CA frame headers, allowing different carriers to maintain slot boundary alignment, but carrier frame headers can be offset. In related protocols, such as TN CA scenarios, the frame header offset between two cells in the CA can be represented by the CA-slot offset.

[0150] Based on the above description, it is necessary to provide the scheduling time offset caused by excessive TA or differences between different cells in the CA scenario of NTN.

[0151] Figure 2a is an interactive schematic diagram illustrating a method for determining the allocation of a time-domain position according to an embodiment of the present disclosure. As shown in Figure 2a, the present disclosure relates to a method for determining the allocation of a time-domain position, the method comprising:

[0152] In step S2101, network device 102 sends a first RRC message to terminal 101.

[0153] In some embodiments, the first RRC message is used to configure a cell-level first offset, which can be used to determine the timing offset involved in the embodiments of this disclosure. The first offset can be denoted as K. cell,offset .

[0154] Optionally, network device 102 can provide the parameters required for the UE to access the NR via the NTN through the Information Element (IE) NTN-Config. For example, based on this IE, cellSpecificKoffset can be configured, i.e., the first offset can be configured:

[0155] cellSpecificKoffset-r17 INTEGER(1..1023)

[0156] Optionally, the first offset is used for the scheduling offset of NTN to modify timing relationships.

[0157] In some embodiments, terminal 101 receives the first RRC message to obtain the first offset.

[0158] In step S2102, network device 102 sends MAC CE to terminal 101.

[0159] In some embodiments, MAC CE is used to indicate a second offset at the terminal level, which can be used to determine the timing offset involved in the embodiments of this disclosure. The second offset may be denoted as K. UE,offset .

[0160] Optionally, network device 102 can issue a second offset K via the Differential Koffset MAC CE command. UE,offset .

[0161] In some embodiments, terminal 101 receives the MAC CE to obtain the second offset.

[0162] In some embodiments, terminal 101 according to the first offset K cell,offset Second offset K UE,offsetDetermine the timing offset, which includes a first offset and a second offset.

[0163] For example, in this embodiment, the timing offset can be denoted as Koffset, K ofrset =K cell,offset -K UE,offset .

[0164] Optionally, when the subcarrier spacing (SCS) is 15kHz, the unit of the Koffset field can be the number of slots. If the Koffset-related field does not exist, the terminal 101 can assume that Koffset is zero.

[0165] In some embodiments, Koffset can be approximately equal to the TA value, such as Koffset having a time length of RTT, which is twice the round-trip delay (RTD). Here, one RTD can be understood as the transmission delay from terminal 101 to the base station.

[0166] In some embodiments, the timing offset in this disclosure can reuse the indication or determination method of Koffset in 5G NR. In the CA scenario of NTN, terminal 101 needs to determine the scheduling position based on Koffset, as detailed in the following embodiment description.

[0167] In step S2103, network device 102 sends PDCCH to terminal 101 in the first cell.

[0168] In some embodiments, the first cell may be denoted as cell#1.

[0169] In some embodiments, the PDCCH is used to schedule the Physical Shared Channel (PSCH) on the second cell.

[0170] Optionally, the second cell can be denoted as cell#2.

[0171] Optionally, the first cell #1 and the second cell #2 correspond to different component carriers in the CA.

[0172] In some embodiments, PSCH, based on uplink or downlink, can also be denoted as PxSCH.

[0173] In some embodiments, in cross-carrier downlink scheduling, the PSCH can be the Physical Downlink Shared channel (PDSCH), that is, the network device 102 schedules the PDSCH on cell #2 through the PDCCH of cell #1.

[0174] In some embodiments, in cross-carrier uplink scheduling, the PSCH can be the Physical Uplink Shared channel (PUSCH), that is, the network device 102 schedules the PUSCH on cell #2 through the PDCCH of cell #1.

[0175] In some embodiments, in different cells involved in CA, network device 102 may configure a corresponding timing offset such as Koffset for each cell, or configure a corresponding timing offset such as Koffset for at least one of the cells.

[0176] Optionally, at least one of the first cell and the second cell is configured with a corresponding timing offset. For example, network device 102 configures a corresponding timing offset, such as Koffset, for the first cell cell#1 and / or the second cell cell#2 through steps S2101 and S2102.

[0177] In some embodiments, terminal 101 receives PDCCH.

[0178] In some embodiments, terminal 101 may determine the allocated time domain location of the PSCH scheduled by PDCCH based on the timing offset, as described in step S2104.

[0179] In step S2104, terminal 101 determines the allocation time domain position of the scheduled PSCH based on the timing offset corresponding to the first cell and / or the timing offset corresponding to the second cell.

[0180] In some embodiments, in conjunction with the description of the foregoing embodiments, the timing offset is used to represent the offset of the scheduling timing in the CA of the NTN.

[0181] Optionally, the timing offset can be used to compensate for scheduling offsets caused by excessively long timing intervals (TA) and / or time differences between different cells in cross-carrier scheduling in the CA of the NTN.

[0182] In some embodiments, the time domain location allocation can be a slot allocation.

[0183] Optionally, for downlink scheduling, terminal 101 can determine the allocation time domain position of PDSCH based on the timing offset corresponding to cell#1 and / or the timing offset corresponding to cell#2.

[0184] Optionally, for uplink scheduling, terminal 101 can determine the allocation time domain position of PUSCH based on the timing offset corresponding to cell#1 and / or the timing offset corresponding to cell#2.

[0185] In one example, if network device 102 configures corresponding timing offsets for cell #1 and cell #2 respectively, for example, the timing offset value of cell #1 is 60 and the timing offset value of cell #2 is 120; terminal 101 can determine the allocation time domain position of PSCH based on 60 and 120.

[0186] In another example, if network device 102 configures a corresponding timing offset for one of cell #1 and cell #2, terminal 101 determines the allocation time domain position of the PSCH based on that timing offset. For example, if the timing offset value of cell #1 is 60 and cell #2 is not configured with a timing offset, terminal 101 can determine the allocation time domain position of the PSCH based on 60. Alternatively, if cell #1 is not configured with a timing offset and the timing offset value of cell #2 is 120, terminal 101 can determine the allocation time domain position of the PSCH based on 120.

[0187] In some embodiments, when determining the time-domain location of the PSCH allocation, the timing offset corresponding to the first cell or the timing offset corresponding to the second cell is selected by means of the protocol definition, wherein the PSCH is the Physical Uplink Shared Channel (PUSCH).

[0188] In this embodiment, for uplink scheduling, when cross-carrier scheduling occurs, at least one of cell#1 and cell#2 is configured with a timing offset. When determining the time domain position of PUSCH, terminal 101 can determine which cell's timing offset to use in the calculation of the allocated time domain position in a protocol-predefined manner.

[0189] In some embodiments, the time domain position is assigned based on the offset. Determined; where K offset #1 represents the timing offset corresponding to the first cell, K offset #2 indicates the timing offset corresponding to the second cell, 2 μPSCH This indicates the subcarrier spacing SCS of the PSCH. K represents offset SCS #1 K represents offset SCS #2.

[0190] In this embodiment, when determining the allocation time-domain position of the PSCH, the terminal 101 also needs to consider the aforementioned offset in addition to the relevant parameters. See the following examples for details.

[0191] In this embodiment, terminal 101 can determine the allocated time domain location based on the timing offset of the two cells.

[0192] In some embodiments, when the frame offsets corresponding to different carriers in the CA are configured, the time domain position is allocated based on the timing offset and the frame offset.

[0193] Optionally, in conjunction with the description of the foregoing embodiments, the frame offset can refer to the frame header offset, such as denoted as ca-slot offset. The frame header offset can be ±2.5ms at most; taking an SCS of 30kHz as an example, the inter-carrier frame header can be offset by a maximum of ±5 time slots. The introduction of ca-slot offset greatly facilitates and enhances the flexibility of NR inter-band carrier aggregation deployment, while also providing the prerequisite for staggering the transmission time slots of the two frequency bands of inter-band CA and maximizing the uplink CA transmission rate.

[0194] Optionally, the ca-slot offset and the timing offset involved in the embodiments of this disclosure are two different offsets.

[0195] To facilitate understanding of the method for determining the allocation time domain position of PSCH based on timing offset in the embodiments of this disclosure, some embodiments are listed below: Assume that the slot where PDCCH is located is slot n, K0=1, the SCS of PDCCH is denoted as scs-pdcch, and the SCS of PSCH is denoted as scs-pxsch or scs-psch.

[0196] In cross-carrier downlink scheduling, when frame offset (ca-slot offset) and timing offset (Koffset) are configured, the allocated time slots for the PDSCH can be determined based on these two parameters, as shown in the first example below. When ca-slot offset is not configured, the allocated time slots for the PDSCH can be determined based on the timing offset (Koffset), as shown in the second example below. In cross-carrier uplink scheduling, when frame offset (ca-slot offset) and timing offset (Koffset) are configured, the allocated time slots for the PUSCH can be determined based on these two parameters, as shown in the third and fourth examples below. When ca-slot offset is not configured, the allocated time slots for the PUSCH can be determined based on the timing offset (Koffset), as shown in the fifth and sixth examples below.

[0197] In the first example, if ca-slotoffset and Koffset are configured, the slot where PDSCH resides during cross-carrier scheduling will be Ks, where: in, This indicates the inter-carrier frame offset corresponding to the PDCCH. This indicates the inter-carrier frame offset corresponding to PDSCH. This indicates a floor operation; the meanings of the other parameters can be found in the description of the foregoing embodiments.

[0198] In the second example, if ca-slotoffset is not configured but Koffset is configured, the slot where PDSCH resides during cross-carrier scheduling is Ks, where:

[0199] The meanings of the relevant parameters can be found in the description of the foregoing embodiments, and will not be repeated here.

[0200] In the third example, if ca-slotoffset and Koffset are configured, the slot where PUSCH resides during cross-carrier scheduling will be Ks, where:

[0201] Wherein, Koffset is the timing offset corresponding to the first cell, i.e., the Koffset of the cell where the PDCCH is located. This refers to the SCS of the Koffset.

[0202] In the fourth example, if ca-slotoffset and Koffset are configured, the slot where PUSCH resides during cross-carrier scheduling will be Ks, where:

[0203] Where Koffset is the timing offset corresponding to the first cell, i.e., the Koffset of the cell where the PDCCH is located. This refers to the SCS of the Koffset.

[0204] In the fifth example, if ca-slotoffset is not configured but Koffset is configured, the slot where PUSCH resides will be Ks during cross-carrier scheduling, where:

[0205] Where Koffset is the timing offset corresponding to the first cell, i.e., the Koffset of the cell where PPDCCH is located. This refers to the SCS of the Koffset.

[0206] In the sixth example, if ca-slotoffset is not configured but Koffset is configured, the slot where PUSCH resides will be Ks during cross-carrier scheduling, where:

[0207] Where Koffset is the timing offset corresponding to the first cell, i.e., the Koffset of the cell where the PDCCH is located. This refers to the SCS of the Koffset.

[0208] In the example above, "configured ca-slotoffset" means that at least one cell involved in the cross-carrier scheduling has a ca-slotoffset configured. "Configured Koffset" means that at least one cell involved in the cross-carrier scheduling has a Koffset configured.

[0209] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", and "field" can be used interchangeably.

[0210] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0211] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0212] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0213] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0214] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0215] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0216] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0217] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0218] The method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2104.

[0219] In some embodiments, step S2101 or step S2102 may be omitted, and may be replaced by one or more steps in different embodiments. For example, a timing offset may be defined by a protocol.

[0220] In some embodiments, step S2103 may be omitted, and may be replaced by one or more steps in different embodiments.

[0221] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2a.

[0222] In this embodiment of the disclosure, the existing definition or indication method of Koffset can be reused to introduce the timing offset in the CA scenario of NTN, so that the terminal 101 can determine the allocation time domain position of the scheduled PSCH in the scenario based on the timing offset, thereby improving accuracy.

[0223] Figure 2b is an interactive schematic diagram illustrating a method for determining the allocated time-domain position according to an embodiment of the present disclosure. As shown in Figure 2b, this embodiment of the present disclosure relates to a method for determining the allocated time-domain position, the method comprising:

[0224] In step S2201, network device 102 sends a second RRC message to terminal 101.

[0225] In some embodiments, the second RRC message is used to configure the timing offset.

[0226] Optionally, for the embodiments corresponding to FIG2a, the timing offset involved in the embodiment of FIG2b is denoted as Koffset_CA.

[0227] In some embodiments, the timing offset Koffset_CA can be introduced on the basis of the existing Koffset in the protocol, or the timing offset Koffset_CA can override the existing Koffset in the protocol.

[0228] In some embodiments, the timing offset Koffset_CA in this embodiment may be equal to RTD.

[0229] In some embodiments, the second RRC message configures the timing offset per cell. For example, network device 102 configures the timing offset per cell via broadcast signaling RRC, such as configuring the timing offset for secondary cells (secondary cells or secondary serving cells, spcells).

[0230] Alternatively, the second RRC message is a terminal-specific signaling message used to configure the timing offset corresponding to the secondary cell. For example, network device 102 configures the timing offset for the secondary cell of terminal 101 via UE-specific RRC signaling.

[0231] In some embodiments, the timing offset Koffset_CA can be a positive value, a negative value, or 0.

[0232] In some embodiments, terminal 101 receives a second RRC message to learn the timing offset configured by network device 102.

[0233] In step S2202, network device 102 sends instruction information to terminal 101.

[0234] In some embodiments, the indication information is used to indicate an adjustment of the timing offset. For example, network device 102 uses the indication information to indicate an adjustment of the timing offset configured in step S2201.

[0235] In some embodiments, the indication information is sent via MAC CE or downlink control information DCI.

[0236] Optionally, based on the RRC configuration, network device 102 can further adjust this value through the second signaling MAC CE or DCI to flexibly indicate the timing offset applied by terminal 101.

[0237] In some embodiments, terminal 101 receives the instruction information.

[0238] In step S2203, network device 102 sends PDCCH to terminal 101 in the first cell.

[0239] In some embodiments, the description of step S2203 can be referred to the implementation of step S2103 in FIG2a, and will not be repeated here.

[0240] In some embodiments, terminal 101 receives PDCCH.

[0241] In some embodiments, terminal 101 may determine the allocated time domain location of the PSCH scheduled by PDCCH based on the timing offset, as described in step S2204.

[0242] In step S2204, terminal 101 determines the allocation time domain position of the scheduled PSCH based on the timing offset corresponding to the first cell and / or the timing offset corresponding to the second cell.

[0243] In some embodiments, a portion of the implementation of step S2204 can refer to the implementation of step S2104 in FIG2a. Since the timing offset can be defined differently in the two embodiments, the calculation formula differs, but the remaining description can still refer to step S2104.

[0244] In some embodiments, the time domain position is assigned based on the offset. Determined; where K offset_CA #1 represents the timing offset corresponding to the first cell, K offset _CA#2 represents the timing offset corresponding to the second cell, 2 μPSCH Indicates the subcarrier spacing SCS of the PSCH. K represents offset SCS #1 K represents offset SCS #2.

[0245] In this embodiment, when determining the allocation time-domain position of the PSCH, the terminal 101 also needs to consider the aforementioned offset in addition to the relevant parameters. See the following examples for details.

[0246] In some embodiments, when frame offsets corresponding to different carriers in the CA are configured, the time-domain position allocation is determined based on the timing offset and the frame offset. Referring to the description of the foregoing embodiments, this frame offset can be a CA-slot offset.

[0247] To facilitate understanding of the method for determining the allocation time domain position of PSCH based on timing offset in the embodiments of this disclosure, some embodiments are listed below: Assume that the slot where PDCCH is located is slot n, K0=1, the SCS of PDCCH is denoted as scs-pdcch, and the SCS of PSCH is denoted as scs-pxsch or scs-psch.

[0248] In cross-carrier downlink scheduling, when frame offset (ca-slot offset) and timing offset (Koffset_CA) are configured, the allocated time slots for the PDSCH can be determined based on these two parameters, as shown in Example 7 below. When ca-slot offset is not configured, the allocated time slots for the PDSCH can be determined based on the timing offset (Koffset_CA), as shown in Example 8 below. In cross-carrier uplink scheduling, when frame offset (ca-slot offset) and timing offset (Koffset_CA) are configured, the allocated time slots for the PUSCH can be determined based on these two parameters, as shown in Example 9 below. When ca-slot offset is not configured, the allocated time slots for the PUSCH can be determined based on the timing offset (Koffset_CA), as shown in Example 10 below.

[0249] In the seventh example, if ca-slotoffset and timing offset Koffset_CA are configured, the slot where PDSCH resides during cross-carrier scheduling is Ks, where:

[0250] For a description of the relevant parameters, please refer to the description of the foregoing embodiments.

[0251] In the eighth example, if ca-slotoffset is not configured, but timing offset Koffset_CA is configured, the slot where PDSCH resides during cross-carrier scheduling is Ks, where:

[0252] In the ninth example, if ca-slotoffset and timing offset Koffset_CA are configured, the slot where PUSCH resides during cross-carrier scheduling is Ks, where:

[0253] In the scenario of timed offset Koffset_CA, Koffset is the Koffset offset defined or configured in the cell where the PDCCH is located in the relevant technology or protocol. This refers to the SCS of the Koffset.

[0254] In the tenth example, if ca-slotoffset is not configured, but timing offset Koffset_CA is configured, the slot where PUSCH resides during cross-carrier scheduling is Ks, where:

[0255] The method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2204.

[0256] In some embodiments, step S2201 or step S2202 may be omitted, and may be replaced by one or more steps in different embodiments. For example, a timing offset may be defined by a protocol.

[0257] In some embodiments, step S2203 may be omitted, and may be replaced by one or more steps in different embodiments.

[0258] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2b.

[0259] In this embodiment of the disclosure, a timing offset can be defined in the CA scenario applicable to NTN, so that the terminal 101 can determine the allocation time domain position of the scheduled PSCH in the scenario based on the timing offset, thereby improving accuracy.

[0260] Figure 3a is a flowchart illustrating a method for determining an allocated time-domain location according to an embodiment of the present disclosure. As shown in Figure 3a, this embodiment of the present disclosure relates to a method for determining an allocated time-domain location, which is executed by terminal 101. The method includes:

[0261] Step S3101: Receive the first RRC message.

[0262] In some embodiments, the implementation of step S3101 can be found in the implementation of step S2101 in Figure 2a, and will not be repeated here.

[0263] Step S3102: Receive MAC CE.

[0264] In some embodiments, the implementation of step S3102 can be found in the implementation of step S2102 in Figure 2a, and will not be repeated here.

[0265] Step S3103: Receive PDCCH.

[0266] In some embodiments, the implementation of step S3103 can be found in the implementation of step S2103 in Figure 2a, and will not be repeated here.

[0267] Step S3104: Determine the allocation time domain position of the scheduled PSCH based on the timing offset.

[0268] In some embodiments, the implementation of step S3104 can be found in the implementation of step S2104 in Figure 2a, and will not be repeated here.

[0269] The method involved in the embodiments of this disclosure may include at least one of steps S3101 to S3104.

[0270] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG3a.

[0271] Figure 3b is a flowchart illustrating a method for determining an allocated time-domain location according to an embodiment of the present disclosure. As shown in Figure 3b, this embodiment of the present disclosure relates to a method for determining an allocated time-domain location, which is executed by terminal 101. The method includes:

[0272] Step S3201: Receive the second RRC message.

[0273] In some embodiments, the implementation of step S3201 can be found in the implementation of step S2201 in Figure 2b, and will not be repeated here.

[0274] Step S3202: Receive instruction information.

[0275] In some embodiments, the implementation of step S3202 can be found in the implementation of step S2202 in Figure 2b, and will not be repeated here.

[0276] Step S3203: Receive PDCCH.

[0277] In some embodiments, the implementation of step S3203 can be found in the implementation of step S2203 in Figure 2b, and will not be repeated here.

[0278] Step S3204: Determine the allocation time domain position of the scheduled PSCH based on the timing offset.

[0279] In some embodiments, the implementation of step S3204 can be found in the implementation of step S2204 in Figure 2b, and will not be repeated here.

[0280] The method involved in the embodiments of this disclosure may include at least one of steps S3201 to S3204.

[0281] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG3b.

[0282] Figure 3c is a flowchart illustrating a method for determining an allocated time-domain location according to an embodiment of the present disclosure. As shown in Figure 3c, this embodiment of the present disclosure relates to a method for determining an allocated time-domain location, which is executed by terminal 101. The method includes:

[0283] Step S3301: Determine the allocation time domain position of the scheduled PSCH based on the timing offset.

[0284] In some embodiments, the implementation of step S3301 can be found in the implementation of step S2104 in Figure 2a, and will not be repeated here.

[0285] In some embodiments, the implementation of step S3301 can be found in the implementation of step S2204 in Figure 2b, and will not be repeated here.

[0286] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG3c.

[0287] Figure 4a is a flowchart illustrating a method for determining an allocated time-domain location according to an embodiment of the present disclosure. As shown in Figure 4a, this embodiment of the present disclosure relates to a method for determining an allocated time-domain location, which is executed by a network device 102. The method includes:

[0288] Step S4101: Send the first RRC message.

[0289] In some embodiments, the implementation of step S4101 can be found in the implementation of step S2101 in Figure 2a, and will not be repeated here.

[0290] Step S4102: Send MAC CE.

[0291] In some embodiments, the implementation of step S4102 can be found in the implementation of step S2102 in Figure 2a, and will not be repeated here.

[0292] Step S4103: Send PDCCH.

[0293] In some embodiments, the implementation of step S4103 can be found in the implementation of step S2103 in Figure 2a, and will not be repeated here.

[0294] The method involved in the embodiments of this disclosure may include at least one of steps S4101 to S4103.

[0295] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG4a.

[0296] Figure 4b is a flowchart illustrating a method for determining an allocated time-domain location according to an embodiment of the present disclosure. As shown in Figure 4b, this embodiment of the present disclosure relates to a method for determining an allocated time-domain location, which is executed by network device 102. The method includes:

[0297] Step S4201: Send the second RRC message.

[0298] In some embodiments, the implementation of step S4201 can be found in the implementation of step S2201 in Figure 2b, and will not be repeated here.

[0299] Step S4202: Send instruction information.

[0300] In some embodiments, the implementation of step S4202 can be found in the implementation of step S2202 in Figure 2b, and will not be repeated here.

[0301] Step S4203: Send PDCCH.

[0302] In some embodiments, the implementation of step S4203 can be found in the implementation of step S2203 in Figure 2b, and will not be repeated here.

[0303] The method involved in the embodiments of this disclosure may include at least one of steps S4201 to S4203.

[0304] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG4b.

[0305] Figure 4c is a flowchart illustrating a method for determining an allocated time-domain location according to an embodiment of the present disclosure. As shown in Figure 4c, this embodiment of the present disclosure relates to a method for determining an allocated time-domain location, which is executed by a network device 102. The method includes:

[0306] Step S4301: Send a configuration message (such as an RRC message).

[0307] In some embodiments, the implementation of step S4301 can be found in the implementation of steps S2101 to S2102 in Figure 2a, and will not be repeated here.

[0308] In some embodiments, the implementation of step S4301 can be found in the implementation of steps S2201 to S2202 in Figure 2b, and will not be repeated here.

[0309] In some embodiments, other optional implementations may be described before or after the specification corresponding to FIG4c.

[0310] This invention provides a method for compensating for time offsets between different cells in CA scheduling using Koffset values. To facilitate understanding of this invention, some specific implementation methods are listed below:

[0311] Implementation method 1:

[0312] The UE determines the allocation time domain location of downlink and uplink scheduling based on the cell-based Koffse_CA value, such as the allocation time slot of PDSCH or the allocation time slot of PUSCH.

[0313] Implementation Method 2:

[0314] When a UE performs cross-carrier scheduling, i.e., when the PDCCH transmitted on the serving cell cell #1 schedules the PDSCH / PUSCH on cell #2, and at least one of cell #1 and cell #2 is configured with Koffset_CA, the UE determines the time-domain location of the PDSCH / PUSCH based on at least one Koffset_CA. Here, " / " represents OR.

[0315] In one embodiment, the Koffset_CA value of cell #1 is 60; the Koffset_CA value of cell #2 is 120. The UE then determines the temporal location of the PDSCH based on 60 and 120.

[0316] In one embodiment, cell #1 does not contain a Koffset_CA configuration; the Koffset_CA value of cell #2 is 120. The UE then determines its time-domain position based on 120.

[0317] In one embodiment, the Koffset_CA value of cell#1 is 60; cell#2 does not contain a Koffset_CA configuration. Therefore, the UE determines the temporal location of the PDSCH based on 60.

[0318] Implementation Method 3:

[0319] The definition and indication method of Koffset_CA can be any of the following optional examples:

[0320] Option 1: Reuse the Koffset from 5G NR;

[0321] Option 2: Configured separately via RRC to represent the offset value in the NTN CA scenario.

[0322] This value can be positive, negative, or 0;

[0323] In one embodiment, this value is configured via broadcast signaling RRC per cell, for example, for spcell;

[0324] In one embodiment, this value is configured for the UE's secondary serving cell via UE-specific RRC signaling;

[0325] In one embodiment, based on the RRC configuration, this value can be further adjusted via a second signaling (MAC CE or DCI).

[0326] In this implementation, Koffset_CA can be a positive value, a negative value, or 0;

[0327] In this implementation, Option 1 and Option 2 are presented side-by-side.

[0328] Implementation Method 4:

[0329] Based on implementation method 3, for Option 1:

[0330] In addition to the original calculations, the offset that still needs to be considered for the PDSCH slot is: Where Koffse#1 is the Koffset of the cell containing PDCCH; Koffse#2 is the Koffset of the cell containing PxSCH. μPxSCH SCS for PUSCH / PDSCH SCS for Koffse#1 SCS for Koffse#2.

[0331] Implementation Method 5:

[0332] Based on implementation method 3, for Option 2:

[0333] In addition to the original calculations, the offset that still needs to be considered for the PDSCH slot is: Where Koffset_CA#1 is the Koffset of the cell where PDCCH is located; Koffset_CA#2 is the Koffset of the cell where PxSCH is located.

[0334] Implementation method 6:

[0335] Based on implementation method 3, for Option 1:

[0336] For uplink scheduling only, when cross-carrier scheduling occurs, if at least one cell on cell#1 and cell#2 is configured with Koffset, then when the UE determines the time domain location of the PUSCH, it determines which cell's Koffset is used through a protocol-predefined method.

[0337] In one embodiment, during cross-carrier uplink scheduling, Koffset is the Koffset of the cell where the PDCCH resides. Where Koffset is the Koffset of the cell where PDCCH is located. This refers to the SCS configuration of Koffset. The meaning of the parameters can be found in the description of the previous embodiments. For example, n is the time slot where scheduling DC1 is located, K2 is a constant related to the PUSCH scheduling position (based on numerology of PUSCH), and μ PUSCH This is the SCS configured for PUSCH, μ PDCCH This is the SCS configured for PDCCH.

[0338] Based on the above implementation methods, the following embodiments can be used for Option 1 and Option 2 (see the first to tenth examples above):

[0339] Assume that the slot where PDCCH is located is n, K0 = 1, the SCS of PDCCH is scs-pdcch, and the SCS of PDSCH / PUSCH is scs-pxsch.

[0340] For Option 1:

[0341] If ca-slotoffset and Koffset are configured, then during cross-carrier scheduling, the slot where PDSCH resides is Ks, where...

[0342] If ca-slotoffset is not configured, but Koffset is configured, then during cross-carrier scheduling, the slot where PDSCH resides will be...

[0343] If ca-slotoffset and Koffset are configured, then during cross-carrier scheduling, the slot where PUSCH resides will be [slot value missing]. Where Koffset is the Koffset of the cell where PDCCH is located. This refers to the SCS of the Koffset;

[0344] If ca-slotoffset and Koffset are configured, then during cross-carrier scheduling, the slot where PUSCH resides will be [slot value missing]. Where Koffset is the Koffset of the cell where PDCCH is located. This refers to the SCS of the Koffset;

[0345] If ca-slotoffset is not configured, but Koffset is configured, then during cross-carrier scheduling, the slot where PUSCH resides will be [missing information]. Where Koffset is the Koffset of the cell where PDCCH is located. This refers to the SCS of the Koffset;

[0346] If ca-slotoffset is not configured, but Koffset is configured, then during cross-carrier scheduling, the slot where PUSCH resides will be [missing information]. Where Koffset is the Koffset of the cell where PDCCH is located. This refers to the SCS of the Koffset.

[0347] For Option 2:

[0348] If ca-slotoffset and Koffset_CA are configured, then during cross-carrier scheduling, the slot where PDSCH resides is Ks,where

[0349] If ca-slotoffset is not configured, but Koffset_CA is configured, then during cross-carrier scheduling, the slot where PDSCH resides will be...

[0350] If ca-slotoffset and Koffset_CA are configured, then during cross-carrier scheduling, the slot where PUSCH resides will be... For option 2, the Koffset in the formula is the Koffset of the cell where the PDCCH is located in the relevant protocol or technology. This refers to the SCS of the Koffset;

[0351] If ca-slotoffset is not configured, but Koffset_CA is configured, then during cross-carrier scheduling, the slot where PUSCH resides will be... Where Koffset is the Koffset of the cell where PDCCH is located. This refers to the SCS of the Koffset;

[0352] The above configurations ca-slotoffset and Koffset both refer to at least one cell in the cross-carrier scheduling being configured with ca-slotoffset and / or Koffset.

[0353] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0354] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD), such as a field-programmable gate array (FPGA). This PLD can include a large number of logic gates, and the connection relationships between these logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules in the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0355] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0356] Figure 5a is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. As shown in Figure 5a, the terminal 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the processing module 5102 is used to determine the allocation time-domain position of the scheduled physical shared channel (PSCH) based on a timing offset, wherein the timing offset is used to represent the offset of the scheduling timing in the carrier aggregation (CA) of a non-terrestrial network (NTN).

[0357] Optionally, the transceiver module 5101 is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods, which will not be described in detail here. Optionally, the processing module 5102 is used to perform at least one of the other steps performed by the terminal 101 in any of the above methods, which will not be described in detail here.

[0358] Figure 5b is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. As shown in Figure 5b, the network device 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is used to transmit a downlink control channel PDCCH to the terminal in a first cell, the PDCCH being used to schedule a physical shared channel PSCH on a second cell, wherein the first cell and the second cell respectively correspond to different component carriers in the CA;

[0359] The time domain position of the PSCH allocation is determined based on the timing offset, which is used to represent the offset of the scheduling timing in the carrier aggregation (CA) of the non-terrestrial network (NTN).

[0360] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0361] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0362] Figure 6a is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0363] As shown in Figure 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 can be used to execute any of the above methods. Optionally, one or more processors 6101 can be used to invoke instructions to cause the communication device 6100 to execute any of the above methods.

[0364] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 6101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0365] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Optionally, all or part of the memories 6103 may be located outside the communication device 6100. In optional embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memories 6103 and can be used to receive data from the memories 6103 or other devices, and to send data to the memories 6103 or other devices. For example, the interface circuits 6104 can read data stored in the memories 6103 and send that data to the processor 6101.

[0366] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6a. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0367] Figure 6b is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6b, but it is not limited thereto.

[0368] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

[0369] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of the memories 6203 may be located outside chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.

[0370] In some embodiments, the interface circuit 6202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 6202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 6202 performs data interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps.

[0371] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0372] This disclosure also proposes a storage medium storing instructions that, when executed on the communication device 6100, cause the communication device 6100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0373] This disclosure also provides a program product that, when executed by the communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0374] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods. Industrial applicability

[0375] A timing offset is introduced to express the scheduling timing in the CA of NTN, so that the terminal can more accurately determine the allocation time domain position of PSCH based on the scheduling timing differences between different cells in the NTN CA scenario, thereby improving the scheduling accuracy.

Claims

1. A method for determining an allocated time domain position, performed by a terminal, the method comprising: determining an allocated time domain position of a scheduled physical shared channel (PSCH) according to a timing offset, wherein the timing offset is used to represent an offset of scheduling timing in a carrier aggregation (CA) of a non-terrestrial network (NTN). The method further comprises:

2. The method of claim 1, wherein, receiving a physical downlink control channel (PDCCH) transmitted by a network device in a first cell, wherein the PDCCH is used to schedule the PSCH on a second cell, and wherein the first cell and the second cell correspond to different member carriers in the CA respectively. 3.The method of claim 2, wherein at least one of the first cell and the second cell is configured with a corresponding timing offset. The determining of the allocated time domain position of the PSCH according to the timing offset comprises: determining the allocated time domain position of the PSCH according to the timing offset corresponding to the first cell and / or the timing offset corresponding to the second cell. 5.The method of claim 4, wherein in the determining of the allocated time domain position of the PSCH, the timing offset corresponding to the first cell or the timing offset corresponding to the second cell is selected by a protocol-defined manner, and wherein the PSCH is a physical uplink shared channel (PUSCH).

4. The method of claim 2, wherein, 6.The method of any one of claims 1 to 4, wherein the PSCH is a physical downlink shared channel (PDSCH) or a PUSCH. 7.The method of any one of claims 1 to 6, wherein when a frame offset corresponding to different carriers in the CA is configured, the allocated time domain position is determined according to the timing offset and the frame offset. The method further comprises: receiving a first radio resource control (RRC) message transmitted by the network device, wherein the first RRC message is used to configure a first offset at a cell level; receiving a medium access control (MAC) control element (CE) transmitted by the network device, wherein the MAC CE is used to indicate a second offset at a terminal level; and wherein the timing offset comprises the first offset and the second offset. The method further comprises: receiving a second RRC message transmitted by the network device, wherein the second RRC message is used to configure the timing offset. 10.The method of claim 9, wherein the second RRC message configures the timing offset in units of a cell; or the second RRC message is a terminal-specific signaling used to configure a timing offset corresponding to a secondary cell.

8. The method of any one of claims 1 to 7, wherein, The method further comprises: receiving indication information transmitted by the network device, wherein the indication information is used to indicate an adjustment of the timing offset. 12.The method of claim 11, wherein the indication information is transmitted by a MAC CE or a downlink control information (DCI). 13.The method of claim 8 or 9, wherein the first offset is a cell-specific offset, and wherein the second offset is a terminal-specific offset.

9. The method of any one of claims 1 to 7, wherein, 14.A method for determining an allocated time domain position, performed by a network device, the method comprising: ​ ​ ​ ​ 11. The method of claim 9, wherein, ​ ​ ​ ​ ​ The allocated time domain position is according to an offset determined; wherein K offset #1 represents a timing offset corresponding to a first cell, K offset #2 represents a timing offset corresponding to a second cell, 2 μPSCH represents a subcarrier spacing SCS of the PSCH, represents K offset SCS of #1, K represents offset SCS of #2; or, The allocated time domain position is according to an offset determined; wherein K offset_CA #1 represents a timing offset corresponding to the first cell, K offset _CA#2 represents a timing offset corresponding to the second cell, 2 μPSCH represents a subcarrier spacing SCS of the PSCH, represents K offset SCS of #1, represents K offset SCS of #2. ​ The first cell sends a downlink control channel PDCCH to a terminal, the PDCCH being used for scheduling a physical shared channel PSCH on a second cell, wherein the first cell and the second cell correspond to different member carriers in a CA respectively; The allocation time domain position of the PSCH is determined according to a timing offset, the timing offset being used to represent an offset of scheduling timing in a carrier aggregation CA of a non-terrestrial network NTN.

15. The method of claim 14, wherein, At least one of the first cell and the second cell is configured with a corresponding timing offset.

16. The method of claim 14, wherein, The allocation time domain position of the PSCH is determined according to the timing offset corresponding to the first cell and / or the timing offset corresponding to the second cell.

17. The method of claim 16, wherein, In determining the allocation time domain position of the PSCH, the timing offset corresponding to the first cell or the timing offset corresponding to the second cell is selected by a protocol-defined manner, wherein the PSCH is a physical uplink shared channel PUSCH.

18. The method of any one of claims 14 to 17, wherein, The PSCH is a physical downlink shared channel PDSCH or a PUSCH.

19. The method of any one of claims 14 to 18, wherein, When a frame offset corresponding to different carriers in the CA is configured, the allocation time domain position is determined according to the timing offset and the frame offset.

20. The method of any one of claims 14 to 19, wherein, The method further comprises: sending a first RRC message to a terminal, the first RRC message being used to configure a first offset at a cell level; sending a medium access control layer control element MAC CE to the terminal, the MAC CE being used to indicate a second offset at a terminal level; The timing offset comprises the first offset and the second offset.

21. The method of any one of claims 14 to 19, wherein, The method further comprises: sending a second RRC message to the terminal, the second RRC message being used to configure the timing offset.

22. The method of claim 21, wherein, The second RRC message configures the timing offset in units of a cell; or The second RRC message is terminal-specific signaling used to configure a timing offset corresponding to a secondary cell.

23. The method of claim 21, wherein, The method further comprises: sending indication information to the terminal, the indication information being used to indicate adjustment of the timing offset.

24. The method of claim 23, wherein, The indication information is sent through a MAC CE or a downlink control information DCI.

25. The method of claim 20 or 21, wherein, The allocated time domain position is according to an offset determined; wherein K offset #1 represents a timing offset corresponding to a first cell, K offset #2 represents a timing offset corresponding to a second cell, 2 μPSCH represents a subcarrier spacing SCS of the PSCH, represents K offset SCS of #1, K represents offset the SCS of #2; or, The allocated time domain position is according to an offset determined; wherein K offset_CA #1 represents a timing offset corresponding to the first cell, K offset _CA#2 represents a timing offset corresponding to the second cell, 2 μPSCH represents a subcarrier spacing SCS of the PSCH, represents K offset SCS of #1, represents K offset SCS of #2.

26. A terminal, comprising: a processing module configured to determine an allocation time domain position of a scheduled physical shared channel PSCH according to a timing offset, wherein the timing offset is used to represent an offset of scheduling timing in a carrier aggregation CA of a non-terrestrial network NTN.

27. A network device, comprising: a transceiving module, configured to send, by a first cell, a physical downlink control channel (PDCCH) to a terminal, the PDCCH being used for scheduling a physical shared channel (PSCH) on a second cell, wherein the first cell and the second cell correspond to different member carriers in CA respectively; wherein an allocated time domain position of the PSCH is determined according to a timing offset, the timing offset being used to represent an offset of scheduling timing in a non-terrestrial network (NTN) carrier aggregation (CA). 28.A communication device, comprising: one or more processors; wherein the communication device is configured to implement the method of any one of claims 1-13 or 14-25. 29.A communication system, comprising a terminal and a network device, wherein: the terminal is configured to implement the method of any one of claims 1-13; the network device is configured to implement the method of any one of claims 14-25. 30.A storage medium, storing instructions, wherein: when the instructions are run on a communication device, the communication device is caused to perform the method of any one of claims 1-13 or 14-25. 31.A program product, wherein: when the program product is executed by a communication device, the communication device is caused to perform the method of any one of claims 1-13 or 14-25.

Images