Method for timing advance indication and timing relationship indication for non-terrestrial networks

Abstract

Methods for timing advance indication and timing relationship indication for non-terrestrial networks are disclosed, where a method of implementing communication between a user equipment (UE) and a non-terrestrial network (NTN) is specifically described. The UE can be able to calculate a timing advance. The timing advance can be a differential or full timing advance. An offset value K offset may be indicated to the UE. offset may be used for timing relationship.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 022,085, filed May 8, 2020, and U.S. Provisional Patent Application No. 63 / 090,639, filed October 12, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] One or more aspects of embodiments of this disclosure relate to wireless communication networks, and more specifically to managing timing advance and offset values ​​for uplink transmissions in a wireless communication system. Background Technology

[0004] The demand for data communication to and from mobile communication devices is rising. Traditional mobile wireless communication networks are evolving into networks that can transmit more data over longer distances. The 3GPP standards organization is currently discussing new radio (NR) technologies for the next generation (e.g., 5G NR), and therefore, is submitting and considering changes to the current body of the 3GPP standards to evolve and finalize the 5G NR standard.

[0005] A method and system are disclosed from the perspective of user equipment (UE). Summary of the Invention

[0006] A method for enabling communication between a user equipment (UE) and a non-terrestrial network (NTN) includes: receiving satellite position data from the NTN at the UE; determining a satellite position at the UE based on the satellite position data; determining a UE position at the UE; calculating a first distance between the UE position and the satellite position at the UE; calculating a timing advance at the UE based on the first distance; and receiving a first K at the UE. offset And apply the timing advance and the first K at the UE. offset One or both of these can be used to configure the sending or receiving of communication with the NTN.

[0007] In the method, the satellite position data is ephemeris data or position data.

[0008] The method further includes: receiving gateway location data at the UE, and determining the gateway location at the UE based on the gateway location data.

[0009] In the method, the UE also calculates a second distance between the satellite location and the gateway location.

[0010] In the method, the UE further calculates the timing advance by dividing the first distance by the velocity to obtain a first propagation delay, dividing the second distance by the velocity to obtain a second propagation delay, summing the first propagation delay and the second propagation delay, and doubling the summation result, wherein the velocity is the speed of light in free space.

[0011] In the method, the timing advance is a full timing advance.

[0012] The method further includes: receiving reference point location data at the UE, and determining a reference point location at the UE based on the reference point location data, wherein the reference point location is on the feeder link.

[0013] In the method, the UE also receives a common timing advance.

[0014] In the method, the UE also calculates a third distance between the reference point location and the satellite location.

[0015] In the method, the UE further calculates the timing advance by dividing the first distance by the velocity to obtain a first propagation delay, dividing the third distance by the velocity to obtain a third propagation delay, summing the first propagation delay, the third propagation delay, and the common timing advance, and doubling the summation result, wherein the velocity is the speed of light in free space.

[0016] In the method, the timing advance is one of full timing advance and differential timing advance.

[0017] In the method described above, the reference point location is the satellite location.

[0018] The method further includes: receiving reference point location data at the UE, and determining a reference point location at the UE based on the reference point location data, wherein the reference point location is located in the cell where the UE is located.

[0019] In the method, the UE also receives a common timing advance.

[0020] In the method, the UE also calculates a fourth distance between the reference point location and the satellite location.

[0021] In the method, the UE further calculates differential timing advance by dividing the first distance by the velocity to obtain a first propagation delay, dividing the fourth distance by the velocity to obtain a fourth propagation delay, subtracting the fourth propagation delay from the first propagation delay, and doubling the subtraction result, wherein the velocity is the speed of light in free space.

[0022] In the method, the UE receives the second K in the common DCI format and / or MAC-CE format. offset And the second K offset It is a fixed number of bits.

[0023] In the method, the second K offset It is specific to the UE.

[0024] In the method, the second K offset In the transmission of license type 1 for configuration, the UE will transmit the second K... offset The offset obtained by multiplying by the number of symbols per time slot is added to the timing of licensed type 1 transmissions used for the configuration.

[0025] In the method, the second K offset In the transmission of license type 2 for configuration, the UE transmits via the second K... offset The license type 2 transmissions added to the configuration are scheduled via DCI to send the Physical Uplink Shared Channel (PUSCH).

[0026] In the method, the second K offset For use with a slot format indicator (SFI), wherein the slot format indicator is used to dynamically configure or reconfigure symbols or slots in a subframe, wherein the UE configures or reconfigures at least a second K slot after the uplink slot. offset The symbol or time slot at each time slot.

[0027] In the method, the second K offset Greater than or equal to the aforementioned timing advance.

[0028] In the method, the second K offset Timing used for PUSCH transmissions scheduled by DCI.

[0029] In the method, the second K offset Timing used for Channel State Information (CSI) transmission on PUSCH.

[0030] In the method, the second K offset Timing used for PUSCH transmissions scheduled by Random Access Response (RAR) licenses.

[0031] In the method, the second K offset Timing for Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) transmissions on the Physical Uplink Control Channel (PUCCH).

[0032] In the method, the second K offset Timing used for CSI reference resource transfer.

[0033] In the method, the second K offset Timing used for non-periodic SRS transmission.

[0034] A system for enabling communication between a user equipment (UE) and a non-terrestrial network (NTN), the system being configured to: receive satellite position data from the NTN at the UE; determine a satellite position at the UE based on the satellite position data; determine a UE position at the UE; calculate a first distance between the UE position and the satellite position at the UE; calculate a timing advance at the UE based on the first distance; and receive a first K... offset And apply the timing advance and the first K at the UE. offset One or both of these can be used to configure the sending or receiving of communication with the NTN.

[0035] The system is also configured to receive reference point location data at the UE and determine the reference point location based on the reference point location data.

[0036] The system is also configured to receive common timing advances at the UE.

[0037] In the system, the UE also calculates a third distance between the reference point location and the satellite location.

[0038] In the system, the UE further calculates the timing advance by dividing the first distance by the velocity to obtain a first propagation delay, dividing the third distance by the velocity to obtain a third propagation delay, summing the first propagation delay, the third propagation delay, and the common timing advance, and doubling the summation result, wherein the velocity is the speed of light in free space.

[0039] In the system, the timing advance is one of full timing advance and differential timing advance.

[0040] In this system, the reference point position is the satellite position.

[0041] The system is also configured to receive a second K in Group Common DCI format and / or MAC-CE format at the UE. offset And the second K offset It is a fixed number of bits. Attached Figure Description

[0042] These and other features and advantages of this disclosure will be appreciated and understood by referring to the specification, claims and drawings, wherein:

[0043] Figure 1 This is a schematic diagram of a network according to an embodiment of the present disclosure;

[0044] Figure 2 This is a schematic diagram of full timing advance according to an embodiment of the present disclosure;

[0045] Figure 3 This is a schematic diagram of differential timing advance according to an embodiment of the present disclosure;

[0046] Figure 4 This is a schematic diagram of a non-terrestrial network (NTN) according to an embodiment of the present disclosure;

[0047] Figure 5 This is a schematic diagram of a process for calculating timing advance according to an embodiment of the present disclosure;

[0048] Figure 6 This is a schematic diagram of timing advance according to an embodiment of the present disclosure;

[0049] Figure 7 This is a schematic diagram of an NTN according to an embodiment of the present disclosure;

[0050] Figure 8 This is a schematic diagram of a process for calculating timing advance according to an embodiment of the present disclosure;

[0051] Figure 9 This is a schematic diagram of an NTN according to an embodiment of the present disclosure;

[0052] Figure 10 This is a schematic diagram of differential timing advance according to an embodiment of the present disclosure;

[0053] Figure 11 This is a schematic diagram of differential timing advance according to an embodiment of the present disclosure;

[0054] Figure 12 This is a schematic diagram of a process for calculating timing advance according to an embodiment of the present disclosure;

[0055] Figure 13 This is a schematic diagram of timing offset according to an embodiment of the present disclosure;

[0056] Figure 14 This is a schematic diagram of a group common downlink control information (DCI) format for receiving offset values ​​according to an embodiment of the present disclosure;

[0057] Figure 15 This is a schematic diagram of a Media Access Control-Control Element (MAC-CE) format for receiving offset values ​​according to an embodiment of the present disclosure;

[0058] Figure 16 This is a schematic diagram of offset timing for configuring license type 1 according to an embodiment of the present disclosure;

[0059] Figure 17 This is a schematic diagram of offset timing based on the timing of the slot format indicator (SFI) for DCI format scheduling, according to an embodiment of the present disclosure; and

[0060] Figure 18 It is configured to manage timing advance and K according to some embodiments offset An example of a system. Detailed Implementation

[0061] The detailed description set forth below with reference to the accompanying drawings is intended as a description of exemplary embodiments of networks provided according to this disclosure, and is not intended to represent the only form in which this disclosure may be constructed or utilized. This description, in conjunction with the illustrated embodiments, illustrates the features of this disclosure. However, it should be understood that the same or equivalent functionality and structure may be implemented by different embodiments that are also intended to be included within the scope of this disclosure. As indicated elsewhere herein, the same element numbers are intended to indicate the same elements or features.

[0062] Figure 1 This is a schematic diagram of a network according to an embodiment of the present disclosure. (Refer to...) Figure 1 In some embodiments, a network 100 is shown. Network 100 may be a multiple access wireless communication system supporting broadcast services, such as a non-terrestrial network (NTN). Network 100 may be designed to support one or more standards, such as the 3rd Generation Partnership Project (3GPP). Network 100 may include user equipment (UE) 101, satellite 102, and gateway 103.

[0063] UE 101 may be able to send, receive, store, and process data. UE 101 may be a transceiver system, such as a mobile device, laptop computer, or other device.

[0064] Satellite 102 may be a spaceborne or airborne platform capable of sending and receiving data from UE 101 and gateway 103. Satellite 102 may communicate with UE 101, wherein satellite 102 may be able to send and receive data from UE 101 via service link 104. Service link 104 may include uplink (UL) and downlink (DL) data transmission.

[0065] Gateway 103 may be an antenna capable of transmitting and receiving data from satellite 102. Gateway 103 may be connected to or associated with a base station or logical radio node (such as a gNodeB (gNB) base station, not shown). In one embodiment, actions performed by the gNB (such as scheduling and coordination) may be referred to as being performed by gateway 103; however, it is understood that the gNB may execute commands to transmit uplink data or receive downlink data, and gateway 103 may transmit data for the gNB and also receive data for the gNB. Gateway 103 may communicate with satellite 102 via feeder link 105. Feeder link 105 may include UL and DL data transmission. In one embodiment, UE 101, satellite 102, and gateway 103 may support subcarrier spacing of 15 kHz, 30 kHz, 60 kHz, 120 kHz, or 240 kHz; however, other spacings may be supported.

