Methods, apparatuses, and systems for transmission in non-terrestrial networks

Abstract

Embodiments of the application provide a method, apparatus and system for transmission in a non-terrestrial network (NTN) system. The method comprises: a first transmit and receive point (TRP) obtaining a first transmission time of a first channel, the first TRP transmitting the first channel to an electronic device (ED) at the first transmission time, a second TRP transmitting a second channel to the ED at a second transmission time, the first transmission time being different from the second transmission time, and at least one of the first TRP and the second TRP being a non-terrestrial TRP. This helps to reduce the complexity of the ED receiving channels from different TRPs in the NTN system.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 551,298, filed February 8, 2024, entitled “Method, Apparatus, and System for Transmissions in Non-Terrestrial Networks,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] Embodiments of this application relate to the field of communications, and more specifically, to a method, apparatus, and system for transmission over non-terrestrial networks. Background Technology

[0003] To provide more reliable and high-capacity communication services, electronic devices (EDs) can support multiple transmit and receive points (M-TRP) technology. That is, multiple transmit and receive points (TRPs) can simultaneously transmit channels (channels, data, signals, etc.) to the same ED.

[0004] With the development of non-terrestrial network (NTN) communication systems, non-terrestrial TRPs (NT-TRPs) can participate in M-TRP transmission. However, due to the long distance between the ED and the NT-TRP, and the fact that the NT-TRP may be constantly in motion, the complexity of the ED receiving channels from different TRPs in the time domain increases.

[0005] Therefore, a pressing technical problem is how to reduce the complexity of ED receiving channels from different TRPs in NTN systems. Summary of the Invention

[0006] Embodiments of this application provide a method, apparatus, and system for transmission in a non-terrestrial network. The complexity of receiving channels from different TRPs in an NTN system is also addressed.

[0007] According to a first aspect, embodiments of this application provide a communication method that can be executed by a first TRP or a chip of the first TRP. The method includes: obtaining (1010) a first transmission time of a first channel, wherein the first channel and a second channel are transmitted to an electronic device (ED), the second channel originating from a second TRP, the first transmission time differing from a second transmission time of the second channel, and at least one of the first TRP and the second TRP being a non-terrestrial TRP; and transmitting (1030) the first channel to the ED at the first transmission time.

[0008] According to a second aspect, embodiments of this application provide a communication method that can be executed by an ED or a chip of an ED. The method includes: receiving a first channel (1020, 1030) from a first transmit and receive point (TRP), and receiving a second channel from a second TRP, wherein a first transmission time of the first channel differs from a second transmission time of the second channel, and at least one of the first TRP and the second TRP is a non-terrestrial TRP.

[0009] According to a third aspect, embodiments of this application provide a communication method that can be executed by a second TRP or a chip of the second TRP. The method includes: transmitting (1020) a second channel at a second transmission time, wherein a first channel and a second channel are transmitted to an electronic device (ED), the first channel originating from a first TRP, the second transmission time differing from a first transmission time of the first channel, and at least one of the first TRP and the second TRP being a non-terrestrial TRP.

[0010] According to the above technical solution, the first TRP and the second TRP transmit the first and second channels to the same ED at different transmission times rather than simultaneously, wherein at least one of the first TRP and the second TRP is a non-terrestrial TRP. This helps reduce the complexity of the ED receiving channels from different TRPs in the NTN system.

[0011] In some implementations, combining the first, second, or third aspects, the first and second transmission times are related to the location of the reference point.

[0012] According to the above technical solution, the location of the reference point can help reflect the distance between the first TRP and the ED, as well as the distance between the second TRP and the ED. The first transmission time and the second transmission time can be reasonably determined based on the location of the reference point.

[0013] In some implementations, combining the first, second, or third aspects, the delay between the first and second transmission times is related to the reference point.

[0014] According to the above technical solution, this delay can affect the time difference between the arrival of the first and second channels at the ED, and the time difference can affect the complexity of the ED receiving channels from different TRPs. The delay related to the reference point can help reduce the complexity of the ED.

[0015] In some implementations, the reference point is located at the position of the ED, or the reference point is located at the position of the anchor point, in combination with the first, second, or third aspects.

[0016] Based on the above technical solution, when the reference point is the location of the ED (Edge Controller), the first transmission time can be designed effectively, reducing the complexity of the ED. When the reference point is an anchor point, the mechanism for determining the first transmission time is relatively simple.

[0017] In conjunction with the first aspect, in some implementations, obtaining the first transmission time of the first channel includes: receiving first information from the second TRP, wherein the first information indicates the first transmission time.

[0018] In conjunction with the third aspect, in some implementations, the method further includes: sending a first message to a first TRP, wherein the first message indicates a first transmission time.

[0019] According to the above technical solution, the first TRP and the second TRP can cooperate to send the first channel and the second channel to the same ED.

[0020] In conjunction with the first or third aspect, in some implementations, the first information indicates the time delay between the first transmission time and the second transmission time.

[0021] According to the above technical solution, the first TRP can determine the first transmission time based on the delay.

[0022] In some implementations, in conjunction with the first, second, or third aspects, the first channel includes one or more of the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH), and the second channel includes one or more of the PDCCH and PDSCH.

[0023] In some implementations, combining the first, second, or third aspects, the first and second channels are duplicate channels.

[0024] In conjunction with the second aspect, in some implementations, receiving the first channel and the second channel includes: receiving the first channel and the second channel based on a first reference time; or receiving the first channel and the second channel based on a first time window; or receiving the first channel based on a first correction time and receiving the second channel based on a second correction time; or receiving the first channel based on a first correction time window and receiving the second channel based on a second correction time window.

[0025] According to the above technical solution, the ED can receive the first channel and the second channel in a variety of ways, which enable the ED to reliably receive the first channel and the second channel.

[0026] In conjunction with the second aspect, in some implementations, the method also includes: receiving configuration information, wherein the configuration information configures the reception of the first channel and the second channel.

[0027] In conjunction with the first or third aspect, in some implementations, the method further includes: sending configuration information, wherein the configuration information configures the reception of the first channel and the second channel.

[0028] According to the above technical solution, the ED can be used to reliably receive the first channel and the second channel.

[0029] In some implementations, in conjunction with the first, second, or third aspects, the configuration information indicates one or more of the following: a first reference time, a first time window, a first correction time, a second correction time, a first correction time window, a second correction time window, and the location of the reference point.

[0030] According to the above technical solution, the configuration information can indicate a variety of parameters to configure ED.

[0031] In conjunction with the second aspect, some implementations also include: transmitting capability information, wherein the capability information indicates the capabilities of the global navigation satellite system (GNSS), and configuration information indicates the location of the reference point.

[0032] In conjunction with the first or third aspect, in some implementations, the method further includes: receiving capability information, wherein the capability information indicates the capabilities of the global navigation satellite system (GNSS), and configuration information indicates the location of a reference point.

[0033] Based on the above technical solution, configuration information can be designed based on the ED's capabilities. When the ED has GNSS capabilities, it can determine how to receive the first and second channels based on the location of the reference point.

[0034] According to a fourth aspect, a first TRP is provided. The first TRP includes functions or units for performing the method according to the first aspect or any possible embodiment of the first aspect.

[0035] According to a fifth aspect, an ED is provided. The ED includes functions or units for performing the method according to the second aspect or any possible embodiment of the second aspect.

[0036] According to a sixth aspect, a second TRP is provided. The second TRP includes functions or units for performing the method according to a third aspect or any possible embodiment of the third aspect.

[0037] According to a seventh aspect, a system is provided. The system includes: a first TRP according to a fourth aspect, an ED according to a fifth aspect, and a second TRP according to a sixth aspect.

[0038] According to an eighth aspect, a communication device is provided. The communication device includes at least one processor, and the at least one processor is coupled to at least one memory. The at least one memory is used to store a computer program or one or more instructions. The at least one processor is configured to: invoke the computer program or the one or more instructions from the at least one memory and execute the computer program or the one or more instructions, causing the communication device to perform the method described in the first aspect or any of its possible implementations, or the communication device to perform the method described in the second aspect or any of its possible implementations, or the communication device to perform the method described in the third aspect or any of its possible implementations.

[0039] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the communication device may be a first TRP or a component (e.g., a chip or integrated circuit) installed in the first TRP. For example, the communication device may be an ED or a component (e.g., a chip or integrated circuit) installed in the ED. For example, the communication device may be a second TRP or a component (e.g., a chip or integrated circuit) installed in the second TRP.

[0040] According to a ninth aspect, a communication apparatus is provided. The communication apparatus includes a processor and a communication interface. The processor is connected to the communication interface. The processor is configured to execute one or more instructions, and the communication interface is configured to communicate with other network elements under the control of the processor. The processor is capable of performing the methods described according to the first aspect or any possible embodiment of the first aspect, the second aspect or any possible embodiment of the second aspect, or the third aspect or any possible embodiment of the third aspect.

[0041] According to a tenth aspect, a computer storage medium is provided. The computer storage medium stores program code, and the program code is configured to execute one or more instructions for using the method according to the first aspect or any possible embodiment of the first aspect, the second aspect or any possible embodiment of the second aspect, or the third aspect or any possible embodiment of the third aspect.

[0042] According to the eleventh aspect, this application provides a computer program product comprising one or more instructions, wherein when the computer program product is run on a computer, the computer performs the method according to the first aspect or any possible embodiment of the first aspect, the second aspect or any possible embodiment of the second aspect, or the third aspect or any possible embodiment of the third aspect.

[0043] According to a twelfth aspect, this application provides a non-transitory computer-readable medium storing instructions that cause a processor in a device to implement the method according to the first aspect or any possible embodiment of the first aspect, the second aspect or any possible embodiment of the second aspect, or the third aspect or any possible embodiment of the third aspect.

[0044] According to the thirteenth aspect, this application provides an apparatus for performing the method according to the first aspect or any possible embodiment of the first aspect, the second aspect or any possible embodiment of the second aspect, or the third aspect or any possible embodiment of the third aspect.

[0045] According to the fourteenth aspect, this application provides a processor for executing instructions to cause a device to perform the method according to the first aspect or any possible embodiment of the first aspect, the second aspect or any possible embodiment of the second aspect, or the third aspect or any possible embodiment of the third aspect.

[0046] According to the fifteenth aspect, this application provides an integrated circuit for performing the method according to the first aspect or any possible embodiment of the first aspect, the second aspect or any possible embodiment of the second aspect, or the third aspect or any possible embodiment of the third aspect.

[0047] According to a sixteenth aspect, this application provides a communication apparatus, comprising: a transceiver unit configured to perform a receiving step according to the first aspect or any possible embodiment of the first aspect; and a processing unit configured to perform a processing step according to the first aspect or any possible embodiment of the first aspect.

[0048] According to the seventeenth aspect, this application provides a communication apparatus including a transceiver unit for performing the transmission steps described in the second aspect or any possible embodiment of the second aspect.

[0049] According to the eighteenth aspect, this application provides a communication apparatus including a transceiver unit for performing the transmission steps described in the third aspect or any possible embodiment of the third aspect. Attached Figure Description

[0050] Figure 1 This is a schematic diagram illustrating the application scenario of this application; Figure 2 An exemplary communication system 100 is shown; Figure 3 Another example of an ED and a base station is shown; Figure 4 An example of device 410 is shown; Figure 5 An example of device 510 is shown; Figure 6 A first example of a communication system including NT-TRP and T-TRP is shown; Figure 7 A second example of a communication system including NT-TRP and T-TRP is shown; Figure 8 A third example of a communication system including NT-TRP and T-TRP is shown; Figure 9 An example of an NT-TRP communication link is shown; Figure 10 This is a schematic flowchart of a communication method 1000 according to an embodiment of this application; Figure 11 An example of UE-centric transmission according to an embodiment of this application is shown; Figure 12 A first example of anchor-centric transmission according to an embodiment of this application is shown; Figure 13 Details of a first example of an embodiment according to this application are shown; Figure 14 A second example of anchor-centric transmission according to an embodiment of this application is shown; Figure 15 Details of a first example of an embodiment according to this application are shown; Figure 16 and Figure 17 These are schematic block diagrams of possible devices according to embodiments of this application. Detailed Implementation

[0051] The technical solution of this application will now be described with reference to the accompanying drawings.

[0052] The technical solutions in the embodiments of this application can be applied to various communication systems, such as fifth-generation (5G) wireless communication systems, new radio (NR) wireless communication systems, sixth-generation (6G) wireless communication systems, or other evolved communication systems.

[0053] To facilitate understanding of the embodiments of this application, firstly... Figures 1 to 3 The communication system shown is used as an example to describe in detail the communication system to which embodiments of this application are applicable.

[0054] Figure 1 This is a schematic diagram illustrating an application scenario according to an embodiment of this application.

[0055] refer to Figure 1 As a non-limiting illustrative example, a simplified schematic diagram of a communication system is provided. Communication system 100 (which may be a wireless system) includes a radio access network (RAN) 120. The RAN 120 may be a next-generation (e.g., 6th generation, 6G, or higher) RAN, or a traditional (e.g., 5th generation, 4th generation, 3rd generation, or 2nd generation, 2G) RAN. One or more electronic devices (EDs) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (collectively referred to as 110) may interconnect with each other or be connected to one or more network nodes (170a, 170b, collectively referred to as 170) within the RAN 120. The core network 130 may be part of the communication system and may depend on or be independent of the wireless access technology used in the communication system 100. The communication system 100 may also include a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0056] Typically, communication system 100 enables multiple wireless or wired components to transmit data and other content. Communication system 100 can provide voice, data, video, and / or text content through broadcasting, multicast, ensemble broadcasting, unicast, etc. Furthermore, communication system 100 can provide a wide range of communication services and applications (such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery, and mobility). These services and / or applications can be mobile broadband (MBB) services, ultra-reliable low-latency communication (URLLC) services, or machine-type communication (MTC) services.

[0057] The communication system 100 can operate by sharing resources such as carrier spectrum bandwidth among its constituent components.

[0058] Communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. Communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can create a heterogeneous network that can be considered as comprising multiple layers. Heterogeneous networks can achieve better overall performance through efficient multi-link joint operation, more flexible function sharing, and faster physical layer link switching between terrestrial and non-terrestrial networks.

[0059] Terrestrial communication systems and non-terrestrial communication systems can be considered as subsystems of a communication system.

[0060] Figure 2 A more detailed example of the communication system 100 is shown. (Compared to...) Figure 2 The same applies to the examples shown. Figure 2In the example shown, communication system 100 may include ED 110a, 110b, 110c, 110d (collectively referred to as ED 110) and RAN 120a, 120b. Furthermore, communication system 100 may also include a non-terrestrial network (NTN) 120c. Communication system 100 may also include one or more of CN 130, PSTN 140, Internet 150, and other networks 160. RAN 120a, 120b include corresponding network nodes 170a, 170b, such as base stations 170a, 170b, which may generally be referred to as terrestrial network (TN) equipment or terrestrial transmit and receive point (T-TRP) 170a, 170b (collectively referred to as 170). Note that unless otherwise described, TRP and base station may have the same meaning and are interchangeable throughout the application. T-TRPs 170a and 170b are base stations attached to the ground (e.g., mounted on a building or tower). In one implementation, NTN 120c includes a RAN node, such as base station 172, which may generally be referred to as an NTN device, non-terrestrial node, non-terrestrial network device, non-terrestrial base station, or non-terrestrial transmit and receive point (NT-TRP) 172. NT-TRP 172 is not attached to the ground. A flying base station is one example. A flying base station can be implemented using communication equipment supported or carried by flying equipment. Non-limiting examples of flying equipment include airborne platforms (e.g., small airships or spacecraft), balloons, quadcopters, and other aircraft. In some implementations, a flying base station may be supported or carried by an unmanned aerial system (UAS) or unmanned aerial vehicle (UAV) (e.g., a drone or quadcopter). A flying base station can be a mobile or portable base station that can be flexibly deployed in different locations to meet network requirements. A satellite base station is another example of a non-terrestrial base station. Satellite base stations can be implemented using communication equipment supported or carried by satellites. Satellite base stations are also known as orbital base stations. High-altitude platforms are another example of non-terrestrial base stations, including international mobile telecommunications base stations.

