Method and device for beam activation and switching, and computer readable storage medium
By working collaboratively between terminal devices and non-terrestrial network devices, and utilizing angle direction indication and beam association to dynamically manage beam activation and switching, the problem of communication quality degradation in non-terrestrial networks is solved, achieving efficient communication quality improvement.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- HUAWEI TECH CO LTD
- Filing Date
- 2024-02-27
- Publication Date
- 2026-04-28
AI Technical Summary
In non-terrestrial networks, existing technologies struggle to effectively manage beam activation and switching, leading to a decline in communication quality.
By working together between terminal devices and non-terrestrial network devices, and utilizing angle direction indication and beam association, beams can be dynamically activated or deactivated, beam steering and switching can be optimized, thereby improving link quality.
It improves the communication quality between terminal devices and non-terrestrial networks, reduces resource consumption, lowers power consumption, and enhances the flexibility and reliability of communication.
Smart Images

Figure CN121942233A_ABST
Abstract
Description
Cross-reference to related applications
[0001] This application claims the benefit and priority of U.S. Patent Application No. 63 / 588,159, filed October 5, 2023, the entire contents of which are incorporated herein by reference. Technical Field
[0002] Exemplary embodiments of this disclosure generally relate to the field of communications, and more particularly to methods, apparatus and computer-readable storage media for beam activation and switching. Background Technology
[0003] Wireless communication systems, such as fourth-generation (4G) systems (e.g., Long-Term Evolution (LTE) systems) and fifth-generation (5G) systems (e.g., New Radio (NR) systems), have been deployed to provide various types of applications, such as messaging, voice, video, and other data. Within NR, non-terrestrial networks (NTNs) are being developed, which can utilize space-based or airborne vehicles as base stations or relays to enable communication between different devices. The goal is to propose solutions within NTNs that can work in conjunction with terrestrial networks (TNs) to provide communication services at an acceptable cost (e.g., power consumption and / or complexity). Summary of the Invention
[0004] Overall, exemplary embodiments of this disclosure provide a scheme for beam activation and switching in terrestrial / non-terrestrial networks.
[0005] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description.
[0006] In a first aspect, a method performed by a terminal device is provided. The method includes: the terminal device acquiring an indication of at least one angular direction. The method further includes: transmitting signals with a non-terrestrial network (NTN) device using one of at least one beam associated with the at least one angular direction. In this way, the terminal device can communicate with the NTN device in that angular direction using the beam associated with one of the indicated angular directions. The terminal device can communicate with the NTN device in the non-terrestrial network for a limited time, rather than accessing the cell of an NTN device moving along a track, thereby improving the link quality with the NTN device in the non-terrestrial network.
[0007] In some implementations of this disclosure, the method further includes receiving an association between one or more indications of one or more angular directions and one or more beams. The one or more angular directions include the at least one angular direction, and the one or more beams include the at least one beam. In this way, when a terminal device obtains an indication of an angular direction, it can know the angular direction in which it receives and / or transmits the beam. Therefore, the resource overhead of communicating angular direction indications with NTN devices can be reduced.
[0008] In some implementations of this disclosure, the method further includes: activating the at least one beam associated with the at least one angular direction; and deactivating a remaining beam associated with a remaining angular direction different from the at least one angular direction. The one or more angular directions include the remaining angular directions, and the one or more beams include the remaining beams. In this way, multiple beams of the terminal device can be activated, enabling the terminal device to receive, detect, and measure reference signals from multiple NTN devices located in different directions, thereby improving the communication quality between the terminal device and non-terrestrial networks.
[0009] In some implementations of this disclosure, the indication of the at least one angular direction is carried via one of the following: media access control (MAC) control element (CE) signaling, radio resource control (RRC) signaling, or downlink control information (DCI). The associated indication is carried in the RRC signaling. In this way, the angular direction of the terminal device's receive and / or transmit beam turning can be pre-configured and activated dynamically or semi-statically based on the actual scenario. The terminal device and the NTN device can reach a consensus on the angular direction of the terminal device's receive and / or transmit beam turning. Therefore, the communication quality between the terminal device and non-terrestrial networks can be improved.
[0010] In some implementations of this disclosure, the indication of the at least one angular direction sequentially indicates multiple angular directions, the sequential indication using a priority of the multiple angular directions. In this way, the terminal device can be able to receive, detect, and measure reference signals from NTN devices in different angular directions sequentially based on priority, and determine the angular direction for beam steering its reception and / or transmission. Therefore, the communication quality between the terminal device and non-terrestrial networks can be improved.
[0011] In some implementations of this disclosure, one of the at least one angular direction indications applies to at least one of the following directions: azimuth domain; zenith domain; or elevation domain. In this way, the spatial angular direction of the receiving and / or transmitting beams of the terminal device can be defined.
[0012] In some implementations of this disclosure, the at least one angular direction includes multiple angular directions, including a first angular direction and a second angular direction, wherein the at least one beam includes a first beam associated with the first angular direction and a second beam associated with the second angular direction. Transmitting the signal using one of the at least one beam includes: receiving the signal using the first beam; determining a quality degradation associated with the signal received using the first beam, wherein the first beam is associated with the outermost angular direction in a conical region constrained by the multiple angular directions; and performing a beam switching from the first beam to the second beam. In this way, when a terminal device encounters a quality degradation while communicating using the beam associated with the outermost angular direction, a beam switching of the terminal device can be triggered, and the terminal device can redirect its receive and / or transmit beams to another angular direction. Therefore, the communication quality between the terminal device and non-terrestrial networks can be improved.
[0013] In some implementations of this disclosure, the method further includes: sending capability information of the terminal device, wherein the cone-shaped region is associated with the capability information. In this way, the non-terrestrial network can know the cone-shaped region where the non-terrestrial network device can communicate with the terminal device.
[0014] In some implementations of this disclosure, determining the quality degradation associated with the signal includes at least one of the following: determining that the reference signal received power (RSRP) of the signal is lower than a first threshold for a first duration; determining that the reference signal received quality (RSRQ) of the signal is lower than a second threshold for a second duration; determining that the signal-to-interference-plus-noise ratio (SINR) of the signal is lower than a third threshold for a third duration; or determining that the signal is received using the first beam for a fourth duration. In this way, the terminal device can detect and measure the reference signal from an NTN device located in an angular direction and perform beam switching to another angular direction when the signal quality degrades. Therefore, the communication quality between the terminal device and non-terrestrial networks can be improved.
[0015] In some implementations of this disclosure, a configuration triggering the beam switching is received. The configuration includes at least one of the following: the first threshold and first duration of the RSRP; the second threshold and second duration of the RSRQ; the third threshold and third duration of the SINR; or the fourth duration in the outermost angular direction. This approach can improve the communication quality between the terminal device and non-terrestrial networks.
[0016] In some implementations of this disclosure, the method further includes: receiving a second indication indicating one of the at least one angular directions. Transmitting the signal using one of the at least one beams includes: transmitting the signal using a beam associated with the one of the at least one angular directions, wherein the one beam belongs to the at least one beam. In this way, the beam can be dynamically activated based on the indication of the associated angular direction.
[0017] In some implementations of this disclosure, the method further includes: receiving an indication of one of the at least one angular directions and an indication of correction for the one of the at least one angular directions. Transmitting the signal using the one of the at least one beams includes: transmitting the signal using a beam associated with the one of the at least one angular directions to which the correction has been applied, wherein the one beam belongs to the at least one beam. In this way, the terminal device can direct its receive and / or transmit beams to an angular direction with directional correction, thereby improving the communication quality between the terminal device and non-terrestrial networks.
[0018] In some implementations of this disclosure, transmitting the signal using one of the at least one beam comprises: detecting a reference signal using the at least one beam; determining, based on the detected reference signal, a beam with the strongest reference signal strength, wherein the beam belongs to the at least one beam; and transmitting the signal using the beam with the strongest reference signal strength. This method can improve the communication quality between the terminal device and non-terrestrial networks.
[0019] In some implementations of this disclosure, the at least one angular direction includes multiple angular directions, and the method further includes: receiving an indication of a default angular direction, wherein the default angular direction belongs to the multiple angular directions; performing beam switching to a beam associated with the default angular direction when at least one of the following is determined: a quality degradation associated with the signal received using a first beam among the multiple angular directions, wherein the first beam is associated with the outermost angular direction in a conical region constrained by the multiple angular directions; a state transition of the terminal device from an RRC connected state to a power-saving sleep mode; or a state transition of the terminal device from an RRC connected state to an idle mode. In this way, in certain specific scenarios, the terminal device can redirect its receive and / or transmit beams to a default direction, thereby ensuring the communication quality between the terminal device and non-terrestrial networks while reducing the power consumption of finding a suitable beam angular direction.
[0020] In some implementations of this disclosure, the default angular direction is associated with a time-domain and / or frequency-domain pattern indicating the resources used to transmit the signal. In this way, the default angular direction can be adapted to resource allocation, thereby improving the communication quality between the terminal device and non-terrestrial networks.
[0021] In a second aspect, a method performed by a non-terrestrial network device is provided. The method includes: the non-terrestrial network device transmitting an indication of at least one angular direction, wherein the at least one angular direction is associated with at least one beam; and transmitting a signal to a terminal device, wherein the signal is transmitted by the terminal device using one of the at least one beam. In this manner, the non-terrestrial network device can communicate with the terminal device based on the angular direction of the receiving and / or transmitting beams of the terminal device, thereby improving the link quality with the terminal device.
[0022] In some implementations of this disclosure, the method further includes: transmitting one or more indications of one or more angular directions associated with one or more beams. The one or more angular directions include the at least one angular direction, and the one or more beams include the at least one beam. In this way, non-terrestrial network devices can know the angular direction in which terminal devices receive and / or transmit beams. Therefore, the resource overhead of communicating angular direction indications with NTN devices can be reduced.
[0023] In some implementations of this disclosure, the indication of the at least one angular direction is carried via one of the following: media access control (MAC) control element (CE) signaling, radio resource control (RRC) signaling, or downlink control information (DCI). The associated indication is carried in the RRC signaling. In this way, the angular direction of the terminal device's receive and / or transmit beam turning can be pre-configured and activated dynamically or semi-statically based on the actual scenario. The terminal device and the NTN device can reach a consensus on the angular direction of the terminal device's receive and / or transmit beam turning. Therefore, the communication quality between the terminal device and non-terrestrial networks can be improved.
[0024] In some implementations of this disclosure, the indication of the at least one angular direction sequentially indicates multiple angular directions, the sequential indication using a priority of the multiple angular directions. This approach can improve the communication quality between the terminal device and non-terrestrial networks.
[0025] In some implementations of this disclosure, one of the at least one angular direction indications applies to at least one of the following directions: azimuth domain; zenith domain; or elevation domain. In this way, the spatial angular direction of the receiving and / or transmitting beams of the terminal device can be defined.
[0026] In some implementations of this disclosure, the at least one angular direction includes multiple angular directions, and the method further includes: transmitting a configuration to trigger beam switching. The configuration includes at least one of the following: a first threshold and a first duration for reference signal received power (RSRP); a second threshold and a second duration for reference signal received quality (RSRQ); a third threshold and a third duration for signal-to-interference-plus-noise ratio (SINR); or a fourth duration for the outermost angular direction within a conical region constrained by the multiple angular directions. In this way, the communication quality between the terminal device and non-terrestrial networks can be improved.
[0027] In some implementations of this disclosure, the method further includes: receiving capability information of the terminal device, wherein the cone-shaped region is associated with the capability information. In this way, the non-terrestrial network can determine the cone-shaped region where the non-terrestrial network device can communicate with the terminal device.
[0028] In some implementations of this disclosure, the method further includes: sending a second indication indicating one of the at least one angular directions. The terminal device transmits the signal using a beam associated with the one of the at least one angular directions, wherein the one beam belongs to the at least one beam. In this way, the beam can be dynamically activated based on the indication of the associated angular direction.
[0029] In some implementations of this disclosure, the method further includes: transmitting an indication of one of the at least one angular directions and an indication of correction for the one of the at least one angular directions. The signal is transmitted by the terminal device using a beam associated with the one of the at least one angular directions to which the correction has been applied, wherein the one beam belongs to the at least one beam. In this way, non-terrestrial devices can instruct the terminal device to redirect its receive and / or transmit beams to the angular direction with direction correction, thereby improving the communication quality between the terminal device and the non-terrestrial network.
[0030] In some implementations of this disclosure, the method further includes: sending an indication of a default angle direction, wherein the default angle direction belongs to the at least one angle direction. In this way, in certain specific scenarios, the terminal device can redirect its receive and / or transmit beams to a default direction, thereby ensuring the communication quality between the terminal device and non-terrestrial networks, while reducing the power consumption of finding a suitable beam angle direction.
[0031] In some implementations of this disclosure, the default angular direction is associated with a time-domain and / or frequency-domain pattern indicating the resources used to transmit the signal. In this way, the default angular direction can be adapted to resource allocation, thereby improving the communication quality between the terminal device and non-terrestrial networks.
[0032] In a third aspect, a terminal device is provided. The terminal device includes: a transceiver; and a processor communicatively coupled to the transceiver. The processor is configured to: acquire an indication of at least one angular direction associated with at least one beam; and transmit signals to a non-terrestrial network device using one of the at least one beam associated with the at least one angular direction. In this way, the terminal device can communicate with a non-terrestrial network using a beam associated with one or more indicated angular directions. The terminal device can communicate with an NTN device in that angular direction for a limited time, rather than accessing a cell of an NTN device moving along a track, thereby improving the link quality with NTN devices in the non-terrestrial network.
[0033] In a fourth aspect, a network device is provided. The network device includes: a transceiver; and a processor communicatively coupled to the transceiver. The processor is configured to: transmit an indication of at least one angular direction via the transceiver, wherein the at least one angular direction is associated with at least one beam; and transmit a signal to a terminal device, wherein the signal is transmitted by the terminal device using one of the at least one beam. In this manner, a non-terrestrial network device can communicate with a terminal device based on the angular direction of the receiving and / or transmitting beams of the terminal device, thereby improving the link quality with the terminal device.
[0034] In a fifth aspect, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium includes a computer program stored thereon, which, when executed on at least one processor, causes the at least one processor to perform a method according to the first aspect, the second aspect, or any possible implementation of the first or second aspect.
[0035] In a sixth aspect, a chip is provided. The chip includes at least one processing circuit for performing a method according to the first aspect, the second aspect, or any possible implementation thereof.
[0036] In a seventh aspect, a system is provided. The system includes at least one terminal device according to the third aspect and at least one network device according to the fourth aspect. Attached Figure Description
[0037] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 Examples of communication systems that can implement some exemplary embodiments of this disclosure are shown; Figure 2 Some exemplary embodiments of this disclosure may be implemented therein. Figure 1 Detailed examples of communication systems; Figure 3 Examples of electronic devices and base stations in which some exemplary embodiments of the present disclosure may be implemented are shown; Figure 4 Exemplary modules in a device or apparatus in which some exemplary embodiments of the present disclosure may be implemented are shown; Figure 5 Examples of communication systems with T-TRP and NT-TRP in which some exemplary embodiments of the present disclosure may be implemented are shown; Figure 6 Another example of a communication system with T-TRP and NT-TRP in which some exemplary embodiments of the present disclosure may be implemented is shown; Figure 7 Another example of a communication system with T-TRP and NT-TRP in which some exemplary embodiments of the present disclosure may be implemented is shown; Figure 8 Another example of a communication system with T-TRP and NT-TRP in which some exemplary embodiments of the present disclosure may be implemented is shown; Figure 9 An exemplary signaling diagram is shown in which some exemplary embodiments of the present disclosure may be implemented; Figure 10 An example of a group of covered areas in which some exemplary embodiments of this disclosure may be implemented; Figure 11 Examples of scenarios in which some exemplary embodiments of this disclosure can be implemented, such as activating three beam angle directions for UE to communicate with TN-TRP; Figure 12A An example of an NT-TRP that transmits multiple beams in which some exemplary embodiments of the present disclosure may be implemented is shown; Figure 12B Examples of visible cone-based BAI switching that can implement some exemplary embodiments of this disclosure are shown; Figure 12C Examples of visible cone-based BAI switching in which some exemplary embodiments of this disclosure may be implemented are shown; Figure 13 An example of a default BAI in which some exemplary embodiments of this disclosure may be implemented is shown; Figure 14 Examples of methods that can be implemented in a terminal device according to some exemplary embodiments of this disclosure are shown; Figure 15 Examples of methods that can implement some exemplary embodiments of this disclosure in an NTN device are shown; Figure 16 A block diagram of an apparatus that can be used to implement devices and methods according to some embodiments of the present disclosure is shown; Figure 17 The structure of an apparatus according to some embodiments of the present disclosure is shown; Figure 18 The structure of another device according to some embodiments of the present disclosure is shown.
[0038] In the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation
[0039] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described merely for illustration and to help those skilled in the art understand and implement this disclosure, and do not impose any limitation on the scope of this disclosure. The inventive content described herein can be implemented in various ways other than those described below.
[0040] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0041] References to "an embodiment," "an exemplary embodiment," etc., in this disclosure indicate that the described embodiments may include specific features, structures, or characteristics, but not every embodiment must include specific features, structures, or characteristics. Furthermore, these phrases do not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in connection with an embodiment, it should be understood that those skilled in the art will recognize how such features, structures, or characteristics can be combined with other embodiments to achieve the desired effect, whether explicitly described or not.
[0042] It should be understood that although the terms “first,” “second,” etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. The term “and / or” as used herein includes any and all combinations of one or more of the listed terms. When the words “first,” “second,” etc., are used before the same term (e.g., ED or operation step), it does 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 operation 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.
[0043] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein include the plural meaning. It should also be further understood that the term “comprising” as used herein is used to specify the presence of the stated feature, element, and / or component, but does not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. When used in conjunction with the terms “comprising” or “including” in the claims and / or specification, the words “a” or “an” can mean “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 mean at least a second or more, unless explicitly stated otherwise. 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.” It refers to a list from which you can select “A or B” or “A and B.” 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.” It refers to a list in which you can choose: 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.
[0044] It should be noted that the term "message" in this disclosure can be replaced with "information," which may be carried in a single message or in more than one single message. Unless otherwise specified, the terms "apparatus" and "device" are interchangeable, as are the terms "identifier" and "identifier."
[0045] The terms “coupled,” “coupled,” or “connected” as used herein may have several different meanings depending on the context in which they are used. For example, as used herein, the terms “coupled,” “coupled,” or “connected” may indicate that two elements or devices are directly connected to each other, or, depending on the specific context, are connected to each other by mechanical elements through one or more intermediate elements or devices.
[0046] The terms “receive,” “detect,” and “decode” used in this document 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 include both “detect” and “decode,” or it can mean the same thing; for example, “receive paging” means that the paging was correctly decoded and successfully retrieved, and correspondingly, “received paging not received” means that the receiving side did not detect and / or decode the paging. For example, “not received paging” means that the receiving side attempted to detect and / or decode the paging but failed to retrieve it. The term “receive” can sometimes mean 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. In this case, the receiving side needs to detect and decode the signal to obtain the information carried in it. In this scenario, “receive,” “detect,” and “decode” can represent different processes by which the receiving side obtains information.
[0047] When these functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of this application, in essence, or the parts that contribute to the prior art, or parts of these technical solutions, can be implemented in the form of a software product. This software product is stored in a storage medium and includes several instructions to instruct a computer device (which may be a personal computer, server, or network device) to perform all or part of the steps of the methods described in the embodiments of this disclosure. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, a portable hard drive, read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.
[0048] The above descriptions are merely some specific implementations of this disclosure and are not intended to limit the scope of protection of this disclosure. Any variations or substitutions that are readily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure are within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.
[0049] In cellular communication networks, user equipment (UE) location information is commonly used to improve various network performance metrics. These metrics may include, for example, capacity, agility, and efficiency. This improvement can be achieved when network elements utilize the UE's location, behavior, mobility patterns, etc., within the context of prior information describing the radio environment in which the UE operates.
[0050] Sensing systems can be used to help collect UE attitude information, including the UE's position in the global coordinate system, the UE's speed and direction of movement in the global coordinate system, orientation information, and information about the wireless environment. "Position" is also called "relative position," and these two terms are used interchangeably in this document. Well-known sensing systems include Radio Detection and Ranging (RADAR) and Light Detection and Ranging (LIDAR). While sensing systems can be separated from communication systems, it can be advantageous to use an integrated system to collect information, reducing the hardware (and cost) in the system and the time, frequency, or spatial resources required to perform both functions. However, using communication system hardware to perform the sensing of UE attitude and environmental information is extremely challenging and remains an open problem. The difficulty of this problem is related to factors such as the limited resolution of communication systems, the dynamic nature of the environment, and the large number of objects whose electromagnetic properties and positions need to be estimated.
[0051] Therefore, the integration of sensing and communication (also known as the integration of communication and sensing, joint sensing and communication, and other similar names) is an ideal feature in existing and future communication systems.
[0052] refer to Figure 1 This diagram, provided as an illustrative example and not as limiting, is a simplified schematic of a communication system. 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., sixth-generation, 6G, or later) RAN or a traditional (e.g., 5G, 4G, 3G, or 2G) RAN. One or more electronic devices (EDs) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (collectively referred to as 110) may be interconnected with each other or connected to one or more network nodes (170a, 170b, collectively referred to as 170) within the RAN 120. Core network 130 may be part of the communication system and may depend on or be independent of the radio access technology used in communication system 100. The communication system 100 may also include a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.
[0053] 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, multicasting, groupcasting, unicasting, etc. Communication system 100 can provide a wide range of communication services and applications (e.g., earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc.). The communication system 100 can operate by sharing resources such as carrier spectrum bandwidth among its constituent components.
[0054] Figure 2 A more detailed example of communication system 100 is shown. 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 between terrestrial and non-terrestrial networks, more flexible function sharing, and faster physical layer link switching. Terrestrial and non-terrestrial communication systems can be considered as subsystems of the communication system.
[0055] and Figure 1 The example shown is the same, in Figure 2The exemplary communication system 100 shown may include ED 110a, 110b, 110c, 110d (collectively referred to as ED 110) and RAN 120a, 120b. Furthermore, the communication system 100 may also include a non-terrestrial communication network 120c. The communication system 100 may also include one or more of a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. RAN 120a, 120b include corresponding RAN nodes, such as base stations (BS) 170a and 170b, which may be collectively referred to as terrestrial transmit and receive points (T-TRP) 170a and 170b. In one implementation, the non-terrestrial communication network 120c includes RAN nodes, such as access nodes (or base stations) 172, which may be collectively referred to as non-terrestrial transmit and receive points (NT-TRP) 172. As can be inferred from the similarities in the reference numerals, the non-terrestrial communication network 120c can be considered a radio access network, operating in the same manner as RANs 120a and 120b. In another implementation, the non-terrestrial communication network 120c may include at least one non-terrestrial network (NTN) device and at least one corresponding terrestrial network device, wherein the at least one NTN device operates as a transport layer device, and the at least one corresponding terrestrial network device operates as a RAN node, which communicates with the ED through the NTN device. Furthermore, an NTN gateway may also exist on the ground (i.e., referred to as the terrestrial network device), communicating with the NTN device as a transport layer device, and the RAN node communicates with the ED through both the NTN device and the NTN gateway. In some implementations, the NTN gateway and the RAN node may reside in the same device.
[0056] Alternatively or additionally, any ED 110 can be used to connect, access, or communicate with any T-TRP 170a, 170b, NT-TRP 172, Internet 150, core network 130, PSTN 140, other network 160, or any combination thereof. In some examples, ED 110a can perform uplink and / or downlink transmissions with T-TRP 170a via terrestrial air interface 190a. In some examples, ED 110a, ED 110b, ED 110c, and ED 110d can also communicate directly with each other via one or more sidelink (SL) air interfaces 190b. In some examples, ED 110d can perform uplink and / or downlink transmissions with NT-TRP 172 via non-terrestrial air interface 190c.
[0057] Air interfaces 190a and 190b can use similar communication technologies, such as any applicable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, such as code division multiple access (CDMA), space division multiple access (SDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA) (also known as discrete Fourier transform spread OFDMA (DFT-s-OFDMA)). Air interfaces 190a and 190b can utilize other higher-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.
[0058] 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 via a link. In some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of ED 110s and one or more NT-TRP 172s for multicast transmission.
[0059] RAN 120a and RAN 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to ED 110a, ED 110b, and ED 110c. RAN 120a and RAN 120b and / or core network 130 may communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by core network 130, and may or may not use the same radio access technology as RAN 120a and / or RAN 120b. Core network 130 may also serve as a gateway access between (i) RAN 120a and RAN 120b and / or ED 110a, ED 110b, and ED 110c and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Additionally, some or all of ED110a, ED 110b, and ED 110c may include the ability to communicate with different wireless networks via different wireless links using different wireless technologies and / or protocols. ED 110a, ED 110b, and ED 110c may communicate with a service provider or exchange (not shown) via a wired communication channel and with the Internet 150, rather than wirelessly (or also wirelessly). 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 / or subnets (internal networks) and incorporate protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED110a, ED 110b, and ED 110c may be multimode devices capable of operating according to multiple wireless access technologies and include multiple transceivers required to support these technologies.
[0060] Furthermore, the communication system 100 may include a sensing agent (not shown) to manage sensing data from ED 110 and / or T-TRP 170 and / or NT-TRP 172. In one implementation, the sensing agent is located within T-TRP 170 and / or NT-TRP 172. In another implementation, the sensing agent is a separate node with an interface for communicating with core network 130 and / or RAN 120 (e.g., T-TRP 170 and / or NT-TRP 172).
[0061] Figure 3An example of a device 310 is shown that, according to one embodiment, wirelessly communicates 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 100C). Device 310 may be a UE (e.g., Figure 1 or Figure 2 ED 110 in the example). Device 320a can be a terrestrial network device (e.g., such as ED 110). Figure 1 or Figure 2 The T-TRP 170 shown), device 320b can be a non-terrestrial network device (e.g., such as...). Figure 2 (NT-TRP172 shown). However, this is not a necessary condition. For example, according to this disclosure, 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. In the following description, ED 110 is described 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, it should be noted 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), or by more than one T-TRP 170, or by more than one NT-TRP 172, or by one or more T-TRP 170s and one or more NT-TRP 172s.
[0062] 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), metaverse, 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, etc.
[0063] Each ED 110 represents any end-user equipment suitable for wireless operation and may include (or be referred to as, but not limited to) devices such as: user equipment / device (UE), 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 device, smart book, vehicle, automobile, truck, bus, train, or IoT device, wearable device (e.g., watch, glasses, head-mounted device, etc.), industrial equipment, or devices that include or incorporate the above-mentioned devices (e.g., communication module, modem, or chip). Future generations of ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs and will be referred to as T-TRP 170 below. 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 configured to be dynamically or semi-statically turned on (i.e., established, activated, or enabled), turned off (i.e., released, deactivated, or disabled), and / or in response to one or more of connectivity availability and connectivity necessity.
[0064] 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. One, some, or all of the antennas 204 may also be panels. For example, transmitter 201 and receiver 203 may 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 may also be used to demodulate data or other content received through at least one antenna 204. Each transceiver includes any suitable structure to generate signals for wireless or wired transmission and / or process signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure to transmit and / or receive 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.
[0065] 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 for implementing some or all of the functions and / or embodiments described herein, and executed by one or more processing units (e.g., processor 210). Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory can 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, on-processor cache, etc.
[0066] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., connected to...). Figure 1 (Wired interface of the Internet 150). 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. For example, suitable structures include speakers, microphones, keypads, keyboards, displays, touchscreens, etc.
[0067] Processor 210 performs (or controls ED 110 to perform) operations described herein as being performed by ED 110, as shown below and elsewhere in this disclosure. For example, processor 210 performs or controls ED 110 to perform the following operations: receive a transport block (TB), decode one TB from the received TB using resources, release resources to decode another TB from the received TB, and / or receive configuration information for configuring resources. Specifically, the operations may include operations related to preparing for uplink transmission 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 implements transmit beamforming and / or receive beamforming based on an indication of beam direction (e.g., beam angle information) 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 acquiring system information. In some embodiments, processor 210 may perform channel estimation using the reference signal received from NT-TRP 172 and / or T-TRP 170.
[0068] 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.
[0069] The processing components of processor 210, transmitter 201, and receiver 203 may be implemented by the same or different processors, which execute 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 accelerators such as graphics processing units (GPUs) or artificial intelligence (AI) accelerators.
[0070] 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, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, 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. 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.
[0071] 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. One, some, or all of the antennas 256 may also 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 in the figure, but the T-TRP may include one or more other components.
[0072] In some implementations, the T-TRP 170 can have other names, such as base station, basetransceiver station (BTS), wireless base station, network node, network equipment, network-side equipment, transmit / receive node, 3G base station (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 equipment, 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), positioning node, etc. The T-TRP 170 can be a macro base station (BS), pico base station, relay node, host node, or a combination thereof. T-TRP 170 may refer to the aforementioned equipment or to a device within the aforementioned equipment (such as a communication module, modem, or chip).
[0073] In some embodiments, the various parts of T-TRP 170 may be distributed. For example, some modules of T-TRP 170 may be located remotely from the device housing the antenna 256 for T-TRP 170 and may be coupled to the device housing the antenna 256 via a communication link (not shown) sometimes referred to as a fronthaul (e.g., a common public radio interface (CPRI)). Therefore, in some embodiments, the term "T-TRP 170" may also refer to network-side modules that perform processing operations such as ED 110 location determination, resource allocation (scheduling), message generation, and encoding / decoding, which 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, such as through the use of coordinated multicast transmissions.
[0074] 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 a beam direction indication, which can be scheduled for transmission by scheduler 253. Processor 260 can perform 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 to configure one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172, etc. Any signaling generated by processor 260 is transmitted by transmitter 252. It should be noted that the term "signaling" as used herein can also be referred to as control signaling. Signaling can be transmitted in a physical layer control channel (e.g., a physical downlink control channel (PDCCH)), in which case the signaling can be referred to as dynamic signaling. Signaling transmitted in the downlink physical layer control channel can be referred to as physical layer signaling, such as downlink control information (DCI). Signaling transmitted in the uplink physical layer control channel can be referred to as physical layer signaling, such as uplink control information (UCI). Signaling transmitted in the sidelink physical layer control channel can be called physical layer signaling, such as sidelink control information (SCI).Signaling can be included in higher-layer (e.g., above the physical layer) data packets transmitted in physical layer data channels (e.g., in the physical downlink shared channel, PDSCH). In this case, the signaling can be referred to as higher-layer signaling, static signaling, or semi-static signaling. Higher-layer signaling can also refer to radio resource control (RRC) protocol signaling or media access control-control element (MAC-CE) signaling. Signaling can include a combination of physical layer signaling and higher-layer signaling.
[0075] 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 170. Scheduler 253 may schedule uplink, downlink, lateral, and / or backlink transmissions, including issuing scheduling authorizations and / or configuring schedule-free (e.g., "configuration authorization") resources.
[0076] Memory 258 is used to store information, and optionally data. Memory 258 stores instructions and data used, generated, or collected 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.
[0077] Although not shown, processor 260 may constitute part of transmitter 252 and / or receiver 254. Furthermore, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may constitute part of processor 260.
[0078] The processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented by the same or different one or more processors, which execute instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented using dedicated circuitry, such as a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC.
[0079] 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, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., chips, memory, or buses). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or ED110 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.
[0080] 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. Furthermore, in some implementations, the NT-TRP 172 may be referred to by other names, such as non-terrestrial node, non-terrestrial network equipment, or non-terrestrial base station.
[0081] like Figure 3 As shown, the T-TRP 170 includes 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. One, some, or all of the antennas 256 may also 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 in the figure, but the T-TRP may include one or more other components.
[0082] like Figure 3As 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. Alternatively, one, some, or all of the antennas may 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 in the figure, but the NT-TRP may include one or more other components.
[0083] NT-TRP 172 includes a processor 276 for performing operations related to: preparing a transmission for downlink transmission to ED 110, processing an uplink transmission received from ED 110, preparing a transmission for backhaul transmission to T-TRP 170 and / or NT-TRP 172, and processing a transmission received via backhaul from T-TRP 170 and / or another NT-TRP 172. Processing operations related to preparing downlink or backhaul 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 backhaul 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 received from T-TRP 170. In some embodiments, processor 276 may generate signaling, for example, to configure one or more parameters of ED 110. In some embodiments, the NT-TRP 172 implements physical layer processing but not higher-level functions such as medium access control (MAC) or radio link control (RLC) layer functions. Since this is merely an example, the NT-TRP 172 may more generally implement higher-level functions in addition to physical layer processing.
[0084] Memory 278 is used to store information, and optionally data. Memory 278 stores instructions and data used, generated, or collected 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.
[0085] Although not shown, processor 276 may form part of transmitter 272 and / or receiver 274. Although not shown, memory 278 may form part of processor 276.
[0086] The processing components of processor 276, transmitter 272, and receiver 274 may be implemented by the same or different processors, which execute 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 programmable 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 to serve ED 110, such as by coordinating multicast transmissions.
[0087] 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, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, sending information to T-TRP 170 and / or another NT-TRP 172 and / or ED110 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.
[0088] It should be noted that the term "transmit / receive point (TRP)" as used herein can refer to either a T-TRP or an NT-TRP. Alternatively, a T-TRP can be referred to as a terrestrial network TRP ("TN TRP"), or an NT-TRP can be referred to as a non-terrestrial network TRP ("NTN TRP"). T-TRP 170, NT-TRP 172, and / or ED 110 may include other components, but these components have been omitted for clarity.
[0089] It should be noted that, for simplicity, the term "signaling" used in this article can also be referred to as control signaling, control message, control information, or simply 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 include a combination of physical layer signaling and higher layer signaling.
[0090] It should be noted that in this disclosure, when "information" is different from "message", it can be carried in a single message or in more than one single message.
[0091] One or more steps of the method provided in this disclosure can be achieved by Figure 4 The corresponding unit or module shown will be executed. Figure 4 The diagram illustrates units or modules within a device or apparatus (e.g., ED 110, T-TRP 170, or NT-TRP 172). 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 units or modules may be circuits such as integrated circuits. Examples of integrated circuits include programmable FPGAs, GPUs, or ASICs. For example, one or more units or modules may be logic, 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 one or more instances, and these modules themselves may include instructions for further deployment and instantiation.
[0092] 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.
[0093] Wireless communication systems, such as fourth-generation (4G) systems (e.g., Long-Term Evolution (LTE) systems) and fifth-generation (5G) systems (e.g., New Radio (NR) systems), have been deployed to provide various types of applications, such as messaging, voice, video, and other data. In the NR domain, non-terrestrial networks (NTNs) are developing, which can utilize space vehicles such as satellites (including low Earth orbit (LEO), medium Earth orbit (MEO), geostationary Earth orbit (GEO), and highly elliptical orbit (HEO) satellites), or air vehicles such as drones or aircraft (also known as high-altitude platforms) as base stations or relays to enable communication between different devices. Satellites or drones within the NTN may move at high speeds relative to user equipment (UE) and other devices operating within the NTN, which differs from the scenario between a UE and a terrestrial base station. Furthermore, the distance between the UE and a satellite or drone is much greater than the distance between the UE and a ground base station. This disclosure is directed to terminal devices such as UEs, IoT devices, and automobiles. The types of network scenarios envisioned may include terrestrial TRPs, such as base stations, and / or non-terrestrial TRPs, such as drones, balloons, high-altitude platform stations (HAPS), satellites, and any such devices supporting wireless access technologies such as 5G NR, future 6G, or other technologies.
[0094] Consider a scenario where a terrestrial TRP communicates with a non-terrestrial TRP that is part of a satellite constellation. Figure 5 An example of a communication system 500 with T-TRP and NT-TRP in which some exemplary embodiments of the present disclosure may be implemented is shown. In the communication system 500, a satellite constellation includes multiple satellite orbits, ensuring that the Earth always receives wireless coverage from the satellites. Each satellite orbit may contain multiple satellites, such as satellites or NT-TRPs 505, 510, and 515. Terrestrial TRPs such as T-TRPs 540, 545, 550, 555, 560, and 565 can be connected to the core network 535 via terrestrial gateways (TN gateways) such as 525 and 530, while the satellite constellation can be connected to the core network 535 via a dedicated non-terrestrial gateway (NTN gateway) 520, such as... Figure 5As shown. Depending on factors such as service load, radio link quality, and congestion, devices such as the UE can connect and communicate with terrestrial TRPs 540, 545, 550, 555, 560, or 565, or NT-TRPs 505, 510, or 515. NT-TRPs 505, 510, and 515 can be... Figure 1 , Figure 2 and Figure 3 The implementation of NT-TRP 172 in [the document / reference]. T-TRP 540, 545, 550, 555, 560, and 565 can be [specific implementation details]. Figure 1 , Figure 2 and Figure 3 The implementation method of T-TRP 170 in the document.
[0095] Another scenario can be envisioned, in which the satellite constellation effectively acts as a gateway for ground-based TRPs. Figure 6 Another example of a communication system 600 with T-TRP and NT-TRP in which some exemplary embodiments of the present disclosure may be implemented is shown. In the scenario of communication system 600, a satellite constellation with satellites 605, 615 effectively acts as a gateway for ground-based TRPs 630, 635, 640 and 645, 650, 655. Satellites 605, 610, and 615 in the satellite constellation communicate with the core network 625 via a wireless link through a ground-based NTN gateway 620, which in turn communicates with the core network 625 via a wired link (e.g., a fiber optic link). Ground-based TRPs 630, 635, 640 and 645, 650, 655 communicate with satellites 605 and 615 via wireless links, and the satellites communicate with each other via free-space optical links (e.g., using lasers). Depending on factors such as service load, radio link quality, and congestion, devices such as the UE can connect and communicate with T-TRP 630, 635, 640, 645, 650, or 655, or NT-TRP 605, 610, or 615. NT-TRP 605, 610, and 615 can be... Figure 1 , Figure 2 and Figure 3 The implementation of NT-TRP172 in [the document / reference]. T-TRP 630, 635, 640 and 645, 650, 655 can be [specific implementation details]. Figure 1 , Figure 2 and Figure 3 The implementation method of T-TRP 170 in the document.
[0096] Another scenario can be envisioned, in which the non-terrestrial TRP communicates with the terrestrial TRP through the core network. Figure 7Another example of a communication system 700 with T-TRP and NT-TRP in which some exemplary embodiments of the present disclosure may be implemented is shown. In the scenario of communication system 700, non-terrestrial TRPs 705, 710, and 720 communicate with terrestrial TRPs 740, 745, 750, 755, 760, and 765 via core network 735. Non-terrestrial TRPs 705, 710, and 720 may first communicate with dedicated non-terrestrial gateway 720, which then communicates with core network 735. Core network 735 can then relay power-saving commands from non-terrestrial TRPs 705, 710, and 720 to terrestrial TRPs 740, 745, 750, 755, 760, and 765 via dedicated terrestrial gateways 725 and 730. Depending on factors such as service load, radio link quality, and congestion, devices such as the UE can connect and communicate with T-TRP 740, 745, 750, 755, 760, or 765, or NT-TRP 705, 710, or 715. NT-TRP 705, 710, and 715 can be... Figure 1 , Figure 2 and Figure 3 The implementation of NT-TRP 172 in [the document / reference]. T-TRP 740, 745, 750, 755, 760, and 765 can be [specific implementation details needed]. Figure 1 , Figure 2 and Figure 3 The implementation method of T-TRP 170 in the document.
[0097] In cellular systems such as 5G NR, the UE can receive, detect, and measure reference signals such as SS / PBCH blocks and non-zero power channel state information reference signals (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 UE-specific scrambling identifier. For example, the primary synchronization signal (PSS) and secondary synchronization signal (SSS) sequences are initialized using the physical cell identity (PCI) value, where the PCI is a common scrambling identifier. The NZP-CSI-RS sequence is initialized using a UE-specific scrambling identifier, which is configured to the UE by the network.
[0098] 5G NR Rel-17 introduces support for non-terrestrial networks, namely, enhancements in the following aspects: timing relationship of timing advance, reference timing of channel state information (CSI) resources, transmission timing of DCI for scheduling PUSCH, transmission timing of random access response carried on physical uplink shared channel (PUSCH), and transmission timing of hybrid automatic repeat request-acknowledgement (HARQ-ACK) on physical uplink control channel (PUCCH).
[0099] In 5G NR Rel-17, NTN support was introduced, allowing UEs to support DL / UL communication with satellites in a scenario called "transparent forwarding," where the ground station sends signals to satellites in space, and the satellites reflect the signals back to the UE on the ground. To assist UEs in NTN operations, dedicated signaling related to NTN was introduced. Higher-layer signaling such as RRC introduced signaling satellite ephemeris, satellite position, satellite signal polarization, timing advance offset, System Information Block (SIB), and satellite epochs to support NTN operations. Other introduced features include expanding the HARQ process to 32 steps to accommodate scenarios with large propagation delays and disabling HARQ-ACK feedback.
[0100] 5G NR Rel-17 also introduces a scheme that combines closed-loop and open-loop timing advance compensation. The closed-loop part is controlled by the network, while the open-loop part is executed by the UE. The UE's compensation can be based on knowledge of satellite ephemeris (such as satellite orbit angles and other parameters).
[0101] 5G NR Rel-17 supports a scenario called "transparent forwarding," where the base station is located behind an NTN gateway on the ground, the NTN gateway sends transmissions to the satellite (this link is called the "feeder" link), and the satellite sends transmissions to the UE on the ground (this link is called the "serving" link).
[0102] Figure 8An example of a communication system 800 with T-TRP and NT-TRP in which some exemplary embodiments of the present disclosure may be implemented is shown. In the communication system 800, NT-TRPs 805 and 810 in a satellite constellation communicate with the core network 820 via a radio link through an NTN gateway 815 located on the ground. T-TRP 825 is located behind the NTN gateway 815 on the ground. The NTN gateway 815 sends transmissions to NT-TRPs 805 and 810 using a "feeder" link, and NT-TRP 805 or 810 sends the transmissions to the UE on the ground using a "serving" link. NT-TRPs 805 and 810 may be... Figure 1 , Figure 2 and Figure 3 The implementation of NT-TRP 172 in [the document / reference]. T-TRP 825 can be [the implementation of NT-TRP 172 / reference]. Figure 1 , Figure 2 and Figure 3 The implementation method of T-TRP 170 in the document.
[0103] In 5G NR Rel-18, NTN support is further enhanced, introducing coverage enhancements for NTN, network-verified UE location, and support for TN-to-NTN and NTN-to-NTN mobile scenarios. Satellites transmit multiple beams to the ground, each of which can be associated with a given "physical cell identifier." Furthermore, satellites transmit beams in a "fixed" manner, meaning that the satellite does not steer its beams in a given direction; instead, the beams "slide" across the Earth's surface, thus appearing "moving" from the perspective of ground equipment.
[0104] The NTN support introduced in 5G NR Rel-17 is based on a non-transparent design, meaning that devices such as UEs, IoT devices, and vehicles effectively see each satellite as serving cells. Devices can also learn about the satellite's ephemeris and location at any given time when the satellite explicitly broadcasts its ephemeris and location in System Information Block 19 (SIB19). SIB19 is transmitted by the satellite to help devices like UEs obtain auxiliary information for NTN access (i.e., the UE accesses the NTN and will be served by it). This non-transparent radio access design hinders the seamless integration of transmit diversity schemes, multi-TRP transmission schemes, and distributed satellite systems.
[0105] In low Earth orbit (LEO) NTN access scenarios, satellites are in constant motion, thus the time they can maintain line-of-sight connections with ground equipment is limited. For example, in the Starlink constellation, an LEO satellite might maintain a line-of-sight connection with a given ground device for several minutes. Therefore, any information sent or broadcast by the satellite to ground equipment becomes outdated within minutes and requires constant updates for satellite communication to function properly (due to constantly changing uplink synchronization timing advances and the need to reacquire downlink synchronization). This results in high signaling overhead between the satellite and ground equipment, simply to maintain the communication link.
[0106] LEO satellites use a fixed-beam model to transmit signals and channels to ground equipment. This causes the satellite beam to "slide" across the Earth's surface, triggering a move and handover process whenever a device is located at the edge between two beams. This move and handover process can cause latency and interruptions because the device needs to re-establish an RRC connection when entering the target cell, thus impacting the overall user experience.
[0107] In view of this, some embodiments of this disclosure provide a scheme for implementing beam activation and switching in an NTN. By communicating with the NTN device using a beam in one of the indicated angular directions, the terminal device does not need to access the cell of the NTN device moving along its trajectory for communication, and can switch to another cell of another NTN device for communication when the previous NTN device moves away. Therefore, the power consumption and complexity of communication between the terminal device and the NTN device can be reduced, and the communication quality between the terminal device and non-terrestrial networks can be improved.
[0108] Figure 9 An exemplary signaling diagram is shown of a communication process 900 in which some exemplary embodiments of the present disclosure may be implemented. Terminal device 910 may be... Figure 1 , Figure 2 and Figure 3 The implementation method of ED 110 in NTN equipment 972. Figure 1 , Figure 2 and Figure 3 NT-TRP 172, or Figure 5 NT-TRP 505 to 515, or Figure 6 NT-TRP 605 to 615, or Figure 7 NT-TRP 705 to 715, or Figure 8 The implementation methods of NT-TRP 805 and 810 are described below. Those skilled in the art will understand that the terminal device 910 can be replaced with other devices, such as relay devices within the coverage area of the first network device 905.
[0109] In communication process 900, terminal device 910 acquires at least one angular direction indication 902. For example, NTN device 972 may send 901 at least one angular direction indication 902 to terminal device 910. Alternatively, terminal device 910 may receive at least one angular direction indication 902 from other devices, such as another NTN or TN device (e.g., a base station on Earth) or a nearby terminal device, different from NTN device 972. Terminal device 910 transmits signals to NTN device 972 using one of at least one beam associated with at least one angular direction. For example, terminal device 910 may use a receive beam associated with one of the at least one angular direction to receive signals from NTN device 972. Furthermore, terminal device 910 may use a transmit beam associated with one of the at least one angular direction to transmit signals from NTN device 972.
[0110] In some embodiments, the indication of angular direction may be referred to as beam angular indication (BAI). It should be understood that the term "beam angular indication" is for illustrative purposes only, and other terms may be used. BAI can be defined as a quantized indication of angular direction. For example, the angular direction may be given in the azimuth domain, zenith domain, or elevation domain. This quantized indication can indicate the angular direction in which the terminal device intends to steer its receive and / or transmit beams, for example, such that the line of sight of the receive and / or transmit beams is aligned with the angular direction indicated by the BAI. In this disclosure, the terms "angle" and "angle" are used interchangeably.
[0111] In some embodiments, terminal device 910 may receive associations between one or more indications of one or more angular directions and one or more beams. For example, NTN device 972 may send associations to terminal device 910. Alternatively, terminal device 910 may receive associations from other devices (e.g., another NTN or TN device different from NTN device 972, e.g., a base station on Earth) or nearby terminal devices. One or more angular directions may include at least one angular direction, and one or more beams may include at least one beam. For example, terminal device 910 may receive associations between multiple BAIs and multiple beams. Upon receiving an indication of at least one BAI among the multiple BAIs, terminal device 910 may know that at least one beam associated with at least one BAI can be used for communication with the NTN. Terminal device 910 may determine to use one of the at least one beams for signal transmission and / or reception.
[0112] In some embodiments, terminal device 910 may activate at least one beam associated with at least one angular direction and deactivate a remaining beam associated with a remaining angular direction different from the at least one angular direction. One or more angular directions may include the remaining angular directions, and one or more beams may include the remaining beams. In other words, terminal device 910 may configure a set of angular directions and may activate a subset of the configured angular directions. When communicating with NTN device 972, terminal device 910 may redirect its receive and / or transmit beams to one of the activated angular directions. It should be noted that in this disclosure, the term "subset" may refer to a portion or all of the entire set.
[0113] In some embodiments, the associated indication may be carried in radio resource control (RRC) signaling. At least one angular direction indication may be carried in media access control (MAC) control element (CE) signaling. Alternatively, at least one angular direction indication may be carried in radio resource control (RRC) signaling. Alternatively, at least one angular direction indication may be carried in downlink control information (DCI). In this way, the angular direction can be pre-configured and activated dynamically or semi-statically.
[0114] In some embodiments, at least one angular direction indication sequentially indicates multiple angular directions. The sequential indication uses a priority among the multiple angular directions. For example, terminal device 910 may receive multiple angular direction indications sequentially. Terminal device 910 may use a beam measurement reference signal associated with a first sequential angular direction among the multiple angular directions and determine whether the link quality is suitable for communication. If not, terminal device 910 may switch to a beam associated with a second sequential angular direction.
[0115] In some embodiments, one of the at least one angular directions indicates the direction applied in the azimuth domain. Alternatively or additionally, one of the at least one angular directions indicates the direction applied in the zenith domain. Alternatively or additionally, one of the at least one angular directions indicates the direction applied in the elevation domain. In this way, the spatial orientation of the beam can be determined based on the indication of the angular direction associated with the beam.
[0116] In some embodiments, at least one angular direction may include multiple angular directions. The multiple angular directions may include a first angular direction and a second angular direction. At least one beam may include a first beam associated with the first angular direction and a second beam associated with the second angular direction. When communicating with NTN device 972, terminal device 910 may use the first beam to receive signals from NTN device 972 and determine a quality degradation associated with the signal received using the first beam. The first beam is associated with the outermost angular direction in a conical region constrained by multiple angular directions. Terminal device 910 may perform beam switching from the first beam to the second beam. For example, if multiple angular directions are activated, the conical region is constrained by multiple angular directions. If NTN device 972 moves away from the conical region, terminal device 910 may switch its beam to another angular direction to communicate with another NTN device within the conical region.
[0117] In some embodiments, terminal device 910 can transmit capability information. The conical region is associated with the capability information. In other words, the activated angular direction can be associated with the capabilities of terminal device 910. This improves communication quality and reduces power consumption.
[0118] In some embodiments, when a quality degradation associated with a signal is determined, the terminal device 910 may determine that the reference signal received power (RSRP) of the signal is lower than a first threshold for a first duration. Alternatively or additionally, when a quality degradation associated with a signal is determined, the terminal device 910 may determine that the reference signal received quality (RSRQ) of the signal is lower than a second threshold for a second duration. Alternatively or additionally, when a quality degradation associated with a signal is determined, the terminal device 910 may determine that the signal-to-interference-plus-noise ratio (SINR) of the signal is lower than a third threshold for a third duration. Alternatively or additionally, when a quality degradation associated with a signal is determined, the terminal device 910 may determine that the signal is received using a first beam for a fourth duration.
[0119] In some embodiments, terminal device 910 may receive a configuration to trigger beam switching. For example, NTN device 972 may send the configuration to trigger beam switching to terminal device 910. Alternatively, terminal device 910 may receive the configuration to trigger beam switching from other devices (e.g., another NTN or TN device different from NTN device 972, such as a base station on Earth) or nearby terminal devices. The configuration to trigger beam switching may include a first threshold and a first duration for RSRP. Alternatively or additionally, the configuration to trigger beam switching may include a second threshold and a second duration for RSRQ. Alternatively or additionally, the configuration to trigger beam switching may include a third threshold and a third duration for SINR. Alternatively or additionally, the configuration to trigger beam switching may include a fourth duration for the outermost angular direction.
[0120] In some embodiments, terminal device 910 may receive a second indication indicating one of at least one angular directions. When communicating with NTN device 972, terminal device 910 may use a beam associated with one of the at least one angular directions to transmit or receive signals. A beam belongs to at least one beam. In other words, terminal device 910 may be instructed to direct its beam to a specific angular direction among the active angular directions. NTN device 972 may send the second indication to terminal device 910. Alternatively, terminal device 910 may receive the second indication from other devices (e.g., another NTN or TN device different from NTN device 972 (e.g., a base station on Earth)) or nearby terminal devices.
[0121] In some embodiments, terminal device 910 may receive an indication of one of at least one angular directions and an indication of correction for that angular direction. When communicating with NTN device 972, terminal device 910 may use a beam associated with one of the at least one angular directions to which correction has been applied, wherein the beam belongs to at least one beam. In this way, even if only a limited number of angular directions are configured or activated, the terminal device can direct its beam to suitable spatial directions not limited to the configured or activated angular directions, thereby improving the communication quality with the NTN. NTN device 972 may send the indication of the angular direction and the indication of correction for the angular direction to terminal device 910. Alternatively, terminal device 910 may receive the indication of the angular direction and the indication of correction for the angular direction from other devices (e.g., another NTN or TN device different from NTN device 972, e.g., a base station on Earth) or nearby terminal devices.
[0122] In some embodiments, when communicating with the NTN device 972, the terminal device 910 can use at least one beam to detect a reference signal and determine the beam with the strongest reference signal strength based on the detected reference signal, wherein the beam belongs to at least one beam. The terminal device 910 can use the beam with the strongest reference signal strength to send signals to / receive signals from the NTN device 972. In this way, the communication quality with the NTN can be improved.
[0123] In some embodiments, at least one angular direction includes multiple angular directions. Terminal device 910 can receive an indication of a default angular direction. The default angular direction belongs to multiple angular directions. For example, NTN device 972 can send an indication of the default angular direction to terminal device 910. Alternatively, terminal device 910 can receive an indication of the default angular direction from other devices, such as another NTN device or TN device (e.g., a base station on Earth) different from NTN device 972, or a nearby terminal device. If there is a quality degradation associated with the signal received using a first beam among the multiple angular directions, terminal device 910 can perform a beam switching to the beam associated with the default angular direction, wherein the first beam is associated with the outermost angular direction in a conical region constrained by multiple angular directions. For example, when NTN device 972 moves away from the conical region of terminal device 910, terminal device 910 can switch its beam to another NTN device located in the default angular direction. Alternatively, terminal device 910 can perform a beam switching to the beam associated with the default angular direction when terminal device 910 transitions from an RRC connected state to a power-saving sleep mode. When terminal device 910 is in power-saving sleep mode, terminal device 910 can use the default angle direction for the entire duration. Alternatively, terminal device 910 can perform beam switching to the beam associated with the default angle direction when terminal device 910 transitions from RRC connected state to idle mode. When terminal device 910 is in idle mode, terminal device 910 can use the default angle direction for the entire duration.
[0124] Power-saving sleep mode is a mode in which a terrestrial TRP can cease performing communication or sensing functions on terminal devices 910 (e.g., EDs) within its coverage area. The terrestrial TRP can stop sending any kind of physical layer signal or channel to any terminal device 910 (e.g., UE, automotive, IoT devices, robots, etc.), and can also stop detecting and measuring any physical layer signals sent by any terminal device 910, or detecting and decoding any physical layer channels sent by any terminal device 910. This allows the terrestrial TRP to significantly reduce its power consumption to achieve goals such as carbon neutrality or energy consumption targets. In power-saving sleep mode, the terrestrial TRP can perform one or more monitoring power consumption (PC) indications (or one or more wake-up indications) from one or more non-terrestrial TRPs. In some examples, a terrestrial TRP in power-saving sleep mode may only perform the function of monitoring wake-up indications sent from other devices. For example, the terrestrial TRP does not send any signals / channels, nor does it receive any signals / channels from the ground toward UEs, automotive, robots, and IoT devices, etc. The terrestrial TRP only performs the basic functions required to further receive power consumption indications, such as NT-TRP search and synchronization. It should be noted that the “power saving hibernation” mode may also be called “hibernation” mode, “low power” mode, “ultra-low power” mode or other such names, that is, the names used in this disclosure should not limit the scope of this disclosure.
[0125] In some embodiments, the default angular orientation is associated with a time-domain and / or frequency-domain pattern that indicates the resources on which signals can be transmitted. For example, the default angular orientation may be associated with a pattern called "beam hopping," where the beam hopping pattern can be used to indicate a time-domain and / or frequency-domain pattern on which resources beams can be transmitted.
[0126] The foregoing section provided a general description of some embodiments of beam activation and switching in non-terrestrial networks. The following section will describe in further detail some exemplary implementations of beam activation and switching in terrestrial / non-terrestrial networks with reference to different exemplary implementations.
[0127] In the first exemplary implementation, different BAIs can be "activated" by receiving an "activation" command. Examples of activation commands include MAC-CE-based activation. The principle behind "activating" a BAI is that a configured BAI can be "activated" via an "activation" command. For example, this can be done by setting a configured BAI to an "active" state, thus assuming that the BAI is in an "active" state. One activation command can activate one zenith BAI, or it can activate multiple zenith BAIs.
[0128] In some embodiments, there may be a coverage area on the ground, and some devices, such as UEs, are within that coverage area. Figure 10 An example of a coverage area 1000 in which some exemplary embodiments of this disclosure may be implemented is shown. For example, four UEs are located within the coverage area 1000. The UEs within the coverage area 1000 may be connected to the network, i.e., the UEs may establish an RRC connection with the network and be in a connected mode. Alternatively, the UEs within the coverage area 1000 may not be connected to the network, i.e., the UEs may not establish an RRC connection with the network and be in an idle mode or an inactive mode. Alternatively, the UEs may be in a power-saving sleep mode associated with having an RRC connection (for connected mode), or the UEs may be in a power-saving sleep mode unrelated to having an RRC connection (for idle mode or inactive mode).
[0129] To connect with non-terrestrial systems (e.g., satellite mega-constellations), the UE needs to point its beam into the sky. However, there may be a large number of non-terrestrial TRPs (NT-TRPs), such as satellites within the UE's line of sight. Therefore, there may be a large number of non-terrestrial TRPs with which the UE can establish connections.
[0130] In some embodiments, to help the UE establish a connection with the NT-TRP, the UE may need to generate a transmit / receive beam toward the NT-TRP (e.g., to receive a reference signal transmitted by the NT-TRP). When the UE is in connected mode, a BAI table can be provided to the UE using higher-layer signaling (e.g., RRC) in the zenith angle domain. An example of such a zenith angle BAI table is shown in Table 1.
[0131] Table 1. BAI Tables in the Zenith Angle Region
[0132] As shown in Table 1, each zenith angle corresponds to an absolute angular direction in, for example, degrees, and can be interpreted as the UE being able to point its spatial receiving beam in that angular direction, thereby aligning the line of sight of that spatial receiving beam with that angular direction. It can be assumed that 0 degrees in the zenith angle domain corresponds to the UE's vertically pointing skyward transmit / receive beam. Each angular direction is associated with a BAI provided as a 3-bit codeword. In this example, the codeword width is 3 bits because the zenith angle BAI table includes 7 entries. Other examples of zenith angle BAI tables with more or fewer entries can be considered or envisioned. A zenith angle BAI table may include one or more entries, each containing a 3-bit codeword. The UE can use any one or more entries in the zenith angle BAI table to orient its spatial receiving beam in the direction of any one or more entries. The UE can also use the default zenith angle BAI as its spatial transmit beam to transmit UL signals and / or channels.
[0133] In the example in Table 1, the UE is configured with a zenith angle BAI table containing 7 entries. In some embodiments, the network can use a MAC-CE command to activate a given zenith angle BAI in the table. Table 2 provides an example of a MAC-CE command for activating a zenith angle BAI. As shown in Table 2, the MAC-CE command may include a 3-bit zenith angle BAI with a value set to "011" to instruct the UE that it should direct its transmit / receive beam so that the line-of-sight angle is 0 degrees in the zenith angle domain.
[0134] Table 2 shows the MAC-CE commands used to activate a zenith angle BAI.
[0135] In some embodiments, it can be considered that a given zenith angle BAI is "activated" when a MAC-CE command is received, detected, and decoded. Similarly, if no configured BAI is indicated in the MAC-CE command, it can be considered that such configured BAIs may have been deactivated. In this disclosure, the expression "activation of beam associated with angular direction" can be used interchangeably with the expression "activation of BAI".
[0136] By activating the BAI in the zenith angle domain, ground equipment can connect to multiple NT-TRPs operating as part of a non-terrestrial system, such as a satellite constellation. Especially in the case of what is known as a "mega-constellation," ground equipment may be able to receive, detect, and measure reference signals from multiple NT-TRPs, thus benefiting from NT-TRP diversity. Furthermore, this diversity within NT-TRPs is beneficial to non-terrestrial systems because it prevents "interference" with a single NT-TRP. Such "interference" is particularly likely to occur at higher layers, such as at the Internet Protocol (IP) layer and above, where a given NT-TRP may be considered the "best" NT-TRP serving a given area, and all traffic is sent to that NT-TRP, causing it to overload and thus be "interfered with." Allowing ground equipment to be served by multiple NT-TRPs prevents this interference.
[0137] While Table 2 provides examples of "activation" for a given zenith angle BAI, the MAC-CE command can be implemented in various ways. For example, the MAC-CE command may include additional fields, such as the MAC-CE command type, which can indicate to the UE the type of MAC-CE command. For instance, the MAC-CE command type could indicate at least one of zenith angle BAI activation, zenith angle BAI deactivation, azimuth angle BAI activation, or azimuth angle BAI deactivation. In the examples in Table 2, the MAC-CE command activates only one transmit / receive beam in the zenith angle domain. In some other examples, the MAC-CE command can activate one or more BAIs. Table 3 provides examples of such MAC-CE commands.
[0138] Table 3 shows the MAC-CE commands used to activate multiple Zenith angle BAIs.
[0139] As shown in Table 3, the MAC-CE command can be sent by the NT-TRP. Depending on the UE's capabilities, the MAC-CE command may include one or more zenith angles (BAI). Each zenith angle (BAI) in the MAC-CE command may have a 3-bit width, and their values are set to "011", "010", and "100" respectively, to instruct the UE to guide its transmit / receive beams so that the angle of the line of sight in the zenith angle domain can be 0 degrees (zenith angle BAI=011), –10 degrees (zenith angle BAI=010), or 10 degrees (zenith angle BAI=100).
[0140] In some embodiments, the order of values can indicate an implicit hierarchy, i.e., the UE will first turn its transmit / receive beam to 0 degrees in the zenith angle domain; if the UE fails to use the beam to receive, detect, and measure any reference signal, the UE will turn its transmit / receive beam to -10 degrees in the zenith angle domain; if the UE still fails to use the beam to receive, detect, and measure any reference signal, the UE will turn its transmit / receive beam to 10 degrees in the zenith angle domain.
[0141] Figure 11 Example 1100 illustrates a scenario in which three beam angle directions are activated for UE communication with a TN-TRP, in which some exemplary embodiments of this disclosure can be implemented. In example 1100, NT-TRPs 1105, 1110, and 1115 can provide network services to a UE within a coverage area 1120. NT-TRPs 1105, 1110, and 1115 can be... Figure 1 , Figure 2 and Figure 3The implementation of NT-TRP 172 is as follows: A UE within coverage area 1120 can be configured with multiple zenith angles (BAIs). The UE receives an indication to activate zenith angles BAI 010, 011, and 100 among the configured zenith angles. Beams 1125, 1130, and 1135 are associated with the angular directions indicated by the activated zenith angles BAI 010, 011, and 100 (i.e., –10 degrees, 0 degrees, and 10 degrees in the zenith angle domain), respectively. Beams 1125, 1130, and 1135 are activated and can be used by the UE within coverage area 1120 to communicate with NT-TRP 1105, 1110, and 1115.
[0142] In this way, multiple BAIs can be activated, enabling the UE to receive, detect, and measure reference signals from multiple NT-TRPs located in different directions. Similarly, activating multiple BAIs allows the UE to receive, detect, and decode physical layer downlink control and data transmissions (e.g., PDCCH and PDSCH, respectively) from multiple NT-TRPs located in different directions. Therefore, "transmit diversity" or "NT-TRP diversity" can be enabled, allowing the UE to receive reference signals or downlink transmissions from different NT-TRPs. From a routing perspective, this scheme prevents "interference" with any given NT-TRP, as more than one NT-TRP may provide coverage to a given UE.
[0143] Furthermore, activating multiple BAIs allows the network to restrict the direction in which the UE attempts to receive, detect, and measure reference signals. Alternatively or additionally, activating multiple BAIs allows the network to restrict the direction in which the UE attempts to receive, detect, and decode physical layer downlink transmissions, such as PDCCH / PDSCH. NT-TRPs (e.g., satellites) can move along their orbits, as is the case in low earth orbit (LEO) constellations. The UE does not continuously follow a given NT-TRP but only attempts to detect transmissions from the direction indicated by the zenith angle BAI, regardless of the movement of the NT-TRP. Since it is assumed that all NT-TRPs are on the same orbit, the UE can assume that the timing lead will not change and the downlink timing reference will not change.
[0144] It should be understood that the bit sizes shown in Tables 1, 2, and 3 are for illustrative purposes only. Other bit sizes may also be used. It should also be understood that the embodiments of this disclosure are equally applicable to the uplink. For example, the UE may use an active zenith angle (BAI) to transmit reference signals or physical layer transmissions (e.g., PUCCH / PUSCH).
[0145] In some embodiments, the BAI can be the BAI in the azimuth domain, i.e., a beam pointing in a given direction in the horizontal domain. In some embodiments, the UE can be configured with a zenith BAI table and an azimuth BAI table. In some embodiments, the MAC-CE activation command can activate the azimuth BAI. In some embodiments, the MAC-CE activation command can activate both the azimuth BAI and the zenith BAI simultaneously, instructing the UE to turn its beam in the angular direction indicated by both the azimuth BAI and the zenith BAI. In some embodiments, depending on the UE's capabilities, the MAC-CE activation command can activate more than one azimuth BAI and more than one zenith BAI, instructing the UE to turn its first beam in the angular direction indicated by the first azimuth BAI and the first zenith BAI, then turn its second beam in the angular direction indicated by the second azimuth BAI and the second zenith BAI, and so on.
[0146] In this way, user-centric communication solutions can be designed within an NTN. The UE does not need to access a specific cell of a particular NTN device for network connectivity, nor does it need to frequently switch to another cell due to the movement of the NTN device. Therefore, power consumption can be reduced and communication quality improved.
[0147] The second exemplary implementation can be similar to the first exemplary implementation, the only difference being that the example activation command includes DCI-based activation. Details of the first exemplary implementation can also be applied to the second exemplary implementation, therefore details of the second exemplary implementation are omitted here.
[0148] In one possible example, the DCI format may include a “Zenith Angle BAI” field with a bit width of, for example, 3 bits, and its value may indicate the zenith angle BAI. Therefore, the DCI format can activate and / or instruct the UE to use a transmit / receive beam in the zenith angle domain by indicating a value of the zenith angle BAI. For example, the UE may be configured with a zenith angle BAI table (e.g., Table 1). The network can use a DCI-based activation command to activate a given zenith angle BAI in the table. An example of such a DCI format is shown below (other fields are not shown): DCI_format={ … ZenithBAI={011}, … } The DCI format may include a 3-bit zenith angle BAI with a value set to "011" to instruct the UE to direct its transmit / receive beam so that the line-of-sight angle is 0 degrees in the zenith angle domain. The DCI format may also include other fields (not shown).
[0149] In another possible example, after receiving a MAC-CE activation command to activate multiple zenith angle BAIs, the UE can also receive a DCI format indicating which specific BAI among the activated BAIs can be used. For example, the UE has already received a MAC-CE command (e.g., the MAC-CE command shown in Table 3) to activate three zenith angle BAIs. The UE can then also receive a DCI format indicating which activated zenith angle BAI the UE will use, an example of which is shown below: DCI_format={ … ZenithBAI={00}, … } In this example, the MAC-CE command includes three active zenith AIs. Therefore, 2 bits can be used in the DCI format to indicate the specific BAI among the three active BAIs actually used by the UE. For example, the DCI format may include a "ZenithBAI" field set to the value "00," which indicates to the UE that the UE should use the first active zenith BAI, i.e., the zenith BAI with a value of "011" in Table 3. Similarly, the DCI format may include a "ZenithBAI" field set to the value "01," which indicates to the UE that the UE should use the second active zenith BAI, i.e., the zenith BAI with a value of "010" in Table 3. Similarly, the DCI format may include a "ZenithBAI" field set to the value "10," which indicates to the UE that the UE should use the third active zenith BAI, i.e., the zenith BAI with a value of "100" in Table 3. Other examples and mappings can be envisioned for the codeword of the "ZenithBAI" field.
[0150] By specifying the use of a specific BAI in the zenith angle domain, ground equipment can connect to multiple NT-TRPs operating as part of a non-terrestrial system, such as a satellite constellation. Especially in the case of what is known as a "mega-constellation," ground equipment may be able to receive, detect, and measure reference signals from multiple NT-TRPs, thus benefiting from NT-TRP diversity. Furthermore, this diversity within NT-TRPs is beneficial to non-terrestrial systems because it prevents "interference" with a single NT-TRP. Such "interference" is particularly likely to occur at higher layers, such as at the Internet Protocol (IP) layer and above, where a given NT-TRP might be considered the "best" NT-TRP serving a given area, and all traffic is sent to that NT-TRP, causing it to overload and thus "interfere." Allowing ground equipment to be served by multiple NT-TRPs prevents this interference.
[0151] In some embodiments, the DCI format may also include a "ZenithBAICorrection" field, which indicates to the UE that it should apply correction to the currently active zenith angle BAI. An example of this DCI format is provided below: DCI_format={ … ZenithBAI={00}, ZenithBAICorrection={0011} … } The DCI format may include a "ZenithBAICorrection" field, which may have a bit width of, for example, 4 bits. The value of the "ZenithBAICorrection" field may indicate a correction factor in, for example, 0.25 degrees. If the "ZenithBAICorrection" field is set to the value "0011", this may instruct the UE that it should apply a correction of 0.75 degrees on the active zenith angle BAI, thereby causing the beam to turn 0.75 degrees in an angular direction. Other examples and mappings can be envisioned.
[0152] In some embodiments, the methods and mechanisms mentioned in this disclosure may be applied to devices in idle or inactive modes (or in power-saving sleep modes associated with hibernation or deep hibernation), for example for system information (SI) reception or paging reception.
[0153] Communication quality can be reduced by applying corrections to the angle and direction of the beam that the UE should be guided to. By introducing corrections to the BAI, the number of entries that need to be configured in the BAI table can be reduced, thereby simplifying the configuration of the BAI table and the judgment process for using the BAI.
[0154] In a third exemplary implementation, a feature of BAI switching can be introduced, particularly switching of the BAI in the zenith angle domain. As the NT-TRP moves along its orbit, ground equipment (e.g., the UE) may sense a change in the need to use a different beam in order to, for example, better receive, detect, and measure reference signals from that NT-TRP. This beam switching may be triggered by the movement of the NT-TRP along its orbit, resulting in high power consumption, high complexity, and low communication quality. In the third exemplary implementation, the "visible cone" can serve as a constraint on the zenith angle BAI that the UE can configure. When the NT-TRP moves away from the UE's visible cone, the UE can switch its beam to another NT-TRP located within the UE's visible cone.
[0155] In some embodiments, ground equipment (e.g., UE) may be in connected mode, meaning they have already established a non-terrestrial network, such as an RRC connection. NT-TRP (e.g., satellite) may transmit multiple beams, enabling them to provide coverage to different areas. Figure 12A Example 1200A of an NT-TRP that transmits multiple beams is shown, in which some exemplary embodiments of the present disclosure may be implemented. In example 1200A, NT-TRP 1215 can transmit up to, for example, 30 beams. It should be understood that examples of NT-TRPs capable of generating more or fewer than 30 beams are conceivable. NT-TRP 1215 may be... Figure 1 , Figure 2 and Figure 3 The implementation of NT-TRP 172 in [the context of the document].
[0156] In some embodiments, such beam switching is particularly likely to occur when the NT-TRP moves away from the UE, depending on, for example, a zenith angle BAI table that can be configured at the UE, and on one or more zenith angle BAIs that may already be activated at the UE.
[0157] Figure 12B Example 1200B, which illustrates a visible cone-triggered BAI handover in which some exemplary embodiments of this disclosure may be implemented, is shown. In example 1200B, the NT-TRP 1215 can transmit multiple beams to provide different coverage areas on the ground. The NT-TRP 1215 may be... Figure 1 , Figure 2 and Figure 3 The implementation of NT-TRP 172 in the example is as follows: Beams 1225, 1230, and 1235 are associated with angular directions (i.e., –10 degrees, 0 degrees, and 10 degrees in the zenith angle domain) indicated by activated zenith angles BAI 010, 011, and 100, respectively. Beams 1225, 1230, and 1235 are activated and can be used by UE 1220 to communicate with NT-TRP.
[0158] In Example 1200B, UE 1220 may already be using beam 1235, corresponding to zenith angle BAI, at 10 degrees to receive, detect, and measure reference signals from NT-TRP 1215. Alternatively or additionally, UE 1220 may have used beam 1235 to receive, detect, and decode physical layer transmissions (e.g., PDCCH / PDSCH) from NT-TRP 1215. As NT-TRP 1215 moves along its trajectory, its coverage area may shift away from the UE's location, and the UE may experience a degrade in its link quality. The "visible cone" 1205 can refer to the area located between angular directions corresponding to –10 degrees (i.e., zenith angle BAI=010) and 10 degrees (i.e., zenith angle BAI=100). This can constitute a beam switching trigger for UE 1220 when NT-TRP 1215 leaves the visible cone of UE 1220.
[0159] For example, UE 1220 can use a decrease in the reference signal received power (RSRP) as a trigger condition for beam switching. Alternatively, the UE can use a decrease in the signal-to-interference-noise ratio (SINR) as a trigger condition for beam switching. Another example is that UE 1220 can use a change in the angular direction of the NT-TRP as a trigger condition for beam switching. In some implementations, a combination of one or more of the following can be used to trigger zenith angle beam switching: for example, RSRP-based trigger conditions, SINR-based trigger conditions, and zenith angle-based trigger conditions. UE 1220 can use one or more of the above methods or other methods to determine whether to switch the angular direction of its beam. An example of higher-layer signaling (e.g., RRC) corresponding to RSRP-based beam switching is provided below: BeamSwitchTriggerConfig={ beamSwitchRSRP={ beamSwitchThreshold={-110dBm}, hysteresis={3dB}, timeToTrigger={10ms} } } If the RSRP is below -110 dBm and lasts for 10 ms, the example configuration of the above higher-layer signaling for UE 1220 to switch its beams is provided that the hysteresis parameter is 3 dB. Other examples using SINR and angular direction can be defined in a similar manner.
[0160] Below is another example of higher-layer signaling (e.g., RRC) corresponding to SINR-based beam switching: BeamSwitchTriggerConfig={ beamSwitchSINR={ beamSwitchThreshold={-6dB}, hysteresis={3dB}, timeToTrigger={10ms} } } If the SINR is below -6 dB and lasts for 10 ms, the example configuration of the above higher-layer signaling is to switch the UE 1220 to its beam, provided that the hysteresis parameter is 3 dB.
[0161] Below is another example of higher-level signaling (e.g., RRC) corresponding to beam switching based on zenith angle: BeamSwitchTriggerConfig={ beamSwitchZenithAngle={ beamSwitchThreshold={10deg}, hysteresis={2deg}, timeToTrigger={50ms} } } If the zenith angle is greater than 10 degrees and the duration is 50 ms, the example configuration of the above higher-layer signaling for UE1220 is to switch its beam, provided that the hysteresis parameter is 2 degrees. UE1220 can switch to use another beam, such as beam 1230 corresponding to 0 degrees (i.e., zenith angle BAI=011).
[0162] In another example, UE 1220 can use a drop in reference signal received quality (RSRQ) as a trigger condition for beam switching. Below is another example of higher-layer signaling (e.g., RRC) corresponding to beam switching based on zenith angle: BeamSwitchTriggerConfig={ beamSwitchRSRQ={ beamSwitchThreshold={-6dB}, hysteresis={3dB}, timeToTrigger={10ms} } } If the RSRQ is below -6 dB and lasts for 10 ms, the example configuration of the above higher-layer signaling is to switch the UE 1220 to its beam, provided that the hysteresis parameter is 3 dB.
[0163] Figure 12C Example 1200C is shown, illustrating a visible cone-based BAI switching in which some exemplary embodiments of this disclosure may be implemented. Example 1200C may be... Figure 12B The scenario after triggering the BAI switch in Example 1200B. Figure 12B and Figure 12C Reference numerals with the same number in the code indicate the same element, therefore Figure 12C The detailed description of this component is omitted. For example... Figure 12C As shown, when NT-TRP 1215 leaves the visible cone area of UE 1220, a beam switching of UE 1220 is triggered. UE 1220 switches to another beam in the active beam (e.g., beam 1230) and can communicate with NT-TRP 1210 located in the cone area 1205 of UE 1220. NT-TRP 1210 can be... Figure 1 , Figure 2 and Figure 3 The implementation of NT-TRP 172 in [the context of the document].
[0164] By triggering beam switching (or BAI switching) based on a cone-shaped region of the UE, this transition can be seamless for the UE because the UE does not leave its coverage area, and therefore its physical layer parameters and other higher-layer parameters remain unchanged. This change is limited to the beam the UE might use to communicate with the NT-TRP. Furthermore, the cone-shaped region that limits the zenith angle BAI movement distance may also constrain physical parameters (such as propagation delay) and the resulting timing advance to maintain UL synchronization.
[0165] In the fourth exemplary implementation, a default zenith angle (BAI) feature can be introduced. In one scenario, when the NT-TRP moves away from the UE's visible cone, the UE can switch its beam to another NT-TRP located within the UE's visible cone. In another scenario, when the UE is in idle mode, the UE can use the default zenith angle BAI and can wait until the UE detects a beam from the NT-TRP using the default zenith angle BAI in order to initiate a process, such as the initial access procedure.
[0166] When the UE is in idle mode, it may not retain any previously provided higher-layer signaling (e.g., RRC), and it may rely on one or more "default" zenith angle beams to receive, detect, and measure reference signals transmitted in the NT-TRP beam. Additionally or alternatively, the UE may rely on one or more "default" zenith angle beams to receive, detect, and decode physical layer transmissions (e.g., PDCCH / PDSCH), such as system information and / or paging transmitted in the NT-TRP beam. For example, the default zenith angle beam (BAI) could be a beam with an angular direction pointing to 0 degrees (i.e., vertically towards the sky).
[0167] Figure 13 Example 1300 of a default BAI in which some exemplary embodiments of this disclosure may be implemented is shown. For example, UE 1320 may be in idle mode or power-saving sleep mode. UE 1320 may use beam 1330 associated with the default BAI to perform initial access or monitor a reference signal from NT-TRP 1310 before waking from power-saving sleep mode. NT-TRP 1310 may be... Figure 1 , Figure 2 and Figure 3 The implementation of NT-TRP 172 in [the context of the document].
[0168] When the UE is in idle mode (or when the UE is in a power-saving sleep mode associated with hibernation or deep sleep), the UE 1320 can use the default zenith angle (BAI) for the entire duration. This effectively allows the UE to perform detection and measurement of the reference signal transmitted by the NT-TRP using the default zenith angle (BAI) until the UE 1320 wakes up and / or performs initial access to establish an RRC connection.
[0169] In some embodiments, there may be one or more default zenith angles (BAIs), and the UE will use one or more default zenith angles (BAIs) to perform detection and measurement on the reference signal.
[0170] The zenith angle BAI information can be provided to the device (e.g., UE) from a higher layer (e.g., the non-access stratum (NAS) layer). For example, the UE's universal subscriber identity module (USIM) may include a base file associated with services of non-terrestrial access types, and the base file may include, for example, a zenith angle BAI table (e.g., Table 4) and a default zenith angle BAI (e.g., as shown in Table 5) for selection from which to use.
[0171] Table 4. Zenith Angle BAI Table
[0172] Table 5 Default Zenith Angle BAI
[0173] The zenith angle BAI table in Table 4 includes 3 entries, corresponding to 3 zenith angles: (0 degrees, –10 degrees, and 10 degrees). The default zenith angle BAI in Table 5 is set to 00, corresponding to a zenith angle of 0 degrees, i.e., pointing vertically to the sky. The values in these basic files stored in the USIM can be passed down to the UE's physical layer using internal operating system implementations, protocol stack implementations, or by transferring them from the UE's memory.
[0174] In some implementations, when the UE transitions from, for example, connected mode to, for example, idle mode, the UE can switch from the active zenith angle BAI (where the activation command is, for example, a MAC-CE activation command or a DCI-based activation command) to the default zenith angle BAI. Additionally or alternatively, when the UE transitions from a power-saving mode associated with, for example, connected mode to a power-saving mode associated with, for example, deep sleep mode, the UE can switch from the active zenith angle BAI (where the activation command is, for example, a MAC-CE activation command or a DCI-based activation command) to the default zenith angle BAI.
[0175] By performing a beam switch to the beam associated with the default BAI, power consumption can be reduced because the UE does not need to expend significant processing power searching and scanning for beams from the NT-TRP, since the UE uses its default zenith angle BAI (e.g., the beam pointing towards the sky) as the default beam. By performing a beam switch to the beam associated with the default BAI, seamless transitions can be enabled for the UE, as the UE does not leave its coverage area and therefore its physical layer parameters remain unchanged. This change is limited to the beam the UE might use to communicate with the NT-TRP. Another benefit for UEs in idle mode is that it reduces the complexity of performing measurements on different beams transmitted from the NT-TRP, since the UE will use the default zenith angle BAI when performing measurements on the reference signal, instead of trying all zenith angle BAIs. Furthermore, limiting the zenith angle BAI travel distance can also constrain physical parameters such as propagation delay and the resulting timing advance to maintain UL synchronization.
[0176] In some embodiments, reference signals transmitted on different beams for a given NT-TRP can be generated using different "physical beam identifiers." In this case, beam switching operations may require the UE to search for new reference signals. If the UE has multiple active zenith angle beams (BAIs), the UE can use one of the other active zenith angle beams to detect those new reference signals and select the zenith angle BAI where the UE can detect the strongest reference signal, for example, in terms of RSRP. If the UE only has active zenith angle BAIs, the UE can select a default zenith angle BAI, for example, the zenith angle BAI corresponding to the 0-degree angle direction.
[0177] In some implementations, the BAI can be the BAI in the azimuth domain, i.e., the beam pointing in a given direction in the horizontal domain. In some embodiments, the UE can be configured with a zenith BAI table and an azimuth BAI table. In some embodiments, the default zenith BAI can be associated with a "beam hopping" mode, wherein the beam hopping mode can be used to indicate the time-domain and / or frequency-domain modes on which resources the beam can be transmitted.
[0178] In some implementations, the UE may have certain capabilities regarding, for example, the range of angles supported in the zenith angle domain. For instance, the UE may transmit this capability to the network in its UE capability report, using higher-level parameters that may indicate the maximum angle (e.g., degrees) referred to as the "visible cone." Alternatively, the UE may not transmit this capability parameter to the network, and the capability parameter may be embedded in the UE's internal hardware. The UE may then apply any higher-level signaling related to the zenith angle BAI based on its internal hardware, and subsequently report to the network the specific zenith angle BAI that the UE has applied.
[0179] In some implementations, the UE may have certain capabilities, such as the number of Tx / Rx beams supported in the zenith angle domain. For example, the UE may transmit this capability to the network in its UE capability report, using higher-level parameters that indicate the maximum number of zenith angle BAIs the UE can support within a region known as the "visible cone." Alternatively, the UE may not transmit this capability parameter to the network; instead, the parameter may be embedded in the UE's internal hardware, and any higher-level signaling related to the zenith angle BAI can be applied based on this internal hardware. The UE can then report the specific zenith angle BAIs it has applied to the network.
[0180] In some implementations, the UE may have certain capabilities regarding, for example, the range of angles supported in the azimuth domain. For instance, the UE may transmit this capability to the network in its UE capability report, using higher-layer parameters that may indicate the maximum angle (e.g., degrees) referred to as the "visible cone." Alternatively, the UE may not transmit this capability parameter to the network, and the capability parameter may be embedded in the UE's internal hardware. The UE may then apply any higher-layer signaling related to the azimuth BAI based on its internal hardware, and subsequently report to the network the specific azimuth BAI that the UE has applied.
[0181] In some implementations, the UE may have certain capabilities, such as the number of Tx / Rx beams supported in the azimuth domain. For example, the UE may transmit this capability to the network in its UE capability report, using higher-layer parameters that indicate the maximum number of azimuth BAIs the UE can support within a region known as the "visible cone." Alternatively, the UE may not transmit this capability parameter to the network; instead, the parameter may be embedded in the UE's internal hardware, and any higher-layer signaling related to the azimuth BAI can be applied based on this internal hardware. The UE can then report the specific azimuth BAIs it has applied to the network.
[0182] In some implementations, the network may send a DCI format to the UE, which may carry a "defaultZenithBAI" field. This field may have a bit width of, for example, 4 bits, and may carry the quantized value of BAI. The network may have already provided the UE with a table of such quantized BAI values using, for example, higher-layer signaling. If the DCI format includes the "defaultZenithBAI" field, the UE can switch its Tx / Rx beam from its current beam to a Tx / Rx beam, with the Tx / Rx beam's line of sight pointing in the direction corresponding to the value provided in the "defaultZenithBAI" field. If the DCI format does not include the "defaultZenithBAI" field, the UE can continue to use its current Tx / Rx beam to receive, for example, PDCCH / PDSCH and / or transmit, for example, PUCCH / PUSCH. It should be noted that the UE may require a certain time interval, which may be referred to as, for example, beam application time, in order to switch its Tx / Rx beam from the current beam to the Tx / Rx beam, with the Tx / Rx beam's line of sight pointing in the direction corresponding to the value provided in the "defaultZenithBAI" field.
[0183] In some implementations, the network may send a DCI format to the UE, which may carry a "zenithBAI" field. This field may have a bit width of, for example, 4 bits, and may carry the quantized value of BAI. The network may have already provided the UE with a table of such quantized BAI values using, for example, higher-layer signaling. If the DCI format includes the "zenithBAI" field, the UE can switch its Tx / Rx beam from its current beam to a Tx / Rx beam with the line of sight pointing in the direction corresponding to the value provided in the "zenithBAI" field. If the DCI format does not include the "zenithBAI" field, the UE can continue to use its current Tx / Rx beam to receive, for example, PDCCH / PDSCH and / or transmit, for example, PUCCH / PUSCH. It should be noted that the UE may require a certain time interval, which may be referred to as, for example, beam application time, to switch its Tx / Rx beam from its current beam to a Tx / Rx beam with the line of sight pointing in the direction corresponding to the value provided in the "zenithBAI" field.
[0184] In some implementations, if the UE receives / detects / decodes a DCI format (which may carry the "zenithBAI" and "defaultZenithBAI" fields), the UE can consider the DCI format invalid because the UE can expect the DCI format to carry one of the "zenithBAI" and "defaultZenithBAI" fields, rather than both.
[0185] Figure 14 Examples of methods for implementing some exemplary embodiments of the present disclosure are shown in terminal device 910. Figure 9 The terminal device 910 in the middle can be implemented as Figures 10 to 13 UE in the middle.
[0186] In method 1400, at 1410, terminal device 910 acquires an indication of at least one angular direction. At 1420, terminal device 910 transmits signals to a non-terrestrial network device using one of at least one beam associated with the at least one angular direction.
[0187] Figure 15 Examples of methods for implementing some exemplary embodiments of this disclosure are shown. The NTN device 972 can be implemented as... Figures 10 to 13 NT-TRP in.
[0188] In method 1500, at 1510, the NTN device 972 sends an indication of at least one angular direction, wherein the at least one angular direction is associated with at least one beam. At 1520, the NTN device 972 transmits a signal to the terminal device, wherein the signal is transmitted by the terminal device using one of the at least one beam.
[0189] Figure 16 This is a block diagram of an electronic device (ED) 1600, which can be used to implement devices such as terminal device 910, first network device 905, or NTN device 972, as well as the methods 1400 or 1500 disclosed herein. In some embodiments, device 1600 can be a component of a communication network infrastructure, such as a base station (e.g., a NodeB, an evolved NodeB (eNodeB or eNB), a next-generation NodeB (sometimes called a gNodeB or gNB)), a home subscriber server (HSS), a packet gateway (PGW), or a serving gateway (SGW), or various other nodes or functions in a core network (CN) or a Public Land Mobility Network (PLMN). In some embodiments, device 1600 can be a device connected to the network infrastructure via a wireless interface, such as a mobile phone, smartphone, or other device that can be classified as user equipment (UE). In some embodiments, device 1600 may be a machine-type communications (MTC) device (also known as a machine-to-machine (M2M) device) or other such device that can be classified as a UE (although it does not provide direct service to the user). In some embodiments, device 1600 may be a roadside unit (RSU), a vehicle UE (V-UE), a pedestrian UE (P-UE), or an infrastructure UE (I-UE). In some scenarios, device 1600 may also be referred to as a mobile device, a term intended to indicate a device connected to a mobile network, regardless of whether the device itself is designed for mobility or has mobility capabilities. A particular device may utilize all the components shown or only a subset of the components, and the level of integration may vary from device to device. Furthermore, device 1600 may include multiple instances of components, such as multiple processors, memories, transmitters, receivers, etc.
[0190] Device 1600 typically includes a processor 1602, such as a central processing unit (CPU), and may also include a dedicated processor such as a graphics processing unit (GPU) or other such processors, memory 1604, a network interface 1606, and a bus 1608 connecting the various components of device 1600. Device 1600 may also optionally include components such as a mass storage device 1610, a video adapter 1612, and an I / O interface 1616 (as shown by dashed lines).
[0191] Memory 1604 may include any type of non-transitory system memory that can be read by processor 1602, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In one embodiment, memory 1604 may include more than one type of memory, such as ROM used at power-on and DRAM used to store programs and data during program execution. Bus 1608 may be one or more of any type of bus architecture, including a memory bus or memory controller, peripheral bus, or video bus.
[0192] Device 1600 may also include one or more network interfaces 1606, which may include at least one of wired network interfaces and wireless network interfaces. For example... Figure 16 As shown, network interface 1606 may include a wired network interface for connecting to network 1622, and may also include a radio access network interface 1620 for connecting to other devices via a wireless link. When device 1600 is a network infrastructure element, the radio access network interface 1620 may be omitted for nodes or functions that are elements at the wireless edge (e.g., eNB) rather than at the wireless edge of the network. When device 1600 is infrastructure located at the wireless edge of the network, both the wired network interface and the wireless network interface may be included. When device 1600 is a wirelessly connected device (e.g., user equipment), the radio access network interface 1620 may be present and may be supplemented by other wireless interfaces such as a Wi-Fi network interface. Network interface 1606 enables device 1600 to communicate with remote entities (e.g., entities connected to network 1622).
[0193] Mass storage device 1610 may include any type of non-transitory storage device for storing data, programs, and other information and making such data, programs, and other information accessible via bus 1608. Mass storage device 1610 may include one or more of the following: solid-state drive, hard disk drive, disk drive, or optical disk drive. In some embodiments, mass storage device 1610 may be located remotely from device 1600 and may be accessed via a network interface such as interface 1606. In the illustrated embodiment, mass storage device 1610 differs from the included memory 1604 and typically performs storage tasks insensitive to high latency, but generally provides low or no volatility. In some embodiments, mass storage device 1610 may be integrated with heterogeneous memory 1604.
[0194] Optional video adapter 1612 and I / O interface 1616 (shown as dashed lines) provide interfaces to couple device 1600 to external input and output devices. Examples of input and output devices include a display 1614 coupled to video adapter 1612 and an I / O device 1618 (e.g., a touchscreen) coupled to I / O interface 1616. Other devices may be coupled to device 1600, and more or fewer interfaces may be used. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide interfaces for external devices. Those skilled in the art will understand that in embodiments where device 1600 is part of a data center, I / O interface 1616 and video adapter 1612 may be virtualized and provided via network interface 1606.
[0195] Figure 17 The structure of a device 1700 according to some embodiments of the present disclosure is shown. For example... Figure 17 As shown, the device 1700 includes an acquisition unit 1702 and a communication unit 1704. The device 1700 can be applied to applications such as... Figure 1In the communication system shown, any of the methods provided in the above embodiments can be implemented. Optionally, the physical representation of device 1700 can be a communication device, such as terminal device 910. Device 1700 can also be another device capable of implementing the functions of a communication device, such as a processor, chip, etc., inside a communication device. Specifically, device 1700 can be some programmable chips, such as field-programmable gate array (FPGA), complex programmable logic device (CPLD), application-specific integrated circuit (ASIC), or system-on-a-chip (SoC).
[0196] In some embodiments, the acquisition unit 1702 may be used to acquire an indication of at least one angular direction. The communication unit 1704 may be used to transmit signals to a non-terrestrial network device using one of at least one beam associated with at least one angular direction.
[0197] In some other embodiments, the apparatus 1700 may include various other units or modules that can be used to perform various operations or functions described in conjunction with the above method embodiments. For details, please refer to the detailed description of the above method embodiments, which will not be repeated here.
[0198] Figure 18 The structure of a device 1800 according to some embodiments of the present disclosure is shown. For example... Figure 18 As shown, the device 1800 includes a transmitting unit 1802 and a communication unit 1804. The device 1800 can be applied to applications such as... Figure 1 In the communication system shown, any of the methods provided in the above embodiments can be implemented. Optionally, the physical representation of device 1800 can be a communication device, such as NTN device 972. Device 1800 can also be another device capable of implementing the functions of a communication device, such as a processor, chip, etc., inside a communication device. Specifically, device 1800 can be some programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system-on-a-chip (SoC).
[0199] In some embodiments, the transmitting unit 1802 may be used to transmit an indication of at least one angular direction, wherein the at least one angular direction is associated with at least one beam. The communication unit 1804 may be used to transmit signals with a terminal device, wherein the signals are transmitted by the terminal device using one of the at least one beam.
[0200] In some other embodiments, the apparatus 1800 may include various other units or modules that can be used to perform various operations or functions described in conjunction with the above method embodiments. For details, please refer to the detailed description of the above method embodiments, which will not be repeated here.
[0201] It should be noted that the division of units or modules in the above embodiments of this disclosure is exemplary and merely a logical functional division. In actual implementation, other division methods are also possible. Furthermore, the functional units in the embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0202] When the integrated unit is implemented as a software functional unit and sold or used as an independent product, the integrated unit can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of this disclosure can essentially be implemented, in whole or in part, in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, server, or network device) or processor to perform all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, a portable hard drive, read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.
[0203] Based on the above embodiments, embodiments of this application also provide a computer program. When the computer program is run on a computer, it causes the computer to perform any of the methods provided in the above embodiments.
[0204] Based on the above embodiments, embodiments of this application also provide a computer-readable storage medium. This computer-readable storage medium stores a computer program. When the computer program is executed by a computer, it causes the computer to perform any of the methods provided in the above embodiments. The storage medium can be any available medium that a computer can access. By way of example and not limitation, a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage medium or other magnetic storage devices, or any other medium that can be used to carry or store program code in the form of instructions or data structures and that can be accessed by a computer.
[0205] Based on the above embodiments, this disclosure also provides a chip. This chip is used to read a computer program stored in a memory to implement any of the methods provided in the above embodiments.
[0206] Based on the above embodiments, embodiments of this disclosure provide a chip system. The chip system includes a processor for supporting a computer device in implementing the functions of the communication device involved in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. The chip system may include a chip, or it may include a chip and other discrete components.
[0207] Based on the above embodiments, embodiments of this disclosure provide an apparatus / chipset system including means (e.g., at least one processor) for implementing (or having implemented therein) the methods implemented by (or in connection with) the UE of this disclosure. The apparatus / chipset system may be a UE (i.e., a terminal device) or a module / component within a UE. Specifically, at least one processor may execute instructions stored in a computer-readable medium to implement the methods.
[0208] Based on the above embodiments, embodiments of this disclosure provide an apparatus / chipset system including means (e.g., at least one processor) for implementing (or implementing in) the methods implemented by (or in) a network device (e.g., a base station) of this disclosure. The apparatus / chipset system may be a network device or a module / component within a network device. Specifically, at least one processor may execute instructions stored in a computer-readable medium to implement the methods. In some aspects of this disclosure, a system is provided that includes at least one of means in (or at the UE) of this disclosure or in (or at the network device) of this disclosure.
[0209] It should be understood that any module, component, or device disclosing executable instructions herein may include or otherwise access one or more non-transitory computer / processor-readable storage media 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 disc read-only memory (CD-ROM), digital video disc or digital multifunction disc (i.e., DVD), Blu-ray disc™, or other optical storage devices; volatile and non-volatile, removable and non-removable media, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other storage technologies implemented in any method or technology. Any of these non-transitory computer / processor storage media 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.
[0210] Those skilled in the art will understand that embodiments of this disclosure can be provided as a method, system, or computer program product. Therefore, this disclosure can take the form of a purely hardware embodiment, a purely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can be in the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0211] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products provided herein. It should be understood that computer program instructions can be used to implement each process and / or block in the flowchart illustrations and / or block diagrams, as well as combinations of processes and / or blocks in the flowchart illustrations and / or block diagrams. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to generate a machine such that these instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate means for implementing a specific function in one or more processes in the flowchart and / or one or more blocks in the block diagram.
[0212] These computer program instructions may also be stored in a computer-readable storage medium capable of instructing a computer or other programmable data processing device to operate in a particular manner, thereby causing the instructions stored in the computer-readable storage medium to produce an article of writing including instruction means. The instruction means implements a specific function in one or more processes in a flowchart and / or one or more blocks in a block diagram.
[0213] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to perform a series of operations and steps on the computer or other programmable apparatus, thereby generating a computer-implemented process. Therefore, these instructions, which execute on a computer or other programmable apparatus, provide steps for implementing one or more processes in a flowchart and / or one or more boxes in a block diagram.
[0214] The schemes described in this disclosure are applicable to next-generation (e.g., sixth-generation, 6G or higher) networks, or traditional (e.g., 5G, 4G, 3G or 2G) networks.
[0215] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its scope. Therefore, this disclosure is intended to cover such modifications and variations, provided they fall within the scope of the claims of this disclosure and their equivalents. Although this disclosure has been described with reference to illustrative embodiments, this description is not intended to limit the disclosure. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of this disclosure, will be apparent to those skilled in the art upon reference to this specification. When two or more embodiments are combined, not all features in the embodiments to be combined are necessary for the combination.
[0216] 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, while embodiments are described primarily in the context of methods and apparatus, other implementations are contemplated as instructions stored in non-transitory computer-readable media, etc. Such media may store programs or instructions to perform any of the methods consistent with this disclosure.
Claims
1. A method, characterized in that, include: The terminal device obtains an indication of at least one angular direction; Signals are transmitted to non-terrestrial network devices using one of at least one beams associated with the at least one angular direction.
2. The method according to claim 1, characterized in that, Also includes: Receive one or more indications of one or more angular directions and their association with one or more beams; The one or more angular directions include the at least one angular direction, and the one or more beams include the at least one beam.
3. The method according to claim 2, characterized in that, Also includes: Activate the at least one beam associated with the at least one angular direction; Deactivate the residual beam associated with a residual angular direction different from the at least one angular direction. The one or more angular directions include the remaining angular directions, and the one or more beams include the remaining beams.
4. The method according to claim 3, characterized in that, The indication of the at least one angular direction is carried by one of the following: media access control (MAC) control element (CE) signaling, radio resource control (RRC) signaling, or downlink control information (DCI). The associated indication is carried in the RRC signaling.
5. The method according to any one of claims 1 to 4, characterized in that, The indication of the at least one angular direction indicates a plurality of angular directions in sequence, the sequence indicating the priority of the plurality of angular directions.
6. The method according to any one of claims 1 to 5, characterized in that, One of the at least one angular directions indicates the direction that applies to at least one of the following: Azimuth domain; Zenith angle; or Elevation angle domain.
7. The method according to any one of claims 1 to 6, characterized in that, The at least one angular direction includes multiple angular directions, the multiple angular directions include a first angular direction and a second angular direction, wherein the at least one beam includes a first beam associated with the first angular direction and a second beam associated with the second angular direction, and transmitting the signal using the one of the at least one beams includes: The signal is received using the first beam; Determine the quality degradation associated with the signal received using the first beam, wherein the first beam is associated with the outermost angular direction in a conical region constrained by the plurality of angular directions; Perform a beam switching from the first beam to the second beam.
8. The method according to claim 7, characterized in that, Also includes: The terminal device's capability information is transmitted, wherein the cone-shaped region is associated with the capability information.
9. The method according to claim 7, characterized in that, Determining the quality degradation associated with the signal includes at least one of the following: The reference signal received power (RSRP) of the signal is determined to be below a first threshold for a first duration. The reference signal received quality (RSRQ) of the signal is determined to be below a second threshold for a second duration. The signal-to-interference-plus-noise ratio (SINR) of the signal is determined to be below a third threshold for a third duration; or It is determined that the signal is received using the first beam for a fourth duration.
10. The method according to claim 9, characterized in that, Also includes: Receive a configuration that triggers the beam switching, wherein the configuration includes at least one of the following: The first threshold and the first duration of the RSRP; The second threshold and the second duration of the RSRQ; The third threshold and the third duration of the SINR; or The fourth duration in the outermost angular direction.
11. The method according to any one of claims 1 to 10, characterized in that, Also includes: Receive a second indication indicating one of the at least one angular directions. The use of one of the at least one beams to transmit the signal includes: The signal is transmitted using a beam associated with one of the at least one angular directions, wherein the one beam belongs to the at least one beam.
12. The method according to any one of claims 1 to 10, characterized in that, Also includes: Receive an indication of one of the at least one angular directions and an indication of correction for the one of the at least one angular directions. The use of one of the at least one beams to transmit the signal includes: The signal is transmitted using a beam associated with one of the at least one angular directions to which the correction has been applied, wherein the one beam belongs to the at least one beam.
13. The method according to any one of claims 1 to 10, characterized in that, Transmitting the signal using one of the at least one beams includes: Use at least one of the beams to detect the reference signal; Based on the detected reference signal, determine the beam with the strongest reference signal strength, wherein the beam belongs to the at least one beam; The signal is transmitted using the beam with the strongest reference signal strength.
14. The method according to any one of claims 1 to 13, characterized in that, The at least one angular direction includes multiple angular directions, and the method further includes: Receive an indication of a default angle direction, wherein the default angle direction belongs to the plurality of angle directions; Beam switching to the beam associated with the default angular direction is performed when at least one of the following is determined: The quality degradation associated with the signal received using a first beam in one of the plurality of angular directions, wherein the first beam is associated with the outermost angular direction in a conical region constrained by the plurality of angular directions; The terminal device transitions from RRC connection state to power-saving sleep mode; or The terminal device transitions from RRC connected state to idle mode.
15. The method according to claim 14, characterized in that, The default angular direction is associated with a time-domain and / or frequency-domain mode indicating the resource used to transmit the signal.
16. A method, characterized in that, include: A non-terrestrial network device transmits an indication of at least one angular direction, wherein the at least one angular direction is associated with at least one beam; Transmitting signals to a terminal device, wherein the signals are transmitted by the terminal device using one of the at least one beams.
17. The method according to claim 16, characterized in that, Also includes: Send one or more indications of one or more angular directions and their association with one or more beams; The one or more angular directions include the at least one angular direction, and the one or more beams include the at least one beam.
18. The method according to claim 17, characterized in that, The indication of the at least one angular direction is carried by one of the following: media access control (MAC) control element (CE) signaling, radio resource control (RRC) signaling, or downlink control information (DCI). The associated indication is carried in radio resource control (RRC) signaling.
19. The method according to any one of claims 16 to 18, characterized in that, The indication of the at least one angular direction indicates a plurality of angular directions in sequence, the sequence indicating the priority of the plurality of angular directions.
20. The method according to any one of claims 16 to 19, characterized in that, One of the at least one angular directions indicates the direction that applies to at least one of the following: Azimuth domain; Zenith angle; or Elevation angle domain.
21. The method according to any one of claims 16 to 20, characterized in that, The at least one angular direction includes multiple angular directions, and the method further includes: Sending a configuration to trigger beam switching, wherein the configuration includes at least one of the following: The first threshold and first duration of the reference signal received power (RSRP); The second threshold and the second duration of the reference signal received quality (RSRQ); The third threshold and third duration of the signal-to-interference-and-noise ratio (SINR); or The fourth duration of the outermost angular direction in the conical region constrained by the multiple angular directions.
22. The method according to claim 21, characterized in that, Also includes: The terminal device receives capability information, wherein the cone-shaped region is associated with the capability information.
23. The method according to any one of claims 16 to 22, characterized in that, Also includes: Send a second indication indicating one of the at least one angular directions. The terminal device transmits the signal using a beam associated with one of the at least one angular directions, wherein the one beam belongs to the at least one beam.
24. The method according to any one of claims 16 to 22, characterized in that, Also includes: Send an indication of one of the at least one angular directions and an indication of correction for the one of the at least one angular directions. The terminal device transmits the signal using a beam associated with one of the at least one angular directions to which the correction has been applied, wherein the one beam belongs to the at least one beam.
25. The method according to any one of claims 16 to 24, characterized in that, Also includes: Send an indication of a default angle direction, wherein the default angle direction belongs to the at least one angle direction.
26. The method according to claim 25, characterized in that, The default angular direction is associated with a time-domain and / or frequency-domain mode indicating the resource used to transmit the signal.
27. A terminal device, characterized in that, include: transceiver; The processor is communicatively coupled to the transceiver. The processor is used for: Obtain an indication of at least one angular direction associated with at least one beam; Signals are transmitted to non-terrestrial network devices using one of the at least one beams associated with the at least one angular direction.
28. A non-terrestrial network device, characterized in that, include: transceiver; The processor is communicatively coupled to the transceiver. The processor is used for: The transceiver transmits an indication of at least one angular direction, wherein the at least one angular direction is associated with at least one beam; Transmitting signals to a terminal device, wherein the signals are transmitted by the terminal device using one of the at least one beams.
29. A non-transitory computer-readable medium, characterized in that, It includes a computer program stored thereon, which, when executed on at least one processor, causes the at least one processor to perform the method according to any one of claims 1 to 23.
30. A chip, characterized in that, It includes at least one processing circuit for performing the method according to any one of claims 1 to 26.
31. A computer program product, characterized in that, It is tangibly stored on a computer-readable medium and includes computer-executable instructions that, when executed, cause the apparatus to perform the method according to any one of claims 1 to 26.