[0066] Cell 106 can be a geographical area where UE 101 and other UEs (not shown) can communicate with satellite 102. The size of cell 106 can vary depending on the position of satellite 102 relative to the Earth. For example, in one embodiment, geostationary equatorial orbit (GEO) satellites can allow for larger cells 106, with diameters ranging from 200 km to 3500 km. Medium Earth orbit (MEO) and low Earth orbit (LEO) satellites can have smaller associated cell 106 sizes. Furthermore, the distance of satellite 102 from the Earth can affect the transmission time for sending and receiving data between UE 101 and satellite 102, and between satellite 102 and gateway 103. In one embodiment, the round-trip delay (RTD) can be as high as 560 ms, 180 ms, and 60 ms for GEO, MEO, and LEO satellite systems, respectively. The RTD can be twice the propagation delay between UE 101 and gateway 103. UE101 can handle these RTDs by utilizing modifications to the timing aspects of the physical layer or higher in the Open Systems Interconnection (OSI) model and the Timing Advance (TA) mechanism.

[0067] In operation, UE 101 can send (UL) data to satellite 102 or receive (DL) data from satellite 102, and satellite 102 can send (UL) data to gateway 103 or receive (DL) data from gateway 103, as will be described in more detail below.

[0068] Figure 2 This is a schematic diagram of full timing advance according to an embodiment of the present disclosure. (Refer to...) Figure 2This illustrates full timing advance 200 for downlink and uplink to a base station (such as a gNB) via gateway 103. Full timing advance 200 can be a type of NR timing offset between downlink and uplink transmissions, which will be described in more detail below. Subframe 201 can include multiple data subframes. Subframe 202 can be a subframe within subframe 201. Subframe 202 can include data transmitted within a time period. In one embodiment, subframe 202 can have a duration of 1 ms, but other durations can be used. A subframe can include one or more time slots, which can vary with subcarrier spacing. A time slot can include one or more resource blocks, which can include symbols and subcarriers. A symbol can be a time division within a time slot, and a subcarrier can be a frequency. A resource element can be a time unit and a frequency within a resource block. A basic time unit T can exist. C It can be defined as T C =1 / (15,000×2,048)s=32.6 ns, which can be used to determine the synchronization between UE 101, satellite 102, and gateway 103. In another embodiment, T C It can be defined as T C =1 / (480,000×4096)s, however, other definitions may be used. In one embodiment, a 15kHz subcarrier spacing may have one time slot per subframe, a 30kHz subcarrier spacing may have two time slots per subframe, a 60kHz subcarrier spacing may have four time slots per subframe, and so on for 120kHz and 240kHz.

[0069] Subframe 201 may have a different subframe structure, such as Type 1 for Frequency Division Duplex (FDD) or Type 2 for Time Division Duplex (TDD). Each subframe may have the same or different durations and can be used to transmit and receive data between base station / gateway 103 and UE 101. Subframes may have a reference subframe number and a timestamp associated with the start of each subframe. This information can be used for coordination of downlink and uplink transmissions.

[0070] In another embodiment, subframe 201 may be a frame that can include multiple data frames. In one embodiment, the duration of a frame may be 10 ms, and it may include 10 subframes, each lasting 1 ms; however, the duration of the frame and the number of subframes may vary. The frame may have a frame number, which may be an index value and may be referred to as a System Frame Number (SFN). In one embodiment, the index value of the SFN may be between 0 and 1023, meaning there may be 1024 SFNs, which may repeat after reaching the last index value of 1023.

[0071] Subframe 202 within subframe 201 may have a length n and may contain elements to be specified. Figure 1 Data transmitted between gateway 103 and UE 101. The base station (not shown) can transmit data via gateway downlink time 203. Figure 1 Gateway 103 transmits subframe 202 to UE 101's downlink. In one embodiment, gateway downlink time 203 can be a time, or it can be a timeslot number or other identifier. Subframe 202 can be received by UE downlink time 204 after propagation delay 205, wherein propagation delay 205 can be the time difference between when subframe 202 is transmitted at base station / gateway 103 at gateway downlink time 203 and when subframe 202 is received at UE 101 at UE downlink time 204.

[0072] Similarly, UE 101 may send an uplink subframe 206 to base station / gateway 103 at UE uplink time 207, which can be received at gateway uplink time 208. There may be a propagation delay 205 between UE uplink time 207 and gateway uplink time 208.

[0073] In the case of full timing advance, the gateway downlink time 203 and the gateway uplink time 208 can be aligned. That is, within a certain range, the gateway downlink time 203 can be the same time as the gateway uplink time 208. In one embodiment, this range can be T as previously defined. C However, other values ​​can be used. Data transmitted from the downlink of gateway 103 can be synchronized with data received from the uplink of UE 101. Timing advance 209 can be twice the propagation delay 205, and full timing advance can be allowed. Timing advance can be a negative offset between UE downlink time 204 and UE uplink time 207. Timing advance can be used to ensure synchronization of downlink subframes and uplink subframes. In one embodiment, full timing advance or full timing advance compensation can achieve synchronization of downlink and uplink transmission timing between UE 101 and gateway 103.

[0074] In one embodiment, for a 15kHz subcarrier spacing, the timing advance 209 can be as high as 2ms, which allows for a cell diameter of 300km. However, in NTN, due to the very high altitude of the satellite, such as Figure 1 As described, the RTD or timing advance 209 can range from hundreds of milliseconds to seconds. In one embodiment, the timing advance 209 is twice the propagation delay 205; however, the timing advance 209 can be larger. The timing advance 209 can be large compared to the duration of a subframe (such as subframe 202). In one embodiment, if the duration of a subframe is 1 ms, the timing advance 209 can be 560 ms; however, other values ​​can be used.

[0075] Figure 3 This is a schematic diagram of differential timing advance according to an embodiment of the present disclosure. (Refer to...) Figure 3 It shows the method for connecting to via Figure 1 The differential timing advance 300 is used for the downlink and uplink differential timing advance of the base station (such as a gNB) of gateway 103. The differential timing advance 300 can be a type of NR timing offset between downlink and uplink transmissions. Subframe 301 can include multiple data subframes. Each subframe can have the same duration or different durations and can be used for... Figure 1 Data is transmitted and received between the base station / gateway 103 and the UE 101. In another embodiment, subframe 301 may include multiple data frames.

[0076] Subframe 302 may be within subframe 301. The base station (not shown) may be located via gateway downlink time 303. Figure 1 Gateway 103 sends downlink subframe 302 to UE 101 and can receive subframe 302 at UE downlink time 304. Propagation delay 305 can be the time difference between the transmission of subframe 302 at base station / gateway 103 at gateway downlink time 303 and the reception of subframe 302 at UE downlink time 304.

[0077] Similarly, UE 101 may send an uplink subframe to base station / gateway 103 at UE uplink time 307, which can be received at gateway uplink time 308. There may be a propagation delay 309 between UE uplink time 307 and gateway uplink time 308.

[0078] In addition, a differential timing advance of 306 may exist, where the differential timing advance of 306 can be the difference between the UE uplink time 307 and the UE downlink time 304. The common timing advance offset of 310 can be the sum of the propagation delay 305 and the propagation delay 309 minus the differential timing advance of 306.

[0079] In one embodiment, differential timing advance can be a negative offset between the UE downlink time 304 and the UE uplink time 307. Differential timing advance can be used to ensure that gateway 103 can send downlink subframes to UE 101 at a first time and receive uplink subframes from UE 101 at a second time different from the first time. Gateway 103 may be able to receive uplink subframes from multiple UEs (not shown) at the second time; that is, the uplink subframes sent to gateway 103 are synchronized.

[0080] Using differential timing advance, the common timing advance offset of 310 is not twice the propagation delay of 305, as mentioned above. Figure 2 This is described for full timing advance. In some embodiments, differential timing advance 306 may be specific to each UE 101. A common timing advance offset 310 may exist between the gateway downlink time 303 and the gateway uplink time 308. The value of the common timing advance offset 310 may be as large as 540 ms, depending on how large the round-trip delay is and how small the UE-specific differential timing advance 306 is; however, other values ​​may be used.

[0081] In the previously described full timing advance 200 and differential timing advance 300 methods, additional complexity can be utilized to manage the scheduling and timing of uplink and downlink subframes. New radio physical layer timing relationships can be enhanced to manage timing advance offsets for downlink and uplink timing for UE 101. Timing relationships can be for transmission or reception of communications and can be with the NTN. UE 101 can use timing advance to configure timing relationships. For 4-step and 2-step random access processing, the new radio timing advance can be estimated by the network via MSG1 or msgA steps, respectively. However, additional methods for timing advance estimation can be described previously and below.

[0082] A timing advance command (or indication) can be sent to UE 101. For example, for NTN, UE 101 may have Global Navigation Satellite System (GNSS) capability. That is, UE 101 may know its own geographic location or position. The geographic location data for satellite 102 may also be known (or made known) by UE 101. Satellite 102 may send satellite position data to UE 101, which may be ephemeris data or any other type of position data. Ephemeris data may include the orbital position of satellite 102, including information such as week number, satellite accuracy, health status, data age, satellite clock correction factor, and other orbital parameters. In another embodiment, satellite 102 may send coordinate data to UE 101.

[0083] UE 101 may be able to use its own geographic location data and ephemeris data or coordinate data from satellite 102 to calculate timing advance 209 or common timing advance offset 310, which will be described in more detail below. UE 101 may be able to use satellite position data of satellite 102 and position data of UE 101 to calculate a first distance between UE 101 and satellite 102. A first propagation delay can be calculated from the first distance by dividing the first distance by the velocity. In one embodiment, the velocity may be the speed of light in free space. UE 101 may also be able to use satellite position data of satellite 102 and gateway position data of gateway 103 to calculate a second distance between satellite 102 and gateway 103. A second propagation delay can be calculated from the second distance by dividing the second distance by the velocity. In one embodiment, the velocity may be the speed of light in free space. This information will be described in more detail below and can be used to calculate full timing advance or differential timing advance. In another embodiment, UE 101 may receive first and second propagation delay data and may use it to calculate full timing advance or differential timing advance.

[0084] Depending on the location of satellite 102 (LEO, MEO, or GEO), the round-trip propagation delay can be smaller or larger. UE 101 may have a flexible timing advance mechanism that can adapt to satellite 102 (LEO, MEO, or GEO) deployment scenarios.

[0085] Figure 4 This is a schematic diagram of a non-terrestrial network (NTN) according to an embodiment of the present disclosure. (Refer to...) Figure 4 An example NTN communication architecture 400 is illustrated, wherein the NTN communication architecture 400 may be an NTN communication architecture 100 with an additional UE 401. UE 401 may be in cell 106 and may communicate with satellite 102 via serving link 402. UE 101 may receive information (including GNSS data from UE 101, satellite 102, and reference point 405) to calculate and indicate full timing advance. In one embodiment, reference point 405 may be the geographic location of gateway 103. The distance between satellite 102 and reference point 405 may be distance 406, which may be represented as d. g,s The distance between UE 101 and satellite 102 can be a distance of 404, which can be represented as d. s,u Similarly, the distance between UE 401 and satellite 102 can be distance 403, which can be represented as d. s,u2 .