[0061] It should be noted that "TRP" as used herein may refer to either T-TRP or NT-TRP, unless otherwise specified. T-TRP can be alternatively referred to as "TN TRP," and NT-TRP can be alternatively referred to as NTN TRP. As can be inferred from the similarity in the reference numerals, NTN 120c can be considered a radio access network (RAN), having the same operational aspects as RAN 120a and 120b. In another implementation, NTN 120c may include at least one non-terrestrial network device and at least one corresponding terrestrial network device, wherein the at least one non-terrestrial network device operates as a transport layer device, and the at least one corresponding terrestrial network device operates as a RAN node, the RAN node communicating with the ED through the non-terrestrial network device. Furthermore, an NTN gateway (i.e., referred to as a terrestrial network device) may also exist on the ground, acting as a transport layer device communicating with the NTN device, and the RAN node communicating with the ED through the NTN device and the NTN gateway. In some implementations, the NTN gateway and the RAN node may reside in the same device.

[0062] A base station (as mentioned above, also known as a TRP) is a network element in a radio access network responsible for wireless transmission and reception with user equipment in one or more cells. In some implementations, a base station may use other names, such as base transceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, NodeB, evolved NodeB (eNodeB or eNB), home eNodeB, next-generation NodeB (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, ground node, ground network device, ground base station, positioning node, etc. Base stations 170a and 170b can be macro base stations (BS), pico BS, relay nodes, donor nodes, or combinations thereof. The method in this application is applied to the base station side. For example, it can be understood that the method is applied to the base station or the communication module in the base station, the circuit or chip in the base station responsible for one or more communication functions (e.g., modem chip, also known as baseband chip, system on chip including modem core, or system in package (SIP)).

[0063] ED 110a to 110d and TRP 170a, 170b, 172 are examples of communication devices that can be used to implement some or all of the operations and / or embodiments described herein. Figure 2 In the example shown, T-TRP 170a forms part of RAN 120a, which may include other TRPs and / or other equipment. Similarly, TRP 170b forms part of RAN 120b, which may include other TRPs and / or equipment. Each TRP 170a, 170b transmits and / or receives radio signals within a specific geographic area or region, sometimes referred to as a "cell" or "coverage area." TRPs 170a and 170b may be responsible for allocating / configuring resources and transmission / reception within a set of cells. A cell is a wireless network object that can be uniquely identified by a (cell) identifier broadcast over the geographic area or region from the base station associated with the cell. A cell may be in FDD or TDD mode. A cell may also refer to a carrier frequency within the DL / UL carrier bandwidth resources of a single independent carrier or component carrier in carrier aggregation mode. Cells may be further divided into cell sectors; for example, base stations 170a and 170b may employ multiple transceivers to provide services to multiple sectors. In some implementations, there may be established picocells or femtocells supported by radio access technologies. In some implementations, for example, multiple-input multiple-output (MIMO) technology may be used to use multiple transceivers for each cell. The number of RANs 120a and 120b shown is merely exemplary. Any number of RANs can be envisioned when designing the communication system 100.

[0064] Any base station can be a single element as shown in the figure, or multiple elements distributed within a corresponding RAN. In some implementations, multiple RAN nodes cooperate to assist the ED 110 in achieving radio access, and different RAN nodes implement different functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), a CU control plane (CP), a CU user plane (UP), or a radio unit (RU), etc. CU and DU can be deployed separately, or they can be included in the same element (i.e., a baseband unit (BBU)). RU can be included in radio equipment or radio units (i.e., remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH)). In different systems, CU (or CU-CP and CU-UP), DU, or RU may also have different names, but those skilled in the art will understand their meaning. For example, in an open radioaccess network (ORAN) system, a CU can also be called an open CU (O-CU), a DU can also be called an open DU (O-DU), and a CU-CP can also be called an open CU-CP (O-CU-CP). A CU-UP can also be called an open CU-UP (O-CU-UP), and a RU can also be called an open RU (O-RU). Any of the CU (or CU-CP, CU-UP), DU, and RU can be implemented using software modules, hardware modules, or a combination of software and hardware modules.

[0065] Furthermore, in various embodiments of this application, one or more communications between different devices / apparatus can refer to direct communication between different devices / apparatus (i.e., without the need for forwarding by another device / apparatus), or it can refer to one or more communications between different devices / apparatus via another device / apparatus (i.e., requiring forwarding by another device / apparatus). Alternatively, it can refer to a functional unit within a device / apparatus communicating with another device / apparatus by using another functional unit. In other words, "sending / transmitting information to... (ED or base station)" in this application can be understood as the destination endpoint of the information being an ED or base station. This can include sending / transmitting information directly or indirectly to an ED or base station. Similarly, "receiving information from... (ED or base station)" can be understood as the source endpoint of the information being an ED or base station, and can include receiving information directly or indirectly from an ED or base station. Necessary processing such as format conversion, digital-to-analog conversion, amplification, and filtering can be performed on the information between the source endpoint and the destination endpoint. However, the destination endpoint can understand valid information from the source endpoint. Similar descriptions in this application can be understood similarly. Details will not be repeated herein.

[0066] The ED 110 is used to connect people, objects, and machines. It can be widely used in various scenarios, including cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), MTC, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), mixed reality (MR), digital twins, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, and mobility.

[0067] Each ED 110 represents any suitable end-user equipment for wireless operation and may include (or be referred to as, but not limited to, the following devices): user equipment (UE) or user device or terminal equipment, wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), MTC device, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics, smartbook, vehicle, automobile, truck, bus, train or IoT device, wearable device (e.g., watch, glasses, head-mounted device, etc.), industrial equipment or devices in or including the above devices (e.g., communication module, modem or chip), etc. Next-generation ED 110 may be referred to using other terms. The methods of this application are applied to the ED side, for example, it can be understood that the methods are applied to the ED or the communication module in the ED, the circuitry or chip in the ED responsible for one or more communication functions (e.g., modem chip, also called baseband chip, system-on-a-chip including modem core or system-in-package (SIP)).

[0068] Each ED 110 connected to TRP 170a and 170b and / or TRP 172 can be dynamically or semi-statically turned on (i.e., established, activated, or enabled), turned off (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connectivity availability and connectivity necessity.

[0069] Alternatively or additionally, any ED 110 can be used to connect, access, or communicate with any of the following: TRP 170a, 170b, and 172; Internet 150; CN 130; PSTN 140; other networks 160; or any combination thereof. In some examples, ED 110a can transmit uplink (UL) and / or downlink (DL) to site TRP 170a via terrestrial air interface 190a. In some examples, ED 110a, 110b, 110c, and 110d can also communicate directly with each other via one or more sidelink (SL) air interfaces 190b. In some examples, ED 110d can transmit UL and / or DL ​​to NT-TRP 172 via non-terrestrial air interface 190c.

[0070] An air interface (e.g., 190a, 190b, 190c) typically includes several components and associated parameters that collectively specify how transmissions are sent and / or received over a wireless communication link between two or more communication devices (e.g., EDs and base stations). For example, an air interface may include one or more waveforms, one or more frame structures, one or more multiple access schemes, one or more protocols, one or more coding schemes, and / or one or more modulation schemes that define the transmission of information (e.g., data) over the wireless communication link. Air interfaces 190a and 190b can use similar communication technologies, such as any suitable wireless access technology.

[0071] The non-terrestrial air interface 190c enables communication between the ED 110d and one or more NT-TRP 172s via a wireless link or simply through a link. In some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection for multicast transmission between a group of ED 110s and one or more NT-TRP 172s.

[0072] TRPs 170a and 170b, 172 can communicate with each other via one or more air interfaces 190e, 190f using wireless communication links (e.g., radio frequency, microwave, infrared, IR, etc.) or wired communication links. Air interfaces 190e, 190f can utilize any suitable wireless access technology and can be substantially similar to, or substantially different from, the air interfaces 190a, 190c used when EDs 110a to 110d communicate with one or more of TRPs 170a and 170b, 172. For example, communication system 100 can implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA).

[0073] RANs 120a and 120b communicate with CN 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 120b, and / or CN 130, can communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by CN 130, and may or may not use the same radio access technology as RANs 120a, RAN 120b, or both. CN 130 can also serve as a gateway access between (i) RANs 120a and 120b, or EDs 110a, 110b, and 110c, or both, and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Furthermore, some or all of EDs 110a, 110b, and 110c may include the ability to communicate with different wireless networks via different radio links using different radio technologies and / or protocols. Instead of wireless communication (or other than wireless communication), ED 110a, 110b, and 110c can also communicate with service providers or exchanges (not shown) via wired communication channels and with the Internet 150. PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a network of computers and subnets (internal networks) or both, incorporating protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating under various wireless access technologies and include multiple transceivers required to support these technologies.

[0074] In addition, the communication system 100 may include a sensing agent (not shown) to manage sensing data from ED 110 and / or any of TRPs 170a and 170b, 172. In one implementation, the sensing agent is located in any of TRPs 170a and 170b, 172. In another implementation, the sensing agent is a separate node having an interface for communicating with CN 130 and / or RAN 120 (e.g., any of TRPs 170a and 170b, 172).

[0075] Figure 3An example of a device 310 is shown that performs wireless communication with at least one of two devices (e.g., device 320a and device 320b, referred to as device 320) in a communication system (e.g., communication system 100) according to one embodiment. Device 310 may be a UE (e.g., Figure 3 ED 110 in the example). Device 320a can be a terrestrial network device (e.g., such as ED 110). Figure 3 The T-TRP 170 shown), and device 320b can be a non-terrestrial network device (e.g., such as...). Figure 3 (NT-TRP 172 shown). However, this is not a necessary condition. For example, according to the invention, device 320a can be NT-TRP, device 320b can be T-TRP, and both devices 320a and 320b can be either T-TRP or NT-TRP. ED 110 is described below as an example of device 310, T-TRP 170 is described as an example of device 320a, and NT-TRP 172 is described as an example of device 320a. Although only one device 310, one device 320a, and one device 320b are shown, note that the number of devices 310 (e.g., ED 110) can be one or more, and the number of devices 320a and / or 320b can be one or more. For example, an ED 110 can be served by only one T-TRP 170 (or one NT-TRP 172), by more than one T-TRP 170, by more than one NT-TRP 172, or by one or more T-TRP 170 and one or more NT-TRP 172.

[0076] The ED 110 is used to connect people, objects, and machines. It can be widely used in various scenarios, including cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), MTC, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), mixed reality (MR), digital twins, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, and mobility.

[0077] Each ED 110 represents any suitable end-user equipment used for wireless operation and may include (or be referred to as, but not limited to, the following devices): user equipment (UE) / terminal equipment, wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), MTC equipment, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics, smartbook, vehicle, automobile, truck, bus, train, or IoT device, wearable device (e.g., watch, glasses, head-mounted device, etc.), industrial equipment, or devices in or including the above-mentioned equipment (e.g., communication module, modem, or chip), etc. Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs, referred to below as T-TRP 170. Also in Figure 3 As shown, the non-terrestrial (NT) device will be referred to as NT-TRP 172 below. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically turned on (i.e., established, activated, or enabled), turned off (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connectivity availability and connectivity necessity.

[0078] like Figure 3As shown, ED 110 includes at least one processor 210. Only one processor 210 is shown in the figure to avoid congestion. ED 110 may also include a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown in the figure to avoid congestion. Alternatively, one, some, or all of the antennas 204 may be panels. The transmitter 201 and receiver 203 may, for example, be integrated as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver is also used to demodulate data or other content received through at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals. ED 110 may include at least one memory 208. For simplicity, only transmitter 201, receiver 203, processor 210, memory 208 and antenna 204 are shown, but ED 110 may include one or more other components.

[0079] Memory 208 stores instructions. Memory 208 may also store data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules executed by one or more processing units (e.g., processor 210) for implementing some or all of the functions and / or embodiments described herein. Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory may be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, and on-processor cache, etc.

[0080] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., connected to...). Figure 1 (Wired interface of Internet 150 in the network). Input / output devices or interfaces support interaction with users or other devices in the network. Each input / output device or interface includes any suitable structure for providing or receiving information from the user, and / or for communication on the network interface. Suitable structures include, for example, speakers, microphones, keypads, keyboards, displays, touchscreens, etc.

[0081] Processor 210 performs (or controls ED 110 to perform) operations described herein as being performed by ED 110, as shown below and elsewhere in the invention. For example, processor 210 performs or controls ED 110 to perform the following operations: receive a transport block (TB), decode one of the received TBs using resources, release resources to decode another of the received TBs, and / or receive configuration information for configuring resources. Specifically, the operations may include operations related to preparing for uplink transmissions to NT-TRP 172 and / or T-TRP 170; operations related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170; and operations related to processing sidelink transmissions to and from another ED 110. Processing operations related to preparing for uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. Processing operations related to downlink transmissions may include transmit / receive beamforming, modulation / demodulation, and encoding / decoding symbols. According to embodiments, downlink transmissions may be received by receiver 203 using receive beamforming, and processor 210 may extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). For example, an example of signaling may be a reference signal transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 210 performs transmit beamforming and / or receive beamforming based on an indication of beam direction (e.g., beam angle information (BAI)) received from T-TRP 170. In some embodiments, processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and obtaining system information. In some embodiments, processor 210 may perform channel estimation, for example, using the reference signal received from NT-TRP 172 and / or T-TRP 170.

[0082] Although not shown, processor 210 may be part of transmitter 201 and / or receiver 203. Although not shown, memory 208 may be part of processor 210.

[0083] The processing components of processor 210, transmitter 201, and receiver 203 may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 208). Alternatively, some or all of the processing components of processor 210, transmitter 201, and receiver 203 may be implemented using dedicated circuitry such as a programmable field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), or hardware accelerator (e.g., a graphics processing unit (GPU) or artificial intelligence (AI) accelerator).

[0084] In some implementations, ED 110 may be a device (also called a component), such as a communication module, modem, chip, or chipset, which includes at least one processor 210 and an interface or at least one pin. In this scenario, the transmitter 201 and receiver 203 may be replaced by an interface or at least one pin for connecting the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Accordingly, sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as sending information to an interface or at least one pin, or as sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin, and receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as receiving information from an interface or at least one pin, or as receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin. The information may include control signaling and / or data.

[0085] like Figure 3As shown, the T-TRP 170 includes at least one processor 260. Only one processor 260 is shown in the figure to avoid congestion. The T-TRP 170 may also include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figure to avoid congestion. Alternatively, one, some, or all of the antennas 256 may be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. The T-TRP 170 may also include at least one memory 258. The T-TRP 170 may also include a scheduler 253. For simplicity, only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256, and scheduler 253 are shown, but the T-TRP may include one or more other components.

[0086] In some implementations, the T-TRP 170 can use other names, such as base station, base transceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, NodeB, evolved NodeB (eNodeB or eNB), home eNodeB, next-generation NodeB (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, ground node, ground network device, ground base station, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), location node, etc. The T-TRP 170 can be a macro base station (BS), pico BS, relay node, donor node, or a combination thereof. T-TRP 170 may refer to the aforementioned device or a component of the aforementioned device (e.g., a communication module, modem, or chip).

[0087] In some embodiments, the various parts of T-TRP 170 may be distributed. For example, some of the modules of T-TRP 170 may be located remotely from the device housing the antenna 256 of T-TRP 170 and may be coupled to the device housing the antenna 256 via a communication link (not shown) (e.g., a common public radio interface, CPRI) sometimes referred to as the fronthaul. Therefore, in some embodiments, the term T-TRP 170 may also refer to network-side modules that perform processing operations such as determining the location of ED 110, resource allocation (scheduling), message generation, and encoding / decoding; these modules are not necessarily part of the device housing the antenna 256 of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs operating together to serve ED 110, for example, through cooperative multicast transmission.

[0088] The operations performed by processor 260 include those related to: preparing transmissions for downlink transmission to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for return transmission to T-TRP 170 and / or NT-TRP 172, and processing transmissions received via return transmission from T-TRP 170 and / or NT-TRP 172. Processing operations related to preparing transmissions for downlink or return transmission may include operations such as encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via return transmission may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. Processor 260 may also perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating the contents of a synchronization signal block (SSB) and generating system information. In some embodiments, processor 260 also generates an indication of beam direction (e.g., BAI), which scheduler 253 can schedule for transmission. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110, determining the deployment location of NT-TRP 172, etc. In some embodiments, processor 260 can generate signaling, for example, configuring one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252.

[0089] Scheduler 253 may be coupled to or integrated into processor 260. Scheduler 253 may be included within T-TRP 170 or may operate separately from T-TRP. Scheduler 253 may schedule uplink, downlink, lateral link, and / or backlink transmissions, including issuing scheduling authorizations and / or configuring schedule-free (e.g., "configuration authorization") resources.

[0090] Memory 258 is used to store information, and optionally data. Memory 258 stores instructions and data used, generated, or acquired by T-TRP 170. For example, memory 258 may store software instructions or modules executed by processor 260 for implementing some or all of the functions and / or embodiments described herein.

[0091] Although not shown, processor 260 may constitute part of transmitter 252 and / or receiver 254. Additionally, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may constitute part of processor 260.

[0092] The processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processing components of the processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented using dedicated circuitry such as a programmed FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC.

[0093] When T-TRP 170 is a device (also referred to as a component, such as a communication module, modem, chip, or chipset in a device), it includes at least one processor, an interface, or at least one pin. In this scenario, transmitter 252 and receiver 254 can be replaced by an interface or at least one pin used to connect the device (e.g., a chip) to other devices (e.g., a chip, memory, or bus). Accordingly, sending information to NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as sending information to an interface or at least one pin, and receiving information from NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. The information may include control signaling and / or data.

[0094] Although the NT-TRP 172 is shown as an example of a drone only, it can be implemented in any suitable non-terrestrial form, such as satellites and high-altitude platforms including international mobile telecommunications base stations and unmanned aerial vehicles. Additionally, in some implementations, the NT-TRP 172 may use other names, such as non-terrestrial node, non-terrestrial network device, or non-terrestrial base station.

[0095] like Figure 3 As shown, the T-TRP 170 may also include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figure to avoid congestion. Alternatively, one, some, or all of the antennas 256 may be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. The T-TRP 170 may also include at least one memory 258. The T-TRP 170 may also include a scheduler 253. For simplicity, only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256, and scheduler 253 are shown, but the T-TRP may include one or more other components.

[0096] like Figure 3 As shown, the NT-TRP 172 includes at least one processor 276. Only one processor 276 is shown in the figure to avoid congestion. The NT-TRP 172 may include a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is shown in the figure to avoid congestion. One, some, or all of the antennas may alternatively be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 may also include at least one memory 278. The NT-TRP 172 may also include a scheduler. For simplicity, only the transmitter 272, receiver 274, processor 276, memory 278, and antenna 280 are shown, but the NT-TRP may include one or more other components.

[0097] NT-TRP 172 includes a processor 276 for performing various operations, including operations related to: preparing a transmission for downlink transmission to ED 110, processing an uplink transmission received from ED 110, preparing a transmission for return transmission to T-TRP 170 and / or another NT-TRP 172, and processing a transmission received via return transmission from T-TRP 170 and / or another NT-TRP 172. Processing operations related to preparing for downlink or return transmissions may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via return transmission may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, for example, for configuring one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-layer functions, such as those in the medium access control (MAC) layer or radio link control (RLC) layer. Since this is merely an example, NT-TRP 172 may more generally implement higher-layer functions in addition to physical layer processing.

[0098] Memory 278 is used to store information, and optionally data. Memory 258 stores instructions and data used, generated, or acquired by NT-TRP 172. For example, memory 278 may store software instructions or modules executed by processor 276 for implementing some or all of the functions and / or embodiments described herein.

[0099] Although not shown, processor 276 may be part of transmitter 272 and / or receiver 274. Although not shown, memory 278 may be part of processor 276.

[0100] The processing components of processor 276, transmitter 272, and receiver 274 may each be implemented by the same or different one or more processors for executing instructions stored in memory (e.g., memory 278). Alternatively, some or all of the processing components of processor 276, transmitter 272, and receiver 274 may be implemented using dedicated circuitry such as a programmed FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC. In some embodiments, NT-TRP 172 may actually be multiple NT-TRPs operating together, for example, via cooperative multicast service ED 110.

[0101] When NT-TRP 172 is a device within a machine (e.g., a communication module, modem, chip, or chipset), it includes at least one processor and an interface or at least one pin. In this scenario, transmitter 272 and receiver 257 can be replaced by an interface or at least one pin used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Accordingly, sending information to T-TRP 170 and / or another NT-TRP 172 and / or ED 110 can be referred to as sending information to an interface or at least one pin, and receiving information from T-TRP 170 and / or another NT-TRP 172 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. The information may include control signaling and / or data.

[0102] It should be noted that, as used herein, "transmit / receive point (TRP)" can refer to either T-TRP or NT-TRP. T-TRP can alternatively be referred to as terrestrial network TRP (TNTRP), and NT-TRP can alternatively be referred to as non-terrestrial network TRP (NTNTRP). T-TRP 170, NT-TRP 172, and / or ED 110 may include other components, but these are omitted for clarity.

[0103] It should be noted that, for simplicity, the term "signaling" as used herein can be alternatively referred to as control signaling, control message, control information, or message. Signaling between a BS (e.g., network node 170) and a terminal or sensing device (e.g., ED 110), or between different terminals or sensing devices (e.g., between ED 110i and ED 110j), can be carried in physical layer signaling (also known as dynamic signaling), which is transmitted in the physical layer control channel. For the downlink, physical layer signaling can be referred to as downlink control information (DCI) transmitted in the physical downlink control channel (PDCCH). For the uplink, physical layer signaling can be referred to as uplink control information (UCI) transmitted in the physical uplink control channel (PUCCH). For sidelinks, signaling between different terminals or sensing devices (e.g., between ED 110i and ED 110j) can be referred to as sidelink control information (SCI) transmitted in the physical sidelink control channel (PSCCH). Signaling can be carried in higher-layer (e.g., above the physical layer) signaling, which is transmitted in physical layer data channels. For example, downlink signaling is transmitted in the physical downlink shared channel (PDSCH), uplink signaling in the physical uplink shared channel (PUSCH), and sidelink signaling in the physical sidelink shared channel (PSSCH). Higher-layer signaling can also be referred to as static signaling or semi-static signaling. Higher-layer signaling can be radio resource control (RRC) protocol signaling or media access control-control element (MAC-CE) signaling. Signaling can be included in a combination of physical layer signaling and higher layer signaling.

[0104] It should be noted that in this invention, when "information" and "message" are different, they can be carried in a single message or in more than one single message.

[0105] Figure 4 An example of device 410 is shown. According to... Figure 4 One or more steps of the method provided by the present invention can be executed by the corresponding unit or module. Figure 4 Units or modules in devices or apparatuses such as ED 110, T-TRP 170, or NT-TRP 172 are illustrated. For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by an artificial intelligence (AI) module or a machine learning (ML) module. The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of these units or modules may be circuits such as integrated circuits. Examples of integrated circuits include programmed FPGAs, GPUs, or ASICs. For example, one or more of these units or modules may be logical, such as logical functions executed by circuits, a portion of an integrated circuit, or software instructions executed by a processor. It should be understood that if these modules are implemented using software executed by a processor, etc., then these modules may be retrieved by the processor, wholly or partially, individually or collectively, for processing, in single or multiple instances, and these modules themselves may include instructions for further deployment and instantiation.

[0106] Additional details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0107] As mentioned above, NT-TRP can communicate directly or indirectly with one or more of other NT-TRPs, core networks, EDs, and T-TRPs.

[0108] In some implementations, an NT-TRP can communicate with another NT-TRP. For example, NT-TRPs (e.g., satellites) communicate with each other using free-space optical links (e.g., lasers).

[0109] In some implementations, the NT-TRP can communicate with the core network (e.g., one or more functions within the core network). For example, the NT-TRP can communicate with the core network through a gateway. The gateway can be a terrestrial gateway or a non-terrestrial gateway, which can be a dedicated gateway for the NT-TRP. The gateway can be located on the ground. The NT-TRP can communicate with the gateway using a wireless link, and the gateway can communicate with the core network using a wired link (e.g., a fiber optic link). This application does not limit this.

[0110] In some implementations, the NT-TRP can communicate with the T-TRP. For example, the T-TRP can communicate with the NT-TRP using a wireless link. Alternatively, the T-TRP and NT-TRP can communicate through the core network. In one implementation, the T-TRP communicates with the core network, and the core network communicates with the NT-TRP.

[0111] In some implementations, the NT-TRP can communicate with the ED (e.g., the UE). In the first example, the NT-TRP can communicate with the ED using a radio link. In the second example, the NT-TRP can communicate with the ED via the core network. In the third example, the NT-TRP can communicate with the ED via a T-TRP.

[0112] This invention is directed to devices such as UEs, IoT devices, and automobiles. The envisioned network scenarios may include terrestrial TRPs (e.g., base stations) and / or non-terrestrial TRPs (e.g., drones, balloons, high-altitude platform stations (HAPS), satellites), as well as any such devices that support wireless access technologies (e.g., 5G NR, 6G, or other technologies).

[0113] For illustrative purposes, combined with Figures 5 to 9 Here are some examples.

[0114] Figure 5 A first example of a communication system including NT-TRP and T-TRP is shown. For instance, one possible scenario is T-TRP communicating with NT-TRP as part of a satellite constellation. The satellite constellation comprises multiple satellite orbits, ensuring that Earth is always covered by satellites, and each orbit can contain multiple satellites. T-TRP can connect to the core network via a terrestrial network (TN) gateway, while the satellite constellation can connect to the core network via a dedicated non-terrestrial network (NTN) gateway. Devices such as EDs can connect to and communicate with either T-TRP or NT-TRP, depending on conditions such as traffic load, radio link quality, and congestion.

[0115] Figure 6A second example of a communication system including NT-TRP and T-TRP is shown. For example, a satellite constellation can effectively act as a gateway for a terrestrial T-TRP. Satellites in the constellation communicate with the core network via a wireless link through the terrestrial gateway, which in turn can communicate with the core network via a wired link (e.g., a fiber optic link). T-TRP communicates with satellites via a wireless link, and satellites communicate with each other via free-space fiber optic links (e.g., using lasers). Devices such as EDs can connect to and communicate with either T-TRP or NT-TRP, depending on conditions such as traffic load, wireless link quality, and congestion.

[0116] Figure 7 A third example of a communication system including NT-TRP and T-TRP is shown. For example, NT-TRP communicates with T-TRP via the core network. NT-TRP may first communicate with a dedicated NTN gateway, which then communicates with the core network. The core network can then relay energy-saving commands from non-terrestrial TRPs to terrestrial TRPs via a dedicated terrestrial gateway. Devices such as EDs can connect to and communicate with either T-TRP or NT-TRP, depending on conditions such as traffic load, radio link quality, and congestion.

[0117] Figure 8 An example of an NT-TRP communication link is shown. As described above, the NT-TRP and NTN gateway can communicate using a wireless link, and the NT-TRP and ED can also communicate using a wireless link. The communication link between the NT-TRP and the NTN gateway can be referred to as a feeder link, and the communication link between the NT-TRP and the ED can be referred to as a service link. In some embodiments, the T-TPR (e.g., a base station) is located after the NTN gateway on the ground, the NTN gateway transmits data to the satellite via the feeder link, and the satellite transmits data to the ED on the ground via the service link. This scenario is called a bend-pipe scenario.

[0118] It is worth noting that a single NT-TRP can serve one or more EDs. For example, there may be a coverage area on the ground, and some devices (e.g., EDs) are located within the coverage area of ​​the NT-TRP. The NT-TRP (e.g., a satellite) can transmit multiple beams to the ground, and each beam can be associated with a given physical cell identity (PCI). Furthermore, the satellite can transmit beams in such a way that instead of directionalizing its beams, the beams can glide across the Earth's surface, so from the perspective of devices on the ground, the beams appear to be moving.