[0086] The geographic location information of reference point 405 can be in the form of Earth-centered Earth-fixed (ECEF) coordinates, or it can be any other form of coordinates that provides the relative position of reference point 405 with respect to a fixed origin, wherein the fixed origin is known to both the gNB of gateway 103 and UE 101. The geographic location information of reference point 405 can also be in the form of an index of a position in a table pointing to a set of position information for all predetermined reference points. UE 101 may additionally have ephemeris data for satellite 102, which can be in ECEF Cartesian form and may include x, y, and z coordinates as a function of time. UE 101 may be able to calculate the position of satellite 102 using any interpolation technique.

[0087] UE 101 can calculate the first propagation delay between UE 101 and satellite 102 by calculating distance 404 and dividing distance 404 by velocity. In one embodiment, velocity can be the speed of light c in free space, and the first propagation delay can be expressed as T. s,u This can be equation T. s,u =d s,u / c. Distance 404 can be calculated by UE 101 using the geographic location data of UE 101 and satellite 102. Similarly, UE 101 can calculate the second propagation delay (which can be represented as T) between satellite 102 and reference point 405 by calculating distance 406 and dividing distance 406 by the speed of light c in free space. g,s This could be equation T. g,s =d g,s / c. The distance 404 can be calculated by UE 101 using the geographic location data of satellite 102 and reference point 405. The total timing advance TA can be calculated as T by UE 101. g,s and T s,u Twice the sum of, or TA = 2 (T g,s +T s,u In one embodiment, this could be... Figure 2 The timer is set 209 minutes in advance.

[0088] UE 401 can perform similar calculations. UE 401 can calculate the propagation delay between UE 401 and satellite 102 by calculating distance 403 and dividing distance 403 by velocity. In one embodiment, the velocity can be the speed of light c in free space, and the propagation delay can be expressed as T. s,u2 This can be equation T. s,u2 =d s,u2 / c. Distance 403 can be calculated by UE 401 using the geographic location data of UE 401 and satellite 102. Similarly, UE 401 can calculate the propagation delay (which can be expressed as T) between satellite 102 and reference point 405 by calculating distance 406 and dividing distance 406 by the speed of light c in free space. g,s This could be equation T. g,s =d g,s / c. The distance 403 can be calculated by UE 401 using the geographic location data of satellite 102 and reference point 405. The total timing advance TA can be calculated as T by UE 401. g,s and T s,u2 Twice the sum of, or TA = 2 (T g,s +T s,u2 Other UEs (not shown) in cell 106 can perform similar calculations.

[0089] As described in 3GPP TS 38.213 v16.0.0 “Physical layer procedures for control (Revision 16)”, this can be achieved by using offset number N. TA,offset and T C Convert the subframe number to a time value. N can be calculated by advancing the total timing TA and the offset. TA,offset ×Tc are added together to calculate the uplink subframe number used for transmission from UE 101 to satellite 102. For simplicity, N can be used in the following description. TA,offset Set to 0.

[0090] Figure 5 This is a schematic diagram of a process for calculating timing advance according to an embodiment of the present disclosure. (Refer to...) Figure 5 , showed Figure 1 The process of UE 101 calculating the timing in advance and indicating the value to gateway 103 is shown in Figure 500.

[0091] Processing step 501 may involve UE 101 receiving geographic location data of UE 101 and geographic location data of reference point 405. The geographic location data of UE 101 may be the UE's location. In some embodiments, the reference point may be location data and may be located at gateway 103. UE 101 may also receive ephemeris data from satellite 102, which may be satellite location data.

[0092] Processing 502 can be UE 101 calculating the position of satellite 102 from satellite position data.

[0093] Processing 503 can be used by UE 101 to determine the first distance d between UE 101 and satellite 102. s,uand the second distance d between satellite 102 and the reference point at gateway 103 g,s .

[0094] Processing 504 can be used by UE 101 to determine the second propagation delay T between satellite 102 and the reference point at gateway 103. g,s , or T g,s =d g,s / c, where c is the velocity. In one embodiment, the velocity can be the speed of light in free space. UE 101 can determine the first propagation delay T between UE 101 and satellite 102. s,u It can be T s,u =d s,u / c. UE 101 can also calculate the timing advance TA as the propagation delay T. g,s and T s,u Twice the sum of, or TA = 2 (T g,s +T s,u ).

[0095] Processing option 505 allows UE 101 to pre-indicate data to gateway 103 using a timing mechanism. The uplink subframe number used to send data from UE 101 can be specified in TA+N. TA,offset ×Tc begins, which can occur before the start of the corresponding downlink subframe at UE 101, such as... Figure 2 As shown, the UE uplink time 207 occurs before the start of the corresponding gateway downlink time 203. In one embodiment, as... Figure 2 As described herein, UE 101 can use full timing advance. In another embodiment, as... Figure 3 As described, UE 101 can use differential timing advance.

[0096] Figure 6 This is a schematic diagram illustrating timing advance according to an embodiment of the present disclosure. (Refer to...) Figure 6 An example embodiment of full timing advance 600 for two UEs with different propagation delays is shown. Gateway / gNB downlink subframe 601 may be transmitted by gateway 103 at gateway downlink time 602 and may be received by a first UE (UE 1) at UE 1 downlink time 603. The first UE may be as follows: Figure 4The UE 101 shown may have a UE 1 propagation delay 604, which can be the difference between the UE 1 downlink time 603 and the gateway downlink time 602. UE 101 may transmit uplink subframe 606 at UE 1 uplink time 607, whereby uplink subframe 606 can be received by gateway 103 at uplink time 608. In one embodiment, utilizing full timing advance, uplink time 608 may be approximately the same as gateway downlink time 602. The UE 1 propagation delay 604, previously described as the difference between UE 1 downlink time 603 and gateway downlink time 602, can be approximately equal to the difference between uplink time 608 and UE 1 uplink time 607. In one embodiment, the UE 1 timing advance 605 can be approximately twice the UE 1 propagation delay 604, and can be the round-trip time between sending downlink data from gateway 103 to UE 101 and sending uplink data from UE 101 to gateway 103.

[0097] Furthermore, gateway 103 can send gateway / gNB downlink subframe 601 at gateway downlink time 602, and the second UE (UE 2) can receive gateway / gNB downlink subframe 601 at UE 2 downlink time 609. UE 2 can be... Figure 4 UE 401.

[0098] There may be a UE 2 propagation delay 610, which can be the difference between the UE 2 downlink time 609 and the gateway downlink time 602. UE 401 may transmit uplink subframe 612 at UE 2 uplink time 613, and gateway 103 may receive uplink subframe 612 at uplink time 614. In one embodiment, utilizing full timing advance, uplink time 614 may be approximately the same as gateway downlink time 602 and uplink time 608. The UE 2 propagation delay 610 (previously described as the difference between UE 2 downlink time 609 and gateway downlink time 602) may be approximately equal to the difference between uplink time 614 and UE 2 uplink time 613. In one embodiment, the UE 2 timing advance 611 can be approximately twice the UE 2 propagation delay 610, and can be the round-trip time between sending downlink data from gateway 103 to UE 401 and sending uplink data from UE 401 to gateway 103.

[0099] Figure 7 This is a schematic diagram of an NTN according to an embodiment of the present disclosure. (Refer to...) Figure 7 It shows the method of using Figure 1The NTN communication architecture 700 uses a reference point on feeder link 105 for timing advance. UE 701 can... Figure 1 In cell 106 with UE 101. UE 701 may have a serving link 702, wherein the serving link 702 may have a distance 708 between UE 701 and satellite 102. Feeder link 105 may have a reference point 704, wherein the reference point 704 may be any point on feeder link 105 between satellite 102 and gateway 103. Distances 706 and 703 may exist, wherein distance 706 may be the distance between satellite 102 and reference point 704 (which may be referred to as the third distance), and distance 703 may be the distance between reference point 704 and gateway 103. Distance 703 may have an associated common timing advance T. common The common timing advance can be a common timing advance between all UEs in cell 106 and the associated gateway 103. In one embodiment, reference point 705 can be a special case of reference point 704, where the reference point is satellite 102 itself. In another embodiment, reference point 704 can be a point between satellite 102 and gateway 103.

[0100] In one embodiment, the network may send or indicate information to UE 101 to calculate timing advance. UE 101 may receive GNSS data from UE 101, satellite 102, and reference point 704. Furthermore, UE 101 may also receive common timing advance T. common .like Figure 7 As described in the text, the distance between UE 101 and satellite 102 can be a distance of 707, which can be expressed as d. s,u The distance 706 (the distance between satellite 102 and reference point 704) can be represented as d. r,s The geographic location information of reference point 704 can be in the form of ECEF coordinates or any other form of coordinates that provides the relative position of reference point 704 with respect to a fixed origin, where the fixed origin is known to both the network and UE 101. The geographic location information of reference point 704 can also be in the form of an index to a position in a table pointing to location information of a set of all predetermined reference points. UE 101 may additionally have ephemeris data for satellite 102, which can be in ECEF Cartesian form and may include x, y, and z coordinates as a function of time. UE 101 may be able to calculate the position of satellite 102 using any interpolation technique.

[0101] UE 101 can calculate the propagation delay between UE 101 and satellite 102 by calculating the distance 707 and dividing the distance 707 by the velocity. In one embodiment, the velocity can be the speed of light c in free space, and the propagation delay can be expressed as T. s,u This can be equation T.s,u =d s,u / c. The distance 707 can be calculated by UE 101 using the geographic location data of UE 101 and satellite 102.

[0102] Similarly, UE 101 can calculate the propagation delay (which can be expressed as T) between satellite 102 and reference point 704 by calculating distance 706 and dividing distance 706 by the speed of light c in free space. r,s This could be equation T. r,s =d r,s / c, and can be referred to as the third propagation delay.

[0103] The distance 706 can be calculated by UE 101 using the geographic location data of satellite 102 and reference point 704. The total timing advance TA can be calculated as T by UE 101. r,s T s,u and T common Approximately twice the sum, or TA = 2(T r,s +T s,u +T common In one embodiment, this could be... Figure 6 The timer should be set 605 minutes in advance.

[0104] In another embodiment, a reference point 704, which could be anywhere between satellite 102 and gateway 103 on feeder link 105, can be replaced by reference point 705, wherein reference point 705 can be satellite 102 itself. Because d r,s =0, so this could be T r,s The special case where =0. In this case, the calculated total timing advance will be T. s,u and T common Twice the sum of, or TA = 2 (T s,u +T common As previously mentioned, the uplink subframe number used to transmit from UE 101 can be prefixed with TA+N before the start of the corresponding downlink subframe to UE 101. TA,offset ×Tc starts; however, for simplicity, this value can be ignored in the diagram. For example, UE 1's uplink time of 607 can be... Figure 6 The corresponding gateway downlink time 602 occurred before that.

[0105] Figure 8 This is a schematic diagram of a process for calculating timing advance according to an embodiment of the present disclosure. (Refer to...) Figure 8 This could be used to utilize, for example Figure 7 The NTN architecture 700 shown is used to calculate and instruct the timing advance processing diagram for UE 101. Unlike previous timing advance calculations, this timing advance calculation can utilize... Figure 7 Reference point 704 and public time advance.

[0106] Processing 801 may involve UE 101 receiving its own geographic location data, satellite 102's ephemeris data, reference point 704's geographic location data, and common timing advance. In some embodiments, if satellite 102 is selected as the reference point, UE 101 may receive geographic location or ephemeris data from reference point 705 instead of reference point 704. In some embodiments, reference point 704 may be on the path of feeder link 105 between satellite 102 and gateway 103.

[0107] Processing 802 can be used by UE 101 to calculate the geographical location of satellite 102 using ephemeris data of satellite 102.

[0108] Processing 803 can be used by UE 101 to determine the distance d between UE 101 and satellite 102. s,u And the distance d between satellite 102 and reference point 704 r,s In some embodiments, if satellite 102 is used as reference point 705, UE 101 may only determine the distance between UE 101 and satellite 102.

[0109] Processing 804 can involve UE 101 determining the differential timing advance, and then determining the full timing advance TA. UE 101 can calculate the propagation delay T between UE 101 and satellite 102. s,u Among them, the propagation delay T s,u It can be distance d s,u Divide by velocity. In one embodiment, velocity can be the speed of light c in free space, or T s,u =d s,u / c. UE 101 can determine the propagation delay T between satellite 102 and reference point 704. r,s Among them, the propagation delay T r,s It can be distance d r,s Divide by speed c, or T r,s =d r,s / c. UE 101 can calculate TA as T r,s T s,u and T common Twice the sum, or TA = 2 (T r,s +T s,u +T common ).

[0110] Processing 805 may involve UE 101 sending or indicating data to gateway 103 using full timing advance TA. In one embodiment, UE 101 may apply full timing advance to uplink subframes, where, as described above, TA = 2(Tr,s +T s,u +T common In one embodiment, satellite 102 can be used as reference point 705, and T r,s =0. The geographic location data of satellite 102 extracted from the ephemeris data is the same as the geographic location data of reference point 705, and TA=2 (T s,u + T common The uplink subframe number used to send data from UE101 to gateway 103 can be TA+N. TA,offset ×Tc, where the uplink subframe number can be sent before the start of the corresponding downlink subframe at UE 101. This can be... Figure 6 As shown in the figure, for simplicity, N TA,offset =0.

[0111] Figure 9 This is a schematic diagram of an NTN according to an embodiment of the present disclosure. (Refer to...) Figure 9 This could be an example NTN communication architecture 900 for timing advance using a reference point 901 on the trajectory of satellite 102. Unlike previous examples, in this example, the reference point 901 can be anywhere with which satellite 102 can communicate. In one embodiment, the reference point 901 can be within a geographic area of ​​cell 106. The reference point 901 may have a distance d. r,s , where the distance d r,s This could be the distance between reference point 901 and satellite 102. A common timing advance of 903 T is possible. common Public time 903 T common This could be a timing advance between satellite 102 and gateway 103. As previously described, UE 101 can receive geographic location data for gateway 103 and can receive ephemeris data from satellite 102, wherein UE 101 can use the ephemeris data to calculate the geographic location data of satellite 102. UE 101 may be able to calculate distance 902, wherein distance 902 can be the distance d between reference point 901 and satellite 102. r,s This distance can be referred to as the fourth distance. Additionally, UE 101 may be able to calculate distance 904, where distance 904 can be the distance d of the service link 104 or the path between UE 101 and satellite 102. s,u .

[0112] After receiving the geographic location data of reference point 901, the ephemeris data of satellite 102, and the common timing advance 903, UE 101 may be able to calculate the propagation delay T between reference point 901 and satellite 102. r,s (This could be the fourth propagation delay) and the propagation delay T between UE 101 and satellite 102. s,uThese propagation delays can be calculated by dividing the distance by the speed of light c in free space. Therefore, T r,s =d r,s / c, and T s,u =d s,u / c. UE 101 can pre-calculate differential timing as T. s,u With T r,s Twice the difference between them, or TA=2(T) s,u -T r,s ).

[0113] Figure 10 This is a schematic diagram of differential timing advance according to an embodiment of the present disclosure. (Refer to...) Figure 10 It shows the method for connecting to via Figure 1 The differential timing advance 1000 is used for the downlink and uplink of the base station (such as a gNB) of the gateway 103. In one embodiment, the differential timing advance 1000 may utilize NTN architecture 900; however, it may also utilize other NTN architectures, such as NTN architecture 700, NTN architecture 400, NTN architecture 100, or other NTN architectures not shown.

[0114] Subframe 1001 may include multiple data subframes. Each subframe may have the same number of bits or a different number of bits, and can be used to transmit data via... Figure 1 Data is sent and received between the base station of gateway 103 and UE 101.

[0115] Subframe 1002 may be within subframe 1001. In one embodiment, subframe 1002 may transmit downlink data from gateway 103 to UE 101 at gateway downlink time 1003, and UE 101 may receive the downlink data at UE downlink time 1004. A downlink propagation delay 1005 may exist, wherein the downlink propagation delay 1005 may be the difference between UE downlink time 1004 and gateway downlink time 1003.

[0116] Furthermore, UE 101 may send subframe 1006 to the uplink of gateway 103 at UE uplink time 1007. Subframe 1006 may arrive at gateway 103 at gateway uplink time 1008 with uplink propagation delay 1010. In one embodiment, uplink propagation delay 1010 may be approximately the same as downlink propagation delay 1005. UE uplink time 1007 can be determined by subtracting differential timing advance 1009 from UE downlink time 1004. Differential timing advance 1009 may be different for each UE 101 used, or it may be the same for two or more UEs. In one embodiment, differential timing advance 1009 may be as follows: Figure 9 As described in the text, it is calculated as TA=2 (T s,u -T r,s However, other differential timing methods can be used to calculate in advance.

[0117] In one embodiment, to calculate the differential timing advance 1009, information about the propagation delay T can be broadcast in cell 106. r,s Information and will be about the propagation delay T r,s The information is sent to all UEs in cell 106. Broadcasting can be performed via System Information Block (SIB), Master Information Block (MIB), or any other method. Regarding the propagation delay T... r,s The information can be absolute time or can be normalized to T. C , such as N r,s =T r,s / T C UE 101 can determine the uplink subframe number to be sent to gateway 103, wherein the uplink subframe number can be T s,u +(N) r,s +N TA,offset )×T C And it can be done before the start of the corresponding downlink subframe at UE 101. The uplink subframe number can be sent at UE uplink time 1007. In one embodiment, all uplink subframes from UEs in cell 106 can be transmitted via 2(T common +T r,s The delay of ) reaches gateway 103, of which 2 (T) common +T r,s The common timing advance 1011 can be used. The common timing advance 1011 allows gateway 103 to receive all uplink transmissions from all UEs in cell 106 at the same gateway uplink time 1008. Therefore, for each UE in cell 106, there can be different differential timing advances 1009; however, each uplink transmission for each UE in cell 106 can arrive at gateway 103 simultaneously.

[0118] Figure 11 This is a schematic diagram of differential timing advance according to an embodiment of the present disclosure. (Refer to...) Figure 11 This shows the route to the two UEs via... Figure 1 A timing diagram 1100 for differential timing advance of the downlink and uplink of the base station (such as a gNB) of gateway 103. In one embodiment, timing diagram 1100 may utilize NTN architecture 900; however, other NTN architectures may also be used. Subframe 1101 may include multiple data subframes. Each subframe may be the same number of bits or a different number of bits and can be used for differential timing advance of the downlink and uplink of the base station (such as a gNB) of gateway 103. Figure 1Data is sent and received between the base station of gateway 103 and UE 101.

[0119] Subframe 1102 may be within subframe 1101. In one embodiment, subframe 1102 may transmit downlink data from gateway 103 to UE 101 at gateway downlink time 1103, and UE 101 may receive the data at UE 1 downlink time 1104. A UE 1 downlink propagation delay 1105 may exist, wherein the UE 1 downlink propagation delay 1105 may be the difference between UE 1 downlink time 1104 and gateway downlink time 1103.

[0120] Furthermore, UE 101 may transmit UE 1 subframe 1106 to the uplink of gateway 103 at UE 1 uplink time 1107. UE 1 subframe 1106 may arrive at gateway 103 at gateway uplink time 1108 with UE 1 uplink propagation delay 1110. In one embodiment, UE 1 uplink propagation delay 1110 may be approximately the same as UE 1 downlink propagation delay 1005. UE 1 uplink time 1107 can be determined by subtracting UE 1 differential timing advance 1109 from UE 1 downlink time 1104. UE 1 differential timing advance 1109 may be specific to the UE 1 used. In one embodiment, UE 1 differential timing advance 1109 may be as follows: Figure 9 As described in the text, it is calculated as TA=2 (T s,u -T r,s However, other differential timing methods can be used to calculate in advance.

[0121] Furthermore, the second UE (UE 2) can receive subframe 1102 at UE 2 downlink time 1111. A UE 2 downlink propagation delay 1112 may exist, where the UE 2 downlink propagation delay 1112 can be the difference between UE 2 downlink time 1111 and the gateway downlink time 1103. UE 2 can send or indicate UE 2 subframe 1113 at UE 2 uplink time 1114, and gateway 103 can receive UE 2 subframe 1113 at gateway uplink time 1108. The propagation delay between UE 2 uplink time 1114 and gateway uplink time 1108 can be a UE 2 uplink propagation delay 1116. In differential timing advance mode, gateway 103 can send downlink data at the first time and receive uplink data at the second time. That is, the downlink time and uplink time can be different. In full timing advance mode, gateway 103 can send downlink data and receive uplink data at the same time. Figure 11An example of a differential timing advance scheme is shown, in which UE 1 and UE 2 indicate uplink data to gateway 103 at different times; however, the data can be received by gateway 103 at the same time, which can be gateway uplink time 1108.

[0122] Figure 12 This is a schematic diagram of a process for calculating timing advance according to an embodiment of the present disclosure. (Refer to...) Figure 12 This could be used to exploit Figure 9 The reference point 901, located anywhere in cell 106, is used to calculate and indicate the timing advance of UE 101 in Figure 1200. Unlike the previous figures, Figure 12 The timing advance can be determined by using the difference between the propagation delay between UE 101 and satellite 102 and the propagation delay between reference point 901 and satellite 102.

[0123] Processing the received data 1201 may involve UE 101 receiving its own geographic location data, satellite ephemeris data, reference point 901's geographic location, and common timing advance 903. In some embodiments, reference point 901 may be a point anywhere within cell 106. In some embodiments, UE 101 may receive data from gNB via gateway 103 within NTN architecture 900. In another embodiment, regarding the propagation delay T between reference point 901 and satellite 102... r,s The information can be broadcast by satellite 102 to cell 106, and all UEs in cell 106 can receive the information. The broadcast can occur via SIB, MIB, or other broadcast mechanisms.

[0124] Processing 1202 can be UE 101 using ephemeris data of satellite 102 to calculate the geographical location of satellite 102.

[0125] Processing 1203 can be used by UE 101 to calculate the distance d between UE 101 and satellite 102. s,u And the distance d between satellite 102 and reference point 901 r,s .

[0126] Processing 1204 can allow UE 101 to determine the timing in advance. UE 101 can calculate the propagation delay T between UE 101 and satellite 102. s,u This could be T s,u =d s,u / c, where c is the speed of light in free space. UE 101 can calculate the propagation delay T between satellite 102 and reference point 901. r,s This could be T r,s =d r,s / c. UE 101 can calculate the differential timing advance TA as the propagation delay T.s,u With propagation delay T r,s Twice the difference between them, or TA=2(T) s,u -T r,s ).

[0127] In some embodiments, UE 101 may determine full timing advance. In other embodiments, UE 101 may determine differential timing advance. For each UE in cell 106, differential timing advance may be unique to the UE or may be shared.

[0128] Processing 1205 may involve UE 101 using a timer to send or indicate data to gateway 103 in advance. The uplink subframe number used for transmission from UE 101 can be specified in TA+N. TA,offset Starting at ×TC, this uplink subframe number can be transmitted before the start of the corresponding downlink subframe at UE 101. This information can be the absolute time T. r,s The form, or can be normalized to T C For example, the uplink subframe number can be normalized to N. r,s =T r,s / T C In the normalization method, UE 101 can calculate T. s,u The uplink subframe number used to transmit from UE 101 can be in the form of T. s,u +(N) r,s +N TA,offset Starting with ×TC, where T s,u +(N) r,s +N TA,offset )×T C This can be done before the start of the corresponding downlink subframe at UE 101, such as... Figure 10 As shown. In Figure 10 For simplicity, N TA,offset =0. Uplink subframes from all UEs in cell 106 can be transmitted via gateway 103 with a known delay of 2 (T). common +T r,s Arrive at gateway 103.

[0129] Figure 13 This is a schematic diagram of timing offset according to an embodiment of the present disclosure. (Refer to...) Figure 13 This demonstrates the addition of features to the NTN architecture (such as...). Figure 1 The offset value K of the timing relationship in the NTN communication architecture 100) offset Example timing offset diagram 1300. K offset It can be used for any timing relationship, such as uplink or downlink communication between gateway 103 and UE 101. offsetIt can be an offset value added to the existing NR timing relationship between downlink and uplink transmissions. In one embodiment, K offset It can be applied at the slot level within a subframe; however, it can also be applied to a subframe or a frame. For example, a gNB via gateway 103 can transmit data to a specified slot n. Figure 1 The UE 101 sends a command to the downlink. Then, the UE 101 can execute the command in time slot n+k2+K. offset The response is transmitted via uplink, where k2 can be a predefined value. If n=100, k=16, and K... offset If the value is 200, then UE 101 can send uplink data at time slot 100+16+200=316.

[0130] Due to propagation delays in the NTN, NR timing relationships involving downlink and uplink timing interactions can be modified and enhanced. Existing NR timing relationships can use several standard Radio Resource Control (RRC) configuration parameters (such as K1 and K2) for different downlink-uplink interactions to establish timing relationships between gateway 103 / gNB and UE 101. The range of existing RRC parameters may not compensate for NTN timing advances; therefore, K1 and K2 can be modified. offset Added to downlink-uplink timed interactions for NTN.

[0131] Subframe 1301 may include multiple subframes, wherein subframe 1301 may be divided into subframes of equal size. Each subframe may have the same duration or different durations, and may be used for transmission via... Figure 1 The base station or gNB of gateway 103 sends and receives data with UE 101.

[0132] Subframe 1302 may be within subframe 1301. In one embodiment, subframe 1302 may transmit downlink data from gateway 103 to UE 101 at gateway downlink time 1303, and UE 101 may receive the data at UE downlink time 1304. A timeslot number may exist associated with gateway downlink time 1303, and a timeslot number may also exist associated with UE downlink time 1304. A UE propagation delay 1305 may exist, wherein the UE propagation delay 1305 may be the difference between UE downlink time 1304 and gateway downlink time 1303.

[0133] Furthermore, UE 101 may transmit subframe 1306 to the uplink of gateway 103 at UE uplink time 1307. Subframe 1306 may arrive at gateway 103 at gateway uplink time 1309 with UE propagation delay 1305. UE uplink time 1307 can be determined by subtracting UE timing advance 1308 from UE downlink time 1304. In one embodiment, differential timing advance may be employed using any of the previously described methods; however, full timing advance may also be employed. In one embodiment, the difference between gateway uplink time 1309 and gateway downlink time 1303 may be common timing advance T. common It is twice the time, however, any other timing can be used in advance.

[0134] Furthermore, the second subframe 1312 can be uplinked to gateway 103 at the second UE uplink time 1313 and arrive at gateway 103 at the second gateway uplink time 1314. The time delay between the second gateway uplink time 1314 and the second UE uplink time 1313 can be a UE propagation delay 1305. This can be achieved by using a subframe with K... offset The NR timing 1311 is added to the UE uplink time 1307 to calculate the second UE uplink time 1313. In one embodiment, K... offset The NR timing 1311 can be selected by the gNB via gateway 103 as a value greater than the UE timing advance 1308. In one embodiment, K offset It can be the same as or greater than the value of UE timing 1308 in advance.

[0135] In one embodiment, Figure 1 Each UE in cell 106 can receive UE-specific K from the network. offset In another embodiment, a K offset It can be used for all UEs in cell 106. A dedicated downlink control information (DCI) format can be defined to send K to each UE. offset Among them, this dedicated downlink control information (DCI) format can be referred to as the format used to configure K. offset The group common DCI format. In one embodiment, a dedicated radio network temporary identifier (RNTI) may also be defined to send K to each UE. offset .

[0136] In one embodiment, a DCI format such as DCI format 2_0 or 2_4 may be defined, and the DCI format may be used to provide K to the UE in cell 106. offsetHowever, any DCI format standard can be used. In another embodiment, a dedicated RNTI designated as K-RNTI can also be used for scrambling DCI formats. When receiving a DCI format, the UE can address via its K-RNTI. The UE can address by using the K-RNTI to scramble the Cyclic Redundancy Check (CRC) bits that can be added to the DCI payload. The UE can be configured with a K-RNTI using downlink parameters.

[0137] Figure 14 This is a schematic diagram of a Group Common Downlink Control Information (DCI) format for receiving offset values ​​according to an embodiment of the present disclosure. (Refer to...) Figure 14 This shows how to configure K within it. offset The group's public DCI format. In one embodiment, K offset This can be specific to each UE in cell 106. In another embodiment, a dedicated DCI format can also be used for UE group common signaling, allowing multiple UEs to be assigned the same K-RNTI. Multiple UEs can decode the same Physical Downlink Control Channel (PDCCH); however, each UE can extract only the information addressed to a specific UE. Downlink parameters can be used to configure the provision of index or location ID information to the UE. The index or location ID can send or indicate the starting location of information associated with the UE. Figure 14 As shown, the DCI structure can contain n K elements within the DCI. offset And each K offset It can occupy b bits. It can be based on K. offset The range is determined by extracting the number of bits *b* from the DCI payload. The value of *b* can be network-specific or cell-specific. All UEs within a network or a cell within a network (such as cell 106) can be configured with the same *b* value. The maximum size of the DCI can be network-specific or cell-specific. The actual size of the DCI can be communicated to the UE via an information element. The UE can also specify its own K... offset This applies to all associated downlink-uplink timing relationships of the UE, which will be described in more detail later.

[0138] Figure 15 This is a schematic diagram of a Media Access Control-Control Element (MAC-CE) format for receiving offset values ​​according to an embodiment of this disclosure. (Refer to...) Figure 15 This illustrates the use of the Media Access Control-Control Element (MAC-CE) for K. offset Example of indication. K offset It can occupy m bits. The network can configure all UEs, such as the UEs in cell 106, through the value of m, where the value of m can be used to send or indicate K. offsetThe number of bits of the value. Then, the network can use MAC-CE and the corresponding logical channel identifier to target the UE-specific K. offset Configure the UE separately.

[0139] In another embodiment, during the scheduling process, K can be sent or indicated to the UE per transmission in the DCI or RAR license. offset K can be indicated based on the downlink-uplink timing relationship. offset These various relationships are described below.

[0140] In one embodiment, K offset This can be based on the timing used for Physical Uplink Shared Channel (PUSCH) transmission scheduled by the DCI. In NR, when the UE is scheduled by the DCI to transmit the PUSCH, the DCI can send or indicate the slot offset value K2 as described above. For NTN or used in the network Figure 1 The scene of satellite 102, K offset It can be sent as a new field in DCI. The time slot allocated for PUSCH can be...

[0141] Where n can be the time slot number for scheduling DCI, k2 can be the parameter set based on PUSCH, and K offset It can be based on the UE's timing advance, and and These can be subcarrier spacing configurations for PUSCH and PDCCH, respectively.

[0142] In another embodiment, K offset The timing can be based on license type 2 for configuration, wherein the timing of license type 2 for configuration can follow the same rules as those described above for the timing of PUSCH transmissions scheduled by DCI.

[0143] In another embodiment, K offset The timing can be based on the transmission of Channel State Information (CSI) on the PUSCH. The transmission timing of CSI on the PUSCH can follow the same rules mentioned in the paragraphs above for PUSCH transmissions that can be scheduled by DCI.

[0144] In another embodiment, K offset The timing can be based on the PUSCH transmission scheduled by RAR permission. If the UE receives a PDSCH with RAR messages in time slot n, which is used for transmission from the corresponding Physical Random Access Channel (PRACH) of the same UE, the UE can transmit in the time slot. Send PUSCH in, where K offsetThe timing can be advanced based on the UE and can be indicated in the RAR license. K2 and Δ can be defined and provided in 3GPP TS 38.214 v16.0.0, "Physical layer procedures for data (Release 16)".

[0145] In another embodiment, K offset The timing can be based on the hybrid automatic repeat request acknowledgment (HARQ-ACK) transmission on the Physical Uplink Control Channel (PUCCH). Referring to the time slot used for PUCCH transmission, for Physical Downlink Shared Channel (PDSCH) reception in time slot n or semi-persistent scheduling (SPS) PDSCH release via PDCCH in time slot n, the UE can... The internal code provides the corresponding HARQ-ACK information during PUCCH transmission, where K... offset It can be indicated in DCI, where K1 can be the number of time slots and can be indicated by the PDSCH to HARQ timing indicator field in DCI format.

[0146] In another embodiment, K offset The timing can be based on the CSI reference resource transmission. The CSI reference resource for CSI reporting in uplink slot n can be generated from a single downlink slot. Define, where, and These can be the subcarrier spacing configurations for DL ​​and UL, respectively. They can be defined in 3GPP TS 38.214 v16.0.0, "Physical layer procedures for data (Rev. 16)". The value of K. For non-periodic CSI reporting, the UE can be instructed by the DCI to report CSI, and K offset It can be based on the UE's timing and can be included in the DCI.

[0147] In another embodiment, K offset This can be based on the timing used for aperiodic sounding reference signal (SRS) transmission. If the UE receives a DCI that triggers the aperiodic SRS in time slot n, the UE can then transmit the signal in time slot n. In each triggered SRS resource set, an aperiodic SRS is sent, where K offset The timing can be advanced based on the UE and can be included in the DCI that triggers aperiodic SRS. k can be configured via the high-level parameter slotOffset for each triggered SRS resource set, and and These can be the subcarrier spacing configurations for the triggered SRS and the PDCCH carrying the trigger command, respectively.

[0148] In another embodiment, K offset It can be based on the timing used for MAC control element actions. When the PDSCH carries the MAC control element (MAC-CE) command and sends the corresponding HARQ-ACK in time slot n, it can be from the time slot. The first time slot thereafter applies the corresponding actions and UE assumptions regarding the downlink configuration as indicated by the MAC-CE command, whereby... This can be the number of time slots per subframe used for subcarrier spacing configuration, and Both can be integers depending on the UE's capabilities. K can be indicated to the UE in the MAC-CE command. offset The value of .

[0149] In another embodiment, refer to Figure 16 K offset It can be based on the timing of license type 1 used for configuration. Figure 16 A timing offset diagram 1600 for license type 1 can be described. Subframe 1601 may include multiple subframes, which may have the same size or different sizes. Each subframe in subframe 1601 may have a start transmission time and an end transmission time, which may be represented as a timeslot number or time. Subframe 1602 may be a subframe within subframe 1601. Subframe 1602 may be transmitted by gateway 103 at gateway downlink time 1603, wherein subframe 1602 may be received by UE 101 at UE downlink time 1604. There may be a UE propagation delay 1605, wherein propagation delay 1605 may be the difference between UE downlink time 1604 and gateway downlink time 1603.

[0150] UE 101 may transmit or indicate subframe 1606 at UE uplink time 1607, wherein subframe 1606 may be received by gateway 103 at gateway uplink time 1609. A UE propagation delay 1605 (not shown) may exist, which may be the difference between gateway uplink time 1609 and UE uplink time 1607. UE uplink time 1607 can be calculated by subtracting UE timing advance 1608 from UE downlink time 1604. UE timing advance 1608 can be determined according to any of the previously mentioned timing advance techniques.

[0151] Subframe 1612 can be a subframe transmitted by UE 101 and can be transmitted using Configurable Citation (CG). Subframe 1613 can be a subframe within subframe 1612. Subframe 1612 can have a period 1611 between each subframe transmitted using CG. UE 101 can transmit subframe 1613 at CG UE uplink transmission time 1614. Gateway 103 can receive subframe 1613 at CG gateway uplink reception time 1615.

[0152] When using the configured license type 1, the transmission timing can begin when the following equation is satisfied in (1):

[0153]

[0154] Both `timeDomainOffset` and `periodicity` can be specified within the `ConfiguredGrantConfig` parameter structure, which can be found in 3GPP TS 38.331 V16.2.0, “RadioResourceControl (RRC) protocol specification (Revision 16)”. `SFN` can be the system frame number. `S` can correspond to the start symbol subtracted from `timeDomainAllocation`; for example, `N≥0` can be an integer corresponding to the Nth transmission timing of subframe 1612. The terms are defined as follows, as described in the 3GPP TS 38.331 V16.2.0 standard:

[0155] SFN: System frame number (ranging from 0 to 1023);

[0156] numberOfSlotsPerFrame: The number of slots per frame;

[0157] numberOfSymbolsPerSlot: The number of symbols per slot;

[0158] slotnumberinthefram: The number within the frame;

[0159] symbolnumberintheslot: The symbol number within the time slot;

[0160] timeReferenceSFN: An SFN that can be used to determine the resource offset in the time domain. The UE may use the closest SFN with the indicated number before receiving the permitted configuration.

[0161] timeDomainOffset: The offset of the resource relative to SFN = timeReferenceSFN in the time domain;

[0162] S: Corresponds to the starting symbol deducted from timeDomainAllocation IE (TS38.331);

[0163] N: Transmission timing; and

[0164] periodicity: The periodicity of the configured license type 1.

[0165] In one embodiment, the time between the CG gateway uplink receive time 1615 and the CG UE uplink transmit time 1614 can be a UE propagation delay 1605. The gNB via gateway 103 can configure the timing of UE 101 transmitting subframe 1612 such that the first transmission opportunity for subframe 1613 can occur after subframe 1606 arrives at gateway 103 at gateway uplink time 1609. Referring to Equation 1, the configured symbol number in the time slot associated with the CG UE uplink transmit time 1614 can appear after UE uplink time 1607 by an amount greater than or equal to UE timing advance 1608. This can be referred to as timing relation K. offset Time 1610. From gateway UL time 1609 to CG gateway uplink reception time 1615, the gNB via gateway 103 may not receive any UL CG data packets. This can be achieved by matching numberOfSymbolsPerSlot with K. offset Multiply the components, and then add the product to the timing used for the first CG transmission to calculate the timing relationship K. offset Time: 1610. Equation 1 above illustrates this relationship in more detail.

[0166] In another embodiment, K offset Timing can be based on the slot format indicator (SFI) used for DCI format scheduling, and can be used for TDD, such as Figure 2 As described herein. In one embodiment, the DCI format may be DCI format 2_0; however, the DCI format may also be any other DCI format. See reference [link to documentation]. Figure 17 This demonstrates the K-format of DCI 2_0 using SFI with scheduling. offset Timing offset diagram. SFI can be a format of time slots that can be sent to the DCI of UE 101.

[0167] Subframe 1701 may be a subframe associated with a gNB via gateway 103 and may receive SFIs scheduled in DCI format. Subframe 1701 may have a start time and / or slot number. A DCI period 1702 may exist for subframe 1701, which may include one or more of downlink, flexible slot, uplink, and empty slot types, and may be referred to as period 1702.

[0168] In one embodiment, the timing of the SFI scheduled in DCI format during cycle 1702 can be statically performed in a cell-specific, UE-specific, or a combination of both, and can utilize RRC signaling via the information elements tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, as defined in 3GPP TS 38.331 V16.2.0, “RadioResourceControl (RRC) protocol specification (Rev. 16)”. The gNB via gateway 103 can send configuration commands to UE 101 in each cycle 1702. Downlink, uplink, and flexible subframe, frame, and / or time slot configurations may exist. The resulting time slot configuration in cycle 1702 may include subframe 1703, which may include unallocated flexible time slots or symbols. Gateway 103 can send DCI format commands to UE 101 within cycle 1702 to configure downlink, uplink, or flexible subframes (which may include time slots within the subframe). Subframe 1704, configured using DCI 2_0, can be applied to subframe 1703 using the DCI format. Some or all of the remaining flexible slots or symbols can be dynamically configured or reconfigured in subframe 1703.

[0169] Subframe 1703 may include unassigned flexible time slots or symbols in DCI period 1702, wherein the time slots or symbols may be previously configured and may be valid, and may be dynamically configured or reconfigured to DCI-configured time slots or symbols 1704. Subframe 1705 may include unassigned flexible time slots or symbols in DCI period 1702, which may be newly configured to be valid, and may be dynamically configured or reconfigured to DCI-configured time slots or symbols 1706.

[0170] UE 101 may have a UE downlink subframe 1707, wherein the UE downlink subframe 1707 may be a subframe having downlink time slots and empty time slots for each DCI period 1702. UE 101 may have a UE uplink subframe 1712, wherein the UE uplink subframe 1712 may begin at the UE uplink time slot 1713 and may include empty time slots and uplink time slots in each DCI period 1702. The UE uplink subframe 1712 may include a previous uplink configuration 1714 and a new uplink configuration 1715. The previous uplink configuration 1714 may be valid in the first period 1702, and the new uplink configuration 1715 may be valid in subsequent periods 1702.

[0171] UE 101 can be configured to periodically monitor the PDCCH (such as DCI cycle 1702), enabling UE 101 to decode the DCI format. UE 101 can receive DCI format data in UE downlink time slot 1708, where the DCI format data may include new downlink configuration data 1709. A UE downlink receive time 1711 may exist, which may be the time when UE 101 receives data from the gateway downlink transmit time 1710, and may be the start of a new DCI cycle 1702.

[0172] In one embodiment, there may be a propagation delay between UE 101 sending uplink data to gateway 103 and gateway 103 sending downlink data to UE 101. Therefore, UE 101 may not need to send uplink data after UE uplink time slot 1713. offset The uplink slots or symbols of UE 101 can be reconfigured at any time before slot 1716. UE 101 can reconfigure its uplink slots or symbols in several slots (UE uplink slot 1713 plus K). offset (1716) Afterwards, the uplink time slots are reconfigured, which can be indicated to UE 101 in the SFI by the gNB via gateway 103. In one embodiment, the number of time slots that can be indicated in the SFI can be K. offset1 The 1716 time slots are roughly the same. In another embodiment, the number of time slots indicated in the SFI can be higher than K. offset 1716.

[0173] In another embodiment, the number of time slots indicated by UE 101 to gateway 103 in the SFI can be applied to K after the current time slot. offsetThe quantity 1716 is the uplink portion indicated in the SFI. The current timeslot can be UE uplink timeslot 1713. The uplink portion indicated in the SFI can be UE uplink portion 1717. UE uplink portion 1717 can begin at the start of UE uplink timeslot 1718, where the start of UE uplink timeslot 1718 can be K distance from UE uplink timeslot 1713. offset 1716 values ​​or greater. In another embodiment, the UE uplink time slot start 1718 may be less than K from the UE uplink time slot 1713. offset In one embodiment, UE 101 may receive the uplink portion of the SFI scheduled by DCI at UE uplink time slot 1713, and may apply the provided time slot format to K after UE uplink time slot 1713. offset The uplink time slot at time slot 1716 can be the UE uplink time slot start 1718. For uplink time slots prior to the UE uplink time slot start 1718, UE 101 can use the previously configured configuration, which can be the previous uplink configuration 1714.

[0174] In another embodiment, the SFI for UE uplink slot 1713 may implicitly indicate UE uplink portion 1717 at the UE uplink slot start time, and UE uplink portion 1717 may be indicated by a previously received SFI. UE 101 may apply a new slot configuration to the uplink slot or symbol, wherein the new slot configuration may be a new uplink configuration 1715.

[0175] In another embodiment, for a downlink slot or symbol, after UE 101 decodes the DCI format in UE downlink slot 1708, UE 101 can configure subsequent slots as downlink slots or symbols based on the SFI indicated to UE 101 in the DCI format. This can be a new downlink configuration 1709. In one embodiment, the new downlink configuration 1709 can be based on UE 101 configuring downlink slots or symbols for subsequent slots after UE downlink slot 1708 according to the SFI indicated in the DCI format, wherein the DCI format is received in UE downlink slot 1708.

[0176] In another embodiment, K offset K can be based on cell- or beam-specific dynamic indications offset All UEs in cell 106 can be accessed via the network through a single value K of the RRC parameter. offset Configured. K can be configured in the same way as other timing RRC parameters (such as K1 and K2). offsetAlternatively, K can be configured differently. offset K can be selected. offset To support the worst-case scenario, where K offset It can be greater than the timing advance of the UE with the longest timing advance in cell 106.

[0177] Figure 18 The following are illustrations of configurations for managing timing advance and K according to some embodiments. offset Example of System 1800. See also... Figure 18 In network environment 1800, electronic device 1801 (which may be similar to or the same as UE 101) may communicate with electronic device 1802 via a first network 1898 (e.g., a short-range wireless communication network, such as a Wi-Fi network), or with electronic device 1804 or server 1808 (which may be similar to or the same as gNB via gateway 103) via a second network 1899 (which may be similar to or the same as network 100 that can use satellite 102) (e.g., a long-range wireless communication network, such as a cellular communication network, such as a 5G network)). Electronic device 1801 may communicate with electronic device 1804 via server 1808. Electronic device 1801 may include processor 1820, memory 1830, input device 1850, sound output device 1855, display device 1860, audio module 1870, sensor module 1876, interface 1877, haptic module 1879, camera module 1880, power management module 1888, battery 1889, communication module 1890, subscriber identification module (SIM) 1896, and / or antenna module 1897. In one embodiment, at least one component (e.g., display device 1860 or camera module 1880) may be omitted from electronic device 1801, or one or more other components may be added to electronic device 1801. In one embodiment, some components may be implemented as a single integrated circuit (IC). For example, sensor module 1876 (e.g., fingerprint sensor, iris sensor, or illuminance sensor) may be embedded in display device 1860 (e.g., display), or display device 1860 may include one or more sensors in addition to sensor module 1876.

[0178] In some embodiments, the electronic device 1801 may include components configured to implement management timing advance and K offset (such as the management of timed advances and K as described in this article) offset A computing device or processor (method of which).

[0179] Processor 1820 can execute, for example, software (e.g., program 1840) to control at least one other component (e.g., hardware or software component) coupled to processor 1820 of electronic device 1801, and can perform various data processing and / or calculations. As at least part of data processing and / or calculations, processor 1820 can load commands or data received from another component (e.g., sensor module 1876 or communication module 1890) into volatile memory 1832, process the commands or data stored in volatile memory 1832, and store the resulting data in non-volatile memory 1834. Processor 1820 may include a main processor 1821 (e.g., central processing unit (CPU) or application processor (AP)) and auxiliary processors 1823 (e.g., graphics processing unit (GPU), image signal processor (ISP), sensor hub processor, or communication processor (CP)) that may operate independently of or in conjunction with main processor 1821. Additionally or optionally, the auxiliary processor 1823 may be adapted to consume less power than the main processor 1821 and / or perform specific functions. The auxiliary processor 1823 may be implemented separately from the main processor 1821 or as part of the main processor 1821.

[0180] The auxiliary processor 1823 may, when the main processor 1821 is inactive (e.g., in sleep) state, control at least some of the functions or states associated with at least one component of the electronic device 1801 (e.g., display device 1860, sensor module 1876, or communication module 1890) in place of the main processor 1821, or, when the main processor 1821 is active (e.g., executing an application), control, together with the main processor 1821, at least some of the functions or states associated with at least one component of the electronic device 1801 (e.g., display device 1860, sensor module 1876, or communication module 1890). According to one embodiment, the auxiliary processor 1823 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., a camera module 1880 or communication module 1890) functionally associated with the auxiliary processor 1823.

[0181] Memory 1830 may store various data used by at least one component of electronic device 1801 (e.g., processor 1820 or sensor module 1876). The various data may include, for example, software (e.g., program 1840) and input or output data for commands associated with the software (e.g., program 1840). Memory 1830 may include volatile memory 1832 and / or non-volatile memory 1834.

[0182] Program 1840 may be stored as software in memory 1830 and may include, for example, an operating system (OS) 1842, middleware 1844, or application 1846.

[0183] Input device 1850 can receive commands or data from outside electronic device 1801 (e.g., a user) to be used by another component of electronic device 1801 (e.g., processor 1820). Input device 1850 may include, for example, a microphone, mouse, and / or keyboard.

[0184] The sound output device 1855 can output sound signals to the outside of the electronic device 1801. The sound output device 1855 may include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as playing multimedia or recording, and the receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part of the speaker.

[0185] Display device 1860 can visually provide information to the outside of electronic device 1801 (e.g., to a user). Display device 1860 may include, for example, a display, a holographic device, and / or a projector, and control circuitry for controlling a respective one of the display, holographic device, and projector. According to one embodiment, display device 1860 may include touch circuitry adapted to detect touch, or sensor circuitry adapted to measure the intensity of the force caused by touch (e.g., a pressure sensor).

[0186] The audio module 1870 can convert sound into electrical signals and vice versa. According to one embodiment, the audio module 1870 can obtain sound via an input device 1850 and / or output sound via a sound output device 1855 or an earphone of an external electronic device 1802 directly (e.g., wired) or wirelessly coupled to the electronic device 1801.

[0187] Sensor module 1876 can detect the operating state of electronic device 1801 (e.g., power or temperature) and / or the environmental state outside electronic device 1801 (e.g., user state), and then generate an electrical signal or data value corresponding to the detected state. Sensor module 1876 may include, for example, a gesture sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biosensor, a temperature sensor, a humidity sensor, and / or an illuminance sensor.

[0188] Interface 1877 may support one or more specified protocols for direct (e.g., wired) or wireless coupling of electronic device 1801 to external electronic device 1802. According to one embodiment, interface 1877 may include, for example, a High Definition Multimedia Interface (HDMI), a Universal Serial Bus (USB) interface, a Secure Digital Card (SD) interface, and / or an audio interface.

[0189] Connection terminal 1878 may include a connector via which electronic device 1801 can be physically connected to external electronic device 1802. According to one embodiment, connection terminal 1878 may include, for example, an HDMI connector, a USB connector, an SD card connector, and / or an audio connector (e.g., a headphone connector).

[0190] The haptic module 1879 can convert electrical signals into mechanical stimuli (e.g., vibration or motion) and / or electrical stimuli that can be recognized by a user via touch or kinesthesia. According to one embodiment, the haptic module 1879 may include, for example, a motor, a piezoelectric element, and / or an electrical stimulator.

[0191] Camera module 1880 can capture still or moving images. According to one embodiment, camera module 1880 may include one or more lenses, an image sensor, an image signal processor, and / or a flash.

[0192] The power management module 1888 manages the power supplied to the electronic device 1801. The power management module 1888 may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

[0193] Battery 1889 can supply power to at least one component of electronic device 1801. According to one embodiment, battery 1889 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, and / or a fuel cell.

[0194] Communication module 1890 can support the establishment of a direct (e.g., wired) or wireless communication channel between electronic device 1801 and external electronic devices (e.g., electronic device 1802, electronic device 1804, and / or server 1808), and perform communication via the established communication channel. Communication module 1890 may include one or more communication processors that can operate independently of processor 1820 (e.g., AP), and can support direct (e.g., wired) communication and / or wireless communication. According to one embodiment, communication module 1890 may include wireless communication module 1892 (e.g., cellular communication module, short-range wireless communication module, and / or Global Navigation Satellite System (GNSS) communication module) or wired communication module 1894 (e.g., local area network (LAN) communication module or power line communication (PLC) module). The corresponding communication modules in these communication modules can communicate with external electronic devices via a first network 1898 (e.g., a short-range communication network, such as Bluetooth®, Wi-Fi Direct, and / or Infrared Data Association (IrDA) standards) or a second network 1899 (e.g., a long-range communication network, such as a cellular network, the Internet, and / or a computer network (e.g., a LAN or a wide area network (WAN))). Bluetooth® is a registered trademark of Bluetooth SIG, Inc., Kirkland, and WA. These various types of communication modules can be implemented as a single component (e.g., a single IC) or as multiple components that are separate from each other (e.g., multiple ICs). The wireless communication module 1892 can use user information (e.g., International Mobile Subscriber Identity (IMSI)) stored in the user identification module 1896 to identify and authenticate electronic devices 1801 in the communication network (such as the first network 1898 or the second network 1899).

[0195] Antenna module 1897 can transmit signals and / or power to and / or receive signals and / or power from the outside of electronic device 1801 (e.g., external electronic device). According to one embodiment, antenna module 1897 may include one or more antennas, and at least one antenna suitable for a communication scheme used in a communication network such as a first network 1898 and / or a second network 1899 can then be selected by communication module 1890 (e.g., wireless communication module 1892). Signals and / or power can then be transmitted and / or received between communication module 1890 and external electronic device via the selected at least one antenna.

[0196] At least some of the aforementioned components may be coupled to each other and transmit signals (e.g., commands and / or data) between them via peripheral communication schemes (e.g., bus, general purpose input and output (GPIO), serial peripheral interface (SPI) and / or mobile industrial processor interface (MIPI)).

[0197] According to one embodiment, commands and / or data can be sent and / or received between electronic device 1801 and external electronic device 1804 via server 1808 coupled to a second network 1899. Each of electronic devices 1802 and 1804 may be a device of the same or different type as electronic device 1801. All or some of the operations to be performed at or by electronic device 1801 can be performed at one or more of the external electronic devices 1802, 1804, or server 1808. For example, if electronic device 1801 is required to perform a function and / or service automatically or in response to a request from a user or another device, electronic device 1801 may request one or more external electronic devices to perform at least a portion of the function and / or service, rather than performing the function and / or service itself, or may request one or more external electronic devices to perform at least a portion of the function and / or service in addition to performing the function and / or service itself. One or more external electronic devices receiving the request may perform at least a portion of the requested function and / or service, and / or additional functions and / or services related to the request, and transmit the result of the performance to electronic device 1801. Electronic device 1801 may provide the result, with or without further processing, as at least part of a response to the request. For this purpose, cloud computing, distributed computing, and / or client-server computing technologies may be used, for example.

[0198] One embodiment may be implemented as including software (e.g., program 1840) containing one or more instructions stored in a storage medium (e.g., internal memory 1836 or external memory 1838) readable by a machine (e.g., electronic device 1801). For example, a processor of electronic device 1801 may, under the control of the processor, invoke at least one of the instructions stored in the storage medium, with or without one or more other components, and execute the invoked instructions. Thus, the machine is operable to perform at least one function according to the invoked at least one instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term "non-transitory" indicates that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term distinguishes between data that is semi-permanently stored in the storage medium and data that is temporarily stored in the storage medium.

[0199] As used herein, “part” of something means “at least some” of that thing, and therefore can mean less than or all of that thing. Thus, “part” of an object includes the whole object as a special case, that is, an example where the whole object is a part of the object.

[0200] As used herein, the term “array” refers to an ordered collection of numbers, regardless of how they are stored (e.g., whether they are stored in contiguous memory locations or in a linked list). As used herein, the term “rectangle” includes a square as a special case, i.e., a square is an example of a rectangle. As used herein, the term “or” should be interpreted as “and / or”, such that, for example, “A or B” refers to either “A” or “B” or “A and B”.

[0201] As used herein, when a method (e.g., adjustment) or a first quantity (e.g., a first variable) is referred to as “based on” a second quantity (e.g., a second variable), this means that the second quantity is an input to the method or affects the first quantity. For example, the second quantity may be an input to a function that calculates the first quantity (e.g., a unique input or one of several inputs), or the first quantity may be equal to the second quantity, or the first quantity may be the same as the second quantity (e.g., stored in the same location in memory).

[0202] It should be understood that although the terms “first,” “second,” “third,” etc., may be used herein to describe various elements, components, regions, layers, and / or portions, these elements, components, regions, layers, and / or portions should not be limited by these terms. These terms are used only to distinguish one element, component, region, layer, or portion from another element, component, region, layer, or portion. Therefore, without departing from the spirit and scope of the inventive concept, the first element, component, region, layer, or portion discussed herein may be referred to as the second element, component, region, layer, or portion.

[0203] For ease of description, this document uses spatially relative terms such as “below,” “under,” “lower,” “below,” “above,” “upper,” etc., to describe the relationship of one element or feature to another or more elements or features as shown in the figures. It should be understood that such spatially relative terms are intended to cover different orientations of the device in use or operation, in addition to those shown in the figures. For example, if the device in the figures is flipped, an element described as “below,” “below,” or “below” other elements or features will be oriented “above” other elements or features. Thus, the exemplary terms “below” and “below” can cover both above and below orientations. The device may be oriented in other ways (e.g., rotated 90 degrees or in other orientations), and the spatially relative descriptive terms used herein should be interpreted accordingly. Furthermore, it should be understood that when a layer is referred to as being “between” two layers, it can be the only layer between the two layers, or there may be one or more intermediate layers.

[0204] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the inventive concept. As used herein, the terms “substantially,” “about,” and similar terms are used as approximate terms rather than terms of degree and are intended to take into account the inherent biases of measured or calculated values ​​that will be recognized by one of ordinary skill in the art. As used herein, the term “major component” refers to a component present in a composition, polymer, or product in an amount greater than that of any other single component in the composition or product. Conversely, the term “primary component” refers to a component that constitutes at least 50% or more by weight of the composition, polymer, or product. As used herein, when applied to multiple items, the term “major portion” refers to at least half of the items.

[0205] As used herein, unless the context clearly indicates otherwise, the singular forms (“a” and “an”) are intended to include the plural forms as well. It will be further understood that, when used in this specification, the terms “comprising and / or including” specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items. Expressions such as “at least one of…” modify the entire list of elements when following a list of elements, without modifying individual elements of the list. Furthermore, the use of “may” when describing embodiments of the inventive concept means “one or more embodiments of this disclosure.” Additionally, the term “exemplary” is intended to indicate or illustrate. As used herein, the terms “use,” “currently using,” and “already used” may be considered synonymous with the terms “utilize,” “currently exploiting,” and “already exploited,” respectively.

[0206] It should be understood that when a component or layer is referred to as being "on," "connected to," "coupled to," or "adjacent to" another component or layer, it may be directly on, connected to, coupled to, or adjacent to the other component or layer, or one or more intermediate components or layers may exist. For example, if a first component is "connected to" a second component, a third component may be connected between the first and second components (e.g., a first side of the third component may be connected to the first component, and a second side of the third component may be connected to the second component). Conversely, when a component or layer is referred to as being "directly on," "directly connected to," "directly coupled to," or "adjacent to" another component or layer, no intermediate components or layers exist.

[0207] Any numerical range described herein is intended to include all subranges containing the same numerical precision within the range. For example, the range “1.0 to 10.0” or “between 1.0 and 10.0” is intended to include (and include) the minimum value 1.0 and the maximum value 10.0, that is, all subranges having a minimum value equal to or greater than 1.0 and a maximum value equal to or less than 10.0, such as, for example, 2.4 to 7.6. Any maximum numerical limit described herein is intended to include all lower numerical limits contained therein, and any minimum numerical limit described in this specification is intended to include all higher numerical limits contained therein.

[0208] Although exemplary embodiments of wireless communication networks have been specifically described and illustrated herein, and more specifically, the management of timing advance and offset values ​​for uplink transmissions has been described and illustrated, many modifications and variations will be apparent to those skilled in the art. Therefore, it should be understood that wireless communication networks constructed according to the principles of this disclosure, and more specifically, the management of timing advance and offset values ​​for uplink transmissions, can be implemented in ways different from those specifically described herein. The invention is also defined in the claims and their equivalents.

Claims

1. A method for realizing communication between a user equipment (UE) and a non-terrestrial network (NTN), comprising: The UE receives the satellite location data of the NTN. The satellite position is determined at the UE based on the satellite position data. Determine the UE location at the UE. Calculate the first distance between the UE's location and the satellite's location at the UE. Timing advance is calculated at the UE based on the first distance. The first K in the group common DCI format is received at the UE. offset Among them, the first K offset It is the offset value of the timing relationship sent by the NTN, and the first K offset It is a fixed number of bits, and Apply the timing advance and the first K at the UE offset One or both of these can be used to configure the sending or receiving of communication with the NTN.

2. The method according to claim 1, wherein, The satellite position data is ephemeris data or position data.

3. The method according to claim 1, further comprising: The gateway location data is received at the UE, and The gateway location is determined at the UE based on the gateway location data.

4. The method according to claim 3, wherein, The UE also calculates a second distance between the satellite location and the gateway location.

5. The method according to claim 4, wherein, The UE also calculates the timing advance through the following steps: Divide the first distance by the speed to obtain the first propagation delay. Divide the second distance by the speed to obtain the second propagation delay. Summing the first propagation delay and the second propagation delay, and Double the summation result. The speed mentioned here is the speed of light in free space.

6. The method according to claim 4, wherein, The timing advance mentioned is a full timing advance.

7. The method according to claim 1, further comprising: The reference point position data is received at the UE, and The reference point position is determined at the UE based on the reference point position data. The reference point is located on the feeder link.

8. The method according to claim 7, wherein, The UE also receives a common timing advance.

9. The method according to claim 8, wherein, The UE also calculates a third distance between the reference point location and the satellite location.

10. The method according to claim 9, wherein, The UE also calculates the timing advance through the following steps: Divide the first distance by the speed to obtain the first propagation delay. Divide the third distance by the speed to obtain the third propagation delay. The first propagation delay, the third propagation delay, and the common timing advance are summed, and Double the summation result. The speed mentioned here is the speed of light in free space.

11. The method according to claim 10, wherein, The timing advance mentioned is one of full timing advance and differential timing advance.

12. The method according to claim 7, wherein, The reference point location is the satellite location.

13. The method according to claim 1, further comprising: The reference point position data is received at the UE, and The reference point position is determined at the UE based on the reference point position data. The reference point is located within the cell where the UE is located.

14. The method according to claim 13, wherein, The UE also receives a common timing advance.

15. The method according to claim 14, wherein, The UE also calculates a fourth distance between the reference point location and the satellite location.

16. The method according to claim 15, wherein, The UE also calculates differential timing advance through the following steps: Divide the first distance by the speed to obtain the first propagation delay. Divide the fourth distance by the speed to obtain the fourth propagation delay. Subtract the fourth propagation delay from the first propagation delay, and Double the result of the subtraction. The speed mentioned here is the speed of light in free space.

17. The method according to claim 1, further comprising: The second K-type receiver at the UE is in group common DCI format and / or MAC-CE format. offset And the second K offset It is a fixed number of bits.

18. The method according to claim 17, wherein, Second K offset It is specific to the UE.

19. The method according to claim 17, wherein, Second K offset In the transmission of license type 1 for configuration, the UE will transmit the second K... offset The offset obtained by multiplying by the number of symbols per time slot is added to the timing of licensed type 1 transmissions used for the configuration.

20. The method of claim 17, wherein, Second K offset In the transmission of license type 2 for configuration, the UE transmits via the second K... offset The license type 2 transmissions added to the configuration are scheduled via DCI to send the Physical Uplink Shared Channel (PUSCH).

21. The method according to claim 17, wherein, Second K offset For a slot format indicator (SFI), wherein the slot format indicator is used to dynamically configure or reconfigure symbols or slots in a subframe, wherein the UE configures or reconfigures the uplink slot at least two K times later. offset The symbol or time slot at each time slot.

22. The method according to claim 17, wherein, Second K offset Greater than or equal to the aforementioned timing advance.

23. The method according to claim 17, wherein, Second K offset Timing used for PUSCH transmissions scheduled by DCI.

24. The method of claim 17, wherein, Second K offset Timing used for the transmission of Channel State Information (CSI) on the PUSCH.

25. The method according to claim 17, wherein, Second K offset Timing for PUSCH transmissions scheduled by the random access response (RAR) license.

26. The method according to claim 17, wherein, Second K offset Timing for hybrid automatic repeat request acknowledgment (HARQ-ACK) transmissions on the Physical Uplink Control Channel (PUCCH).

27. The method according to claim 17, wherein, Second K offset Timing used for CSI reference resource transfer.

28. The method according to claim 17, wherein, Second K offset Timing used for non-periodic SRS transmission.

29. A system comprising user equipment (UE) and a non-terrestrial network (NTN), wherein, The UE is configured as follows: Receive the satellite position data from the NTN, and determine the satellite position based on the satellite position data. Determine the UE location. Calculate the first distance between the UE location and the satellite location. The timing advance is calculated based on the first distance. The first K in the common DCI format of the receiver group offset Among them, the first K offset It is the offset value of the timing relationship sent by the NTN, and the first K offset It is a fixed number of bits, and Apply the aforementioned timing advance and the first K offset One or both of these can be used to configure the sending or receiving of communication with the NTN.

30. The system of claim 29, wherein the UE is further configured to receive reference point location data and determine a reference point location based on the reference point location data.

31. The system of claim 30, wherein the UE is further configured to receive a common timing advance.

32. The system according to claim 31, wherein, The UE also calculates a third distance between the reference point location and the satellite location.

33. The system according to claim 32, wherein, The UE also calculates the timing advance through the following operations: Divide the first distance by the speed to obtain the first propagation delay. Divide the third distance by the speed to obtain the third propagation delay. The first propagation delay, the third propagation delay, and the common timing advance are summed, and Double the summation result. The speed mentioned here is the speed of light in free space.

34. The system according to claim 33, wherein, The timing advance mentioned is one of full timing advance and differential timing advance.

35. The system according to claim 33, wherein, The reference point location is the satellite location.

36. The system according to claim 29, wherein, The UE is also configured to receive a second K-type receiver in the Common DCI format and / or MAC-CE format. offset And the second K offset It is a fixed number of bits.

Images