[0119] To connect with NT-TRPs (e.g., satellites), the ED can turn its beam towards the sky. However, there may be many NT-TRPs (e.g., satellites within the ED's line of sight), therefore: there may be many NT-TRPs with which the ED can establish RRC connections.

[0120] Figure 9 A schematic diagram of communication between the NT-TRP and the ED is shown. To facilitate the establishment of an RRC connection between the ED and the NT-TRP, the ED may need to generate a transmit / receive beam directed towards the NT-TRP. For example, the ED could receive a channel transmitted by the NT-TRP.

[0121] For example, suppose ED uses BAI corresponding to the angular direction in, for example, the zenith domain or the azimuth domain, or a combination of both. It should be noted that the elevation domain and the zenith domain are related (using degrees) by the following relationship: (Formula 1) In some embodiments, the ED may be equipped with a variety of sensors (e.g., gyroscopes and inclinometers) that allow the UE to determine, for example, the position of the sky or the true north-facing position. Such sensors will allow the UE to determine the azimuth and / or zenith angle without connecting to any specific navigation system. These sensors will also allow the ED to measure angular direction in, for example, the azimuth / zenith domain, where physical layer signals and / or channels are detected, measured, and decoded.

[0122] It should be noted that beam angle information can be equivalently referred to as "beam angle indication," making the two terms interchangeable, and BAI can equivalently refer to beam angle information or beam angle indication. It can be assumed that for DL / UL communication and / or RRM / mobility measurement purposes, the ED is configured with a list or table of BAIs, where each BAI can be a quantized value corresponding to a given angular direction in the azimuth domain / zenith domain (or some combination of these two domains). The term "BAI" can be used to refer to a Tx / Rx spatial filter (or beam) whose aiming line points in the direction indicated by the BAI. For each BAI used by the UE, the UE can generate a Tx / Rx spatial filter or equivalent Tx / Rx beam whose aiming line can correspond to the angular direction provided by the BAI. For example, the UE can configure a BAI with a quantized value set to "000" in the zenith domain, which can correspond to a 0-degree zenith angle (i.e., pointing towards the sky). The UE can then generate a Tx / Rx beam with its aiming line pointing towards the 0-degree zenith angle, i.e., the Tx / Rx beam pointing towards the sky.

[0123] Service BAIs can be configured using higher-layer signaling (e.g., RRC signaling), and such service BAIs can be used by the ED to receive / detect / measure reference signals (e.g., SS / PBCH blocks and / or NZP CSI-RS). Similarly, service BAIs can be used by the ED to receive / detect / decode physical layer channels (e.g., PDCCH / PDSCH) and transmit physical layer channels (e.g., PUCCH / PUSCH).

[0124] A BAI table that uses higher-level signaling (such as RRC signaling) in the zenith domain can be provided to the ED in RRC connection mode. An example of such a table is shown in Table 1: Table 1

[0125] As shown in Table 1 above, each zenith angle corresponds to an absolute angular direction, for example, in degrees, and can be interpreted as an angular direction in which the ED can control its space receiving beam such that the aiming line of the space receiving beam points towards that angular direction. Assume that 0 degrees in the zenith domain corresponds to the ED's vertically pointing skyward transmit / receive beam. Each angular direction is associated with a BAI provided as a 4-bit codeword. In this example, the codeword has a 4-bit width. Since the default zenith angle BAI table includes 15 entries, other examples of zenith angle BAI tables with more or fewer entries can be considered or envisioned. Table 1 above can include one or more entries, each including a 4-bit codeword, and the ED can use one or more entries from Table 1 above to direct its space receiving beam toward the direction of any one or more entries.

[0126] To assist the ED in performing communication functions with non-terrestrial networks, the network can use higher-level signaling (e.g., RRC signaling for servingZenithBaiList) to configure the ED's "serving BAI list" and higher-level signaling (e.g., RRC signaling for candidateZenithBaiList) to configure the "candidate BAI list".

[0127] exist Figure 9 The diagram shows multiple Tx / Rx beams pointing in different directions within the zenith domain, specifically for the ED. The five beams represented by solid lines can correspond to beams with... servingZenithBaiList The higher-level parameter configuration of the BAI's Tx / Rx beams. The eight beams, indicated by dashed lines, can correspond to... candidateZenithBaiListThe BAI's Tx / Rx beams are configured with high-level parameters. The aiming line for each beam can point in a given direction within the zenith domain, as shown by the dashed lines. Each dashed line can intersect the satellite orbit at a given point. It can be assumed that two different satellites may be in orbit, for example, one satellite with a zenith angle of -20 degrees (the satellite on the left) and the other with a zenith angle of 0 degrees (the satellite on the right). It can be assumed that there are other satellites in the same orbit, but they are not shown in the figure. It can be assumed that the two satellites shown in the figure may be coordinating their scheduling to coordinate their Earth-facing ED scheduling using, for example, a non-coherent joint transmission (NC-JT) scheme, where NC-JT refers to a transmission scheme that does not report channel phase shifts between different TRPs to the network.

[0128] It is worth noting that the ED can be connected to a network, meaning the ED can have an RRC connection to the network and be in connected mode. Alternatively, the ED can be in a power mode associated with having an RRC connection (for connected mode).

[0129] The support for NTN introduced in 5G NR is based on a non-transparent design, meaning that each satellite is actually treated as a serving cell by devices such as UEs, IoT devices, and vehicles. Devices also have access to the satellite's ephemeris and its location at any given time because the satellite explicitly broadcasts this information in System Information Block 19 (SIB19), which is sent by the satellite to assist in providing NTN access assistance information to devices such as UEs (i.e., the UE accesses the NTN and will be served by the NTN). This results in a non-transparent radio access design, preventing the smooth integration of transmit diversity schemes, multi-TRP transmission schemes, and distributed satellite systems.

[0130] In traditional cellular systems such as 5G NR, the ED (Edge Receiver) can receive, detect, and measure reference signals such as SS / PBCH blocks and NZP-CSI-RS. These reference signals are based on pseudo-random noise (PRN) binary sequences, such as the Gold sequence, and these sequences can be initialized using either a common or ED-specific scrambling code identifier. For example, the primary synchronization signal (PSS) and secondary synchronization signal (SSS) sequences are initialized using a physical cell identity (PCI) value, which is a common scrambling code identifier. The NZP-CSI-RS sequence is initialized using an ED-specific scrambling code identifier, which is configured to the ED by the network.

[0131] In some implementations, 5G NR supports non-terrestrial networks by introducing multiple enhancements to the timing relationship of timing advance, the reference time of channel state information (CSI) resources, the transmission time of DCI for scheduling PUSCH, the transmission time of random access response carried by PUSCH, and the transmission time of HARQ-ACK on PUCCH.

[0132] In 5G NR, NTN support is introduced, allowing the ED (Electronic Device) to communicate with satellites via DL / UL (Depth / Low Length) in a so-called "bend" scenario. This involves the ground station sending signals to a satellite in space, which then reflects the signals back to the ED on the ground. Dedicated signaling related to NTN is introduced to assist the ED in NTN operations. Higher-layer signaling such as RRC (Radio Recognition Control) introduces information such as satellite ephemeris, satellite position, satellite signal polarization, time advance offset, system information block (SIB), and satellite epochs to support NTN operations. Other introduced features include expanding the number of hybrid automatic repeat request (HARQ) processes to 32 to accommodate scenarios with large propagation delays and disabling HARQ-ACK feedback.

[0133] In 5G NR, NTN support is further enhanced, introducing coverage enhancements for NTN, ED positioning for network verification, and support for TN-to-NTN and NTN-to-NTN mobility scenarios.

[0134] 5G NR also introduces a scheme that combines closed-loop and open-loop timing advance compensation, where the closed-loop part is controlled by the network and the open-loop part is executed by the ED (Edge Analyzer). The compensation from the ED can be based on knowledge of satellite ephemeris (such as satellite orbital angles and other parameters).

[0135] In low Earth orbit (LEO) NTN access scenarios, satellites are constantly in motion, resulting in a limited time within line of sight for ground-based devices. For example, in the Starlink constellation, the duration an LEO satellite remains within line of sight of a given ground-based device might be only a few minutes. Therefore, any information sent or broadcast by the satellite to ground-based devices becomes outdated within minutes and requires constant updates for satellite communication to function properly (due to constantly changing uplink synchronization lead and the need to re-acquire downlink synchronization). This results in high signaling overhead between the satellite and ground-based devices, just to maintain the communication link.

[0136] LEO satellites use a fixed-beam model to transmit signals and channels to devices on the ground. This causes the satellite beam to "slide" across the Earth's surface, triggering a movement and handover process whenever a device is located at the edge between two beams. This movement and handover process can cause delays and interruptions because an RRC connection needs to be re-established upon entering the target cell, thus impacting the overall user experience.

[0137] 5G NR supports NTN based on assigning unique physical cell identities (PCIs) to different beams. The use of fixed beams introduces two types of interference problems in reference signal measurements and / or physical layer channel communication. The first problem is "PCI confusion," which occurs when two or more adjacent beams use the same PCI. The second problem is "PCI conflict," which occurs when adjacent beams use the same PCI as their serving beam. Both problems can occur when beams transmitted from different satellites begin to overlap.

[0138] As LEO satellites move along their orbits, they inevitably leave a given coverage area, and all EDs within that area need to undergo a relocation process to maintain connectivity with, for example, LEO satellites. This inherently introduces latency due to the need to re-establish RRC connections with the target satellites, and this problem is exacerbated in NTN LEO scenarios because such handovers occur continuously. Therefore, every time a handover is required, the connection between the ED and, for example, the LEO satellite is interrupted and reset, degrading the user experience for the ED.

[0139] Terrestrial and non-terrestrial networks are treated as “separate” networks by the ED (Edge Controller) because they are considered separate “public land mobile networks” (PLMNs) with their own unique codes. PLMN information consists of a Mobile Country Code (MCC) and a Mobile Network Code (MNC), which are unique numbers assigned by the ITU-T. In 5G NR, the ED needs to scan all RF channels, detect the strongest cells, and find available PLMNs in order to report them to its non-access stratum (NAS) and register them with the appropriate PLMN. This necessitates the ED running the initial access procedures for both terrestrial and non-terrestrial networks.

[0140] Because LEO satellites move along their orbits, mobility measurements (which can be equivalently called radio resource management (RRM) measurements) will be affected. This is because the signals transmitted by the satellites are affected by very different propagation delays, which will affect when these measurements can be performed. Terrestrial networks allow the assumption that the serving cell's time is applied to all neighboring cells when performing RRM / mobility measurements because the distance the wave travels to the ED is small relative to the speed of light. However, for non-terrestrial networks, this assumption no longer holds because the distance is significantly increased, and non-terrestrial TRPs are constantly in motion. This effectively causes the ED to "miss" the reference signal used for RRM measurements because the signal's arrival time is earlier or later than the time actually indicated by the higher-layer signaling. This will disrupt the entire RRM / mobility framework, as the ED will be unable to perform RRM / mobility measurements correctly.

[0141] 6G systems are expected to integrate large-scale satellite constellations, potentially containing thousands or tens of thousands of satellites in a given constellation. With too many satellites on the same orbital plane at the same altitude, the planning and utilization of satellites and orbits will face challenges; for example, there is a risk of satellite collisions at intersection points. In large-scale constellation scenarios, this could lead to the so-called "Kessler syndrome," where debris from a single collision triggers further collisions, generating even more debris. This would effectively make the deployment of large-scale constellations impossible.

[0142] In some implementations, the ED can support intra-cell multi-TRP (M-TRP) transmission schemes for both ideal and non-ideal backhaul deployments. For example, in a non-ideal backhaul deployment, T-TRPs within the same cell can send corresponding PDCCH / PDSCH transmissions to the ED, each carrying its own service data. In one possible implementation, the ED can be configured with a higher-layer parameter called CoresetPoolIndex, which can take two values ​​(0 or 1), where each value of CoresetPoolIndex distinguishes different TRPs. In another implementation, inter-cell M-TRP is supported, where a CoresetPoolIndex value of 1 is associated with a neighboring cell using a different PCI than the serving cell.

[0143] When M-TRP transmissions involve multiple T-TRPs, the two T-TRPs can use the same serving cell time reference because the T-TRPs are stationary. However, this assumption no longer holds true when M-TRP transmissions involve NT-TRPs, especially in NTN (particularly LEO constellations) scenarios, because satellites typically move along their orbital planes, resulting in constantly changing distances between satellites and the ED (Edge Controller). This necessitates continuous time reference updates. Furthermore, different satellites will be at different distances relative to the ED, requiring independent time reference updates for each satellite. Inaccurate time reference assumptions will cause the ED to miss PDCCH / PDSCH transmissions, ultimately leading to a poor user experience.

[0144] The embodiments described herein illustrate information sufficient to practice the claimed subject matter and explain methods for practicing such subject matter. Upon reading the following description with reference to the accompanying drawings, those skilled in the art will understand the concepts of the claimed subject matter and recognize that the application of these concepts is not specifically mentioned herein. It should be understood that these concepts and applications are within the scope of this invention and the appended claims.

[0145] Accordingly, the present invention provides a method. The present invention introduces the characteristics of PDCCH / PDSCH reception centered on ED, specifically, it introduces PDCCH / PDSCH delay, PDCCH / PDSCH time window and / or PDCCH / PDSCH time correction scheme.

[0146] Therefore, this application provides an M-TRP transmission method involving NT-TRP, which helps to reduce the complexity of ED receiving channels from different TRPs in NTN systems.

[0147] Figure 10 This is a schematic flowchart of a communication method 1000 according to an embodiment of this application.

[0148] At step 1010, the first TRP obtains the first transmission time of the first channel.

[0149] The first and second channels are sent to the ED. The second channel originates from a second TRP. The first transmission time differs from the second transmission time of the second channel, and at least one of the first and second TRPs is an NT-TRP. In other words, the first and second TRPs can send the first and second channels to the same ED at different transmission times, rather than simultaneously. This helps reduce the complexity of the ED receiving channels from different TRPs in an NTN system.

[0150] At least one of the first TRP and the second TRP is an NT-TRP, and an NT-TRP can refer to any type of NT-TRP described above. For example, both the first TRP and the second TRP are NT-TRPs, or the first TRP is an NT-TRP and the second TRP is a T-TRP, or the first TRP is a T-TRP and the second TRP is an NT-TRP.

[0151] It is worth noting that, for ease of description, the embodiments of this application describe the first TRP and the second TRP (both of which are NT-TRP) for illustrative purposes.

[0152] The distance between the first TRP and the ED and the distance between the second TRP and the ED can be different. For example, the distance between the first TRP and the ED may be less than the distance between the second TRP and the ED. Alternatively, the distance between the first TRP and the ED may be greater than the distance between the second TRP and the ED. For ease of description, the TRP that is farther away can be named the farther TRP (e.g., the farther NT-TRP), and the other TRP can be named the closer TRP (e.g., the closer NT-TRP).

[0153] It is worth noting that, since the NT-TRP may move continuously, the roles of the more distant NT-TRP and the more nearby NT-TRP may change over time. In some implementations of this application, for ease of description, the first TRP is regarded as the more nearby NT-TRP, and the second TRP is regarded as the more distant NT-TRP. This application does not limit this.

[0154] For ease of description, in this application, "transmission time" refers to the time when the channel (signal, data, or information) is sent from the transmitter; "transmission time" refers to the time it takes for the channel (signal, data, or information) to travel from the transmitter to the receiver, i.e., the propagation delay, transmission time, or transmission delay of the channel; and "reception time" refers to the time when the channel (signal, data, or information) arrives at the receiver.

[0155] The transmission time of a channel from a more distant TRP to an ED is longer than that of a channel from a closer TRP to an ED.

[0156] When an ED interacts with multiple TRPs (e.g., in a multi-TRP technology), the first transmission time from the first channel of the first TRP differs from the second transmission time from the second channel of the second TRP. This different first and second transmission time is designed based on the different transmission times of the first and second channels. For example, the design of the first and second transmission times can take into account the reception time requirements of the first and second channels to reduce the processing complexity of the ED due to the difference in reception times between the first and second channels.

[0157] The first and second transmission times can be determined in various ways. For example, the first and / or second transmission times can be related to the location of a reference point. The reference point can help represent the distance between the first TRP and the ED (hereinafter referred to as distance #1) and the distance between the second TRP and the ED (hereinafter referred to as distance #2). For example, since the main difference between distance #1 and distance #2 is due to the excessive distance between the NT-TRP and the ground, the reference point can be located on or near the ground.

[0158] In some implementations, one of the first and second transmission times is determined based on network scheduling (in channel-based applications). The delay between the first and second transmission times is related to a reference point; for example, the delay can be determined based on the location of the reference point.

[0159] For example, the second transmission time is determined based on network scheduling. The first transmission time is determined based on the second transmission time and the delay. The delay is determined based on the location of the reference point. For example, the delay is determined based on the distance between the first TRP and the reference point (hereinafter referred to as distance #3) and the distance between the second TRP and the reference point (hereinafter referred to as distance #4). The delay can be the difference between the transmission time through the first channel at distance #3 and the transmission time through the second channel at distance #4.

[0160] In some implementations, ED assumes that the first and second channels are received at specific times or time periods. The first and second transmission times can be determined based on the specific time or time period and are related to a reference point.

[0161] An example of a time period can be expressed relatively, such as 3 to 4 time slots, where the unit "time slot" can be replaced by other units (e.g., subframe, symbol, etc.). Another example of a time period can be expressed absolutely, such as 3 to 4 microseconds, where "millisecond" can be replaced by other terms (e.g., millisecond, etc.). Similarly, an example of a specific time can be expressed relatively, such as 20 symbols, or absolutely, such as 3 microseconds.

[0162] It is worth noting that the first and second transmission times can be designed to allow the first and second channels to arrive at the reference point simultaneously (or relatively simultaneously). Since the reception time is related to distances #3 and #4, this design is based on the location of the reference point.

[0163] Reference points can be determined in various ways. Reference points can be dynamic or static, and can be located on or near the ground; this application does not impose any limitations on this.

[0164] In the first implementation, the reference point can be the location of the ED. For example, the first and second transmission times can be related to the location of the ED. The delay between the first and second transmission times can be determined based on the location of the ED. For example, the delay is determined based on the difference between distance #3 (which is the same as distance #1 in this case) and distance #4 (which is the same as distance #2 in this case). The more distant TRP can transmit the first channel at the first transmission time, and the closer TRP can wait for the delay before transmitting the second channel at the second transmission time. The ED can simultaneously (or relatively simultaneously) receive, detect, or decode the first and second channels from the first and second TRPs. For ease of description, the delay in this implementation can be referred to below as the ED-centric delay. A detailed example of this implementation will be provided in conjunction with... Figure 11 and Figure 12 For the sake of brevity, the detailed example is omitted here.

[0165] It is worth noting that the location of the ED can be obtained in multiple ways. This application does not exclude any implementation that can obtain the location of the ED.

[0166] In the second implementation, the reference point can be the location of an anchor point. For example, the first and second transmission times can be related to the location of the anchor point. The time delay between the first and second transmission times can be determined based on the location of the anchor point.

[0167] It is worth noting that the delay can be determined based on the difference between distance #3 (which may differ from distance #1 in this case) and distance #4 (which may differ from distance #2 in this case). The more distant TRP can transmit the first channel at the first transmission time, and the closer TRP can wait for the delay before transmitting the second channel at the second transmission time. Since the distance between the ED's location and the reference point may be short, the ED may receive, detect, or decode the first and second channels from the first and second TRPs with a smaller delay.

[0168] For ease of description, the latency in this implementation can be referred to as the anchor-centric latency. If the first TRP and the second TRP send the first channel and the second channel to the anchor location respectively, then the first channel and the second channel can arrive at the anchor location simultaneously. If the ED is not at the precise anchor location, the arrival times of the first channel and the second channel at the ED may differ slightly. Details of this implementation will be discussed in conjunction with... Figures 13 to 15 For the sake of brevity, these details are omitted here.

[0169] Anchor points can be selected in several ways. For example, an anchor point can be a common reference point located on (or near) the ground, or a point on the feeder link (such as...). Figure 8 (as shown), or a point located on an NTN gateway, or the usual location of an ED, etc., this application does not limit this to.

[0170] The first channel transmitted to the ED can be any type of signal, data, etc. In some implementations, the first channel includes one or more of the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH). For example, the first TRP can obtain the transmission time of the PDCCH or the transmission time of the PDSCH. It is worth noting that when the first channel includes both PDCCH and PDSCH, the first TRP obtaining the first transmission time of the first channel can include obtaining both the transmission time of the PDCCH and the transmission time of the PDSCH. The first TRP can obtain the transmission time of the PDCCH and the transmission time of the PDSCH separately. Alternatively, the first TRP can first obtain one of the transmission times of the PDCCH and the PDSCH (e.g., the transmission time of the PDCCH), and obtain the other transmission time (e.g., the transmission time of the PDSCH) based on the determined transmission time. This application does not limit this. The signal can be a reference signal, such as a channel state information-reference signal (CSI-RS) or a tracking reference signal (TRS). The channel can be an ED-specific channel, a cell-specific channel, or a group-based channel.

[0171] Similarly, the second channel transmitted to the ED can be any type of signal, data, etc. In some implementations, the second channel includes one or more of the physical downlink control channel (PDCCH) and the physical downlink shared channel (PDSCH). Details can be found in the description of the first channel above; for brevity, these details have been omitted. The signal can be a reference signal, such as CSI-RS, TRS, etc. The channel can be an ED-specific channel, a cell-specific channel, or a group-based channel.

[0172] In some implementations, the first and second channels can be associated or duplicated. For example, the first and second channels can be duplicated PDCCH or PDSCH. The ED can receive PDCCH or PDSCH from two TRPs (i.e., the first TRP and the second TRP). Therefore, even if the PDCCH or PDSCH from one of the TRPs fails to be received by the ED, the ED can still receive PDCCH or PDSCH from the other TRP. This can improve the reliability of PDCCH or PDSCH transmission. Again, the first and second channels can be associated or duplicated data; this application does not limit this. It is worth noting that duplication can occur within more than two TRPs (e.g., three or more TRPs).

[0173] The first TRP can obtain the first transmission time of the first channel in various ways. In a first implementation, the first TRP can determine the first transmission time, for example, based on the location of a reference point. In a second implementation, the first TRP can obtain the first transmission time from a second TRP.

[0174] For example, the first TRP receives first information from the second TRP, where the first information indicates a first transmission time. The first TRP and the second TRP can transmit the first channel and the second channel based on interactive cooperation.

[0175] The first information can indicate the first transmission time in various ways. For example, the first information can explicitly indicate the first transmission time. Another example is that the first information can indicate the delay between the first transmission time and the second transmission time. The first TRP can determine the first transmission time based on the delay and the second transmission time, wherein the second transmission time can be known to the first TRP or indicated by the first information. This application does not limit this.

[0176] The first information may indicate a first parameter, which may indicate a delay. For example, the first channel may include a PDCCH. The first parameter may also be called pdcchTimeDelay. For example, this parameter may represent a delay interval, indicating how much the first TRP expects its transmission of the PDCCH to the ED will be delayed. The delay may be given with a specific precision, such as in seconds, milliseconds, microseconds, nanoseconds, or OFDM symbol numbers. This application does not limit this.

[0177] In some implementations, the first information may also indicate a second parameter, which indicates a second transmission time. For example, the second parameter may be called schedulingSlotApplicationTime. This parameter may represent, for instance, the absolute or relative time of the scheduling slot that the second TRP will transmit to the ED-scheduled second channel (e.g., PDCCH). The time can be given with specific precision, for example: [aaaa]:[bbb]:[cc]:[dd]:[ee]:[fff]:[ggg]:[hhh]:[iii], where “aaaa” represents a year, “bbb” represents a day, “cc” represents an hour, “dd” represents a minute, “ee” represents a second, “fff” represents a millisecond, “ggg” represents a microsecond, “hhh” represents a nanosecond, and “iii” represents a picosecond.

[0178] In some implementations, the first information may also indicate a third parameter, which indicates the radio network temporary identifier (RNTI) corresponding to the ED receiving the first and second channels. For example, this parameter could be called ueRnti. This parameter could represent the ED radio network temporary identifier (RNTI) that will be scheduled using, for example, non-coherent joint transmission (NCJT) in a multi-TRP manner. The ED RNTI can be an integer value within a given range of bits N, for example, N=48. In one possible implementation, ueRnti can be replaced by another ED identifier different from ueRnti (e.g., a temporary mobile subscriber identity (TMSI)). The first TRP can determine its RNTI as provided by the higher-layer parameters of ueRnti.

[0179] In some implementations, the first channel may include a PDCCH, and the first TPR may also obtain the transmission time of the PDSCH scheduled by the PDCCH. For example, the first TRP may derive the transmission time of the PDSCH based on the first transmission time of the PDCCH. As another example, the first information may also indicate a fourth parameter, wherein the fourth parameter indicates the delay between the transmission time of the PDSCH scheduled by the PDCCH sent by the first TRP and the transmission time of the PDSCH scheduled by the PDCCH sent by the second TRP. For example, the fourth parameter may be called pdschTimeDelay. This parameter may represent a delay interval used to indicate how much the first TRP expects its PDSCH transmission to the ED (whose RNTI is provided by the ueRnti higher-layer parameter) to be delayed. The delay may be given with a specific precision, such as in seconds, milliseconds, microseconds, nanoseconds, or OFDM symbol numbers. In one possible implementation, this parameter may be omitted, and when omitted, the delay of the PDSCH is the same as the delay of the PDCCH provided by the first parameter (e.g., pdcchTimeDelay).

[0180] For illustrative purposes, the first piece of information may be carried in the return message: backhaulMsg = { schedulingSlotApplicationTime = 0000:000:00:00:00:005:000:000, pdcchTimeDelay = 0.2ms, pdschTimeDelay = 0.2ms, ueRnti = 1283 } In some implementations, the second TRP can coordinate with the first TRP using a laser-based inter-satellite link (L-ISL). For example, the second TRP can use L-ISL to send first information to the first TRP.

[0181] It is worth noting that NT-TRPs can synchronize with each other; that is, if it is, for example, 12:00 pm for a given NT-TRP in the constellation, then it is 12:00 pm for all NT-TRPs in the constellation. Similarly, if an NT-TRP performs its scheduling operation every, for example, 1 millisecond, then all NT-TRPs can perform their scheduling operation at the same time. Likewise, if a given NT-TRP starts sending its system frames from, for example, 12:00 pm, and each frame has a duration of, for example, 10 milliseconds, then all NT-TRPs can send their system frames at the same time and for the same duration.

[0182] At step 1020, the second TRP transmits the second channel to the ED at the second transmission time. Correspondingly, the ED receives the second channel from the second TRP.

[0183] At step 1030, the first TRP transmits the first channel to the ED at the first transmission time. Correspondingly, the ED receives the first channel from the first TRP.

[0184] The first and second channels from different TRPs are sent to the same ED. The reception time of the first and second channels can depend on the first and second transmission times.

[0185] The ED can receive the first and second channels in various ways. As mentioned above, the first and second transmission times are related to the location of the reference point. For ease of description, assuming the first channel transmits the first channel to the reference point, the time when the first channel arrives at the reference point is called reference time #1. In some implementations, assuming the second channel transmits the second channel to the reference point, the second channel can arrive at the reference point at the same reference time #1.

[0186] In the first implementation, the ED can receive the first and second channels based on a first reference time. For example, as described above, the delay between the first and second transmission times is determined based on the location of the ED (i.e., the delay centered on the ED). In other words, the reference point is the location of the ED, and the first reference time can be considered as reference time #1. The first and second channels are perceived as arriving at the ED at the first reference time. Detailed examples will be provided in conjunction with... Figure 11 A detailed example is provided, but omitted here.

[0187] In the second implementation, the ED can receive both the first and second channels based on a first time window. The ED can monitor the first time window to receive both the first and second channels. For example, the delay between the first and second transmission times is determined based on the location of the anchor point (i.e., the delay centered on the anchor point). If the ED is not located at the anchor point, there may be a time difference between the reception times of the first and second channels. The time window allows the ED to receive both the first and second channels simultaneously.

[0188] It is worth noting that, although not shown, if the delay is determined based on the location of the ED, the ED can receive the first and second channels based on the first time window.

[0189] The first time window can be designed in several ways. For example, reference time #1 can be located in the middle of the time window, and the length of the first time window can be related to the anchor point. Detailed examples will be provided in conjunction with... Figure 12 A detailed example is provided, but omitted here.

[0190] In the third implementation, the ED can receive a first channel based on a first correction time and a second channel based on a second correction time. For example, the delay is a delay centered on the anchor point. Due to the distance between the ED's location and the anchor point's location, the ED may not receive the first and second channels simultaneously. The ED can obtain a first correction time and a second correction time, where the first correction time can be related to the location of the first TRP, the ED's location, and the anchor point's location, and the second correction time can be related to the location of the second TRP, the ED's location, and the anchor point's location. Detailed examples will be provided in conjunction with... Figure 14 A detailed example is provided, but omitted here.

[0191] In the fourth implementation, the ED can receive the first channel based on a first correction time window and the second channel based on a second correction time window. For example, the delay is the delay centered on the anchor point. Due to the distance between the ED's location and the anchor point's location, the ED may not receive the first and second channels simultaneously. The ED can monitor the first channel within the first correction time window and the second channel within the second correction time window.

[0192] It is worth noting that the first correction time window can be related to the position of the first TRP, the position of the ED, and the position of the anchor point. For example, the first correction time described in the third embodiment can be located in the middle of the first correction time window. Similarly, the second correction time window can be related to the position of the second TRP, the position of the ED, and the position of the anchor point. For example, the second correction time described in the third embodiment can be located in the middle of the second correction time window. This application does not limit this.

[0193] The ED can know how to receive the first and second channels in various ways. In some implementations, the ED can determine how to receive the first and second channels based on some known parameters. For example, the ED can determine a first reference time based on its own location and the locations of the first TRP and / or the second TRP. In some other embodiments, the ED can be used to receive the first and second channels. That is, before step 1020, the method may further include step 1040.

[0194] Optionally, at step 1040, the ED obtains configuration information, wherein the configuration information configures the reception of the first channel and the second channel.

[0195] It is worth noting that the ED can receive configuration information from functions (or points, devices, etc.) used for configuration in the communication system. In some implementations, the ED can receive configuration information from either the first TRP or the second TRP. For example, the TRP initially connected to the ED can send configuration information to the ED. This application does not limit this.

[0196] In some implementations, the configuration information may indicate one or more of the following: a first reference time, a first time window, a first correction time, a second correction time, a first correction time window, a second correction time window, and the position of the reference point. The configuration information may carry various parameters to configure reception on the first and second channels. One or more parameters may directly indicate the reception time (or time window), or the ED may derive the reception time (or time window) based on one or more parameters.

[0197] For example, the configuration information may include parameters indicating a first reference time, and the ED may receive a first channel and a second channel at the first reference time.

[0198] For example, the configuration information may include a parameter indicating reference time #1 and a parameter indicating the length of the first time window, and the ED may determine the first time window based on the reference time #1 and the length. For example, the first time window may be a time interval spanning half the length value before reference time #1 and half the length value after reference time #1.

[0199] For example, the configuration information may include parameters indicating reference time #1, parameters indicating time offset #1, and parameters indicating time offset #2. The ED can determine a first correction time based on reference time #1 and time offset #1, and determine a second correction time based on reference time #2.

[0200] For example, the configuration information may include parameters indicating reference time #1, parameters indicating time offset #1, parameters indicating time offset #2, and parameters indicating the length of the time window. The ED can determine a first correction time window based on reference time #1, time offset #1, and the time window length. For example, the first correction time window may be the time interval between half the time window length value before the reference time #1 plus time offset #1 and half the time window length value after the reference plus time offset #1. Similarly, the ED can determine a second correction time window based on reference time #1, time offset #2, and the time window length. It is worth noting that the time window lengths of the first and second correction time windows can be the same or different. When they are different, the configuration information may include parameters indicating different lengths respectively. This application does not limit this.

[0201] The above examples are for illustrative purposes only, and this application does not exclude other possible implementations. For example, referring to the parameter indicating reference time #1 in the above examples, this parameter can be replaced with a parameter indicating the location of the reference point. The ED can determine reference time #1 based on the location of the reference point. This application does not limit this.

[0202] In some implementations, the ED can report its Global Navigation Satellite System (GNSS) capabilities to the network (e.g., a first TRP or a second TRP). The network can determine configuration information based on the GNSS capabilities. For example, if the ED has GNSS capabilities, the configuration information may include the location of a reference point. The ED can determine the remaining time based on its own location (from its GNSS capabilities) and the location of the reference point. If the ED does not have GNSS capabilities, the configuration information may include a remaining time configuration. This application does not limit this.

[0203] In some implementations, the ED can indicate in its ED capability report the maximum time-domain offset it can support for a PDCCH time window. The maximum time-domain offset can be represented as an integer number of OFDM symbols, microslots, slots, etc. Alternatively, the maximum time-domain offset can be represented as an integer number of time intervals Tc, where the time unit can be, for example, seconds, milliseconds, microseconds, or nanoseconds, and Tc is defined as Tc = 1 / (Δfmax.Nf), where Δfmax = 480000 Hz and Nf = 4096. The network can configure the ED such that the PDCCH time window has a time interval less than or equal to the maximum offset supported by the ED.

[0204] In some implementations, the ED can indicate in its ED capability report the maximum time-domain offset it can support for a PDSCH time window. The maximum time-domain offset can be represented as an integer number of OFDM symbols, microslots, slots, etc. Alternatively, the maximum time-domain offset can be represented as an integer number of given time units Tc, where the time unit can be, for example, seconds, milliseconds, microseconds, nanoseconds, where Tc is defined as Tc = 1 / (Δfmax.Nf), where Δfmax = 480000 Hz and Nf = 4096. The network can configure the ED such that the PDSCH time window has a time interval less than or equal to the maximum offset supported by the ED.

[0205] In some implementations, the ED can indicate in its ED capability report the maximum number of PDCCH and / or PDSCH transmissions that the ED can monitor / detect / decode in parallel. The network can configure the ED such that the number of PDCCH and / or PDSCH transmissions that the ED can monitor / detect / decode is less than or equal to the maximum number of PDCCH and / or PDSCH transmissions supported by the ED.

[0206] When the first channel includes PDCCH and / or PDSCH, and the second channel includes PDCCH and / or PDSCH, the configuration information may include one or more parameters related to the control resource set (CORESET).

[0207] In some implementations, the ED can be used to monitor / detect / decode one or more PDCCH transmissions, wherein the one or more PDCCH transmissions are associated with one or more control resource sets (CORESETs). Each CORESET can use, for example, higher-level parameters. coresetIdentity To identify, and different PDCCH transmissions from different NT-TRPs can be linked with higher-layer parameters. coresetIdentity Different values ​​are associated with each PDCCH transmission. Each corresponding PDSCH transmission can schedule a corresponding PDSCH transmission. In other words, the configuration information can indicate the CORESET associated with the first and second channels, and the ED can monitor, detect, or decode the first and second channels based on the indicated CORESET.

[0208] Furthermore, the ED is provided with higher-level parameters related to the PDCCH and PDSCH configurations, and these parameters ensure that each PDCCH configuration is associated with a corresponding BAI assumption. This allows the ED to detect and decode PDCCHs using beams associated with different BAIs, where the PDCCHs originate from different NT-TRPs. If the NT-TRPs can coordinate, the more distant NT-TRPs will transmit their PDCCHs and PDSCHs immediately, while the closer NT-TRPs will transmit theirs with a delay.

[0209] In some implementations, ED can be used to monitor / detect / decode one or more PDCCH transmissions, wherein the one or more PDCCH transmissions are associated with one or more service BAIs. Each service BAI can use, for example, higher-level parameters. bai To identify. Different PDCCH transmissions from different NT-TRPs can be linked with higher-layer parameters. bai Different values ​​are associated with each PDCCH transmission. Each corresponding PDSCH transmission can schedule a corresponding PDSCH transmission. In other words, the configuration information can indicate the BAI associated with the first and second channels, and the ED can monitor, detect, or decode the first and second channels based on the indicated BAI.

[0210] In some implementations, ED can be configured with higher-level parameters. pdcchTimeWindow and / or pdschTimeWindow Multiple values. High-level parameters. pdcchTimeWindow and / or pdschTimeWindow The multiple values ​​can be, for example, two or more integers. ED can monitor, detect, or decode the first and second channels within the time window indicated by the above parameters.

[0211] In some implementations, ED can be configured with higher-level parameters. pdcchTimeWindow and coresetIdentity High-level parameters pdcchTimeWindow Portable and compatible coresetIdentity The first value associated with the first value, and the higher-level parameters pdcchTimeWindow Portable and compatible coresetIdentity The second value is associated with the second value. ED can monitor, detect, or decode the first and second channels within the time window indicated by the above parameters.

[0212] In some implementations, ED can be configured with higher-level parameters. pdschTimeWindow and coresetIdentity High-level parameters pdschTimeWindow Portable and compatible coresetIdentity The first value associated with the first value, and the higher-level parameters pdschTimeWindow Portable and compatible coresetIdentityThe second value is associated with the second value. ED can monitor, detect, or decode the first and second channels within the time window indicated by the above parameters.

[0213] In some implementations, ED can be configured with higher-level parameters. pdcchTimeWindow and servingZenithBaiList High-level parameters pdcchTimeWindow Portable and compatible bai The first value associated with the first value, and the higher-level parameters pdcchTimeWindow Portable and compatible bai The second value is associated with the second value. ED can monitor, detect, or decode the first and second channels within the time window indicated by the above parameters.

[0214] In some implementations, ED can be configured with higher-level parameters. pdschTimeWindow and servingZenithBaiList High-level parameters pdcchTimeWindow Portable and compatible bai The first value associated with the first value, and the higher-level parameters pdschTimeWindow Portable and compatible bai The second value is associated with the second value. ED can monitor, detect, or decode the first and second channels within the time window indicated by the above parameters.

[0215] In some implementations, ED can be configured with higher-level parameters. pdcchTimeCorrection and coresetIdentity High-level parameters pdcchTimeCorrection Portable and compatible coresetIdentity The first value associated with the first value, and the higher-level parameters pdcchTimeCorrection Portable and compatible coresetIdentity The second value is associated with the second value. ED can monitor, detect, or decode the first and second channels within the time or time window indicated by the above parameters.

[0216] In some implementations, ED can be configured with higher-level parameters. pdcchTimeCorrection and servingZenithBaiList High-level parameters pdcchTimeCorrection Portable and compatible bai The first value associated with the first value, and the higher-level parameters pdcchTimeCorrection Portable and compatible bai The second value is associated with the second value. ED can monitor, detect, or decode the first and second channels within the time or time window indicated by the above parameters.

[0217] According to the above technical solution, the first TRP and the second TRP transmit the first channel and the second channel to the same ED at different transmission times rather than simultaneously, wherein at least one of the first TRP and the second TRP is a non-terrestrial TRP. This helps reduce the complexity of the ED receiving channels from different TRPs in the NTN system.

[0218] To facilitate understanding of the embodiments of this application, and for illustrative purposes, the following are combined with... Figures 11 to 15 Some detailed examples are given. The first channel includes the PDCCH, i.e., PDCCH#2 transmitted by the closer NT-TRP in the example below. The second channel includes the PDCCH, i.e., PDCCH#1 transmitted by the farther NT-TRP in the example below. PDCCH#2 schedules PDSCH#2 and can be considered as part of the first channel or a channel independent of the first channel. Similarly, PDCCH#1 schedules PDSCH#1 and can be considered as part of the second channel or a channel independent of the second channel. The PDCCH / PDSCH time window, PDCCH / PDSCH reference time (or time reference), and time correction in the example below can correspond to the reception time (or time window) of the first and second channels described above.

[0219] Figure 11 An example of an ED-centric transmission according to an embodiment of this application is shown. In this example, both the first TRP and the second TRP are NT-TRPs, with the more distant TRP denoted as NT-TRP#1 and the closer TRP denoted as NT-TRP#2. Both the first and second channels are PDCCHs, with the PDCCH from NT-TRP#1 denoted as PDCCH#1 and the PDCCH from NT-TRP#2 denoted as PDCCH#2. PDCCH#1 and PDCCH#2 can schedule PDSCHs, where the scheduled PDSCHs are denoted as PDSCH#1 and PDSCH#2, respectively.

[0220] See Figure 11 NT-TRP#1 is a more distant NT-TRP, while NT-TRP#2 is a closer NT-TRP (i.e., the distance between NT-TRP#1 and the ED is greater than the distance between NT-TRP#2 and the ED). NT-TRP#2 can coordinate with NT-TRP#1 using, for example, a laser-based inter-satellite link (L-ISL) and exchange return information (e.g., first information), which may include PDCCH delay.

[0221] NT-TRP#1 is a more distant TRP that can send scheduled PDSCH transmissions to EDs on the ground. PDCCH transmissions can begin at the dashed lines depicting the scheduling slot boundaries; the time corresponding to the scheduling slot boundaries can be determined using higher-layer parameters. schedulingSlotApplicationTime The higher-level parameters can be identified by the return information. In one possible implementation, NT-TRP#1 sends the return information, and NT-TRP#2 receives the return information from NT-TRP#1. The information indicates which EDs can be scheduled using NC-JT.

[0222] In one possible implementation, the pdcchTimeDelay and pdschTimeDelay It can be a parameter for the delay of PDCCH and PDSCH transmission (e.g., TimeDelay).

[0223] NT-TRP#2 can schedule and send PDCCH transmissions to the same ED on the ground, scheduling PDSCH transmissions. NT-TRP#2 can adjust its PDCCH transmission delay according to higher-layer parameters. pdcchTimeDelay Given the time, the higher-layer parameters can be provided by the first information. Similarly, NT-TRP#2 can determine its PDSCH transmission delay by the higher-layer parameters. pdschTimeDelay Given the time, the higher-level parameters can be provided by the returned information. This can be selected. pdcchTimeDelay and / or pdschTimeDelay The value of allows PDCCH and / or PDSCH transmissions from both NT-TPRs to arrive simultaneously from the perspective of ED.

[0224] Assume that the ground-based ED can monitor PDCCH transmissions from different NT-TRPs, i.e., PDCCH transmissions from different zenith angles. Similarly, assume that the ED can detect and decode PDSCH transmissions from different NT-TRPs. Through coordination between NT-TRP#1 and NT-TRP#2, the ED receives, detects, and decodes PDCCH and PDSCH transmissions from NT-TRP#1 and NT-TRP#2, respectively. Each PDCCH and PDSCH transmission is perceived by the ED as arriving simultaneously, even if the corresponding PDCCH and PDSCH transmissions from NT-TRP#1 and NT-TRP#2 have traveled different propagation distances.

[0225] This ED-centric PDCCH / PDSCH reception configuration may have several advantages. It allows the ED to use only a single synchronization circuit, enabling the ED to maintain a time reference (i.e., reference time #1), thereby helping to minimize receiver complexity on the ED side. Note that "ED-centric" in this embodiment can refer to the network side (e.g., different NT-TRPs) being able to adjust / coordinate its behavior (e.g., PDCCH / PDSCH transmission delay) to simplify ED operation.

[0226] In such Figure 12 Another possible implementation shown introduces the characteristics of PDCCH / PDSCH reception centered on the anchor point, specifically explaining the concept of PDCCH / PDSCH time windows. Note that the PDCCH / PDSCH time window scheme can be implemented based on the aforementioned PDCCH / PDSCH delay scheme, or it can be implemented independently.

[0227] Figure 12 A first example of anchor-centric transmission according to an embodiment of this application is shown.

[0228] like Figure 12 As shown, assume NT-TRP#1 is a more distant TRP and can send PDCCHs to the ED on the ground, scheduling PDSCH transmissions. PDCCH transmissions can begin at the dashed lines depicting the scheduling slot boundaries; the time corresponding to the scheduling slot boundaries can be determined using higher-layer parameters. schedulingSlotApplicationTime The higher-layer parameters can be identified by backhaul information (e.g., first information). Assume NT-TRP#2 receives backhaul signaling from NT-TRP#1, indicating which EDs can be scheduled using NC-JT.

[0229] NT-TRP#2 can schedule and send PDCCH transmissions to the same ED on the ground, scheduling PDSCH transmissions. NT-TRP#2 can adjust its PDCCH transmission delay according to higher-layer parameters. pdcchTimeDelay Given the time, the higher-layer parameters can be provided by the return signaling. Similarly, NT-TRP#2 can provide its PDSCH transmission delay by the higher-layer parameters. pdschTimeDelay The higher-level parameters can be provided by backhaul signaling at the given time.

[0230] NT-TRP#1 and NT-TRP#2 can select high-level parameters. pdcchTimeDelay and / or pdschTimeDelay The value of causes the PDCCH and / or PDSCH transmissions to arrive at the so-called "anchor position" simultaneously.

[0231] Assume that the ground-based ED can monitor PDCCH transmissions from different NT-TRPs, i.e., PDCCH transmissions from different zenith angles. Similarly, assume that the ED can detect and decode PDSCH transmissions from different NT-TRPs. Through the coordination of NT-TRP#1 and NT-TRP#2, the ED receives, detects, and decodes PDCCH and PDSCH transmissions from NT-TRP#1 and NT-TRP#2, respectively.

[0232] If the ED on the ground is not at the precise location of the anchor point, there may be a time difference in the time when the ED actually receives a given PDCCH or PDSCH transmission. If the ED maintains its time reference assumptions such that it matches the time reference at the anchor point location, the network can provide the ED with higher-layer signaling, such as providing a time offset, so that the ED applies the offset to the downlink time it acquires during, for example, initial access by detecting, for example, SS / PBCH blocks. Higher-layer parameters, for example, can be used. dlTimingOfffset The network provides a time offset to the ED, and the value of the higher-layer parameters can be given as a positive integer value in the form of, for example, OFDM symbol number, microslot number, slot number, or some other time unit (e.g., second, millisecond, microsecond, nanosecond, etc.). This downlink time offset can be calculated by the network using, for example, the coordinates of the ED, which can be obtained through, for example, positioning, and then sent to the ED using, for example, RRC signaling. The ED can obtain its downlink time by detecting synchronization signals (e.g., SS / PBCH blocks), and then the network can provide the higher-layer parameters to the ED. dlTimingOffset This causes the ED to update its acquired downlink time, thereby matching the downlink time to, for example, the time closest to the anchor position of the ED.

[0233] Using PDCCH / PDSCH time windows to implement anchor-centric PDCCH / PDSCH reception may have several advantages. Using PDCCH / PDSCH time windows can reduce implementation complexity on the network, while providing an ED with a window within which the ED can receive PDCCH / PDSCH transmissions from the network.

[0234] Figure 13 Details of a first example of an embodiment according to this application are shown.

[0235] As an example, higher-level parameters can be provided to the ED, such as pdcchTimeWindow and / or pdschTimeWindow As described below: servingConfig = { pdcchTimeWindow = 14ofdmSymbols, pdschTimeWindow = 14ofdmSymbols } If high-level parameters are provided to ED pdcchTimeWindow Therefore, it can be expected that the ED will monitor PDCCH transmission within a time window surrounding its downlink time reference. Higher layer parameters pdcchTimeWindow It can be given as a positive integer value in the form of, for example, OFDM symbol number, microslot number, slot number, or some other time unit (e.g., second, millisecond, microsecond, nanosecond, etc.).

[0236] In one example, the corresponding time window can be inferred from the ED as the downlink time reference across the ED. pdcchTimeWindow Half the value and the downlink time of ED are referenced later. pdcchTimeWindow The time interval is half the value.

[0237] Similarly, if high-level parameters are provided to the ED pdschTimeWindow Therefore, it can be expected that the ED will monitor PDSCH transmission within a time window surrounding its downlink time reference. Higher layer parameters pdschTimeWindow It can be given as a positive integer value in the form of, for example, OFDM symbol number, microslot number, slot number, or some other time unit (e.g., second, millisecond, microsecond, nanosecond, etc.).

[0238] In one example, the corresponding time window can be inferred from the ED as the downlink time reference across the ED. pdcchTimeWindow Half the value and the downlink time of ED are referenced later. pdschTimeWindow The time interval is half the value. For example, if the value provided to ED pdcchTimeWindow Setting it to the value "14ofdmSymbols" allows the ED to monitor PDCCH transmissions within a time window of 7 OFDM symbols before and after its downlink time reference. The time interval before its downlink time reference can correspond to, for example, -7 OFDM symbols, while the time interval after its downlink time reference can correspond to, for example, +7 OFDM symbols.

[0239] If high-level parameters are provided to ED pdcchTimeWindow Therefore, it can be expected that the ED will be around the downlink time reference it obtains through the initial access procedure. pdcchTimeWindow The ED monitors / detects / decodes PDCCH transmissions within the indicated time window. The ED can update its downlink time reference accordingly to correctly detect and decode PDCCH transmissions.

[0240] If high-level parameters are not provided to ED pdcchTimeWindow However, it provides higher-level parameters. dlTimingOffset Therefore, it can be expected that the ED will use the downlink time reference of the anchor location (i.e., the downlink time reference it obtains through the initial access procedure plus the time reference obtained by the anchor location).dlTimingOffset The ED (Indicated Time Offset) is used to monitor / detect / decode PDCCH transmissions. The ED can update its downlink time reference accordingly to correctly detect and decode PDCCH transmissions.

[0241] If high-level parameters are provided to ED pdcchTimeWindow and dlTimingOffset Therefore, it can be expected that the ED will use the downlink time reference obtained through the initial access procedure (i.e., the downlink time reference obtained through the initial access procedure plus the time reference obtained through the initial access procedure). dlTimingOffset The indicated time offset) is surrounded by pdcchTimeWindow The ED monitors / detects / decodes PDCCH transmissions within the indicated time window. The ED can update its downlink time reference accordingly to correctly detect and decode PDCCH transmissions.

[0242] If high-level parameters are not provided to ED pdcchTimeWindow And no high-level parameters were provided. dlTimingOffset Therefore, it can be expected that the ED will use its downlink time reference obtained through the initial access procedure to monitor / detect / decode PDCCH transmissions.

[0243] If high-level parameters are provided to ED pdschTimeWindow Therefore, it can be expected that the ED will be around the downlink time reference it obtains through the initial access procedure. pdschTimeWindow The ED monitors / detects / decodes PDSCH transmissions within the indicated time window. The ED can update its downlink time reference accordingly to correctly detect and decode PDSCH transmissions.

[0244] If high-level parameters are not provided to ED pdschTimeWindow However, it provides higher-level parameters. dlTimingOffset Therefore, it can be expected that the ED will use the downlink time reference of the anchor location (i.e., the downlink time reference it obtains through the initial access procedure plus the time reference obtained by the anchor location). dlTimingOffset (Indicated time offset) Monitor / detect / decode PDSCH transmissions. The ED can update its downlink time reference accordingly to correctly detect and decode PDSCH transmissions.

[0245] If high-level parameters are provided to ED pdschTimeWindow and dlTimingOffset Therefore, it can be expected that the ED will use the downlink time reference obtained through the initial access procedure (i.e., the downlink time reference obtained through the initial access procedure plus the time reference obtained through the initial access procedure). dlTimingOffset The indicated time offset) is surrounded by pdschTimeWindow The ED monitors / detects / decodes PDSCH transmissions within the indicated time window. The ED can update its downlink time reference accordingly to correctly detect and decode PDSCH transmissions.

[0246] If high-level parameters are not provided to EDpdschTimeWindow And no high-level parameters were provided. dlTimingOffset Therefore, it can be expected that the ED will use its downlink time reference obtained through the initial access procedure to monitor / detect / decode PDSCH transmissions.

[0247] Please note that the downlink time reference in this invention can also be referred to as downlink reference time.

[0248] This anchor-centric PDCCH / PDSCH reception configuration may have several advantages. It allows for reduced network implementation complexity by aligning the PDCCH / PDSCH transmission time to a given anchor location on the ground, rather than the precise ED location (which may not always be known with sufficient accuracy, or there may be too many EDs on the ground, making ED-centric compensation for PDCCH / PDSCH transmission time computationally infeasible). The burden of maintaining proper time synchronization of PDCCH / PDSCH transmissions (with respect to EDs on the ground) can then be more evenly distributed between the network and the EDs.

[0249] In another possible implementation, the characteristics of PDCCH / PDSCH receive time correction are introduced, specifically outlining the concept of PDCCH / PDSCH time correction. Note that the PDCCH / PDSCH time window scheme can be implemented based on the aforementioned PDCCH / PDSCH delay scheme, or it can be implemented independently.

[0250] Using PDCCH / PDSCH time correction for multi-PDCCH / PDSCH reception may have several advantages. Using PDCCH / PDSCH time correction allows the ED to reduce complexity in blindly monitoring / detecting / decoding PDCCH / PDSCH transmissions from the network.

[0251] Figure 14 A second example of anchor-centric transmission according to an embodiment of this application is shown.

[0252] In another possible implementation, the characteristics of PDCCH / PDSCH receive time correction are introduced, specifically outlining the concept of PDCCH / PDSCH time correction. Note that the PDCCH / PDSCH time window scheme can be implemented based on the aforementioned PDCCH / PDSCH delay scheme, or it can be implemented independently.

[0253] like Figure 14 As shown, assume NT-TRP#1 is a more distant TRP and can send PDCCHs to the ED on the ground, scheduling PDSCH transmissions. PDCCH transmissions can begin at the dashed lines depicting the scheduling slot boundaries; the time corresponding to the scheduling slot boundaries can be determined using higher-layer parameters. schedulingSlotApplicationTimeThe higher-level parameters can be provided by the feedback information. NT-TRP#2 receives feedback information from NT-TRP#1, which indicates which EDs can be scheduled using NC-JT.

[0254] NT-TRP#2 can schedule and send PDCCH transmissions to the same ED on the ground, scheduling PDSCH transmissions. NT-TRP#2 can adjust its PDCCH transmission delay according to higher-layer parameters. pdcchTimeDelay Given the time, the higher-layer parameters can be provided by the return information. Similarly, NT-TRP#2 can provide its PDSCH transmission delay by the higher-layer parameters. pdschTimeDelay The given timeframe can be provided by the backhaul information.

[0255] NT-TRP#1 and NT-TRP#2 can select high-level parameters. pdcchTimeDelay and / or pdschTimeDelay The value of causes the PDCCH and / or PDSCH transmissions to arrive at the so-called "anchor position" simultaneously.

[0256] Assume that the ground-based ED can monitor PDCCH transmissions from different NT-TRPs, i.e., PDCCH transmissions from different zenith angles. Similarly, assume that the ED can detect and decode PDSCH transmissions from different NT-TRPs. Through the coordination of NT-TRP#1 and NT-TRP#2, the ED receives, detects, and decodes PDCCH and PDSCH transmissions from NT-TRP#1 and NT-TRP#2, respectively.

[0257] If the ED on the ground may not be at the precise location of the anchor point, there may be a time difference in the time when the ED actually receives a given PDCCH or PDSCH transmission. Assuming the ED maintains its time reference assumptions such that it matches the time reference at the anchor point location, the network provides the ED with higher-layer signaling, which, for example, provides a time offset, such that the ED applies the offset to the downlink time it acquires during, for example, initial access by detecting, e.g., SS / PBCH blocks. Higher-layer parameters, for example, can be used. dlTimingOfffset The time offset is provided to the ED, and the value of the higher-level parameter can be given as a positive integer value in the form of, for example, the number of OFDM symbols, the number of microslots, the number of slots, or some other time unit (e.g., seconds, milliseconds, microseconds, nanoseconds, etc.).

[0258] Figure 15 Details of a second example of an embodiment according to this application are shown.

[0259] As an example, higher-level parameters can be provided to the ED, such as pdcchTimeWindow , pdschTimeWindow and pdcchTimeCorrection As described below: servingConfig = { pdcchTimeWindow = 14ofdmSymbols, pdschTimeWindow = 14ofdmSymbols, pdcchTimeCorrection = {-9ofdmSymbols, 6ofdmSymbols} } If high-level parameters are provided to ED pdcchTimeWindow Therefore, it can be expected that the ED will monitor PDCCH transmission within a time window surrounding the downlink time reference it obtains during the initial access procedure. Higher layer parameters pdcchTimeWindow It can be given as a positive integer value in the form of, for example, OFDM symbol number, microslot number, slot number, or some other time unit (e.g., second, millisecond, microsecond, nanosecond, etc.).

[0260] In one example, the corresponding time window can be inferred from the ED as the downlink time reference across the ED. pdcchTimeWindow Half the value and the downlink time of ED are referenced later. pdcchTimeWindow The time interval is half the value.

[0261] Similarly, if high-level parameters are provided to the ED pdschTimeWindow Therefore, it can be expected that the ED will monitor PDSCH transmission within a time window surrounding the downlink time reference it obtains during the initial access procedure. Higher layer parameters pdschTimeWindow It can be given as a positive integer value in the form of, for example, OFDM symbol number, microslot number, slot number, or some other time unit (e.g., second, millisecond, microsecond, nanosecond, etc.).

[0262] If high-level parameters are provided to ED pdcchTimeWindow and high-level parameters pdcchTimeCorrection The first value (e.g., -9ofdmSymbols) can then be used to predict that ED will be applied by pdcchTimeCorrection The first value provides time correction to monitor / detect / decode the first PDCCH transmission within a time window surrounding its downlink time reference.

[0263] If high-level parameters are provided to ED pdcchTimeWindow and high-level parameters pdcchTimeCorrection The second value (e.g., 6ofdmSymbols) can then be used to predict that ED will be applied by pdcchTimeCorrection The second value provides time correction to monitor / detect / decode the second PDCCH transmission within a time window surrounding its downlink time reference.

[0264] exist Figure 15In the example shown above, ED can be used as... dlTimingReference + dlTimingOffset + pdcchTimeCorrection The first PDCCH of the obtained downlink time monitoring / detection / decoding schedule first PDSCH, where pdcchTimeCorrection Corresponding to high-level parameters pdcchTimeCorrection The first value of ED. dlTimingReference + dlTimingOffset + pdcchTimeCorrection The obtained downlink time monitoring / detection / decoding schedules the second PDSCH and the second PDCCH, where pdcchTimeCorrection Corresponding to high-level parameters pdcchTimeCorrection The second value. Other implementation methods and ED behaviors can be considered.

[0265] In some implementations, PDCCH time correction can be provided by higher-layer signaling (e.g., RRC). In other implementations, PDCCH time correction can be semi-statically indicated to the ED using, for example, the MAC-CE command.

[0266] This configuration of PDCCH time correction may have several advantages. It can reduce the complexity of ED implementation by directly aligning the downlink time reference to the correct value, rather than blindly monitoring the possible position of the PDCCH within the PDCCH time window.

[0267] The above text combined Figures 10 to 15 The method according to embodiments of this application is described in detail below. (The following is in conjunction with...) Figure 16 and Figure 17 The apparatus provided in the embodiments of this application has been described in detail. The description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, any content not described in detail can be referred to the above method embodiments. For the sake of brevity, details will not be repeated herein.

[0268] refer to Figure 16 This diagram illustrates a schematic block diagram of a communication device according to an embodiment of the present application. The communication device 10 includes a transceiver unit 11 and a processing unit 12. The transceiver unit 11 can implement corresponding communication functions, and the processing unit 11 is used to perform data processing. The transceiver unit 11 can also be referred to as a communication interface or a communication unit.

[0269] In some implementations, the communication device 10 may further include a storage unit. The storage unit may be used to store instructions and / or data. The processing unit 12 may read the instructions and / or data from the storage unit to enable the communication device to implement the method embodiments described above.

[0270] The communication device 10 can be used to perform the actions performed by the ED in the above method embodiments. In this case, the communication device 10 can be the ED or a component that can be configured in the ED. The transceiver unit 11 is used to perform communication-related (e.g., receive / transmit related) operations on the ED side in the above method embodiments. The processing unit 12 is used to perform processing-related operations on the ED side in the above method embodiments.

[0271] Communication device 10 can implement the embodiments according to this application. Figures 10 to 15 The steps or processes performed by the ED. The communication device 10 may include methods for performing... Figures 10 to 15 The unit is the one that executes the method by the ED. Furthermore, each unit in the communication device 10 and the other operations and / or functions described above are used to implement... Figures 10 to 15 The corresponding process in the text.

[0272] Alternatively, the communication device 10 can be used to perform the actions performed by the first NT-TRP in the above method embodiments. In this case, the communication device 10 can be the first NT-TRP or a component that can be configured in the first NT-TRP. The transceiver unit 11 is used to perform communication-related (e.g., receive / transmit related) operations on the first NT-TRP side in the above method embodiments. The processing unit 12 is used to perform processing-related operations on the first NT-TRP side in the above method embodiments.

[0273] Communication device 10 can implement the embodiments according to this application. Figures 10 to 15 The steps or processes performed by the first NT-TRP. Communication device 10 may include methods for performing... Figures 10 to 15 The unit is the one that executes the method by the first NT-TRP. Furthermore, each unit in the communication device 10 and the other operations and / or functions described above are used to implement... Figures 10 to 15 The corresponding process in the text.

[0274] The specific process by which the unit performs the corresponding steps described above is described in detail in the above method embodiments. For the sake of brevity, the details will not be repeated here.

[0275] refer to Figure 17 This diagram illustrates a schematic block diagram of another communication device according to an embodiment of this application. The communication device 20 includes a processor 21. The processor 21 is coupled to a memory 22. The memory 22 is used to store computer programs or instructions and / or data. The processor 21 is used to execute the computer programs or instructions and / or data stored in the memory 22 to perform the methods described in the above method embodiments.

[0276] In some embodiments, the communication device 20 includes one or more processors 21.

[0277] In one example, such as Figure 17As shown, the communication device 20 may also include a memory 22.

[0278] In some embodiments, the communication device 20 may include one or more memories 22.

[0279] In one example, memory 22 may be integrated with processor 21 or arranged separately from processor 21.

[0280] In one example, such as Figure 17 As shown, the communication device 20 may further include a transceiver 23, wherein the transceiver 23 is used to receive and / or transmit signals. For example, the processor 21 may be used to control the transceiver 23 to receive and / or transmit signals.

[0281] In some embodiments, the communication device 20 may be an ED or a component that can be configured in the ED (e.g., a chip, circuit, or processing system); or the communication device 20 may be a first NT-TRP or a component that can be configured in the first NT-TRP (e.g., a chip, circuit, or processing system).

[0282] In one embodiment, the communication device 20 is used to perform the operations performed by the ED in the above method embodiments.

[0283] For example, processor 21 can be used to perform processing-related operations performed by ED in the above method embodiments, and transceiver 23 can be used to perform communication-related (e.g., receive / transmit related) operations performed by ED in the above method embodiments.

[0284] In another embodiment, the communication device 20 is used to perform the operations performed by the first NT-TRP in the above method embodiment.

[0285] For example, processor 21 can be used to perform processing-related operations performed by the first NT-TRP in the above method embodiments, and transceiver 23 can be used to perform communication-related (e.g., receive / transmit related) operations performed by the first NT-TRP in the above method embodiments.

[0286] In some aspects of the invention, a device / chipset system is provided, including components (e.g., at least one processor) for implementing a method implemented by (or at the ED of the invention) of the present invention. The device / chipset system may be the ED (i.e., a terminal device) or a module / component within the ED. Specifically, the at least one processor may execute instructions stored in a computer-readable medium to implement the method.

[0287] In some aspects of the invention, a device / chipset system is provided, including components (e.g., at least one processor) for implementing a method by a first NT-TRP (e.g., a satellite) of the invention (or implemented at the first NT-TRP (e.g., a satellite) of the invention). The device / chipset system may be the first NT-TRP or a module / component within the first NT-TRP. Specifically, the at least one processor may execute instructions stored in a computer-readable medium to implement the method.

[0288] In some aspects of the invention, a system is provided comprising at least one of a device in the ED of the invention (or at the ED of the invention) or a device in the first NT-TRP of the invention (or at the first NT-TRP of the invention).

[0289] In some aspects of the invention, a method is provided performed by a system comprising at least one of a device in the ED of the invention (or at the ED of the invention) or a device in the first NT-TRP of the invention (or at the first NT-TRP of the invention).

[0290] In some aspects of the invention, a computer program comprising instructions is provided. When executed by a processor, the instructions enable the processor to implement the method of the invention.

[0291] In some aspects of the invention, a non-transitory computer-readable medium is provided that stores instructions which, when executed by a processor, enable the processor to implement the method of the invention.

[0292] Embodiments of this application also provide a computer-readable storage medium. The computer-readable storage medium stores computer instructions for implementing the method executed by the ED or by the first NT-TRP in the above method embodiments.

[0293] For example, when the computer program is executed by a computer, it can enable the computer to implement the method executed by the ED or the method executed by the first NT-TRP in the above method embodiments.

[0294] Embodiments of this application also provide a computer program product including instructions. When the instructions are executed by a computer, the computer is able to implement the method executed by the ED or the method executed by the first NT-TRP in the above method embodiments.

[0295] For an explanation of the relevant content and beneficial effects of any communication device provided above, please refer to the corresponding method embodiments provided above. Details will not be repeated herein.

[0296] The processor mentioned in the embodiments of this application may be a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gates, transistor logic devices, or discrete hardware components. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor.

[0297] It should be understood that any module, component, or device disclosing executable instructions herein may include or otherwise access a non-transitory computer / processor-readable storage medium for storing information such as computer / processor-readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer / processor-readable storage media includes magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, compact discread-only memory (CD-ROM), digital video disc or digital versatile disc (i.e., DVD), Blu-ray disc™ and other optical discs, or other optical storage; volatile and non-volatile, removable and non-removable media implemented in any method or technology; random-access memory (RAM); read-only memory (ROM); electrically erasable programmable read-only memory (EEPROM); flash memory or other memory technologies. Any such non-transitory computer / processor-readable storage medium may be part of a device or apparatus, or may be accessed or connected to a device or apparatus. Computer / processor-readable / executable instructions used to implement the methods, applications, or modules described herein may be stored by such non-transitory computer / processor-readable storage media or otherwise preserved.

[0298] It should be noted that the message in this invention can be replaced with information, which can be carried in a single message or in more than one single message.

[0299] Unless otherwise specified, the terms "apparatus" and "device" are used interchangeably, as are the terms "identifier" and "identifier". The terms "system" and "network" are used interchangeably in the embodiments of this application.

[0300] In this invention, when used in conjunction with the terms "comprising" or "including" in the claims and / or specification, the word "a" or "an" may refer to "one," but it also has the same meaning as "one or more," "at least one," and "one or more," unless explicitly stated otherwise. Similarly, the word "another" may refer to at least a second or more, unless explicitly stated otherwise.

[0301] In this invention, when used before the same term (e.g., ED or operational step), the terms "first," "second," etc., do not imply an order or sequence of the terms. For example, unless otherwise specified, "first ED" and "second ED" refer to two different EDs; similarly, unless otherwise specified, "first step" and "second step" refer to two different operational steps, but this does not mean that the first step must occur before the second step. The actual order depends on the logical relationship between the two steps.

[0302] The terms “coupled” or “connected” as used herein can have several different meanings depending on the context in which they are used. For example, the terms “coupled” or “connected” as used herein can indicate that two elements or devices are directly connected to each other or connected to each other via one or more intermediate elements or devices through mechanical elements, depending on the specific context.

[0303] It should be noted that the expression "at least one of A or B" as used herein is interchangeable with the expression "A and / or B". This refers to a list from which A, or B, or both A and B can be selected. Similarly, the expression "at least one of A, B, or C" as used herein is interchangeable with "A and / or B and / or C" or "A, B, and / or C". This expression refers to a list from which the following can be selected: A or B or C, or A and B, or A and C, or B and C, or all of A, B, and C. The same principle applies to longer lists with the same format.

[0304] This invention includes various embodiments, not only method embodiments but also other embodiments, such as apparatus embodiments and embodiments related to non-transitory computer-readable storage media. Embodiments may be combined individually or in combination with the features disclosed herein. Therefore, this application may take the form of a purely hardware embodiment, a purely software embodiment, or an embodiment combining software and hardware. Furthermore, this application may take the form of a computer program product implemented on one or more computer-readable storage media (including, but not limited to, disk storage and optical storage) including computer-readable program code.

[0305] This application is described in conjunction with flowcharts and / or block diagrams of the methods, apparatus (systems), and computer program products according to this application. It should be understood that computer program instructions can be used to implement each process and / or each block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or another programmable data processing device to generate a machine such that these instructions, executed by the processor of said computer or said other programmable data processing device, generate means for implementing a specific function in one or more processes in the flowcharts and / or one or more blocks in the block diagrams.

[0306] These computer program instructions may alternatively be stored in a computer-readable storage medium capable of instructing a computer or another programmable data processing device to operate in a particular manner, such that these instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means. The instruction means implement one or more processes in the flowchart and / or a specific function in one or more blocks of the block diagram.

[0307] These computer program instructions can alternatively be loaded onto a computer or another programmable data processing device to cause a series of operations and steps to be performed on the computer or the other programmable device, thereby generating a computer-implemented process. Therefore, these instructions, which execute on the computer or the other programmable device, provide steps for implementing one or more processes in the flowchart and / or one or more boxes in the block diagram to perform specific functions.

[0308] As used herein, the terms “receive,” “detect,” and “decode” can have several different meanings depending on the context in which they are used. For example, without specific indication, the term “receive” can indicate that information (e.g., DCI or MAC-CE, RRC signaling, or TB) has been successfully received by the receiving node, meaning that the receiving side correctly detected and decoded the information. In this scenario, “receive” can encompass both “detect” and “decode,” or can indicate the same meaning; for example, “receive paging” means that the paging was correctly decoded and successfully obtained, and correspondingly, “received paging” means that the receiving side did not detect and / or decode the paging. “Not received paging” means that the receiving side attempted to detect and / or decode the paging but was unsuccessful in obtaining it. The term “receive” can sometimes indicate that a signal has arrived at the receiving side, but this does not necessarily mean that the information in the signal has been correctly detected and decoded. The receiving side then needs to perform detection and decoding on the signal to obtain the information carried in it. In this scenario, “receive,” “detect,” and “decode” can indicate different processes at the receiving side for obtaining information.

[0309] While this invention has referenced illustrative embodiments, it is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention, will be apparent to those skilled in the art upon reference to this specification. When combining two or more embodiments, not all features of the embodiments to be combined are necessary for the combination.

[0310] Additionally or alternatively, features disclosed herein in the context of any particular embodiment may be implemented in other embodiments. For example, method embodiments may be implemented in apparatus, system, and / or computer program product embodiments. Furthermore, although embodiments have been described primarily in the context of methods and apparatus, other implementations are contemplated, for example, as instructions stored on one or more non-transitory computer-readable media. Such media may store programs or instructions to perform any of the various methods consistent with the present invention.

[0311] Those skilled in the art will recognize that, based on the examples described in the embodiments disclosed in this specification, the units and methods can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of protection of this application.

[0312] The above description is merely a specific implementation of this application and is not intended to limit the scope of protection of this application. Any variations or substitutions that are readily conceived by those skilled in the art within the scope of the technology disclosed in this application should fall within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims and the specification.

Claims

1. A communication method, characterized in that, The method is executed at the first transmit / receive point (TRP), including: Obtain (1010) a first transmission time of a first channel, wherein the first channel and a second channel are transmitted to an electronic device ED, the second channel is from a second TRP, the first transmission time is different from the second transmission time of the second channel, and at least one of the first TRP and the second TRP is a non-terrestrial TRP; The first channel is transmitted (1030) to the ED at the first transmission time.

2. The method according to claim 1, characterized in that, The first transmission time and the second transmission time are related to the position of the reference point.

3. The method according to claim 1 or 2, characterized in that, The delay between the first transmission time and the second transmission time is related to the reference point.

4. The method according to claim 2 or 3, characterized in that, The location of the reference point is the location of the ED, or the location of the reference point is the location of the anchor point.

5. The method according to any one of claims 1 to 4, characterized in that, The process of obtaining the first transmission time of the first channel includes: Receive first information from the second TRP, wherein the first information indicates the first transmission time.

6. The method according to claim 5, characterized in that, The first information indicates the time delay between the first transmission time and the second transmission time.

7. The method according to any one of claims 1 to 6, characterized in that, The first channel includes one or more of the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH), and the second channel includes one or more of the PDCCH and PDSCH.

8. The method according to any one of claims 1 to 7, characterized in that, The first channel and the second channel are duplicate channels.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Send configuration information, wherein the configuration information configures the reception of the first channel and the second channel.

10. A communication method, characterized in that, The method is performed at an electronic device ED, including: A first channel (1020, 1030) is received from a first transmit / receive point (TRP), and a second channel is received from a second TRP, wherein the first transmission time of the first channel is different from the second transmission time of the second channel, and at least one of the first TRP and the second TRP is a non-terrestrial TRP.

11. The method according to claim 10, characterized in that, The first transmission time and the second transmission time are related to the position of the reference point.

12. The method according to claim 10 or 11, characterized in that, The delay between the first transmission time and the second transmission time is related to the reference point.

13. The method according to claim 11 or 12, characterized in that, The location of the reference point is the location of the ED, or the location of the reference point is the location of the anchor point.

14. The method according to any one of claims 10 to 13, characterized in that, The receiving of the first channel and the second channel includes: The first channel and the second channel are received based on a first reference time; or The first channel and the second channel are received based on a first time window; or The first channel is received based on a first correction time, and the second channel is received based on a second correction time; or The first channel is received based on a first correction time window, and the second channel is received based on a second correction time window.

15. The method according to any one of claims 10 to 14, characterized in that, The method further includes: Receive configuration information, wherein the configuration information configures the reception of the first channel and the second channel.

16. The method according to claim 15, characterized in that, The configuration information indicates one or more of the following: the first reference time, the first time window, the first correction time, the second correction time, the first correction time window, the second correction time window, and the position of the reference point.

17. The method according to claim 15 or 16, characterized in that, The method further includes: Send capability information, wherein the capability information indicates the Global Navigation Satellite System (GNSS) capability, and the configuration information indicates the location of the reference point.

18. The method according to any one of claims 10 to 17, characterized in that, The first channel includes one or more of the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH), and the second channel includes one or more of the PDCCH and PDSCH.

19. The method according to any one of claims 10 to 18, characterized in that, The first channel and the second channel are duplicate channels.

20. A communication method, characterized in that, The method is executed at the second transmit / receive point (TRP), including: The second channel is transmitted (1020) at the second transmission time, wherein the first channel and the second channel are transmitted to the electronic device ED, the first channel comes from the first TRP, the second transmission time is different from the first transmission time of the first channel, and at least one of the first TRP and the second TRP is a non-terrestrial TRP.

21. The method according to claim 20, characterized in that, The first transmission time and the second transmission time are related to the position of the reference point.

22. The method according to claim 20 or 21, characterized in that, The time delay between the first transmission time and the second transmission time is related to the position of the reference point.

23. The method according to claim 21 or 22, characterized in that, The location of the reference point is the location of the ED, or the location of the reference point is the location of the anchor point.

24. The method according to any one of claims 20 to 23, characterized in that, The method further includes: Send a first message to the first TRP, wherein the first message indicates the first transmission time.

25. The method according to claim 24, characterized in that, The first information indicates the time delay between the first transmission time and the second transmission time.

26. The method according to any one of claims 20 to 25, characterized in that, The first channel includes one or more of the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH), and the second channel includes one or more of the PDCCH and PDSCH.

27. The method according to any one of claims 20 to 26, characterized in that, The first channel and the second channel are duplicate channels.

28. The method according to any one of claims 20 to 27, characterized in that, The method further includes: Send configuration information, wherein the configuration information configures the reception of the first channel and the second channel.

29. An apparatus, characterized in that, The device includes: one or more processors; A memory storing instructions that, when executed by the one or more processors, cause the apparatus to perform the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 19, or the method according to any one of claims 20 to 28.

30. An apparatus, characterized in that, Used to perform the method according to any one of claims 1 to 9, or to perform the method according to any one of claims 10 to 19, or to perform the method according to any one of claims 20 to 28.

31. The apparatus according to claim 30, characterized in that, The device includes one or more processors and interface circuits.

32. The apparatus according to claim 30, characterized in that, The interface circuit includes one or more transceivers.

33. A communication system, characterized in that, It includes a first transmit / receive point (TRP), an electronic device (ED), and a second TRP, wherein the first TRP performs the method according to any one of claims 1 to 9, the ED performs the method according to any one of claims 10 to 19, and the ED performs the method according to any one of claims 20 to 28.

34. A non-transitory computer-readable medium for storing instructions, characterized in that, The instructions cause the processor in the device to implement the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 19, or the method according to any one of claims 20 to 28.

35. A device, characterized in that, Used to perform the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 19, or the method according to any one of claims 20 to 28.

36. A processor, characterized in that, The instructions are used to execute the device to perform the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 19, or the method according to any one of claims 20 to 28.

37. An integrated circuit, characterized in that, Used to perform the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 19, or the method according to any one of claims 20 to 28.

38. A communication device, characterized in that, include: Transceiver unit, configured to perform the receiving step according to any one of claims 1 to 9; A processing unit for performing the processing steps according to any one of claims 1 to 9.

39. A communication device, characterized in that, It includes a transceiver unit for performing the receiving step according to any one of claims 10 to 19.

40. A communication device, characterized in that, It includes a transceiver unit for performing the receiving step according to any one of claims 20 to 28.

Images