Parameter transmission method and device

Abstract

The embodiment of the invention provides a parameter transmission method and device, relates to the technical field of wireless communication, and is used for enabling terminal equipment to determine timing related parameters. In the method, a terminal device can receive first information. The first information may include a time parameter. Wherein the time parameter may be used to determine a timing offset. The timing offset amount includes at least one of a first timing offset amount and a second timing offset amount. Wherein the first timing offset can be used for determining the delay degree of information sending of the terminal equipment or the first timing offset can be used for determining the advance degree of information receiving of the terminal equipment, and the second timing offset can be used for determining the delay degree of effective configuration information received by the terminal equipment.

Description

[0001] This application is a divisional application. The application number of the original application is 202110055050.X, the original application date is January 15, 2021, and the entire content of the original application is incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technologies, and in particular, to a method and apparatus for transmitting parameters. Background Art

[0003] With the development of terrestrial communication, convenient data and voice services have been provided for urban, suburban, and rural users. However, for some areas with sparse population or unsuitable living conditions, communication networks are not covered, and voice and data services cannot be provided for users in these areas. Non-terrestrial networks (NTN) communication has characteristics such as a large coverage area and flexible network formation. NTN includes satellite communication, high-altitude platform communication, air to ground (ATG) communication, etc. If terrestrial and non-terrestrial networks are combined, seamless coverage communication services can be provided globally. Therefore, currently, research is being conducted on adapting 5G new radio (NR) technology to NTN communication to build a unified communication network for sky, air, and ground communication.

[0004] In non-terrestrial networks, the network device and the terminal device are far apart and have a huge difference in altitude, resulting in a large round-trip delay between the terminal device and the network device. In NTN communication, due to the influence of large delay and large delay compensation on the network side, problems such as insufficient scheduling delay of uplink data on the network side, insufficient feedback delay configured by the network side for the terminal device, or insufficient timing delay for the downlink configuration to take effect may occur. Therefore, the network device can indicate timing-related parameters to the terminal device to solve the above problems. For example, when the feedback delay configured by the network side for the terminal device is insufficient, the network device can indicate timing-related parameters to the terminal device, adjust the time slot for the terminal device to send feedback information, and increase the scheduling delay of the terminal device's feedback, so as to give the terminal device enough time length to perform timing advance adjustment.

[0005] However, when the network device indicates timing-related parameters to the terminal device, additional signaling overhead is required. Moreover, in order to solve problems such as insufficient scheduling delay of uplink data on the network side, insufficient feedback delay configured by the network side for the terminal device, or insufficient timing delay for the downlink configuration to take effect, the network device needs to send multiple timing-related parameters to the terminal device, resulting in a large signaling overhead. Summary of the Invention

[0006] This application provides a method and apparatus for transmitting parameters, which are used to send timing-related parameters to a terminal device and save signaling overhead.

[0007] In a first aspect, a method for transmitting parameters is provided. This method can be executed by a terminal device or a chip with similar terminal device functions. In this method, the terminal device can receive first information. The first information can include a time parameter. Among them, the time parameter can be used to determine a timing offset. Here, the timing offset includes at least one of a first timing offset and a second timing offset. Among them, the first timing offset can be used to determine the delay degree of the information sent by the terminal device or the first timing offset can be used to determine the advance degree of the information received by the terminal device, and the second timing offset can be used to determine the delay degree of the configuration information received by the terminal device from taking effect.

[0008] Based on the above solution, the terminal device can determine one of the first timing offset and the second timing offset based on the time parameter sent by the network device, which can solve the problems of insufficient scheduling delay of uplink data on the network side, insufficient feedback delay configured by the network side for the terminal device, or insufficient timing delay for the downlink configuration to take effect. In addition, the terminal device can determine the first timing offset and the second timing offset based on the time parameter, which can save signaling overhead.

[0009] In a possible implementation, the time parameter is also used to determine the delay start duration of the random access RAR window. Among them, the delay start duration of the RAR window is used to determine the delay degree of the terminal device to open the RAR window.

[0010] Based on the above solution, the terminal device can determine the delay start duration of the RAR window based on the time parameter and can delay the start of the RAR window. In addition, the terminal device can determine the first timing offset, the second timing offset, and the delay start duration of the RAR window based on the time parameter, and can eliminate the need for additional signaling overhead to indicate the delay start duration of the RAR window, which can reduce signaling overhead.

[0011] In a possible implementation, the time parameter can include the difference of the first timing offset and a common timing advance value TA_common, where TA_common is a parameter determined according to the round-trip delay between the satellite and the reference point. The terminal device can determine the first timing offset based on the difference of the first timing offset and TA_common. Among them, the first timing offset can satisfy the following formula:

[0012]

[0013] Among them, slot_duration represents the time unit, represents the ceiling operation, and △Koffset is the difference of the first timing offset.

[0014] In a possible implementation, the time parameters include the minimum round-trip delay parameter Service_RTD_min of the service link in the area covered by the satellite, the common timing advance value TA_common, and the duration of the RAR window. TA_common is a parameter determined according to the round-trip delay between the satellite and the reference point. The terminal device can determine the first timing offset based on Service_RTD_min, TA_common, and the duration of the RAR window. Among them, the first timing offset satisfies the following formula:

[0015]

[0016] Among them, slot_duration represents the time unit, represents the ceiling operation.

[0017] In a possible implementation, the time parameters may include the maximum round-trip delay parameter Service_RTD_max of the service link in the area covered by the satellite and the common timing advance value TA_common. TA_common is a parameter determined according to the round-trip delay between the satellite and the reference point. The terminal device can determine the first timing offset based on Service_RTD_max and TA_common. Among them, the first timing offset may satisfy the following formula:

[0018]

[0019] Among them, slot_duration represents the time unit, represents the ceiling operation.

[0020] In a possible implementation, the time parameters may include the duration of the RAR window, the delayed start duration of the RAR window, and the round-trip delay parameter Delay_compensated between the reference point and the network device. The terminal device can determine the first timing offset based on the duration of the RAR window, the delayed start duration of the RAR window, and Delay_compensated. Among them, the first timing offset may satisfy the following formula:

[0021]

[0022] Among them, slot_duration represents the time unit, represents the ceiling operation.

[0023] In a possible implementation, the time parameter may include the duration of the RAR window and the delayed start duration of the RAR window. The terminal device may determine a first timing offset based on the duration of the RAR window and the delayed start duration of the RAR window. Among them, the first timing offset may satisfy the following formula:

[0024]

[0025] where slot_duration represents the time unit, represents the ceiling operation.

[0026] In a possible implementation, the time parameter may include the duration of the RAR window, the delayed start duration of the RAR window, and a second timing offset. The terminal device may determine a first timing offset based on the duration of the RAR window, the delayed start duration of the RAR window, and the second timing offset. Among them, the first timing offset may satisfy the following formula:

[0027]

[0028] where slot_duration represents the time unit, represents the ceiling operation, and K_mac represents the second timing offset.

[0029] Based on the above possible implementation, the terminal device may determine a first timing offset based on the time parameter from the network device and the corresponding calculation relationship.

[0030] In a possible implementation, the terminal device may determine a first timing offset according to the time parameter and the adjustment parameter of the first timing offset. Among them, the adjustment parameter of the first timing offset is preset or indicated by the network device.

[0031] Based on the above solution, the terminal device may determine a first timing offset according to the adjustment parameter of the first timing offset and the time parameter, which may reduce the influence of factors such as positioning error on the time parameter and make the first timing offset more accurate.

[0032] In a possible implementation, the time parameter may include the round-trip delay parameter Delay_compensated between the reference point and the network device. The terminal device may determine a second timing offset based on Delay_compensated. Among them, the second timing offset may satisfy the following formula:

[0033]

[0034] where slot_duration represents the time unit, represents the ceiling operation.

[0035] In a possible implementation, the time parameters may include the round-trip delay parameter Feeder_RTD between the satellite and the network device and the common timing advance value TA_common, and TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine a second timing offset based on Feeder_RTD and TA_common. Among them, the second timing offset may satisfy the following formula:

[0036]

[0037] where slot_duration represents the time unit, represents the ceiling operation.

[0038] In a possible implementation, the time parameters may include the duration of the RAR window, the delay start duration of the RAR window, and the first timing offset. The terminal device may determine the second timing offset of the terminal device based on the duration of the RAR window, the delay start duration of the RAR window, and the first timing offset. Among them, the second timing offset satisfies the following formula:

[0039]

[0040] where slot_duration represents the time unit, represents the ceiling operation, and Koffset is the first timing offset.

[0041] In a possible implementation, the time parameters may include the first timing offset and the common timing advance value TA_common, and TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine the round-trip delay parameter TA_cal of the serving link of the terminal device based on the position information of the satellite. The terminal device may determine the second timing offset of the terminal device based on the first timing offset, TA_cal, and TA_common. Among them, the second timing offset may satisfy the following formula:

[0042]

[0043] where slot_duration represents the time unit, represents the ceiling operation, and Koffset is the first timing offset.

[0044] In a possible implementation, the time parameters may include the duration of the RAR window, the delay start duration of the RAR window, and the common timing advance value TA_common, where TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine the round-trip delay parameter TA_cal of the serving link of the terminal device based on the position information of the satellite. The terminal device may determine a second timing offset based on the duration of the RAR window, the delay start duration of the RAR window, TA_cal, and TA_common. Among them, the second timing offset satisfies the following formula:

[0045]

[0046] Among them, slot_duration represents the time unit, represents the ceiling operation.

[0047] Based on the above various possible implementations, the terminal device may determine a second timing offset based on the time parameters and calculation relationships from the network device.

[0048] In a possible implementation, the terminal device may determine a second timing offset according to the time parameters and the adjustment parameter of the second timing offset. Among them, the adjustment parameter of the second timing offset is preset or indicated by the network device.

[0049] Based on the above solution, the terminal device may determine a second timing offset based on the time parameters and the adjustment parameter of the second timing offset, which can reduce the influence of factors such as positioning errors on the time parameters and make the second timing offset more accurate.

[0050] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters may include the round-trip delay parameter Delay_compensated between the reference point and the network device and the common timing advance value TA_common. The TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine the round-trip delay parameter TA_cal of the serving link of the terminal device based on the position information of the satellite. The terminal device may determine the delay start duration of the first RAR window based on TA_cal, TA_common, and Delay_compensated. Among them, the delay start duration of the first RAR window satisfies the following formula:

[0051] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common.

[0052] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters may include a second timing offset and a common timing advance value TA_common. The TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine the round-trip delay parameter TA_cal of the serving link of the terminal device based on the location information of the satellite. The terminal device may determine the delay start duration of the first RAR window based on TA_cal, TA_common, and the second timing offset. Among them, the delay start duration of the first RAR window satisfies the following formula:

[0053] RAR_window_delay1 = TA_cal + TA_common + K_mac * slot_duration

[0054] Among them, slot_duration is the time unit, and K_mac is the second timing offset.

[0055] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters include the round-trip delay parameter Feeder_RTD between the satellite and the network device. The terminal device may determine the round-trip delay parameter TA_cal of the serving link of the terminal device based on the location information of the satellite. The terminal device may determine the delay start duration of the first RAR window based on TA_cal and Feeder_RTD. Among them, the delay start duration of the first RAR window satisfies the following formula:

[0056] RAR_window_delay1 = TA_cal + Feeder_RTD.

[0057] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters include the first timing offset and the duration of the RAR window. The terminal device may determine the delay start duration of the first RAR window based on the first timing offset and the duration of the RAR window. Among them, the delay start duration of the first RAR window may satisfy the following formula:

[0058] RAR_window_delay1 = Koffset * slot_duration – RAR_window

[0059] Among them, Koffset is the first timing offset, and slot_duration is the time unit.

[0060] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters may include the minimum round-trip delay parameter Service_RTD_min of the serving link in the area covered by the satellite and the round-trip delay parameter Delay_compensated between the reference point and the network device. The terminal device may determine the delay start duration of the first RAR window based on Service_RTD_min and Delay_compensated. Among them, the delay start duration of the first RAR window may satisfy the following formula:

[0061] RAR_window_delay1 = Service_RTD_min + Delay_compensated + TA_common.

[0062] Based on the above possible implementations, the terminal device may determine the delay start duration of the first RAR window based on the time parameters from the network device.

[0063] In a possible implementation, the terminal device may determine the delay start duration of the first RAR window according to the time parameters and the adjustment parameter of the delay start duration of the RAR window. Among them, the adjustment parameter of the delay start duration of the RAR window is preset or indicated by the network device.

[0064] Based on the above solution, the terminal device may determine the delay start duration of the first RAR window based on the time parameters and the adjustment parameter of the delay start duration of the RAR window, which can reduce the influence of factors such as positioning errors on the time parameters and make the delay start duration of the first RAR window more accurate.

[0065] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the second RAR window. The terminal device may determine the delay start duration of the second RAR window based on the delay start duration of the first RAR window and the timing advance value used by the terminal device. Alternatively, the terminal device may determine the delay start duration of the second RAR window based on the delay start duration of the first RAR window, the timing advance value used by the terminal device, and the adjustment parameter of the delay start duration of the RAR window. Among them, the adjustment parameter of the delay start duration of the RAR window is preset or indicated by the network device.

[0066] Based on the above solution, the terminal device may determine the delay start duration of the second RAR window based on the delay start duration of the first RAR window. The terminal device may choose to use different delay start durations of the RAR window according to its own understanding of the start time of the RAR window.

[0067] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the second RAR window, and the time parameter may include the delay start duration of the first RAR window. The terminal device may determine the delay start duration of the second RAR window based on the delay start duration of the first RAR window and the timing advance value used by the terminal device. Alternatively, the terminal device may determine the delay start duration of the second RAR window based on the delay start duration of the first RAR window, the timing advance value used by the terminal device, and the adjustment parameter of the delay start duration of the RAR window. Wherein, the adjustment parameter of the delay start duration of the RAR window is preset or indicated by the network device.

[0068] Based on the above solution, the terminal device may determine the delay start duration of the first RAR window based on the delay start duration of the second RAR window. The terminal device may select to use different delay start durations of the RAR window according to its different understandings of the start time of the RAR window.

[0069] In a possible implementation, the terminal device may receive indication information. The indication information may be used to indicate that the network device compensates for the round-trip delay of the feeder link, or the indication information may be used to indicate that the network device does not compensate for the round-trip delay of the feeder link.

[0070] Based on the above solution, the terminal device may determine whether the network device compensates for the round-trip delay of the feeder link based on the indication information, and thus determine the first timing offset, the second timing offset, and the delay start duration of the RAR window according to the time parameter.

[0071] In a possible implementation, the time parameter may include the difference between the common timing value and the first timing offset. Here, the common timing value is determined based on the round-trip delay of the feeder link. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the terminal device may determine the first timing offset based on the difference of the first timing offset and not based on the common timing value. When the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link, the terminal device may determine the first timing offset based on the difference of the first timing offset and the common timing value.

[0072] In a possible implementation, the time parameter includes the common timing value. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the terminal device determines the second timing offset based on the common timing value. When the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link, the terminal device determines the second timing offset based on 0 and not based on the common timing value.

[0073] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameter includes a common timing value, and the common timing value is determined based on the round-trip delay of the feeder link. The terminal device determines the round-trip delay parameter TA_cal of its service link based on the position information of the satellite. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the terminal device determines the delay start duration of the first RAR window based on TA_cal and the common timing value. When the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link, the terminal device determines the delay start duration of the first RAR window based on TA_cal and the common timing value.

[0074] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the second RAR window. The time parameter includes a common timing value, and the common timing value is determined based on the round-trip delay of the feeder link. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the terminal device determines the delay start duration of the second RAR window based on the common timing value. When the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link, the terminal device determines the delay start duration of the second RAR window based on the common timing value.

[0075] In a possible implementation, the time parameter may include a common timing value. The common timing value is determined based on the round-trip delay of the feeder link. The terminal device determines the round-trip delay parameter TA_cal of its service link based on the position information of the satellite. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the terminal device determines the timing advance value to be used based on TA_cal and not based on the common timing value. When the indication information is used to indicate that the network device has compensated for the round-trip delay of the feeder link, the terminal device determines the timing advance value to be used based on TA_cal and the common timing value.

[0076] Based on the above solution, it is possible to indicate whether the network device compensates for the round-trip delay of the feeder link through the indication information, and jointly indicate the round-trip delay of the feeder link and the common timing advance value through the common timing value, which can further save signaling overhead.

[0077] In a possible implementation, the time parameter includes the difference between the first timing offset and the second timing offset, and the terminal device determines the first timing offset based on the difference between the first timing offset and not based on the second timing offset.

[0078] Alternatively, the delay start duration of the RAR window includes the delay start duration of the first RAR window, and the time parameter may include a second timing offset. The terminal device determines the round-trip delay parameter TA_cal of the service link of the terminal device based on the position information of the satellite, and the terminal device determines the delay start duration of the first RAR window based on TA_cal and the second timing offset.

[0079] Alternatively, the delay start duration of the RAR window includes the delay start duration of the second RAR window, the time parameter may include a second timing offset, and the terminal device may determine the delay start duration of the first RAR window based on the second timing offset.

[0080] Alternatively, the time parameter may include the difference of the first timing offsets and a common timing value, the common timing value is determined based on the round-trip delay of the feeder link, and the terminal device determines the first timing offset based on the difference of the first timing offsets and the common timing value.

[0081] Alternatively, the time parameter may include a common timing value, the common timing value is determined based on the round-trip delay of the feeder link, and the terminal device determines the second timing offset based on 0 and not based on the common timing value.

[0082] Alternatively, the delay start duration of the RAR window includes the delay start duration of the first RAR window, the time parameter includes a common timing value, and the common timing value is determined based on the round-trip delay of the feeder link; the terminal device determines the round-trip delay parameter TA_cal of the service link of the terminal device based on the position information of the satellite, and the terminal device determines the delay start duration of the first RAR window based on TA_cal and the common timing value.

[0083] Alternatively, the delay start duration of the RAR window includes the delay start duration of the second RAR window, the time parameter includes a common timing value, and the common timing value is determined based on the round-trip delay of the feeder link; the terminal device determines the delay start duration of the second RAR window based on the common timing value.

[0084] Based on the above solutions, it is possible to indicate whether the network device compensates for the round-trip delay of the feeder link through the common timing value or K_mac, without the need for indication information, which can reduce signaling overhead.

[0085] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the first RAR window and the delay start duration of the second RAR window. The delay start duration of the second RAR window is determined based on the round-trip delay parameter Delay_compensated between the reference point and the network device. The time parameter includes the delay start duration of the second RAR window. The terminal device determines the second timing offset based on the delay start duration of the second RAR window. Alternatively, the terminal device determines the delay start duration of the first RAR window based on the delay start duration of the second RAR window and the timing advance value used by the terminal device.

[0086] Based on the above solution, the terminal device can determine the second timing offset or the delay start duration of the first RAR window based on the delay start duration of the second RAR window.

[0087] In a second aspect, a method for transmitting parameters is provided. This method can be executed by a network device or a chip with similar network device functions. In this method, the network device can send first information. The first information may include a time parameter, and the time parameter is used to determine a timing offset. The timing offset here includes at least one of a first timing offset and a second timing offset. The first timing offset can be used to determine the delay degree of the network device receiving information or the first timing offset is used to determine the advance degree of the network device sending information, and the second timing offset is used to determine the delay degree of the configuration information sent by the network device taking effect.

[0088] Based on the above solution, the network device can indicate to the terminal device the time parameter for determining one of the first timing offset and the second timing offset, which can solve the problems of insufficient scheduling delay of uplink data on the network side, insufficient feedback delay configured by the network side for the terminal device, or insufficient timing delay for downlink configuration to take effect. In addition, the time parameter can be used to determine the first timing offset and the second timing offset, which can save signaling overhead.

[0089] In a possible implementation, the time parameter is also used to determine the delay start duration of the random access RAR window. The delay start duration of the RAR window is used to determine the delay degree of the terminal device to open the RAR window.

[0090] Based on the above solution, the network device can indicate to the terminal device the time parameter for determining the delay start duration of the RAR window, and the terminal device can start the RAR window with a delay. In addition, since the time parameter can be used to determine the first timing offset, the second timing offset, and the delay start duration of the RAR window, it is not necessary to use additional signaling overhead to indicate the delay start duration of the RAR window, which can reduce signaling overhead.

[0091] In a possible implementation, the time parameter is used to determine the first timing offset. The time parameter may include the difference of the first timing offset and the common timing advance value TA_common, where TA_common is a parameter determined according to the round-trip time delay between the satellite and the reference point. The terminal device may determine the first timing offset based on the difference of the first timing offset and TA_common. Among them, the first timing offset may satisfy the following formula:

[0092]

[0093] where slot_duration represents the time unit, represents the ceiling operation, and △Koffset is the difference of the first timing offset.

[0094] Alternatively, the time parameter includes the minimum round-trip delay parameter Service_RTD_min of the service link in the area covered by the satellite, the common timing advance value TA_common, and the duration of the RAR window. TA_common is a parameter determined according to the round-trip time delay between the satellite and the reference point. The terminal device may determine the first timing offset based on Service_RTD_min, TA_common, and the duration of the RAR window. Among them, the first timing offset satisfies the following formula:

[0095]

[0096] where slot_duration represents the time unit, represents the ceiling operation.

[0097] Alternatively, the time parameter may include the maximum round-trip delay parameter Service_RTD_max of the service link in the area covered by the satellite and the common timing advance value TA_common. TA_common is a parameter determined according to the round-trip time delay between the satellite and the reference point. The terminal device may determine the first timing offset based on Service_RTD_max and TA_common. Among them, the first timing offset may satisfy the following formula:

[0098]

[0099] where slot_duration represents the time unit, represents the ceiling operation.

[0100] Alternatively, the time parameter may include the duration of the RAR window, the delay start duration of the RAR window, and the round-trip delay parameter Delay_compensated between the reference point and the network device. The terminal device may determine a first timing offset based on the duration of the RAR window, the delay start duration of the RAR window, and Delay_compensated. Among them, the first timing offset may satisfy the following formula:

[0101]

[0102] Among them, slot_duration represents the time unit, represents the ceiling operation.

[0103] Alternatively, the time parameter may include the duration of the RAR window and the delay start duration of the RAR window. The terminal device may determine a first timing offset based on the duration of the RAR window and the delay start duration of the RAR window. Among them, the first timing offset may satisfy the following formula:

[0104]

[0105] Among them, slot_duration represents the time unit, represents the ceiling operation.

[0106] Alternatively, the time parameter may include the duration of the RAR window, the delay start duration of the RAR window, and a second timing offset. The terminal device may determine a first timing offset based on the duration of the RAR window, the delay start duration of the RAR window, and the second timing offset. Among them, the first timing offset may satisfy the following formula:

[0107]

[0108] Among them, slot_duration represents the time unit, represents the ceiling operation, and K_mac represents the second timing offset.

[0109] Based on the above solution, the network device may indicate to the terminal device the time parameter for determining the first timing offset, and the terminal device may determine the first timing offset based on the time parameter from the network device and the corresponding calculation relationship.

[0110] In a possible implementation, the time parameter is used to determine a second timing offset. The time parameter may include the round-trip delay parameter Delay_compensated between the reference point and the network device. The terminal device may determine the second timing offset based on Delay_compensated. Among them, the second timing offset may satisfy the following formula:

[0111]

[0112] Among them, slot_duration represents the time unit, represents the ceiling operation.

[0113] Alternatively, the time parameter may include the round-trip delay parameter Feeder_RTD between the satellite and the network device and the common timing advance value TA_common, and TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine a second timing offset based on Feeder_RTD and TA_common. Among them, the second timing offset may satisfy the following formula:

[0114]

[0115] Among them, slot_duration represents the time unit, represents the ceiling operation

[0116] Alternatively, the time parameter may include the duration of the RAR window, the delayed start duration of the RAR window, and the first timing offset. The terminal device may determine a second timing offset of the terminal device based on the duration of the RAR window, the delayed start duration of the RAR window, and the first timing offset.

[0117] Among them, the second timing offset satisfies the following formula:

[0118]

[0119] Among them, slot_duration represents the time unit, represents the ceiling operation, and Koffset is the first timing offset.

[0120] Alternatively, the time parameter may include the first timing offset and the common timing advance value TA_common, and TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine the round-trip delay parameter TA_cal of the serving link of the terminal device based on the position information of the satellite. The terminal device may determine a second timing offset of the terminal device based on the first timing offset, TA_cal, and TA_common. Among them, the second timing offset may satisfy the following formula:

[0121]

[0122] Among them, slot_duration represents the time unit, represents the ceiling operation, and Koffset is the first timing offset.

[0123] Alternatively, the time parameter may include the duration of the RAR window, the delay start duration of the RAR window, and the common timing advance value TA_common, where TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine the round-trip delay parameter TA_cal of the serving link of the terminal device based on the position information of the satellite. The terminal device may determine the second timing offset based on the duration of the RAR window, the delay start duration of the RAR window, TA_cal, and TA_common. Among them, the second timing offset satisfies the following formula:

[0124]

[0125] where slot_duration represents the time unit, represents the ceiling operation.

[0126] Based on the above solution, the network device may indicate to the terminal device the time parameter for determining the second timing offset, and the terminal device may determine the second timing offset based on the time parameter from the network device and the calculation relationship.

[0127] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the first RAR window, and the time parameter is used to determine the delay start duration of the first RAR window. The time parameter may include the round-trip delay parameter Delay_compensated between the reference point and the network device and the common timing advance value TA_common. The TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine the round-trip delay parameter TA_cal of the serving link of the terminal device based on the position information of the satellite. The terminal device may determine the delay start duration of the first RAR window based on TA_cal, TA_common, and Delay_compensated. Among them, the delay start duration of the first RAR window satisfies the following formula:

[0128] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common.

[0129] Alternatively, the time parameter may include the second timing offset and the common timing advance value TA_common. The TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The terminal device may determine the round-trip delay parameter TA_cal of the serving link of the terminal device based on the position information of the satellite. The terminal device may determine the delay start duration of the first RAR window based on TA_cal, TA_common, and the second timing offset. Among them, the delay start duration of the first RAR window satisfies the following formula:

[0130] RAR_window_delay1 = TA_cal + TA_common + K_mac * slot_duration

[0131] Wherein, slot_duration is a time unit, and K_mac is a second timing offset.

[0132] Alternatively, the time parameter includes the round-trip delay parameter Feeder_RTD between the satellite and the network device. The terminal device can determine the round-trip delay parameter TA_cal of the service link of the terminal device based on the position information of the satellite. The terminal device can determine the delay start duration of the first RAR window based on TA_cal and Feeder_RTD. Wherein, the delay start duration of the first RAR window satisfies the following formula:

[0133] RAR_window_delay1 = TA_cal + Feeder_RTD.

[0134] Alternatively, the time parameter includes the first timing offset and the duration of the RAR window. The terminal device can determine the delay start duration of the first RAR window based on the first timing offset and the duration of the RAR window. Wherein, the delay start duration of the first RAR window can satisfy the following formula:

[0135] RAR_window_delay1 = Koffset * slot_duration – RAR_window

[0136] Wherein, Koffset is the first timing offset, and slot_duration is a time unit.

[0137] Alternatively, the time parameter can include the minimum round-trip delay parameter Service_RTD_min of the service link in the area covered by the satellite and the round-trip delay parameter Delay_compensated between the reference point and the network device. The terminal device can determine the delay start duration of the first RAR window based on Service_RTD_min and Delay_compensated. Wherein, the delay start duration of the first RAR window can satisfy the following formula:

[0138] RAR_window_delay1 = Service_RTD_min + Delay_compensated + TA_common.

[0139] In a possible implementation, the delay start duration of the RAR window includes the delay start duration of the first RAR window and the delay start duration of the second RAR window. The time parameter can be used to determine the delay start duration of the second RAR window, and the time parameter includes the delay start duration of the first RAR window. Alternatively, the time parameter is used to determine the delay start duration of the first RAR window, the time parameter includes the delay start duration of the second RAR window, and the delay start duration of the second RAR window is determined based on the round-trip delay parameter Delay_compensated between the reference point and the network device.

[0140] Based on the above solution, the network device can indicate to the terminal device the time parameter for determining the delay start duration of the first RAR window, and the terminal device can determine the delay start duration of the first RAR window based on the time parameter from the network device.

[0141] In a possible implementation, the network device sends indication information, where the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, or the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link. The time parameter can include a common timing value. Among them, the common timing value is determined based on the round-trip delay of the feeder link.

[0142] Based on the above solution, the network device can indicate whether to compensate for the round-trip delay of the feeder link based on the indication information, and jointly indicate the round-trip delay of the feeder link and the common timing advance value through the common timing value, which can further save signaling overhead.

[0143] In a possible implementation, the time parameter includes a second timing offset, or the time parameter includes a common timing value. Among them, the common timing value is determined based on the round-trip delay of the feeder link.

[0144] Based on the above solution, the network device can indicate whether to compensate for the round-trip delay of the feeder link through the common timing value or K_mac, and can avoid indicating through the indication information, which can reduce signaling overhead.

[0145] In a possible implementation, the network device sends at least one of an adjustment parameter for the first timing offset, an adjustment parameter for the second timing offset, and an adjustment parameter for the delay start duration of the RAR window.

[0146] Based on the above solution, by adjusting the first timing offset, the second timing offset, and the delay start duration of the RAR window through the adjustment parameter for the first timing offset, the adjustment parameter for the second timing offset, and the adjustment parameter for the delay start duration of the RAR window, the influence of factors such as positioning error on the time parameter can be reduced.

[0147] In a third aspect, a communication device is provided. The communication device may include various modules / units for performing the operations in the first aspect or any possible implementation manner of the first aspect, or may further include various modules / units for performing the operations in the second aspect or any possible implementation manner of the second aspect. For example, a processing module and a transceiver module.

[0148] In one example, when the communication device includes various modules / units for performing the operations in the first aspect or any possible implementation manner of the first aspect, the transceiver module may be used to receive first information. The first information includes a time parameter, and the time parameter is used to determine a timing offset. The timing offset may include at least one of a first timing offset and a second timing offset. For related descriptions, reference may be made to the first aspect above, which will not be elaborated here. The processing module may be used to determine the timing offset based on the time parameter, such as determining at least one of the first timing offset and the second timing offset.

[0149] In one example, when the communication device includes various modules / units for performing the operations in the second aspect or any possible implementation manner of the second aspect, the processing module may be used to generate first information. The first information includes a time parameter, and the time parameter is used to determine a timing offset. The timing offset may include at least one of a first timing offset and a second timing offset. For related descriptions, reference may be made to the second aspect above, which will not be elaborated here. The transceiver module may be used to send the first information.

[0150] In a fourth aspect, a communication device is provided, which may include a processor and a transceiver. The transceiver may perform the transceiver operations in the first aspect and / or various possible implementation manners, and the processor may perform the operations other than the transceiver operations in the first aspect and / or various possible implementation manners. For example, the transceiver may be used to receive first information, and the processor may be used to determine the timing offset based on the first information. Or, the transceiver may perform the transceiver operations in the second aspect and / or various possible implementation manners, and the processor may perform the operations other than the transceiver operations in the second aspect and / or various possible implementation manners. For example, the processor may be used to generate first information, and the transceiver may be used to send the first information.

[0151] In a fifth aspect, a communication device is provided, which may include a processor and a memory. The memory is used to store computer-executable instructions. When the controller runs, the processor executes some or all of the computer-executable instructions in the memory to perform the operation steps of the method in the first aspect or any possible implementation manner of the first aspect, or perform the operation steps of the method in the second aspect or any possible implementation manner of the second aspect.

[0152] In one design, the processor and the memory are integrated together.

[0153] In a sixth aspect, a chip is provided, which may include a logic circuit and a communication interface. Among them, the communication interface may perform the transceiver operations in the first aspect and / or each possible implementation manner above, and the logic circuit may perform operations other than the transceiver operations in the first aspect and / or each possible implementation manner above. For example, the communication interface may be used to input the first information. The logic circuit may be used to determine the timing offset based on the time parameter. Alternatively, the communication interface may perform the transceiver operations in the second aspect and / or each possible implementation manner above, and the logic circuit may perform operations other than the transceiver operations in the second aspect and / or each possible implementation manner above. For example, the logic circuit may be used to generate the first information, and the communication interface may be used to send the first information.

[0154] In a seventh aspect, a communication system is provided, which may include a communication device for performing the method in the first aspect and / or each possible implementation manner and a communication device for performing the method in the second aspect and / or each possible implementation manner.

[0155] In an eighth aspect, the present application provides a computer-readable storage medium, in which instructions are stored, and when it runs on a computer, it causes the computer to execute the methods in the above aspects.

[0156] In a ninth aspect, the present application provides a computer program product storing instructions, and when it runs on a computer, it causes the computer to execute the methods in the above aspects.

[0157] In addition, the beneficial effects of the third aspect to the eighth aspect can refer to the beneficial effects shown in the first aspect and the ninth aspect. Description of the Drawings

[0158] Figure 1 It is a schematic diagram of the round-trip delay between a satellite and a terminal device;

[0159] Figure 2 It is a schematic diagram of the relationship between the height of a satellite and the round-trip delay;

[0160] Figure 3 It is a schematic diagram of the round-trip delay in terrestrial communication;

[0161] Figure 4 It is a schematic diagram of the round-trip delay of communication between a network device and a terminal device;

[0162] Figure 5A It is a schematic diagram of a terminal device sending HARQ-ACK / NACK without introducing the first timing offset;

[0163] Figure 5BSchematic diagram of the terminal device sending HARQ-ACK / NACK when introducing the first timing offset;

[0164] Figure 6A Schematic diagram of the terminal device sending uplink data when not introducing the first timing offset;

[0165] Figure 6B Schematic diagram of the terminal device sending uplink data when introducing the first timing offset;

[0166] Figure 7A Schematic diagram of the effective time of the MAC signaling when not introducing the second timing offset;

[0167] Figure 7B Schematic diagram of the effective time of the MAC signaling when introducing the second timing offset;

[0168] Figure 8 Schematic diagram of the common timing advance value at the reference point in the feeder link provided by the embodiment of the present application;

[0169] Figure 9 Schematic diagram of the common timing advance value at the reference point in the serving link provided by the embodiment of the present application;

[0170] Figure 10A Schematic diagram of the terminal device opening the RAR window when not introducing the delay start duration of the RAR window;

[0171] Figure 10B Schematic diagram of the terminal device opening the RAR window when introducing the delay start duration of the RAR window;

[0172] Figure 11 One of the schematic diagrams of the communication system applicable to the transmission method of the parameters provided by the embodiment of the present application;

[0173] Figure 12 One of the schematic diagrams of the communication system applicable to the transmission method of the parameters provided by the embodiment of the present application;

[0174] Figure 13 Schematic diagram of the time parameter provided by the embodiment of the present application;

[0175] Figure 14 Exemplary flowchart of the transmission method of the parameters provided by the embodiment of the present application;

[0176] Figure 15A Schematic diagram of determining the RAR window in the actual timing manner provided by the embodiment of the present application;

[0177] Figure 15B Schematic diagram of determining the delay start duration of the RAR window in the actual timing manner provided by the embodiment of the present application;

[0178] Figure 16A Schematic diagram of determining the RAR window in a logical timing manner provided by an embodiment of the present application;

[0179] Figure 16B Schematic diagram of determining the delay start duration of the RAR window in a logical timing manner provided by an embodiment of the present application;

[0180] Figure 17 Schematic diagram of the position of the reference point provided by an embodiment of the present application;

[0181] Figure 18 One of the schematic diagrams of the communication device provided by an embodiment of the present application;

[0182] Figure 19 One of the schematic diagrams of the communication device provided by an embodiment of the present application;

[0183] Figure 20 Schematic diagram of the terminal device provided by an embodiment of the present application. Detailed implementation manners

[0184] The following is an explanation and description of the nouns involved in the embodiments of the present application for the convenience of understanding the embodiments of the present application.

[0185] 1) The multiple involved in the embodiments of the present application refers to two or more. "And / or" describes the association relationship of the associated objects and indicates that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the front and back associated objects. In addition, it should be understood that although terms such as first and second may be used to describe each object in the embodiments of the present invention, these objects should not be limited to these terms. These terms are only used to distinguish each object from each other.

[0186] 2) + / - can mean "+" or "-". For example, A+ / -B can be understood as A+B or A-B.

[0187] The following is an explanation of the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.

[0188] In a non-terrestrial network, the distance between the satellite and the terminal device is relatively far and the altitude difference is relatively large, resulting in a large round-trip delay. Taking satellite communication as an example, refer to Figure 1 , when the terminal device is near the position below the satellite, the distance between the terminal device and the satellite is the closest, and the round-trip delay between the terminal device and the satellite is the smallest; when the communication elevation angle between the terminal device and the satellite is the smallest, the round-trip delay between the terminal device and the satellite is the largest. In the communication scenario of the geostationary earth orbit (GEO), the maximum round-trip delay between the satellite and the terminal device can reach 541.46 ms. Refer toFigure 2 When the orbital altitude of the satellite is 1200 km, the minimum round-trip delay between the terminal device and the satellite is 8 ms, and the maximum round-trip delay between the terminal device and the satellite is 20.9 ms. When the satellite operates in the staring mode, the mobile communication elevation angle of the satellite can vary from an elevation angle of 90 degrees to an elevation angle of 10 degrees, and the round-trip delay will gradually change from 8 ms to 20.9 ms. In the terrestrial communication network, the altitude difference between the base station and the terminal device is not significant, so the round-trip delay is relatively small. Refer to Figure 3 In terrestrial communication, the maximum radius of a cell is 300 km, and the maximum round-trip delay is 2 ms.

[0189] In summary, the round-trip delay of the NTN communication system is much greater than that of terrestrial communication.

[0190] Currently, in order to avoid inter-symbol interference (ISI) when the uplink data arrives at the network device, it is required that the time difference of the uplink data of the terminal devices using the same frequency band does not exceed the size of the cyclic prefix (CP) when it arrives at the network device. Therefore, the terminal device can perform timing advance adjustment on the uplink data. Taking terrestrial communication as an example, refer to Figure 4 If the network device does not perform delay compensation on the uplink data, the value of the timing advance adjustment made by the terminal device on the uplink data is equal to the round-trip delay between the terminal device and the network device. Therefore, in NTN communication, due to the large round-trip delay, the value of the timing advance adjustment made by the terminal device on the uplink data will also be very large.

[0191] To solve the above problems, timing-related parameters such as the first timing offset, the second timing offset, the common timing advance value (TA_common), and the delay start duration of the random access response (RAR) window are introduced in NTN communication. Below, the above-mentioned timing-related parameters will be introduced separately.

[0192] I. The first timing offset

[0193] The first timing offset Koffset can solve problems such as insufficient feedback delay configured by the network side for the terminal device. The following is an example of the scenario where Koffset is used.

[0194] Scenario 1

[0195] After the terminal device receives the physical downlink shared channel (PDSCH) sent by the network device, it can send a hybrid automatic repeat request (HARQ) acknowledgement (ACK) or non-acknowledgement (NACK) feedback to indicate whether the decoding of the PDSCH is successful. If the terminal device receives the PDSCH in downlink slot n, then the terminal device can feedback HARQ-ACK or HARQ-NACK in uplink slot n + K 1 slots. Refer to Figure 5A , the maximum value of the timing advance adjustment that the terminal device can make is K 1 -1 slot lengths. Currently, the maximum value of K 1 is 15. When the subcarrier spacing (SCS) is 15 KHz and the length of one slot is 1 ms, the maximum value of the timing advance adjustment that the terminal device can make is 14 ms. Through Figure 2 it can be known that the round-trip delay in NTN communication will be greater than 14 ms, that is, the value of the timing advance adjustment that the terminal device needs to make for uplink data will also be greater than 14 ms. Therefore, K 1 -1 slot lengths cannot provide enough time length for the terminal device to make timing advance adjustment and cannot meet the timing advance requirements of the terminal device for round-trip delay compensation in NTN communication. As Figure 5A shown, when the value of the timing advance adjustment for the terminal device to send uplink data is greater than K 1 -1 slot lengths, the terminal device can no longer deliver HARQ-ACK or HARQ-NACK to the network device on time.

[0196] Therefore, a first timing offset Koffset can be introduced to ensure that there is enough time length for the terminal device to make timing advance adjustment between receiving the PDSCH data and sending HARQ-ACK or HARQ-NACK.

[0197] Refer to Figure 5B, the terminal device can send HARQ-ACK or HARQ-NACK in time slot n+K1+Koffset. Accordingly, the network device can receive HARQ-ACK or HARQ-NACK in the uplink time slot n+K1+Koffset. By introducing Koffset, the time slot in which the terminal device sends HARQ-ACK or HARQ-NACK can be adjusted, and the scheduling delay of the terminal device to feedback HARQ-ACK or HARQ-NACK can be increased, so as to give the terminal device enough time length to perform timing advance adjustment.

[0198] Scenario 2

[0199] When scheduling the physical uplink shared channel (PUSCH) by downlink control information (DCI), there will be a problem that the scheduling delay is less than the value of the timing advance adjustment. Refer to Figure 6A , the terminal device receives the uplink grant (UL grant) scheduled by DCI in the downlink time slot n, and the terminal device sends the physical uplink shared channel (physical uplink shared channel, PUSCH) data in the corresponding uplink time slot . Among them, μ,PUSCH is related to the subcarrier spacing of PUSCH, μ,PDCCH is related to the subcarrier spacing of PDCCH, PUSCH subcarrier spacing = 2 μ,PUSCH *15KHz, PDCCH subcarrier spacing = 2 μ,PDCCH *15KHz. When the time length of the value of the timing advance adjustment for sending uplink data is greater than K 2 -1 time slot length, the terminal device will not be able to send uplink data in the time slot , and cannot make the network device receive the corresponding PUSCH data in the time slot as agreed . In the prior art, the value range of K 2 is 0-32. When the uplink subcarrier width is the same, the time slot length of K 2 will also be different. As shown in Table 1, when SCS = 15KHz, the maximum value of the time slot length of K 2 is 32ms. It can be seen that under the condition of different subcarrier widths, the maximum value that the terminal device can perform timing advance adjustment when sending PUSCH data scheduled by DCI is 32ms. For the GEO scenario, the maximum round-trip delay is 541.46ms, and the value of K 2 cannot meet the timing advance requirements. For the low earth orbit (LEO)-1200 scenario, when the subcarrier width is 30KHz, K 2The maximum value of a time slot length is 16 ms, and the maximum round-trip delay in the LEO-1200 scenario is greater than 20 ms. Therefore, the value of K 2 also cannot meet the requirements for timing advance adjustment in this scenario.

[0200] Table 1

[0201] Uplink subcarrier width <![CDATA[K 2 Maximum value of the length of 15KHz 32ms 30KHz 16ms 60KHz 8ms 120KHz 4ms

[0202] Therefore, by introducing the first timing offset Koffset, there can be a sufficient time length between receiving the DCI and sending the PUSCH, allowing the terminal device to have sufficient scheduling delay for the PUSCH to perform timing advance adjustment.

[0203] Refer to Figure 6B and the terminal device can send the PUSCH in time slot By Koffset, the delay of the DCI scheduling uplink data is increased, ensuring that the terminal device has sufficient time interval to perform timing advance adjustment.

[0204] Scenario Three

[0205] In the two-step random access process, the terminal device can send Message A (message A, MsgA) to the network device. If the network device fails to successfully decode all of MsgA, such as only successfully decoding the preamble. Then the network device can send a fallback RAR message (fall back RAR) to the terminal device. After receiving the PDSCH carrying the fallback RAR message in time slot n, the terminal device has to send the random access Message 3 (message 3, Msg3) scheduled by the fallback RAR message on the uplink PUSCH. Among them, the terminal device can send Msg3 in time slot n + K 2 + Δ, where Δ is a value agreed upon by the protocol. From the foregoing, the value of K 2 cannot meet the requirements for timing advance adjustment.

[0206] To have a sufficient time length between receiving the PDSCH and sending the PUSCH, and allow the terminal device to have sufficient scheduling delay for the PUSCH to perform timing advance adjustment, Koffset can be introduced. The terminal device can receive the PDSCH data carrying the fallback RAR message in the downlink time slot n, and the terminal device can send Msg3 in time slot n + K 2 + Δ + Koffset.

[0207] Scenario Four

[0208] When the terminal device receives DCI requesting channel state information (CSI), the terminal device may send a PUSCH carrying the CSI. For example, when the terminal device receives DCI requesting CSI in slot n, the terminal device needs to send a PUSCH carrying the CSI in slot n+K. Here, K is determined according to the DCI instruction. However, since the round-trip delay in non-terrestrial communication scenarios is much greater than that in terrestrial communication scenarios, the value of K in the prior art cannot meet the requirement of the terminal device for timing advance adjustment of the PUSCH.

[0209] Therefore, Koffset can be introduced so that there is a sufficient time length between receiving the DCI and sending the PUSCH, allowing the terminal device to have sufficient time for timing advance adjustment of sending the PUSCH. The terminal device may send the PUSCH in slot n+K+Koffset.

[0210] Scenario Five

[0211] When the terminal device receives a DCI instruction triggering an aperiodic sounding reference signal (SRS) in slot n, the terminal device needs to send an SRS signal in the slot after each triggering of the SRS resource. Here, k is determined by the high-layer parameter slot offset of each triggering of the SRS resource. μ, SRS is related to the subcarrier spacing of sending the SRS, and μ, PDCCH is related to the subcarrier spacing of the PDCCH. The descriptions of μ, PUSCH and μ, PDCCH in Scenario Two can be referred to. However, since the round-trip delay in non-terrestrial communication scenarios is much greater than that in terrestrial communication scenarios, the value of k in the prior art cannot meet the requirement of the terminal device for timing advance adjustment of sending the SRS.

[0212] Therefore, Koffset can be introduced so that there is a sufficient time length between receiving the DCI and sending the SRS, allowing the terminal device to have sufficient time for timing advance adjustment of sending the SRS. The terminal device may send the SRS in the slot send the SRS.

[0213] Scenario Six

[0214] When the terminal device sends a CSI report in the uplink slot n’, the terminal device needs to receive a CSI reference resource in the slot n-n CSI_ref from the terminal device. Here, n CSI_ref is a value related to the CSI report type agreed upon by the protocol. μ UL is related to the uplink data subcarrier spacing, and μ DLIt is related to the downlink data subcarrier spacing, and the descriptions of μ, PUSCH and μ, PDCCH in Scenario 2 can be referred to. However, since the round-trip delay in the non-terrestrial communication scenario is much greater than that in the terrestrial communication scenario, the value of n in the prior art CSI_ref cannot meet the requirement of the terminal device for timing advance adjustment of the received CSI reference resource.

[0215] Therefore, Koffset can be introduced so that there is enough time length between receiving the CSI reference resource and sending the CSI report, allowing the terminal device to have enough time length to perform timing advance adjustment on the received CSI reference resource. The terminal device can receive the CSI reference resource at slot n - n CSI_ref + Koffset.

[0216] Scenario 7.

[0217] The network device indicates the transmission occasion of the physical random access channel (PRACH) to the terminal device through the PDCCH. For example, the network device can randomly select a random access occasion from consecutive random access occasions (PRACH occasion) through media access control (MAC) signaling. The terminal device can determine the next available random access occasion according to the PDCCH. To solve the problem of large round-trip delay in the non-terrestrial communication scenario, the terminal device can determine the next available random access occasion, such as the random access preamble, after a time length of Koffset after the last symbol of the PDDCH that can be received.

[0218] It should be noted that the time interval between the first time-domain symbol of the random signal sent by the terminal device and the last time-domain symbol of the received PDCCH should be greater than or equal to N T,2 + Δ BWPSwitching + Δ Delay + T switch ms. If Koffset is considered, the time interval should be greater than or equal to N T,2 + Δ BWPSwitching + Δ Delay + T switch + Koffset * slot length ms. N T,2 represents the time length of N2 time-domain symbols, and this time length corresponds to the ability of the terminal device to process the PUSCH. Assume that the subcarrier spacing of the PDCCH and the PRACH is configured as the minimum subcarrier spacing. If the activated uplink bandwidth part (BWP) does not change, then Δ BWPSwitching= 0. For other cases, the value of Δ configured by the network device or agreed upon by the protocol can be used. BWPSwitching If the frequency range of the PRACH is FR1, then Δ Delay = 0.5 ms; if the frequency range of the PRACH is FR2, then Δ Delay = 0.25 ms. Generally, FR1 represents the frequency range not greater than 6 GHz, and FR2 represents the frequency range greater than 6 GHz and less than 52.6 GHz. T switch is the conversion interval time, which is configured by the network device or agreed upon by the protocol.

[0219] In addition, it should be noted that the time unit of the first timing offset Koffset in the embodiments of the present application is described by taking the uplink / downlink slot length as an example. It should be understood that Koffset can also be in other time units, such as ms. In the above-mentioned various scenarios, the time unit can be unified when using Koffset. For example, if the time unit of Koffset is ms, and the uplink slot length is related to the uplink subcarrier spacing μ DL is related, so the length of Koffset in ms is equal to number of slot lengths. Similarly, if Koffset uses ms as the unit, then Koffset in other application scenarios can be replaced with or When Koffset uses other time units, only Koffset needs to be converted to the corresponding slot length unit. Or, convert other parameters using the slot length as the time unit to the same time unit as Koffset, which will not be elaborated below.

[0220] Hereinafter, Scenario 2 will be used as an example for illustration.

[0221] The terminal device receives the PDSCH data carrying the RAR message in the downlink slot n. The terminal device needs to send the random access message 3 (message 3) scheduled by the RAR in the uplink PUSCH slot n + K2 + Δ + Koffset / ( where Δ is a value agreed upon by the protocol. The reason for the modification is that if the time unit of Koffset is ms, and the uplink slot length is related to the uplink subcarrier spacing, that is, related to μ UL is related, the length of Koffset in ms is equal to number of slot lengths. Similarly, if Koffset uses ms as the unit, then the description of Koffset in other application scenarios can be replaced with or For other units used for Koffset, it is only necessary to convert Koffset into the number of corresponding time slot length units. Alternatively, convert other parameters representing the time slot length into the same time unit as that used for Koffset. The principle is similar to the above description and will not be elaborated here.

[0222] II. Second timing offset

[0223] To distinguish it from the first timing offset, the timing-related parameter here can be called the second timing offset. It should be noted that the second timing offset can be the same as or different from the first timing offset, and the difference lies in the different application scenarios of the two. The second timing offset K_mac can solve the problem of insufficient timing delay for the effective time of the downlink configuration sent by the network side. Below, the scenarios for introducing K_mac are introduced.

[0224] The network device receives a HARQ-ACK for the PDSCH carrying the MAC signaling in the uplink time slot n. This MAC signaling is a configuration instruction for the downlink signal. The effective time of this downlink signal configuration instruction is the first time slot after the downlink time slot to take effect. Among them, is the number of time slots included in a subframe when the subcarrier spacing is 2 μ *15KHz, and X is a non-negative integer agreed in the protocol or configured by the network device.

[0225] The MAC signaling carried in the PDSCH can be a resource configuration for the downlink zero power channel state information signal (ZP CSI-RS), or a deactivation of the already effective downlink ZP CSI-RS resource configuration. Another example is that the MAC instruction carried in the PDSCH can indicate the mapping relationship between the transmission configuration indication (TCI) state and the code point in the DCI field. Another example is that the MAC instruction carried in the PDSCH can be an activation / deactivation of the semi-static CSI reporting configuration. Another example is that the MAC instruction carried in the PDSCH can be an activation / deactivation of the CSI-RS / channel state information-interference measurement (CSI-IM) configuration.

[0226] Refer to Figure 7A and it can be seen that the timing compensation of the network device for the uplink data is greater than or equal to When the network device receives the HARQ ACK / NACK for the PDSCH carrying the MAC signaling sent by the terminal device, it will not be earlier than the effective time of the MAC signaling. The network device will not be able to know in time whether the terminal device has correctly decoded the MAC signaling, that is, when the MAC signaling becomes effective, the network device has not yet received the HARQ ACK / NACK feedback from the terminal device. After the terminal device sends the HARQ ACK in time slot n, it will consider that the MAC signaling becomes effective from the downlink time slot starts to take effect. This will cause different understandings of the effective time of the MAC signaling between the terminal device and the network device, resulting in communication conflicts. Here, the timing compensation value for the uplink data of the network device represents the size of the reception window delay compensation when the network device receives the uplink data.

[0227] To solve the above problems, a K_mac parameter can be introduced. Assume that the MAC signaling is in the first time slot after the downlink time slot , that is, time slot becomes effective. Referring to Figure 7B , it can be seen that when using the K_mac value to delay the effective time of the MAC signaling, that is, the time length represented by K_mac should not be less than the time length represented by the timing compensation value for the uplink data of the network device, ensuring that the MAC signaling becomes effective only after the network device receives the corresponding HARQ-ACK, and ensuring that the terminal device and the network device have the same understanding of the effective time of the MAC signaling.

[0228] III. Common Timing Advance Value TA_common

[0229] A terminal device with positioning function can process the round-trip delay of the service link based on its own location and the location of the satellite. Among them, the location of the satellite can be obtained according to the ephemeris information. However, the satellite cannot obtain the round-trip delay of the feeder link. If the network side performs delay compensation on the uplink signal, then the terminal device cannot obtain the delay compensation value of the network side either. Therefore, a terminal device with positioning function cannot obtain complete propagation delay information only through its own location information and the location information of the satellite, including the round-trip delay of the feeder link and the propagation delay compensation value of the network side.

[0230] Referring to Figure 8 , if the compensation value of the propagation delay compensation performed by the network side on the uplink signal is less than the round-trip delay of the feeder link, then the common timing advance value (TA_common) can be used to represent the remaining propagation delay value after subtracting the propagation delay compensation of the network side from the feeder link. For example, if the round-trip propagation delay of the feeder link is a and the propagation delay compensation value of the network side for the feeder link is b, then the TA_common sent by the network side to the terminal device is equal to a - b. At this time, since the reference point is on the feeder link, the value of TA_common is a positive number.

[0231] The terminal device can calculate the round-trip delay TA_cal of the service link based on its own position and the position of the satellite. When the terminal device receives TA_common, it can obtain the timing advance value (TA) used when the terminal device sends the uplink signal according to the sum of TA_cal and TA_common.

[0232] Refer to Figure 9 , when the compensation value of the propagation delay compensation made by the network side for the uplink signal is greater than the round-trip delay of the feeder link, TA_common can be used to represent the compensation value of the network side for the partial propagation round-trip delay of the service link. For example, the absolute value of TA_common is d. At this time, since the reference point is on the service link, TA_common is negative. The TA_common sent by the network side to the terminal device is -d. Then, the terminal device can add the calculated round-trip delay of the service link and TA_common to obtain the TA value for timing advance adjustment of the uplink signal.

[0233] IV. Delay start duration of the RAR window (RAR_window_delay)

[0234] Scenario 1

[0235] In the prior art, in the 4-step random access procedure, the terminal device sends Message 1 (Msg1). After the last symbol of Msg1, or after the last symbol of the PRACH occasion of the preamble transmitted by the terminal device for PRACH, the terminal device starts to detect the window of the physical downlink control channel (PDCCH) information at the first symbol of the earliest configured control resource set (CORESET). The terminal device can detect the PDCCH information within this window, and this detection window can be referred to as the random access response (RAR) window / reception window / detection window. The terminal device can receive the corresponding Message 2 (Msg2) RAR message according to the PDCCH. Here, the length of the RAR window is defined as RAR_window. The network device sends this RAR_window to the terminal device. For example, the RAR reception window length is configured for the terminal device by means of broadcasting or through the ra-ResponseWindow or ra-ResponseWindow-v1610 parameter. If the terminal device fails to successfully detect the PDCCH message within the RAR window, the random access fails. Currently, the maximum value that RAR_window can be configured is 160 ms. In the GEO scenario, the round-trip delay can reach 541.46 ms.

[0236] See Figure 10A , since the length of the RAR_window is less than the round-trip delay, the terminal device cannot receive the PDCCH information sent by the network device within the RAR window, and the random access fails. In the figure, the PDCCH is used to schematically represent the PDCCH information in the CORESET, that is, the resource information represented by the PDCCH can be the resources occupied by the CORESET. The following can all be understood in this way and will not be elaborated any further.

[0237] In the two-step random access procedure, the terminal device sends MsgA. After the last symbol of the PUSCH occasion (PUSCHOccasion) corresponding to the PRACH transmission or the last symbol of the PRACH occasion (PRACH Occasion), the terminal device starts to detect the PDCCH information at the first symbol of the earliest configured CORESET, or the terminal device receives the corresponding MsgB RAR message according to the PDCCH. The terminal device detects the PDCCH information or receives the corresponding MsgB RAR message within the RAR window. The network device can send the length of this RAR window to the terminal device, and its length is defined as RAR_window. Currently, the maximum configurable value of RAR_window is 320 ms. If the terminal device fails to successfully detect the PDCCH information within the RAR window, the random access fails. Similar to the above RAR window, when the round-trip time delay of signal transmission is greater than the time length of MsgB_RAR_window, the terminal device cannot receive the PDCCH information indicating the MsgB RAR message sent by the network device within the window, and the random access fails.

[0238] To avoid the failure of the terminal device to receive the PDCCH information or receive the MsgB RAR message, a delay start duration or start offset can be introduced, which can be defined as RAR_widow_delay, used to represent the delay degree of starting the RAR window. Refer to Figure 10B , in the four-step random access procedure, the terminal device sends Msg1. After the last symbol of Msg1, or after the last symbol of the PRACH occasion used by the terminal device, after waiting for the duration of RAR_widow_delay, the RAR window is started at the first symbol of the earliest configured CORESET to detect the PDCCH, or receive the Msg2 RAR message. In the two-step random access procedure, the terminal device sends MsgA. After the last symbol (symbol) corresponding to the PUSCH occasion or the PRACH occasion, after waiting for the duration of RAR_widow_delay, the terminal device starts the RAR window at the first symbol of the earliest CORESET to detect the PDCCH information, that is, to open the MsgB-RAR reception window / detection window or the MsgB response reception window (MsgBresponse window).

[0239] It should be noted that the RAR_widow_delay used in the four-step random access procedure and the RAR_widow_delay used in the two-step random access procedure can be the same or different. Here, for the sake of convenient description, convenient use, and saving signaling, both are represented by RAR_window_delay or RAR_offset.

[0240] The RAR_widow_delay can ensure that the terminal device can successfully receive the PDCCH information within the RAR window. In addition, the terminal device can avoid starting the detection process before the PDCCH arrives, saving power.

[0241] Scenario 2

[0242] In the 4-step random access procedure or when the 2-step random access falls back to the 4-step random access procedure, once the terminal device sends Message 3 (message3, Msg3), the terminal device starts the random access contention resolution timer (ra-ContentionResolutionTimer) at the first symbol after sending Msg3. Alternatively, the terminal device starts the random access contention resolution timer (ra-ContentionResolutionTimer) at the first symbol after retransmitting Msg3. During the effective period of the random access contention resolution timer, the terminal device detects the PDCCH information sent by the network device. The PDCCH can carry the cell-radio network temporary identifier (C-RNTI) or the semi-static C-RNTI (TEMPORARY_C-RNTI), and may contain a new uplink transmission grant. If the terminal device successfully detects the PDCCH sent by the network device, the random access contention resolution timer can be stopped, and thus the random access procedure can be considered successfully completed. If the terminal device fails to successfully detect the PDCCH sent by the network device before the random access contention resolution timer expires or until the random access contention resolution timer expires, the random access procedure is considered to have failed.

[0243] Currently, the length of the random access contention resolution timer is sent from the network device to the terminal device. The maximum configurable value of the random access contention resolution timer is 64 ms. When the terminal device sends Msg3, it starts the random access contention resolution timer and begins to receive PDCCH. In non-terrestrial communication scenarios such as the GEO scenario, the round-trip delay can reach 541.46 ms. After the network device receives Msg3, the round-trip delay for sending PDCCH and message 4 (Msg4) to the terminal device is relatively large. The length of the random access contention resolution timer is much smaller than the round-trip delay, and the terminal device cannot receive the PDCCH information within the timing validity period of the random access contention resolution timer, resulting in random access failure. Therefore, the random access contention resolution timer can be started with a delay to solve the above problem, that is, the terminal device waits for a period of time and then starts the random access contention resolution timer to detect the PDCCH information, which can enable the terminal device to receive the corresponding PDCCH within the timing validity period of the random access contention resolution timer and can also achieve the purpose of power saving. Among them, the duration of starting the random access contention resolution timer with a delay can be defined as the random access contention resolution timer delay start duration.

[0244] It should be noted that the RAR_window_delay used in the 4-step random access process, the RAR_window_delay used in the 2-step random access process, and the random access contention resolution timer delay start duration can be the same or different. Here, for the convenience of description, use, and saving signaling, RAR_window_delay is used to represent all of them.

[0245] In summary, to solve the problem of large round-trip delay in non-terrestrial communication, the network device can send the timing-related parameters in the above one to four to the terminal device. However, sending these timing-related parameters will generate additional signaling overhead.

[0246] Based on the above problems, an embodiment of the present application provides a method for transmitting parameters. The method provided by the embodiment of the present application can be used in any communication system, which can be a third generation partnership project (3GPP) communication system, for example, a long term evolution (LTE) system, or a fifth generation (5G) mobile communication system, a new radio (NR) system, a new radio vehicle to everything (NR V2X) system, and can also be applied to a system with a hybrid network of LTE and 5G, or a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT), and other next-generation communication systems, or a non-3GPP communication system, without limitation.

[0247] The method provided by the embodiment of the present application can be applied to various communication scenarios, for example, it can be applied to one or more of the following communication scenarios: enhanced mobile broadband (eMBB), ultra reliable low latency communication (URLLC), machine type communication (MTC), massive machine type communications (mMTC), D2D, V2X, and IoT and other communication scenarios.

[0248] The method provided by the embodiment of the present application can also be applied to a long-distance communication scenario, such as a satellite communication scenario where the distance between a terminal device and a network device is constantly changing, or other long-distance communication scenarios, without limitation. The following takes Figure 11 as an example to describe the parameter transmission method provided by the embodiment of the present application. Figure 11 shows a schematic diagram of the communication system provided by the embodiment of the present application. As Figure 11 shown, taking the NTN communication system as an example, the communication system can be composed of a terminal device 01, a satellite 02 (or satellite base station), a gateway station 03 (or ground station, gateway), and a ground base station (gNB) 04.

[0249] Referring to Figure 12 , the method provided by the embodiment of the present application can also be applied to such asFigure 12 The air-to-ground (ATG) scenario shown. In this ATG communication system, it may include at least one network device and at least one terminal device.

[0250] The terminal device involved in this application includes a device that provides voice and / or data connectivity to a user. Specifically, it includes a device that provides voice to a user, or a device that provides data connectivity to a user, or a device that provides both voice and data connectivity to a user. The terminal may include a user equipment (UE), a wireless terminal, a mobile terminal, a device-to-device (D2D) terminal, a vehicle-to-everything (V2X) terminal, a machine-to-machine / machine-type communications (M2M / MTC) terminal, an Internet of Things (IoT) terminal, a high-altitude aircraft, a subscriber unit, a subscriber station, a mobile station, a remote station, an access point (AP), a remote terminal, an access terminal, a user terminal, a user agent, or a user device, etc.

[0251] By way of example and not limitation, in an embodiment of this application, the terminal may also be a wearable device. A wearable device may also be referred to as a wearable intelligent device or a smart wearable device, etc. It is a general term for devices developed by applying wearable technology to the intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes. And for the various terminals introduced above, if they are located on a vehicle (for example, placed inside or installed inside a vehicle), they can all be considered in-vehicle terminals. An in-vehicle terminal is also referred to as an on-board unit (OBU) for example.

[0252] The satellite involved in the embodiments of the present application can provide wireless access services for terminal devices, schedule wireless resources for the accessed terminal devices, and provide reliable wireless transmission protocols and data encryption protocols, etc. The satellite can use artificial earth satellites, high-altitude aircraft, etc. as wireless communication base stations, such as evolved Node B (eNB) and 5G base station (gNB), etc. Optionally, the satellite can also act as a relay for these base stations to transparently transmit the wireless signals of these base stations to the terminal devices. In this case, the gateway station can be regarded as a wireless communication base station. Therefore, in some embodiments of the present application, such as in the regeneration scenario of the satellite, the network device can be Figure 11 the satellite base station shown; in other embodiments, such as in the transparent transmission scenario of the satellite, the network device can be Figure 11 the gateway station shown.

[0253] In a possible implementation manner, the satellite can be a geostationary earth orbit (GEO) satellite, or a non-geostationary earth orbit (NGEO) medium earth orbit (MEO) satellite and low earth orbit (LEO) satellite, or a high-altitude platform station (HAPS), etc.

[0254] The gateway station involved in the embodiments of the present application can be used to connect the satellite and the core network. For example, when the satellite is used as a wireless communication base station, the gateway station can transparently transmit the signaling between the satellite and the core network. Or, the gateway station can be used as a wireless communication base station, and the satellite can transparently transmit the signaling between the terminal device and the gateway station. Exemplarily, when communicating, the gateway station can send the signaling from the core network to the satellite through the feeder link; and the satellite can send the signaling to the terminal device through the service link between the satellite and the terminal device. Correspondingly, the terminal device can also send signaling to the satellite through the service link, and the satellite can send the signaling to the core network through the gateway station. Optionally, the base station and the gateway station can be deployed separately, then the delay of the feeder link includes two parts: the delay from the satellite to the gateway station and the delay from the gateway station to the gNB. The transparent transmission mode discussed later takes the case where the gateway station and the gNB are together or in close proximity as an example. For the case where the gateway station and the gNB are far apart, the feeder link delay can be obtained by adding the delay from the satellite to the gateway station and the delay from the gateway station to the gNB.

[0255] In the embodiments of the present application, the network device may include, but is not limited to, the satellite base station or the gateway station shown above. For example, the base station may also be a base station in a future communication system such as the sixth-generation communication system. Optionally, the network device may also be an access node, a wireless relay node, a wireless backhaul node, etc. in a wireless local area network (WiFi) system. Optionally, the network device may also be a radio controller in a cloud radio access network (CRAN) scenario. Optionally, the network device may also be a wearable device or a vehicle-mounted device, etc. Optionally, the network device may also be a small station, a transmission reception point (TRP) (or may also be referred to as a transmission reception point), etc. It is understood that the network device may also be a base station in a future evolved PLMN, etc.

[0256] It should be understood that Figure 11 only one satellite and one gateway station are shown. Those skilled in the art can adopt a communication system architecture with multiple satellites and / or multiple gateway stations as needed. Among them, each satellite can provide services to one or more terminal devices. Each satellite can correspond to one or more gateway stations, and each gateway station can correspond to one or more satellites, etc. The embodiments of the present application do not make specific limitations.

[0257] To facilitate understanding of the solution provided by the embodiments of the present application, take the attached Figure 13 as an example to illustrate the time parameters involved in the embodiments of the present application. Figure 13 The reference points shown may be such as Figure 8 and such as Figure 9 shown in. It should be understood that Figure 13 the positions of the reference points in are exemplary, and the present application does not limit their positions. The positions of the reference points may be determined by the network device. The reference points may be between the terminal device and the satellite, that is, on the service link, or between the reference point and the gateway station, that is, on the feeder link. The reference points may also be on the satellite or the gateway station. Among them, the round-trip delay between the reference point and the satellite is compensated by the terminal device. The terminal device can compensate the round-trip delay between the reference point and the satellite by performing timing advance compensation on the transmitted signal. The round-trip delay between the reference point and the gateway station is compensated by the network device. The network device can compensate the round-trip delay between the reference point and the gateway station by performing delay compensation on the received signal window.

[0258] 1) TA_cal may represent the round-trip delay between the satellite and the terminal device, or may represent the round-trip delay of the service link. Among them, the terminal device can process and obtain TA_cal based on its own position information and the position information of the satellite.

[0259] 2) TA_common can represent the round-trip delay between the satellite and the reference point. It should be noted that TA_common is negative when the reference point is on the service link and positive when the reference point is on the feeder link.

[0260] 3) Delay_compensated can represent the delay compensation value made by the network device for the signal received from the terminal device. Among them, the delay compensation value can be equal to the round-trip delay between the reference point and the gateway station (or ground base station). The meaning of the delay compensation value is that when the network device receives the signal from the terminal device, it delays the reception window. For example, if the delay compensation value is 200 ms, then when the network device receives the signal from the terminal device, it will start to delay the reception window time by 200 ms.

[0261] 4) Service_RTD_max can represent the maximum round-trip delay between the satellite and the terminal device in its coverage area. Or, it can represent the round-trip delay between the satellite and the farthest point in its coverage area, that is, the maximum round-trip delay of the service link in the satellite's coverage area.

[0262] 5) Service_RTD_min can represent the minimum round-trip delay between the satellite and the terminal device in its coverage area. Or, it can represent the round-trip delay between the satellite and the nearest point in its coverage area, that is, the minimum round-trip delay of the service link in the satellite's coverage area.

[0263] 6) Feeder_RTD can represent the round-trip delay between the satellite and the gateway station, or can represent the round-trip delay of the feeder link.

[0264] 7) TA_UE can represent the timing advance value obtained by the terminal device according to the common timing advance value and TA_cal. TA_UE = TA_cal + TA_common. The terminal device can further obtain the timing advance value TA used for sending uplink data based on TA_UE. For example, the available timing advance value TA can be obtained by adding a correction value and / or an offset to TA_UE.

[0265] 8) RAR_window_delay (terminal level / UE-specific) can refer to the RAR_window_delay at the terminal device level and can represent the delay start duration of the RAR window and / or the random access contention resolution timer. Among them, the RAR_window_delay used by each terminal device in the same cell or beam may be different. It should be understood that the network device may or may not know the RAR_window_delay value of each terminal device, that is, it can be transparent to the network device.

[0266] 9) RAR_window_delay (common / general level), which can refer to the RAR_window_delay at the general level and can represent the delay start duration of the RAR window and / or the random access contention resolution timer. Among them, the terminal devices in the same cell or beam use the same RAR_window_delay (common). Generally speaking, if a terminal device uses RAR_window_delay (common), the network device needs to send it to the terminal device. The RAR_window_delay at the terminal device level has the same function and usage scenario as RAR_window_delay (common), but the difference lies in the scope of use for the terminal device and whether it can be transparent to the network device.

[0267] 10) RAR_window can represent the receiving window length of the PDCCH for the terminal device to receive the indication Msg2 / MsgB / fallback RAR message (fallbackRAR) after sending Msg1 / MsgA. For its description, refer to the above-mentioned timing-related parameter four, which will not be elaborated here.

[0268] 11) Koffset can be used to determine the delay degree of the terminal device sending information or can determine the advance degree of the terminal device receiving information. For its description, refer to the above-mentioned timing-related parameter one, which will not be elaborated here.

[0269] 12) K_mac can represent the delay degree of the configuration information (such as MAC signaling) received by the terminal device taking effect. For its description, refer to the above-mentioned timing-related parameter two, which will not be elaborated here.

[0270] In summary, from Figure 13 it can be seen the relationship between some time parameters and the round-trip delay. For example, Koffset = TA_common + Service_RTD_max = RAR_window_delay (common) - RAR_window; TA_UE = TA_common + TA_cal; RAR_window_delay = TA_cal + TA_common + Delay_compensated, etc.

[0271] It can be seen from this that there are overlapping / redundant indications among the time parameters. Therefore, the network device can indicate to the terminal device the time parameters with overlapping indication relationships so that the terminal device can process to obtain one or more of the above-mentioned timing-related parameters one to four. Hereinafter, the technical solutions provided in the embodiments of the present application will be described with reference to the accompanying drawings.

[0272] Refer to Figure 14, which is an exemplary flowchart of the parameter transmission method provided by the embodiments of this application, may include the following steps.

[0273] Step 1401: The network device sends the first information to the terminal device.

[0274] The first information here includes a time parameter. Among them, the time parameter can be used to determine the timing offset. It should be noted that the timing offset can include at least one of the first timing offset shown in the above timing-related parameter one and the second timing offset shown in the above timing-related parameter two. Optionally, the time parameter can also be used to determine the delay start duration of the RAR window. The first information may include one or more of the above 1)-12) time parameters.

[0275] In a possible implementation, the network device may broadcast or multicast the first information to the terminal device. The network device may send the first information through at least one of the broadcast information such as system information block (SIB) 1, other system information (OSI), and master information block (MIB). Based on the above solution, broadcasting or multicasting the above signaling to the network device can avoid scheduling different resources for different terminal devices to send the above signaling, saving the signaling overhead of scheduling resources and reducing the system scheduling complexity.

[0276] In another possible implementation, the network device may send the first information to the terminal device during the radio resource control (RRC) connection phase.

[0277] In an example, the network device may send the first information through an RRC message. For example, an RRC setup message, an RRC Reconfiguration message, and an RRC Resume message.

[0278] In another example, the network device may carry the above RRC message or time parameter through at least one of downlink control information (DCI), group DCI, media access control (MAC) control element (CE), and timing advance command (TAC). Alternatively, the network device may indicate the above RRC message or time parameter to the terminal device in tabular form through the foregoing at least one of the information.

[0279] Optionally, the network device may unicast or multicast time parameters to the terminal device along with data transmission or in a separately allocated PDSCH. Among them, the advantage of separately sending the above signaling to the terminal device is that the parameter values of each terminal device can be flexibly controlled, and different parameter values can be configured for the terminal device according to the different locations or regions where the terminal device is located, so as to optimize the system parameters and the communication performance of the terminal device / system communication performance. For example, different Koffset values can be configured for the terminal device according to different positions of the terminal device to optimize the scheduling delay of each terminal device and improve the system communication efficiency.

[0280] Based on the above solution, the network device can separately send time parameters to the terminal device, and different time parameters can be configured for the terminal device according to the location or region where the terminal device is located, so as to optimize the system parameters, the communication performance of the terminal device, and the system communication performance.

[0281] Optionally, after receiving the above first information, the terminal device may also determine a timing offset based on the time parameter. Specifically, the terminal device may perform the following step 1402.

[0282] Step 1402: The terminal device determines at least one of a first timing offset and a second timing offset based on the time parameter.

[0283] Among them, the terminal device may determine the first timing offset and / or the second timing offset according to the time parameter, and use the determined first timing offset and / or the second timing offset when sending or receiving information. Or, the terminal device may determine the first timing offset and / or the second timing offset according to the time parameter when sending or receiving information, and send or receive information according to the first timing offset and / or the second timing offset. Optionally, the terminal device may also determine the delay start duration of the RAR window according to the time parameter.

[0284] Optionally, the network device may also determine the timing offset and / or the delay start duration of the RAR window through the time parameter. Specifically, the network device may determine at least one of a first timing offset, a second timing offset, and the delay start duration of the RAR window based on the time parameter. Among them, the calculation methods used by the terminal device and the network device need to be the same, mainly because the terminal device and the network device need to determine at least one of the same first timing offset, second timing offset, and delay start duration of the RAR window for transmitting communication data.

[0285] Hereinafter, different cases of the time parameters included in the first information, and the cases where the network device and / or the terminal device determine the first timing offset, the second timing offset, and the delay start duration of the RAR window will be described separately.

[0286] Case 1: The time parameter includes the difference △Koffset of the first timing offset and TA_common.

[0287] The terminal device can determine Koffset based on △Koffset and TA_common. Among them, Koffset satisfies the following calculation relationship / formula (1).

[0288]

[0289] Among them, slot_duration represents a time unit / duration unit or a quantization unit. represents the ceiling operation, and △Koffset is an integer. In the above formula (1), the time units of TA_common, Koffset, and △Koffset can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantized to the same time unit.

[0290] It should be understood that slot_duration can be specified by the communication protocol or can also be indicated by the network device. slot_duration can be the slot length, such as the slot length of uplink data or the slot length of downlink data. Or, slot_duration can also be a duration unit determined according to the actual system needs, for example, any one of 0.5ms, 1ms, a symbol length, a subframe length, a frame length, Ts, 16*Ts, 16*Ts / 2μ, Tc, etc., which is not specifically limited in this application. The symbol represents the ceiling. In specific implementations, the floor can also be used to determine Koffset / K_mac / RAR_window_delay. For example, formula (1) can be rewritten as The above descriptions of the ceiling and the floor also apply below. For the convenience of describing the embodiments of this application, the ceiling is used for description.

[0291] In the above Case 1, the time parameter sent by the network device to the terminal device includes △Koffset, and the terminal device determines the Koffset value to be used according to the △Koffset value. It can be seen from Figure 13 that Koffset has multiple representation methods. For example:

[0292]

[0293] Therefore, in one example, it can be set that

[0294] Then, or

[0295]

[0296] In another example, it is possible to make

[0297] Then, or

[0298] If Delay_compensated is negative, then the above calculation relationship is adopted; if Delay_compensated is positive, then the above calculation relationship takes a negative sign, that is or

[0299] In yet another example, it is possible to make

[0300] Then,

[0301] Among them, RCR_timer represents the time length of the random access contention resolution timer (ra-ContentionResolutionTimer). RCR_timer_delay represents the delay start duration of the random access contention resolution timer. Optionally, RCR_timer_delay can be equal to RAR_window_delay. If Delay_compensated is negative, then the above calculation relationship is adopted; if Delay_compensated is positive, then the above calculation relationship takes a negative sign, that is

[0302] When the reference point is on the service link, it is possible to make the method. When the reference point is on the feeder link, it is possible to make Therefore, when the network device indicates to the terminal device which of the above situations △Koffset belongs to when determining Koffset through a signaling (for example, a 1-bit length signaling), the network device also sends △Koffset to the terminal device.

[0303] For example, when the value of this signaling is 1, The terminal device determines Koffset through determining Koffset.

[0304] When the value of this signaling is = 0, or

[0305] The terminal device determines Koffset through or determining Koffset.

[0306] Scenario 2: The time parameters include Service_RTD_min, TA_common, and RAR_window.

[0307] The terminal device can determine Koffset based on Service_RTD_min, TA_common, and RAR_window. Among them, Koffset satisfies the following formula (2).

[0308]

[0309] Among them, slot_duration represents the time unit, represents the ceiling operation, and the relevant description can be seen in Scenario 1 above. In the above formula (2), the time units of Service_RTD_min, TA_common, and RAR_window can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0310] Scenario 3: The time parameters include Service_RTD_max and TA_common.

[0311] The terminal device can determine Koffset based on Service_RTD_max and TA_common. Among them, Koffset satisfies the following formula (3).

[0312]

[0313] Among them, slot_duration represents the time unit, represents the ceiling operation, and the relevant description can be seen in Scenario 1 above.

[0314] In the above formula (3), the time units of Service_RTD_max and TA_common can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0315] Scenario 4: The time parameters include RAR_window, RAR_window_delay, and Delay_compensated.

[0316] The terminal device can determine Koffset based on RAR_window, RAR_window_delay, and Delay_compensated. Among them, Koffset satisfies the following formula (4).

[0317]

[0318] Among them, slot_duration represents the time unit, represents the ceiling operation. For relevant descriptions, refer to Case 1 above. In the above formula (4), the time units of RAR_window, RAR_window_delay, and Delay_compensated can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0319] Case 5: The time parameters include RAR_window and RAR_window_delay.

[0320] The terminal device can determine Koffset based on RAR_window and RAR_window_delay. Among them, Koffset can satisfy the following formula (5).

[0321]

[0322] Among them, slot_duration represents the time unit, represents the ceiling operation. For relevant descriptions, refer to Case 1 above.

[0323] In the above formula (5), the time units of RAR_window and RAR_window_delay can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0324] Case 6: The time parameters include RAR_window, RAR_window_delay, and K_mac.

[0325] The terminal device can determine Koffset based on RAR_window, RAR_window_delay, and K_mac. Among them, Koffset can satisfy the following formula (6).

[0326]

[0327] Among them, slot_duration represents the time unit, represents the ceiling operation. For relevant descriptions, refer to Case 1 above, and K_mac represents the second timing offset. In the above formula (6), the time units of RAR_window, RAR_window_delay, and K_mac can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0328] Based on the above scenarios 1 - 6, the network device can indicate to the terminal device the time parameters for determining Koffset. Optionally, when considering the influence of positioning errors, such as the positioning error of the terminal device, the positioning error of the satellite, and the positioning error of the gateway station, processing delay, and / or quantization error, etc., to avoid the problem that the value of Koffset determined by the terminal device is too small, resulting in insufficient scheduling delay for uplink data, an adjustment parameter Z of the first timing offset Koffset can be added respectively based on the above formulas (1) - (6). Here, Z can be a real number, and Z can be indicated by the network device or can also be specified by the communication protocol. For example, the information carrying Z can be the same as the information carrying the first information shown in step 201 above. Z and the time parameters can be carried in the same information or in different information. Optionally, when determining Koffset, the terminal device can multiply Z by a time unit and then substitute it into the above calculation relationship. This time unit can be specified by the communication protocol or indicated by the network device. For example, the time unit of Z can be 1ms, 10ms, a time slot length, a sub - frame length, a frame length, Ts, 16 * Ts, 16 * Ts / 2 μ or Tc, etc.

[0329] Taking the above scenario 1 as an example, the case of introducing the adjustment parameter Z of Koffset is described.

[0330] The terminal device can determine Koffset based on △Koffset, TA_common, and the adjustment parameter Z. Here, Koffset can satisfy the following formula (7) or formula (8).

[0331]

[0332] where slot_duration represents the time unit, represents the ceiling operation, and the relevant description can be referred to the above scenario 1. Or, Koffset can satisfy the following formula (8). The + / - in formula (7) can be related to the value range of Z or related to the requirement that Koffset of the system cannot be too large or too small. In specific implementation, + or - can be used for the terminal device through protocol agreement or network configuration.

[0333]

[0334] where slot_duration represents the time unit, represents the ceiling operation, and the relevant description can be referred to the above scenario 1.

[0335] The following describes the case where a network device sends time parameters for determining K_mac to a terminal device.

[0336] Case 7: The time parameters include Delay_compensated.

[0337] The terminal device can determine K_mac based on Delay_compensated. Among them, K_mac can satisfy the following formula (9).

[0338]

[0339] Among them, slot_duration represents the time unit, represents the ceiling operation, and the relevant description can be seen in Case 1 above. In the above formula (9), the time units of Delay_compensated and K_mac can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit. Case 8: The time parameters include Feeder_RTD and TA_common.

[0340] The terminal device can determine K_mac based on Feeder_RTD and TA_common. Among them, K_mac can satisfy the following formula (10).

[0341]

[0342] Among them, slot_duration represents the time unit, represents the ceiling operation, and the relevant description can be seen in Case 1 above. In the above formula (10), the time units of Feeder_RTD and TA_common can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit. Case 9: The time parameters include RAR_window, RAR_window_delay, and Koffset.

[0343] The terminal device can determine K_mac based on RAR_window, RAR_window_delay, and Koffset. Among them, K_mac satisfies the following formula (11).

[0344]

[0345] Among them, slot_duration represents the time unit, Denotes the ceiling operation, and the relevant description can be seen in the above Case 1. Koffset is the first timing offset. In the above formula (11), the time units of RAR_window, RAR_window_delay, Koffset, and K_mac can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0346] Case 10: The time parameters include Koffset and TA_common.

[0347] The terminal device can determine K_mac based on TA_cal, Koffset, and TA_common. Among them, TA_cal is determined by the terminal device based on its own location information and the location information of the satellite, and can represent the round-trip delay value of the service link of the terminal device. For example, the terminal device can determine the location information of the satellite based on the ephemeris information of the satellite, and then determine TA_cal. It should be noted that the location information of the satellite can be sent to the terminal device together with the time parameters, or can also be sent to the terminal device separately, which will not be elaborated below. K_mac satisfies the following formula (12).

[0348]

[0349] Among them, slot_duration represents the time unit. Denotes the ceiling operation, and the relevant description can be seen in the above Case 1. Koffset is the first timing offset. In the above formula (12), the time units of TA_cal, Koffset, TA_common, and K_mac can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0350] Case 11: The time parameters include RAR_window, RAR_window_delay, and TA_common.

[0351] The terminal device can determine K_mac based on TA_cal, RAR_window, RAR_window_delay, and TA_common. Among them, K_mac satisfies the following formula (13).

[0352]

[0353] Among them, slot_duration represents the time unit. Denotes the ceiling operation, and the relevant description can be seen in the above Case 1. In the above formula (13), the time units of TA_cal, RAR_window, RAR_window_delay, and TA_common can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0354] The network device indicates the time parameters for determining K_mac to the terminal device through the above Cases 7 - 12. Optionally, when considering the influence of positioning errors, such as the positioning error of the terminal device, the positioning error of the satellite, and the positioning error of the gateway station, processing delay, and / or quantization error, etc., to avoid the problem that the value of K_mac determined by the terminal device is too small and causes insufficient timing delay for the downlink configuration to take effect, a second timing offset adjustment parameter Y of K_mac can be added respectively based on the above formulas (9) - (14). Among them, Y can be a real number, and Y can be indicated by the network device or can also be specified by the communication protocol. For example, the information carrying Y can be the same as the information carrying the first information shown in the above step 201, and Y and the time parameter can be carried in the same information or different information. Optionally, when the terminal device determines K_mact, Y can be multiplied by a time unit and then substituted into the above calculation relationship. This time unit can be specified by the communication protocol or indicated by the network device. For example, the time unit of Y can be 1ms, 10ms, a slot length, a subframe length, a frame length, Ts, 16*Ts, 16*Ts / 2μ, or Tc, etc.

[0355] Hereinafter, taking Case 8 as an example, the situation of introducing the adjustment parameter Y of K_mac will be described.

[0356] The terminal device can determine K_mac based on Feeder_RTD, TA_common, and Y. Among them, K_mac can satisfy the following formulas (14) and (15).

[0357]

[0358] Alternatively, K_mac can satisfy the following formula (15).

[0359]

[0360] Among them, slot_duration represents the time unit. Denotes the ceiling operation, and the relevant description can be seen in the above Case 1. In formulas (14) and (15), the time unit of Y and K_mac can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0361] In a possible implementation, the terminal device and the network device may agree on the update time of at least one of TA, Koffset, and K_mac. For example, it may be agreed that the time when the network device updates the system message is the time to update at least one of TA, Koffset, and K_mac.

[0362] For example, the network device will start broadcasting the updated system message in certain specific system frames, that is, update the system message content. When the network device updates the system message, it will send a system information change notification to the terminal device. After receiving a system information change notification, the terminal device will start receiving the new system information from the next possible system frame that meets the requirements. For example, when the system frame number meets the requirement of SFN mod m = 0, it can be used as the starting frame for updating the system message. SFN represents the system frame number, and m represents a positive integer, such as 32, 64, 128, 256. Therefore, it can be agreed that when the network device updates the system message, it sends a system message update notification to the terminal device. The terminal device detects the updated system message at the agreed starting frame according to the system message update notification, and then updates the time parameter.

[0363] For example, take the starting time of the starting frame for updating the system message as the agreed time to update at least one of TA, Koffset, and K_mac. The network device can also update at least one of TA, Koffset, and K_mac according to the above agreed time. Based on the above solution, the terminal device and the network device can obtain the same updated at least one of TA, Koffset, and K_mac.

[0364] For example, taking the time parameter including one or more of RAR_window, RAR_window_delay, and TA_common as an example, when the terminal device obtains one or more of RAR_window, RAR_window_delay, and TA_common in the updated system message through the broadcast message, and then determines one or more of the corresponding TA, Koffset, and K_mac. If one or more of the newly determined TA, Koffset, and K_mac change compared with the previously used TA, Koffset, and K_mac, then at the starting time of the starting frame for updating the system message, the calculated and determined timing parameter is updated to the newly determined value. Optionally, the network device can also perform the above process, so that both the terminal device and the network device can obtain the same latest one or more of TA, Koffset, and K_mac.

[0365] Optionally, the terminal device may send determination information to the network device, where the determination information indicates that at least one of the updated TA, Koffset, and K_mac is the latest determined value. For example, the determination information may be at least one of the updated TA, Koffset, and K_mac. Alternatively, the determination information may be a parameter for updating at least one of TA, Koffset, and K_mac. For instance, it may be the TA difference for updating TA, which is used to represent the difference between the TA before update and the TA after update. Or, the determination information may be a one-bit signaling indicating that the terminal device uses at least one of the updated TA, Koffset, and K_mac. Optionally, after the network device sends the relevant value of Koffset for update to the terminal device, or after the network device confirms that the terminal device can update Koffset, the terminal device may further determine and update K_mac. Optionally, after the network device sends the relevant value of K_mac for update to the terminal device, or after the network device confirms that the terminal device can update K_mac, the terminal device may further determine and update K_offset.

[0366] Optionally, the above determination information may also be sent by the network device to the terminal device. The terminal device may use at least one of the updated TA, Koffset, and K_mac based on the determination information.

[0367] In another possible implementation, after the terminal device obtains the K_mac to be updated or to be used according to the calculation relationship / formula for determining K_mac, it may send the latest K_mac or the difference of K_mac to the network device. The difference of K_mac may be the difference between the K_mac used by the terminal device and a certain reference quantity. For example, the reference quantity may be the K_mac reported by the terminal device last time. After receiving the K_mac or the difference of K_mac, the network device may obtain the latest K_mac, and at the same time, may obtain the TA or the relevant value of TA used by the terminal device according to the calculation relationship / formula.

[0368] For example, the terminal device obtains K_mac according to the calculation relationship and sends the K_mac to the network device. After receiving the K_mac, the network device may obtain the relevant value of TA used by the terminal device according to That is, the processed TA value is not necessarily exactly equal to the TA value used by the terminal device, but approximately equal to the TA value used by the terminal device. Optionally, the network device may obtain the first timing offset and / or RAR_window_delay using the processed TA value. And may send the obtained first timing offset and / or RAR_window_delay to the network device.

[0369] For example, the network device can, according to process to obtain Koffset that can be used by the terminal device, and can send the Koffset or the difference of the Koffset to the terminal device.

[0370] Optionally, the terminal device can update the K_mac threshold K_mac_thresh based on K_mac to determine whether the condition for updating K_mac is satisfied. Among them, K_mac_thresh can be specified by the communication protocol or indicated by the network device. For example, the K_mac update threshold can be an integer value, K_mac_thresh = 2. When the terminal device or the network device determines the updated K_mac, the terminal device or the network device can determine whether |updated K_mac - previous K_mac| ≥ K_mac_thresh is satisfied. If it is satisfied, then update K_mac; if not, continue to use the previous K_mac. After the waiting time parameter is updated, then perform the determination operation.

[0371] Taking the foregoing formula (9) as an example, if the terminal device receives the updated Delay_compensated, the terminal device can determine whether |updated K_mac - previous K_mac| ≥ K_mac_thresh is satisfied. Among them, if it is not satisfied, then it can continue to use the previous K_mac, that is, the K_mac used before the update of Delay_compensated.

[0372] Next, different situations where the network device indicates the time parameter for determining RAR_window_delay are introduced. To facilitate the understanding of the embodiments of the present application, first, RAR_window_delay involved in the embodiments of the present application is described below.

[0373] Due to different understandings of the moment to start the RAR window and the moment to start the random access contention resolution timer, different ways to determine RAR_window_delay will occur. For the convenience of distinction, the delay start duration of the RAR window determined by the actual timing method can be called the delay start duration RAR_window_delay1 of the first RAR window, and the delay start duration of the RAR window determined by the logical timing method can be called the delay start duration RAR_window_delay2 of the second RAR window.

[0374] Next, RAR_window_delay1 is described.

[0375] After the terminal device advances the PUSCH opportunity or the last symbol of the PRACH opportunity for sending Msg1 / MsgB according to the used Timing Advance (TA), the terminal device can start detecting the PDCCH from the first symbol of the earliest CORESET according to the actual transmission time of Msg1 / MsgB, that is, the RAR window can be started according to the actual transmission time of Msg1 / MsgB.

[0376] See Figure 15A , the PDCCH can indicate the starting position or the starting symbol of the resources where the CORESET is located. The terminal device can select to determine the starting moment of the RAR window according to the last symbol of the PUSCH opportunity or the PRACH opportunity according to the communication scenario. For example, in the 4-step random access scenario, the starting moment of the RAR window is determined according to the end time of the last symbol of the PRACH opportunity. In the 2-step random access scenario, the terminal device determines the starting moment of the RAR window according to the end time of the last symbol of the PUSCH opportunity. If the PRACH preamble sent by the terminal device is not mapped to a valid PUSCH opportunity, then the terminal device determines the starting moment of the RAR window according to the end time of the last symbol of the PRACH opportunity corresponding to the PRACH transmission.

[0377] See Figure 15B , on the basis of determining the starting timing of starting the RAR detection window according to the actual timing method above, RAR_window_delay1 is used to delay the start of the RAR window. The starting moment of RAR_window_delay1 is the end time of the last symbol of the PUSCH opportunity or the PRACH opportunity for the terminal device to send Msg1 / MsgB, or in other words, the end time of the last symbol of the PUSCH opportunity or the PRACH opportunity for sending Msg1 / MsgB is the starting moment of RAR_window_delay1. Alternatively, the starting symbol of RAR_window_delay1 can be the next symbol after the last symbol of the PUSCH opportunity or the PRACH opportunity, or in other words, the next symbol after the last symbol of the PUSCH opportunity or the PRACH opportunity is the starting symbol of RAR_window_delay1.

[0378] Next, RAR_window_delay2 will be described.

[0379] After the terminal device advances the last symbol of the PUSCH opportunity or PRACH opportunity for sending Msg1 / MsgA according to the used Timing Advance (TA) value, it starts to detect PDCCH information from the first symbol of the earliest CORESET according to the logical timing. That is, the terminal device can start the RAR window according to the logical time of sending Msg1 / MsgA.

[0380] The above logical time can be understood as the time corresponding to when the Timing Advance value TA is equal to 0. For example, refer to Figure 16A , the logical time of the starting moment when the terminal device sends Msg1 / MsgA is Figure 16A the ending moment of the first PDCCH information shown in Figure 16A . Based on the logical time, the starting moment of the RAR window is determined as Figure 16A the starting moment of the second PDCCH information shown in

[0381] Refer to Figure 16B . On the basis of determining the starting time of the RAR window according to the logical time as described above, RAR_window_delay2 is used to delay the start of the RAR window. The starting moment of RAR_window_delay2 is the logical ending time of the last symbol of the PUSCH opportunity or PRACH opportunity for sending Msg1 / MsgB. Or, the logical ending time of the last symbol of the PUSCH opportunity or PRACH opportunity for sending Msg1 / MsgB is the starting moment of RAR_window_delay2. Or, the starting symbol of RAR_window_delay2 is the next symbol after the last symbol of the PUSCH opportunity or PRACH opportunity. Or, the next symbol after the last symbol of the PUSCH opportunity or PRACH opportunity is the starting symbol of RAR_window_delay2. Or, the starting moment of RAR_window_delay2 is the logical starting time of the next symbol after the last symbol of the PUSCH opportunity or PRACH opportunity. Or, the logical starting time of the next symbol after the last symbol of the PUSCH opportunity or PRACH opportunity is the starting moment of RAR_window_delay2.

[0382] In a possible implementation, the network device and the terminal device can determine to use an actual timing method or a logical timing method to determine the start time of the RAR window / random access contention resolution timer. For example, it can be agreed by the protocol to use the actual timing method or the logical timing method, or the network device can indicate to the terminal device to use the actual timing method or the logical timing method, such as indicating to the terminal device to use the actual timing method or the logical timing method through signaling. Correspondingly, the start time of RAR_window_delay is also determined according to the agreement by the protocol or the indication of the network device, using the actual timing method or the logical timing method.

[0383] In the above cases 7 - 11, the RAR_window_delay included in the time parameters sent by the network device to the terminal device is determined by the actual timing method. Below, the case where the RAR_window_delay indicated by the network device to the terminal device is determined by the logical timing method is introduced.

[0384] Case 12: The time parameter includes RAR_window_delay.

[0385] The terminal device determines K_mac based on RAR_window_delay. Among them, K_mac satisfies the following formula (16).

[0386]

[0387] Among them, slot_duration represents the time unit, represents the ceiling operation, and the relevant description can be seen in Case 1 shown above. In the above formula (16), the time units of RAR_window_delay and K_mac can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0388] Below, the cases where the network device sends information for determining RAR_window_delay are described through Cases 13 - 17 respectively. It should be understood that RAR_window_delay can include RAR_window_delay1 and RAR_window_delay2.

[0389] Case 13: The time parameter includes Delay_compensated and TA_common.

[0390] The terminal device can determine RAR_window_delay1 based on TA_cal, Delay_compensated, and TA_common. Among them, RAR_window_delay1 satisfies the following formula (17).

[0391] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common Formula (17)

[0392] In the above formula (17), the time units of TA_cal, Delay_compensated, TA_common, and RAR_window_delay1 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit. For example, in the above formula (17), the time unit of TA_cal is Tc, while the units of Delay_compensated and TA_common are Ts or 16*Ts, then the time units of each time parameter need to be converted to the same measurement unit, such as converting them all to Tc. Among them, Δf max = 480 * 10 3 Hz, N f = 4096. The definition of Ts is That is Δf ref = 15 * 10 3 Hz, N f,ref = 2048.

[0393] The terminal device can also determine RAR_window_delay2 based on the above time parameters. Among them, RAR_window_delay2 satisfies the following formula (18).

[0394] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA

[0395] = Delay_compensated Formula (18)

[0396] Among them, TA represents the timing advance value used by the terminal device, TA = TA_cal + TA_common, which will not be elaborated below.

[0397] In the above formula (18), the time units of TA_cal, Delay_compensated, TA_common, TA, and RAR_window_delay2 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0398] Case 14: The time parameters include K_mac and TA_common.

[0399] The terminal device can determine RAR_window_delay1 based on TA_cal, K_mac, and TA_common. Among them, RAR_window_delay1 satisfies the following formula (19).

[0400] RAR_window_delay1 = TA_cal + TA_common + K_mac * slot_duration Formula (19)

[0401] Among them, slot_duration is the time unit, and the relevant description can be seen in Case 1 above. K_mac is the second timing offset. In formula (19), the time units of TA_cal, K_mac, TA_common, and RAR_window_delay1 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit. The terminal device can also determine RAR_window_delay2 based on the above time parameters. Among them, RAR_window_delay2 satisfies the following formula (20).

[0402] RAR_window_delay2 = TA_cal + TA_common + K_mac * slot_duration - TA

[0403] = K_mac * slot_duration Formula (20)

[0404] Among them, slot_duration is the time unit, and the relevant description can be seen in Case 1 above. K_mac is the second timing offset. In formula (20), the time units of TA_cal, K_mac, TA_common, TA, and RAR_window_delay2 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0405] Case 15: The time parameters include Feeder_RTD.

[0406] The terminal device can determine RAR_window_delay1 based on TA_cal and Feeder_RTD. Among them, RAR_window_delay1 satisfies the following formula (21).

[0407] RAR_window_delay1 = TA_cal + Feeder_RTD Formula (21)

[0408] In Formula (21), the time units of TA_cal, Feeder_RTD, and RAR_window_delay1 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit. The terminal device can also determine RAR_window_delay2 based on the above time parameters. Among them, RAR_window_delay2 satisfies the following formula (22).

[0409] RAR_window_delay2 = TA_cal + Feeder_RTD - TA Formula (22)

[0410] In Formula (21), the time units of TA_cal, Feeder_RTD, TA, and RAR_window_delay2 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0411] Case 16: The time parameters include RAR_window and Koffset.

[0412] The terminal device can determine RAR_window_delay1 based on RAR_window and Koffset. Among them, RAR_window_delay1 satisfies the following formula (23).

[0413] RAR_window_delay1 = Koffset * slot_duration – RAR_window Formula (23)

[0414] Among them, Koffset is the first timing offset, and slot_duration is the time unit. For relevant descriptions, refer to the above Case 1. In formula (23), the time units of RAR_window, Koffset, and RAR_window_delay1 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit. The terminal device can also determine RAR_window_delay2 based on the above time parameters. Among them, RAR_window_delay2 satisfies the following formula (24).

[0415] RAR_window_delay2 = Koffset * slot_duration – RAR_window - TA Formula (24)

[0416] Among them, Koffset is the first timing offset, and slot_duration is the time unit. In formula (24), the time units of RAR_window, Koffset, TA, and RAR_window_delay2 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit. Case 17: The time parameters include Service_RTD_min and Delay_compensated.

[0417] The terminal device can determine RAR_window_delay1 based on Service_RTD_min and Delay_compensated. Among them, RAR_window_delay1 satisfies the following formula (25).

[0418] RAR_window_delay1 = Service_RTD_min + Delay_compensated + TA_common Formula (25)

[0419] In formula (25), the time units of Service_RTD_min, Delay_compensated, and RAR_window_delay1 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit.

[0420] The terminal device can also determine RAR_window_delay2 based on the above time parameters. Among them, RAR_window_delay2 satisfies the following formula (26).

[0421] RAR_window_delay2 = Service_RTD_min + Delay_compensated + TA_common - TA

[0422] Formula (26)

[0423] In Formula (25), the time units of Service_RTD_min, Delay_compensated, TA, and RAR_window_delay1 can be the same or different. If the time units are different, the time units of the time parameters can be converted or quantified to the same time unit. The network device indicates the time parameters used to determine RAR_window_delay to the terminal device through the above Cases 12 - 17. Optionally, when considering the influence of positioning errors, such as the positioning error of the terminal device, the positioning error of the satellite, and the positioning error of the gateway station, processing delay, and / or quantization error, etc., to avoid the problem that the RAR_window_delay determined by the terminal device is too large and the terminal device cannot receive the PDCCH information within the RAR window, an adjustment parameter X of RAR_window_delay can be added respectively based on the above Formulas (17) - (26). Among them, X can be a real number, and X can be indicated by the network device or can also be specified by the communication protocol. For example, the information carrying X can be the same as the information carrying the first information shown in Step 201 above. X and the time parameter can be carried in the same information or different information. Optionally, when the terminal device determines RAR_window_delay, X can be multiplied by a time unit and then substituted into the above calculation relationship. This time unit can be specified by the communication protocol or indicated by the network device. For example, the time unit of X can be 1ms, 10ms, a time slot length, a subframe length, a frame length, Ts, 16 * Ts, 16 * Ts / 2μ, or Tc, etc.

[0424] Hereinafter, taking Case 13 as an example, the case of introducing the adjustment parameter X of RAR_window_delay will be described.

[0425] The terminal device can determine RAR_window_delay1 based on TA_cal, RAR_window_delay, and TA_common. Among them, RAR_window_delay1 can satisfy the following Formula (27).

[0426] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common + / - X Formula (27)

[0427] RAR_window_delay2 can satisfy the following formula (28).

[0428] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA + / - X

[0429] = Delay_compensated + / - X

[0430] = RAR_window_delay1 - TA Formula (28)

[0431] It should be noted that there is a difference of TA between RAR_window_delay1 and RAR_window_delay2. If the terminal device corrects RAR_window_delay1 by adjusting the parameter X, then when calculating RAR_window_delay2, it may not be necessary to further correct RAR_window_delay2. If the terminal device does not correct RAR_window_delay1, then when calculating RAR_window_delay2, it can correct RAR_window_delay2 by adjusting the parameter X.

[0432] Based on the above solution, the network device can indicate to the terminal device the time parameters for determining the first timing offset, the second timing offset, and the delay start duration of the RAR window in the manner shown in Case 1 - Case 17, which can save signaling overhead.

[0433] In the above cases 13 - 17, the time parameter sent by the terminal device may include RAR_window_delay. At this time, the terminal device can determine a more accurate RAR_window_delay based on other time parameters as the RAR_window_delay for actual use. Or for the sake of convenience and to avoid calculation, the terminal device can directly use the RAR_window_delay sent by the network device as the RAR_window_delay for actual use. When the time parameter sent by the network device to the terminal device includes RAR_window_delay, it can be agreed through the communication protocol whether the terminal device determines and uses the UE-level RAR_window_delay based on other time parameters or directly uses the RAR_window_delay sent by the network device to the terminal device. Or, the terminal device can choose according to the actual situation whether to determine and use the UE-level RAR_window_delay based on other time parameters or directly use the RAR_window_delay sent by the network device to the terminal device. Or, the network device can indicate to the terminal device through signaling whether to determine and use the UE-level RAR_window_delay based on other time parameters or directly use the RAR_window_delay sent by the network device to the terminal device. For example, the terminal device is indicated through 1-bit signaling whether to determine and use the UE-level RAR_window_delay based on other time parameters or directly use the RAR_window_delay value sent by the network device to the terminal device.

[0434] In the above cases 1 - 17, the network device and the terminal device need to know TA_cal or the TA value used by the terminal device to determine the K_mac value respectively to ensure that the network device and the terminal device use the same K_mac. The terminal device can report TA_cal or TA_cal + TA_common or the TA value used for the network device to determine the K_mac value in the following ways:

[0435] 1) The terminal device reports the TA_cal or TA value calculated by itself to the network device.

[0436] 2) The terminal device reports its own location information. The network device can process the TA_cal or TA value based on the location information of the terminal device and the location information of the satellite. At this time, the TA_cal or TA processed by the network device is the same as the TA_cal or TA processed by the terminal device because the terminal device also processes the TA_cal or TA value based on its own location information and the location information of the satellite.

[0437] 3) The terminal device reports TA_cal + TA_common or the TA value, that is, the sum of TA_cal and TA_common of the terminal device, for the network device to determine K_mac.

[0438] 4) The terminal device reports the difference of TA. That is, the difference between the TA value used by the terminal device and a certain reference quantity. For example, the reference quantity can be the TA value reported by the terminal device last time, or the reference quantity can be the minimum round-trip delay determined based on the satellite orbit altitude, or the reference quantity can be TA_common. After receiving the difference of TA, the network device can process to obtain the TA value used by the terminal device according to the sum of the difference of TA and the reference quantity.

[0439] In a possible implementation, the network device can indicate location coordinate information to the terminal device. The terminal device can calculate Service_RTD_max based on the location coordinate information. For example, the location coordinate information can be the location coordinate information of the farthest point from the satellite in the coverage area of the satellite (a certain cell or beam). After receiving the location coordinate information, the terminal device can process to obtain Service_RTD_max according to the location information of the satellite and the location information of the farthest point. For example, the terminal device can calculate Service_RTD_max according to 2 * distance (satellite, location coordinate of the farthest point) / speed of light. Where distance(A, B) represents the distance between point A and point B. The terminal device can use Service_RTD_max determined by the received location coordinate information and other timing-related parameters determined according to the calculation relationship in the embodiments of the present application. Therefore, Service_RTD_max in the above cases 1 - 17 can be calculated by the terminal device based on the location coordinate information indicated by the network device, and it is not necessary for the network device to indicate Service_RTD_max.

[0440] Similarly, Service_RTD_min can also be determined by the terminal device based on the location coordinate information indicated by the network device. For example, the location coordinate information can be the location coordinate information of the nearest point to the satellite in the coverage area of the satellite. Therefore, Service_RTD_min in the above cases 1 - 17 can be calculated by the terminal device based on the location coordinate information indicated by the network device, and it is not necessary for the network device to indicate Service_RTD_min.

[0441] In another possible implementation, after the terminal device receives the TA_common sent by the network device, a period of time may have passed when the TA_common is used. Therefore, the TA_common received by the terminal device may be inaccurate and needs to be corrected. The terminal device can determine the TA based on the corrected TA_common. Alternatively, the terminal device can determine one or more of RAR_window_delay, K_mac, and Koffset based on the corrected TA_common.

[0442] In one example, the terminal device can determine the corrected TA_common according to the common timing advance change rate TA_rate indicated by the network device. Alternatively, the terminal device can determine the TA_rate according to the parameter related to TA_rate indicated by the network device, so as to determine the corrected TA_common. For example, the corrected TA_common = received TA_common + △T * TA_rate, where △T represents the time interval, which can be the time interval between the moment when the network device sends the TA_common and the moment when the terminal device uses the TA_common.

[0443] For example, in the above formula (17) for determining RAR_window_delay1 or the formula for determining Koffset that uses TA_common, in actual use, the terminal device may need to correct or adjust the TA_common after receiving the TA_common. For example, adjust the TA_common according to the common timing advance change rate, TA_common_new = TA_common_old + △T * timing advance change rate, where TA_common_new represents the adjusted TA_common value, TA_common_old represents the TA_common before adjustment or the TA_common sent by the network device received by the terminal device, and △T represents the time interval for determining TA_common_new and TA_common_old or the time difference between the time for determining TA_common_new and the time corresponding to TA_common_old. The terminal device can determine Koffset according to the adjusted TA_common as follows:

[0444]

[0445] It should be noted that the network device can determine the time parameter based on each of the above-mentioned scenarios 1 - 17, or the network device can also determine the time parameter based on various combinations of scenarios 1 - 17. For example, the network device can determine the time parameter based on the combination of scenario 1 and scenario 7. Among them, the time parameter can include △Koffset, TA_common, and Delay_compensated. The terminal device can determine one or more of Koffset, K_mac, and RAR_window_delay based on △Koffset, TA_common, and Delay_compensated. Hereinafter, Koffset will be taken as an example for illustration.

[0446]

[0447] or

[0448] or

[0449] Those skilled in the art can determine the time parameter that allows the terminal device to determine at least one of Koffset, K_mac, and RAR_window_delay based on the above-mentioned scenarios 1 - 17 and various combinations of scenarios 1 - 17.

[0450] Optionally, the time parameter sent by the network device can be used by the terminal device to determine Koffset, K_mac, and RAR_window_delay. In this way, the network device can, through a single signaling transmission, enable the terminal device to determine Koffset, K_mac, and RAR_window_delay, further saving signaling overhead.

[0451] In a possible implementation, since TA = TA_cal + TA_common, TA_cal + TA_common in the above formulas (1) - (26) can all be represented by TA. Optionally, during the communication process, the TA used by the terminal device may be added with a correction value and / or an offset on the basis of TA_cal + TA_common. Among them, the correction value may be related to the movement of the satellite, and the offset is related to positioning errors, duplex modes, etc. In the embodiments of the present application, for the sake of convenience of description, TA_cal + TA_common or TA is used to represent the TA used by the terminal device. Similarly, during the communication process, Koffset, K_mac, RAR_window_delay1, and RAR_window_delay2 involved in the embodiments of the present application can be determined through the above time parameters and calculation relationships. Or one or more of other influencing parameters, offsets, variation amounts, and correction values may be added on the basis of the above calculation relationships to obtain one or more of the finally usable Koffset, K_mac, RAR_window_delay1, and RAR_window_delay2, which will not be elaborated below. One or more of the above other influencing parameters, offsets, variation amounts, and correction values may be indicated by the network device, or may also be specified by the communication protocol.

[0452] Hereinafter, a specific embodiment is used to explain and illustrate the combination of the above Case 1 and Case 17.

[0453] Embodiment 1

[0454] The network device sends Delay_compensated, Service_RTD_max, and TA_common to the terminal device.

[0455] The terminal device can determine Koffset through the foregoing formula (3) as follows:

[0456]

[0457] Alternatively, the terminal device can determine Koffset through formula (3) and the adjustment parameter Z of Koffset as follows:

[0458] Or

[0459]

[0460] The terminal device can determine K_mac according to the foregoing formula (9) as follows:

[0461]

[0462] Alternatively, the terminal device may determine K_mac according to the foregoing formula (9) and the adjustment parameter Y of K_mac, as follows:

[0463] Or

[0464]

[0465] The terminal device may determine RAR_window_delay1 according to the foregoing formula (17), as follows:

[0466] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common;

[0467] Alternatively, the terminal device may determine RAR_window_delay1 according to formula (17) and the adjustment parameter X of RAR_window_delay, as follows:

[0468] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common + / - X.

[0469] The terminal device may determine RAR_window_delay2 according to the foregoing formula (18), as follows:

[0470] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA

[0471] = Delay_compensated;

[0472] Alternatively, the terminal device may determine RAR_window_delay2 according to formula (18) and the adjustment parameter X of RAR_window_delay, as follows:

[0473] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA + / - X

[0474] = Delay_compensated + / - X.

[0475] TA = TA_cal + TA_common.

[0476] Embodiment 2

[0477] The network device sends K_mac, △Koffset, and TA_common to the terminal device. For example, the network device can determine K_mac according to the calculation relationship, and △Koffset related to the maximum round-trip delay of the service link. For example, the network device can determine △Koffset according to the maximum round-trip delay Service_RTD_max of the service link. Among them, Or, determine Koffset according to the maximum round-trip delay in the signal coverage area (cell or beam) of the network device. Among them, Or the network device can determine Koffset according to the maximum round-trip delay between the reference point and the signal coverage area (cell or beam). Among them, Then according to determine △Koffset.

[0478] The terminal device can determine Koffset through the foregoing formula (1) as follows:

[0479]

[0480] Or, the terminal device can determine Koffset through the foregoing formula (1) and the adjustment parameter Z of Koffset as follows:

[0481] Or

[0482]

[0483] Optionally, when the terminal device and the network device obtain Koffset / K_mac according to TA_common, if TA_common is negative, the absolute value of TA_common can be selected and substituted into the calculation relationship, and then subtract this quantization value. For example, for the calculation relationship, if TA_common is negative, it can be adjusted to Or adjusted to

[0484] The terminal device can determine K_mac according to the received K_mac and the adjustment parameter Y of K_mac.

[0485] The terminal device can determine RAR_window_delay1 according to the foregoing formula (19) as follows:

[0486] RAR_window_delay1 = TA_cal + TA_common + K_mac * slot_duration;

[0487] Alternatively, the terminal device can determine RAR_window_delay1 according to formula (19) and the adjustment parameter X of RAR_window_delay, as follows:

[0488] RAR_window_delay1 = TA_cal + TA_common + K_mac * slot_duration + / - X.

[0489] The terminal device can determine RAR_window_delay2 according to the foregoing formula (20), as follows:

[0490] RAR_window_delay2 = TA_cal + TA_common + K_mac * slot_duration - TA

[0491] = K_mac * slot_duration

[0492] Alternatively, the terminal device can determine RAR_window_delay2 according to formula (20) and the adjustment parameter X of RAR_window_delay, as follows:

[0493] RAR_window_delay2 = TA_cal + TA_common + K_mac * slot_duration - TA + / - X

[0494] = K_mac * slot_duration + / - X.

[0495] TA = TA_cal + TA_common.

[0496] Embodiment 3

[0497] The network device sends Feeder_RTD, △Koffset, and TA_common to the terminal device. For example, the network device can determine Feeder_RTD according to the round-trip delay between the satellite and the network device, and determine △Koffset through the maximum round-trip delay of the service link.

[0498] The terminal device can determine Koffset through the foregoing formula (1), as follows:

[0499]

[0500] Alternatively, the terminal device can determine Koffset through the foregoing formula (1) and the adjustment parameter Z of Koffset, as follows:

[0501] Or

[0502]

[0503] Optionally, when the terminal device and the network device obtain Koffset / K_mac according to TA_common, if TA_common is negative, the absolute value of TA_common can be selected and substituted into the calculation relation, and then the quantization value is subtracted. For example, for the calculation relation, if TA_common is negative, it can be adjusted to or adjusted to

[0504] The terminal device can determine K_mac according to the foregoing formula (10) as follows:

[0505]

[0506] Alternatively, the terminal device can determine K_mac according to formula (10) and the adjustment parameter Y of K_mac as follows:

[0507] Or,

[0508]

[0509] The terminal device can determine RAR_window_delay1 according to the foregoing formula (21) as follows:

[0510] RAR_window_delay1 = TA_cal + Feeder_RTD;

[0511] Alternatively, the terminal device can determine RAR_window_delay1 according to formula (21) and the adjustment parameter X of RAR_window_delay as follows:

[0512] RAR_window_delay1 = TA_cal + Feeder_RTD + / - X.

[0513] The terminal device can determine RAR_window_delay2 according to the foregoing formula (22) as follows:

[0514] RAR_window_delay2 = TA_cal + Feeder_RTD - TA;

[0515] Alternatively, the terminal device can determine RAR_window_delay2 according to formula (22) and the adjustment parameter X of RAR_window_delay as follows:

[0516] RAR_window_delay2 = TA_cal + Feeder_RTD - TA + / - X.

[0517] TA = TA_cal + TA_common.

[0518] Example 4

[0519] The network device sends Delay_compensated, Koffset, RAR_window, and TA_common to the terminal device. For example, the network device can determine Koffset according to the maximum round-trip delay Service_RTD_max in the coverage area (beam / cell) of the network device. Among them, Or

[0520] The terminal device can determine Koffset according to the received Koffset and the adjustment parameter Z of Koffset.

[0521] The terminal device can determine K_mac according to the foregoing formula (9) as follows:

[0522]

[0523] Or, the terminal device can determine K_mac according to formula (7) and the adjustment parameter Y of K_mac as follows:

[0524] Or

[0525]

[0526] The terminal device can determine RAR_window_delay1 according to the foregoing formula (23) as follows:

[0527] RAR_window_delay1 = Koffset * slot_duration – RAR_window;

[0528] Or, the terminal device can determine RAR_window_delay1 according to formula (23) and the adjustment parameter X of RAR_window_delay as follows:

[0529] RAR_window_delay1 = Koffset * slot_duration – RAR_window + / - X; Or,

[0530] RAR_window_delay1 = (Koffset + / - X) * slot_duration – RAR_window。

[0531] The terminal device can determine RAR_window_delay2 according to the foregoing formula (24) as follows:

[0532] RAR_window_delay2 = Koffset * slot_duration – RAR_window - TA

[0533] Alternatively, the terminal device can determine RAR_window_delay2 according to formula (24) and the adjustment parameter X of RAR_window_delay as follows:

[0534] RAR_window_delay2 = Koffset * slot_duration – RAR_window - TA + / - X; or,

[0535] RAR_window_delay2 = (Koffset + / - X) * slot_duration – RAR_window - TA。

[0536] TA = TA_cal + TA_common。

[0537] Example 5、

[0538] The network device sends Delay_compensated, Service_RTD_min, TA_common, and RAR_window to the terminal device.

[0539] The terminal device can determine Koffset according to the foregoing formula (2) as follows:

[0540]

[0541] Alternatively, the terminal device can determine Koffset according to formula (2) and the adjustment parameter Z of Koffset as follows:

[0542] Or,

[0543]

[0544] The terminal device can determine K_mac according to the foregoing formula (9) as follows:

[0545] K_mac = "Delay_compensated / slot_duration;

[0546] Alternatively, the terminal device can determine K_mac according to Formula (9) and the adjustment parameter Y of K_mac as follows:

[0547] K_mac = "Delay_compensated / slot_duration + / - Y; or

[0548] K_mac = " (Delay_compensated + / - Y) / slot_duration.

[0549] The terminal device can determine RAR_window_delay1 according to the foregoing Formula (17) as follows:

[0550] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common;

[0551] Alternatively, the terminal device can determine RAR_window_delay1 according to Formula (17) and the adjustment parameter X of RAR_window_delay as follows:

[0552] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common + / - X.

[0553] Alternatively, the terminal device can determine RAR_window_delay1 according to the foregoing Formula (25) as follows:

[0554] RAR_window_delay1 = Service_RTD_min + Delay_compensated + TA_common;

[0555] Alternatively, the terminal device can determine RAR_window_delay1 according to Formula (25) and the adjustment parameter X of RAR_window_delay as follows:

[0556] RAR_window_delay1 = Service_RTD_min + Delay_compensated + TA_common + / - X.

[0557] The terminal device can determine RAR_window_delay2 according to the foregoing Formula (18) as follows:

[0558] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA

[0559] = Delay_compensated

[0560] Alternatively, the terminal device can determine RAR_window_delay2 according to formula (18) and the adjustment parameter X of RAR_window_delay, as follows:

[0561] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA + / - X

[0562] = Delay_compensated + / - X.

[0563] Alternatively, the terminal device can determine RAR_window_delay2 according to the foregoing formula (26), as follows:

[0564] RAR_window_delay1 = Service_RTD_min + Delay_compensated + TA_common - TA

[0565] = Service_RTD_min + Delay_compensated - TA_cal;

[0566] Alternatively, the terminal device can determine RAR_window_delay2 according to formula (26) and the adjustment parameter X of RAR_window_delay, as follows:

[0567] RAR_window_delay1 = Service_RTD_min + Delay_compensated + TA_common - TA + / - X

[0568] = Service_RTD_min + Delay_compensated - TA_cal + / - X.

[0569] TA = TA_cal + TA_common.

[0570] Example 6

[0571] The network device sends RAR_window_delay, Service_RTD_max, TA_common, and RAR_window to the terminal device. Optionally, the RAR_window_delay may represent a value related to the minimum round-trip delay between the gateway station and the terminal devices in its coverage area. For example, it may be equal to the minimum round-trip delay value or a quantized value of the minimum round-trip delay value.

[0572] Assume that the RAR_window_delay sent by the network device is determined by the actual timing method. Then, the terminal device can determine Koffset through the aforementioned formula (3), or through formula (3) and the adjustment parameter Z of Koffset, as follows:

[0573] Or

[0574] Or

[0575]

[0576] The terminal device can determine K_mac according to the aforementioned formula (13), or through formula (13) and the adjustment parameter Y of K_mac, as follows:

[0577]

[0578] Or

[0579]

[0580] Or

[0581]

[0582] Or, the terminal device can determine K_mac based on formula (11), or through formula (11) and the adjustment parameter Y of K_mac, as follows:

[0583] Or

[0584] Or

[0585]

[0586] Among them, Koffset in formula (11) can be determined by the terminal device through time parameters.

[0587] If the network device and the terminal device agree to use the RAR_window_delay determined by the actual timing method, the terminal device can use the RAR_window_delay sent by the network device as the delay start duration of the actually used RAR window. Alternatively, the terminal device can determine an accurate RAR_window_delay according to the above time parameters. For example, the terminal device can determine RAR_window_delay1 according to the above formula (17), or formula (17) and the adjustment parameter X of RAR_window_delay, as follows:

[0588] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common; or

[0589] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common + / - X.

[0590] If the network device and the terminal device agree to use the RAR_window_delay determined by the logical timing method, the terminal device can use the received RAR_window_delay minus TA as the delay start duration of the RAR window, or the terminal device can use the received RAR_window_delay, TA, and the adjustment parameter X of the RAR window as the delay start duration of the RAR window.

[0591] Assume that the RAR_window_delay sent by the network device is determined by the logical method. If the network device and the terminal device agree to use the RAR_window_delay determined by the logical timing method, the terminal device can use the received RAR_window_delay as the delay start duration of the actually used RAR window. Alternatively, the terminal device can determine an accurate RAR_window_delay according to the above time parameters. For example, the terminal device can determine RAR_window_delay2 according to the above formula (18), or formula (18) and the adjustment parameter X of RAR_window_delay, as follows:

[0592] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA

[0593] = Delay_compensated; or

[0594] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA + / - X

[0595] = Delay_compensated + / - X.

[0596] If the network device and the terminal device agree to use the actual timing method to determine RAR_window_delay, then the terminal device can use the received RAR_window_delay plus TA as the delay start duration of the RAR window, or the terminal device can use the received RAR_window_delay, TA, and the adjustment parameter X of the RAR window as the delay start duration of the RAR window.

[0597] TA = TA_cal + TA_common.

[0598] Example 7,

[0599] The network device sends Delay_compensated, RAR_window_delay, RAR_window, and TA_common to the terminal device.

[0600] Optionally, the RAR_window_delay can represent a value related to the minimum round-trip delay between the gateway station and the terminal devices in its coverage area. For example, it can be equal to the minimum round-trip delay value or a quantized value of the minimum round-trip delay value.

[0601] Assume that the RAR_window_delay sent by the network device is determined by the actual timing method. Then the terminal device can determine Koffset through the foregoing formula (3) or, the formula (3) and the adjustment parameter Z of Koffset, as follows:

[0602] Or

[0603] Or

[0604] Or,

[0605] The terminal device can determine Koffset through the foregoing formula (4) or, the formula (4) and the adjustment parameter Z of Koffset, as follows:

[0606] Or,

[0607] Or,

[0608]

[0609] The terminal device can determine K_mac according to the foregoing formula (9), or determine K_mac according to formula (9) and the adjustment parameter Y of K_mac, as follows:

[0610] Or

[0611] Or

[0612]

[0613] If the network device and the terminal device agree to use the RAR_window_delay determined by the actual timing method, the terminal device can use the delay start duration of the RAR window actually used by the RAR_window_delay sent by the network device. Or, the terminal device can determine an accurate RAR_window_delay according to the above time parameters. For example, the terminal device can determine RAR_window_delay1 according to the foregoing formula (17), or formula (17) and the adjustment parameter X of RAR_window_delay, as follows:

[0614] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common; or

[0615] RAR_window_delay1 = TA_cal + Delay_compensated + TA_common + / - X.

[0616] If the network device and the terminal device agree to use the RAR_window_delay determined by the logical timing method, the terminal device can use the received RAR_window_delay minus TA as the delay start duration of the RAR window, or the terminal device can use the received RAR_window_delay, TA, and the adjustment parameter X of the RAR window as the delay start duration of the RAR window.

[0617] Assume that the RAR_window_delay sent by the network device is determined in a logical manner. If the network device and the terminal device agree to determine the RAR_window_delay in a logical timing manner, then the terminal device can use the received RAR_window_delay as the delay start duration of the actually used RAR window. Alternatively, the terminal device can determine an accurate RAR_window_delay based on the above time parameters. For example, the terminal device can determine RAR_window_delay2 according to the above formula (18), or formula (18) and the adjustment parameter X of RAR_window_delay, as follows:

[0618] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA

[0619] = Delay_compensated; or

[0620] RAR_window_delay2 = TA_cal + Delay_compensated + TA_common - TA + / - X

[0621] = Delay_compensated + / - X.

[0622] If the network device and the terminal device agree to determine the RAR_window_delay in an actual timing manner, then the terminal device can use the received RAR_window_delay plus TA as the delay start duration of the RAR window, or the terminal device can determine the delay start duration of the RAR window according to the received RAR_window_delay, TA, and the adjustment parameter X of the RAR window.

[0623] TA = TA_cal + TA_common.

[0624] Embodiment 8

[0625] The network device sends K_mac, RAR_window_delay, TA_common, and RAR_window to the terminal device.

[0626] Assume that the RAR_window_delay sent by the network device is determined in an actual timing manner. Then the terminal device can determine Koffset through the foregoing formula (5), or formula (5) and the adjustment parameter Z of Koffset, as follows:

[0627] Or,

[0628] or

[0629]

[0630] Alternatively, the terminal device can determine Koffset through the foregoing formula (6), or through formula (6) and the adjustment parameter Z of Koffset, as follows:

[0631] or

[0632] or

[0633]

[0634] The terminal device can determine K_mac through the received K_mac and the adjustment parameter Y of K_mac.

[0635] If the network device and the terminal device agree to use the actually timed manner to determine RAR_window_delay, the terminal device can use the delay start duration of the actually used RAR window of the RAR_window_delay sent by the network device. Alternatively, the terminal device can determine an accurate RAR_window_delay according to the above time parameters. For example, the terminal device can determine RAR_window_delay1 based on formula (19), or based on formula (19) and the adjustment parameter X of RAR_window_delay, as follows:

[0636] RAR_window_delay1 = TA_cal + TA_common + K_mac * slot_duration; or

[0637] RAR_window_delay1 = TA_cal + TA_common + K_mac * slot_duration + / - X; or

[0638] RAR_window_delay1 = TA_cal + TA_common + (K_mac + / - X) * slot_duration.

[0639] If the network device and the terminal device agree to determine RAR_window_delay in a logical timing manner, the terminal device can subtract TA from the received RAR_window_delay as the delay start duration of the RAR window, or the terminal device can use the received RAR_window_delay, TA, and the adjustment parameter X of the RAR window as the delay start duration of the RAR window.

[0640] Assume that the RAR_window_delay sent by the network device is determined in a logical manner. If the network device and the terminal device agree to determine RAR_window_delay in a logical timing manner, the terminal device can use the received RAR_window_delay as the delay start duration of the actually used RAR window. Alternatively, the terminal device can determine an accurate RAR_window_delay based on the above time parameters. For example, the terminal device can determine RAR_window_delay2 based on formula (20) or formula (20) and the adjustment parameter X of RAR_window_delay as follows:

[0641] RAR_window_delay2 = TA_cal + TA_common + K_mac * slot_duration - TA

[0642] = K_mac * slot_duration; or

[0643] RAR_window_delay2 = TA_cal + TA_common + K_mac * slot_duration - TA + / - X

[0644] = K_mac * slot_duration + / - X; or

[0645] RAR_window_delay2 = TA_cal + TA_common + (K_mac + / - X) * slot_duration - TA

[0646] = (K_mac + / - X) * slot_duration

[0647] If the network device and the terminal device agree to determine RAR_window_delay in an actual timing manner, then the terminal device can use the received RAR_window_delay plus TA as the delay start duration of the RAR window, or the terminal device can use the received RAR_window_delay, TA, and the adjustment parameter X of the RAR window as the delay start duration of the RAR window.

[0648] TA = TA_cal + TA_common.

[0649] Example 9

[0650] The network device sends △Koffset, RAR_window_delay, TA_common, and RAR_window to the terminal device.

[0651] Assume that the RAR_window_delay sent by the network device is determined by the actual timing method. Then, the terminal device can determine Koffset based on the above formula (1) or, the adjustment parameter Z of formula (1) and Koffset, as follows:

[0652] Or

[0653] Or

[0654]

[0655] The terminal device can determine K_mac based on the above formula (11) or, the adjustment parameter Y of formula (11) and K_mac, as follows:

[0656] Or

[0657] Or

[0658]

[0659] If the network device and the terminal device agree to use the RAR_window_delay determined by the logical timing method, the terminal device can subtract TA from the received RAR_window_delay as the delay start duration of the RAR window, or the terminal device can use the received RAR_window_delay, TA, and the adjustment parameter X of the RAR window as the delay start duration of the RAR window.

[0660] Assume that the RAR_window_delay sent by the network device is determined in a logical manner. If the network device and the terminal device agree to determine the RAR_window_delay in a logical timing manner, the terminal device can use the received RAR_window_delay as the delay start duration of the actually used RAR window. Alternatively, the terminal device can determine an accurate RAR_window_delay based on the above time parameters. For example, the terminal device can determine RAR_window_delay2 based on formula (20) or, formula (20) and the adjustment parameter X of RAR_window_delay, as follows:

[0661] RAR_window_delay2 = TA_cal + TA_common + K_mac * slot_duration - TA

[0662] = K_mac * slot_duration; or

[0663] RAR_window_delay2 = TA_cal + TA_common + K_mac * slot_duration - TA + / - X

[0664] = K_mac * slot_duration + / - X; or

[0665] RAR_window_delay2 = TA_cal + TA_common + (K_mac + / - X) * slot_duration - TA

[0666] = (K_mac + / - X) * slot_duration

[0667] If the network device and the terminal device agree to determine the RAR_window_delay in an actual timing manner, then the terminal device can use the received RAR_window_delay plus TA as the delay start duration of the RAR window, or the terminal device can use the received RAR_window_delay, TA, and the adjustment parameter X of the RAR window as the delay start duration of the RAR window.

[0668] TA = TA_cal + TA_common.

[0669] Example 10

[0670] The network device sends RAR_window_delay, TA_common, and RAR_window to the terminal device.

[0671] If the RAR_window_delay sent by the network device is determined by the actual timing method, the terminal device can determine Koffset through the foregoing formula (5), or through formula (5) and the adjustment parameter Z of Koffset, as follows:

[0672] Or

[0673] Or

[0674]

[0675] The terminal device can determine K_mac based on the foregoing formula (11), or through formula (11) and the adjustment parameter Y of K_mac, as follows:

[0676] Or

[0677] Or

[0678]

[0679] Or, the terminal device can determine K_mac based on the foregoing formula (12), or through formula (12) and the adjustment parameter Y of K_mac, as follows:

[0680] Or

[0681] Or

[0682]

[0683] Or, the terminal device can determine K_mac based on the foregoing formula (13), or through formula (13) and the adjustment parameter Y of K_mac, as follows:

[0684]

[0685] Or

[0686]

[0687] Or

[0688]

[0689] TA = TA_cal + TA_common.

[0690] Assume that the RAR_window_delay sent by the network device is determined in a logical manner. If the network device and the terminal device agree to determine the RAR_window_delay in a logical timing manner, the terminal device can use the received RAR_window_delay as the delay start duration of the actually used RAR window. Alternatively, the terminal device can determine an accurate RAR_window_delay based on the above time parameters. If the network device and the terminal device agree to determine the RAR_window_delay in an actual timing manner, then the terminal device can use the received RAR_window_delay plus TA as the delay start duration of the RAR window, or the terminal device can use the received RAR_window_delay, TA, and the adjustment parameter X of the RAR window as the delay start duration of the RAR window.

[0691] Embodiment 11

[0692] Among them, it can be considered that the RAR_window_delay in the time parameters of the above Embodiment 1 - Embodiment 10 is determined in an actual timing manner. In Embodiment 11, it can be considered that the RAR_window_delay in the time parameters is determined in a logical timing manner. For easy distinction, the RAR_window_delay sent by the network device can be called RAR_window_delay’. Among them, RAR_window_delay’ can be determined by the network device based on the delay compensation value for the signal from the terminal device. For example, RAR_window_delay’ can be equal to the delay compensation value Delay_compensated, or considering the influence of processing delay and transmission delay on data accuracy, an offset value can be added to the delay compensation value to obtain RAR_window_delay;. For example,

[0693] RAR_window_delay’ = delay compensation value

[0694] RAR_window_delay’ = delay compensation value + offset value

[0695] Among them, the offset value is a real number, such as 1, 1.5, -2, 0, etc. This offset value can be determined by the network device, and the calculation result of the delay compensation value + the offset value is sent to the terminal device as RAR_window_delay’, or it can also be configured by the network device for the terminal device, or agreed upon through a protocol. The terminal device adds the received RAR_window_delay’ and the offset value to obtain the corrected / updated RAR_window_delay. For example, the terminal device can use the corrected / updated RAR_window_delay as the actually used RAR_window_delay.

[0696] The RAR_window_delay’ that the network device can send to the terminal device can also be a quantization value. For example,

[0697]

[0698] Or

[0699] Among them, slot_duration represents the quantization unit. After receiving RAR_window_delay’, the terminal device multiplies it by the quantization unit to obtain the RAR_window_delay’ sent by the network device to the terminal device.

[0700] If it is defined that the RAR_window_delay’ sent by the network device to the terminal device is determined based on a logical timing method, then when the terminal device receives RAR_window_delay’, when determining the delay start duration of the RAR window it wants to use, the terminal device can, based on its different understandings of the start time of the RAR_window, determine the corresponding delay start duration of the RAR window to be used based on the RAR_window_delay’ sent by the network device.

[0701] 1), The terminal device uses the actual timing as the start time of the RAR window:

[0702] RAR_window_delay1 = TA_cal + TA_common + RAR_window_delay’ or

[0703] RAR_window_delay1 = TA_cal + TA_common + RAR_window_delay’ - / +X or

[0704] RAR_window_delay1 = TA + RAR_window_delay’ or

[0705] RAR_window_delay1 = TA + RAR_window_delay’ - / + X

[0706] 2), The terminal device uses the logical timing as the starting moment of the RAR window:

[0707] RAR_window_delay 1 = RAR_window_delay’ or

[0708] RAR_window_delay 1 = RAR_window_delay’ - / + X

[0709] It should be noted that if RAR_window_delay’ is related to the delay compensation value, then the calculation relationships for determining K_offfset, K_mac, etc. based on RAR_window_delay’ sent by the network device in the above cases 1 - 17 need to be modified.

[0710] For example, in Embodiment 4 or Embodiment 9:

[0711] The calculation relationship can be changed to

[0712] For another example, in Embodiment 7, determining The calculation relationship cannot hold. Therefore, if the RAR_window_delay sent by the network device is determined based on the logical timing method, this calculation relationship cannot be used.

[0713] For another example, in Embodiment 9, determining The calculation relationship cannot hold. Therefore, if the RAR_window_delay sent by the network device is determined based on the logical timing method, this calculation relationship cannot be used.

[0714] For another example, in Embodiment 9, determining The calculation relationship can be changed to

[0715] For the above embodiments 1 - 10 in which the network device sends Delay_compensated to the terminal device, if it is specified that the terminal device determines the actually used RAR_window_delay in the logical timing manner, then the terminal device can determine RAR_window_delay through the following formula:

[0716] RAR_window_delay = Delay_compensated or

[0717] RAR_window_delay = Delay_compensated + offset value.

[0718] Optionally, if the network device updates RAR_window_delay’, the terminal device or the network device also determines the updated K_mac according to the above calculation relationship.

[0719] Optionally, when the aforementioned terminal device or network device determines whether the K_mac update condition is met based on K_mac_thresh, if |updated K_mac - previous K_mac| ≥ K_mac_thresh is not satisfied, the previous K_mac is still used. The terminal device can wait for the update of RAR_window_delay’ and then perform the determination operation.

[0720] In addition, for the above methods of determining K_offfset, K_mac, etc. based on Delay_compensated, Delay_compensated in the formula can be replaced with RAR_window_delay’ sent by the network device to the terminal device. For example, in the above Embodiments 4, 5, and 7 The calculation relationship can be replaced with That is, the network device does not need to send Delay_compensated to the terminal device additionally, avoiding additional signaling overhead.

[0721] In the above technical solution, the reference point can be at any position. For example, the reference point can be on the serving link, or on the feeder link, or on the satellite, or on the gateway station.

[0722] In a possible implementation, if the reference point can be on the satellite or the gateway station, refer to Figure 17 , when the reference point is on the satellite or the gateway station, there are two possibilities when the terminal device determines the timing advance value TA to be used:

[0723] 1) When the reference point is on the satellite, TA = TA_cal. There is no need to add the TA_common value.

[0724] 2) When the reference point is on the gateway station, TA = TA_cal + TA_common, and the TA_common value needs to be added.

[0725] In other words, when the reference point is at the satellite, the common timing advance value TA_common = 0. When the reference point is at the base station, the common timing advance value TA_common = Feeder_RTD.

[0726] Therefore, in order to further reduce signaling overhead, the two values of TA_common and Feeder_RTD can be jointly indicated. Among them, Timing_common can be introduced, and this Timing_common can be determined according to the round-trip delay of the feeder link. For example, Timing_common can be equal to Feeder_RTD or Feeder_RTD plus a difference. The difference here can be set considering the influence of positioning error, processing delay, and / or quantization error, etc.

[0727] The network device can send Timing_common and indication information to the terminal device. The indication information here can be a bit sequence. For example, a signaling with a bit sequence length of 1 bit. The relationship between the value of the bit sequence and the indication of the indication information can be specified by the communication protocol, or it can also be sent by the network device to the terminal device. Alternatively, the indication information can be an identifier, and the relationship between the identifier and the indication of the indication information can be specified by the communication protocol, or it can also be sent by the network device to the terminal device.

[0728] In one example, taking the indication information as a bit sequence as an example. When the value of the bit sequence is "0", the indication information can be used to indicate that the reference point is at or near the satellite, or the indication information can be used to indicate that the network device compensates for the round-trip delay of the feeder link, or the indication information can be used to indicate that the terminal device does not need to add Timing_common when determining TA, or the indication information can be used to indicate that the terminal device does not need to add the round-trip delay of the feeder link when determining TA, or the indication information can be used to indicate that the terminal device determines K_mac according to Timing_common, or the indication information can be used to indicate that the terminal device determines K_mac according to the round-trip delay of the feeder link.

[0729] Optionally, the network device can also send other time parameters other than TA_common and Feeder_RTD in the above cases 1 - 17 to the terminal device, so that the terminal device determines one or more of Koffset, K_mac, and RAR_window_delay according to the time parameters.

[0730] Hereinafter, an example will be given with the network device sending Timing_common, indication information, and △Koffset to the terminal device.

[0731] The terminal device can determine RAR_window_delay based on the following formula.

[0732] RAR_window_delay1 = TA_cal + Timing_common

[0733] Or RAR_window_delay1 = TA_cal + Timing_common + / - X

[0734] RAR_window_delay2 = TA_cal + Timing_common – TA

[0735] = Timing_common

[0736] Or RAR_window_delay2 = TA_cal + Timing_common – TA + / - X

[0737] = Timing_common + / - X

[0738] The terminal device can determine K_mac based on the following formula.

[0739]

[0740] Or

[0741] Or

[0742] The terminal device can determine Koffset based on the following formula.

[0743] Koffset = △Koffset

[0744] Or Koffset = △Koffset + / - Z

[0745] The terminal device can determine TA based on the following formula.

[0746] TA = TA_cal

[0747] In another example, taking the indication information as a bit sequence. When the value of the bit sequence is "1", the indication information can be used to indicate that the reference point is at the gateway station, or the indication information can be used to indicate that the network device does not compensate for the round-trip delay of the feeder link, or the indication information can be used to indicate that the terminal device needs to add Timing_common when determining TA, or the indication information can be used to indicate that the terminal device needs to add the round-trip delay of the feeder link when determining TA, or the indication information can be used to indicate that the K_mac value is equal to 0 or a smaller value, such as a smaller integer value. When the terminal device receives the delay compensation indication signaling TA_indi indicating the above situation, the terminal device can determine K_mac and TA according to the following calculation relationship:

[0748] Optionally, the network device may also send other timing parameters except TA_common and Feeder_RTD in the above cases 1-17 to the terminal device, so that the terminal device determines one or more of Koffset, K_mac, and RAR_window_delay according to the timing parameters.

[0749] Hereinafter, an example will be given in which the network device sends Timing_common, indication information, and △Koffset to the terminal device.

[0750] The terminal device may determine RAR_window_delay based on the following formula.

[0751] RAR_window_delay1 = TA_cal + Timing_common

[0752] Or RAR_window_delay1 = TA_cal + Timing_common + / - X

[0753] RAR_window_delay2 = TA_cal + Timing_common – TA

[0754] = 0

[0755] Or RAR_window_delay2 = TA_cal + Timing_common – TA + / - X

[0756] = X

[0757] The terminal device may determine K_mac based on the following formula.

[0758] K_mac = 0

[0759] Or K_mac is equal to a smaller value, such as 1, 2, or 3, etc. For another example, K_mac = Y.

[0760] The terminal device may determine Koffset based on the following formula.

[0761]

[0762] Or

[0763] Or

[0764] The terminal device may determine TA based on the following formula.

[0765] TA = TA_cal + Timing_common

[0766] Based on the above solution, the network device can jointly indicate TA_common and Feeder_RTD based on Timing common and indication information, which can further save signaling overhead.

[0767] In addition, it should be noted that the above common timing value Timing_common, indication information, time unit / duration unit, etc. can be sent in the first information together with the time parameter. For relevant descriptions, please refer to step 1401 as shown, and details will not be elaborated here.

[0768] In another possible implementation, the network device can implicitly indicate the indication of the above indication information. For example, if the terminal device receives Timing_common from the network device indicating the K_mac value, it can indicate that K_mac is determined according to Timing_common, implicitly indicating that the network device compensates for the round-trip delay of the feeder link. If the terminal device receives Timing_common from the network device that does not indicate K_mac or is not equal to K_mac, it can indicate that K_mac is not determined based on Timing_common, implicitly indicating that the network device does not compensate for the round-trip delay of the feeder link.

[0769] For example, the network device can send Timing_common or K_mac to represent the above two situations. The network device can send Timing_common to the terminal device to implicitly indicate that the network device does not compensate for the round-trip delay of the feeder link. The network device can send K_mac to the terminal device to implicitly indicate that the network device compensates for the round-trip delay of the feeder link. Therefore, if the terminal device receives Timing common or K_mac from the network device, it determines whether the network device compensates for the round-trip delay of the feeder link, so as to determine Koffset, K_mac, and RAR_window_delay.

[0770] In one example, the network device can use the following two signaling to indicate whether Timing common is the same as K_mac.

[0771] K_mac INTEGER(0..127)OPTIONAL,

[0772] Timing_common INTEGER(-1024..1024)OPTIONAL,

[0773] The network device can send the K_mac signaling or Timing_common signaling to the terminal device according to the actual network deployment and working mode. Among them, the K_mac signaling represents the second timing offset for solving the problem of insufficient timing delay for the downlink configuration to take effect. Timing_common represents the round-trip delay of the feeding link, or a parameter value determined based on the round-trip delay of the feeding link. The terminal device can determine RAR_window_delay, Koffset, and TA according to Timing_common.

[0774] For example, when the network device performs delay compensation on the signal received from the terminal device, it can send K_mac to the terminal device and not send the Timing_common signaling at the same time. If the network device does not perform delay compensation on the signal received from the terminal device, it can send Timing_common to the terminal device and not send the K_mac signaling at the same time. After receiving the K_mac or Timing_common signaling, the terminal device can determine whether the network device has performed delay compensation on the uplink signal, and at the same time, according to different situations, determine the parameter values of RAR_window_delay, K_mac, Koffset, and TA according to the above method.

[0775] The above signaling forms are only examples, and the numbers in them are also exemplary. According to the actual network deployment situation, such as satellite orbital altitude, minimum communication elevation angle, beam / cell size, etc., the representation range of K_mac and the number of information bits used can be determined according to the possible maximum delay compensation value for the network device to receive the uplink signal, and the representation range of Timing_common and the number of information bits used can be determined according to the possible maximum round-trip delay between the satellite and the network device.

[0776] Hereinafter, taking the example that the network device sends △Koffset and K_mac to the terminal device and does not send the Timing_common signaling for illustration.

[0777] The terminal device can determine RAR_window_delay based on the following formula.

[0778] RAR_window_delay1 = TA_cal + Timing_common

[0779] Or RAR_window_delay1 = TA_cal + Timing_common + / - X

[0780] RAR_window_delay2 = TA_cal + Timing_common – TA

[0781] =Timing_common

[0782] or RAR_window_delay2 = TA_cal + Timing_common – TA + / - X

[0783] =Timing_common + / - X

[0784] The terminal device can determine K_mac based on the following formulae.

[0785]

[0786] or

[0787] or

[0788] The terminal device can determine Koffset based on the following formulae.

[0789] Koffset = △Koffset

[0790] or Koffset = △Koffset + / - Z

[0791] The terminal device can determine TA based on the following formulae.

[0792] TA = TA_cal.

[0793] In the following, taking the case where the network device sends △Koffset and Timing_common to the terminal device and does not send the K_mac signaling as an example for explanation.

[0794] The terminal device can determine RAR_window_delay based on the following formulae.

[0795] RAR_window_delay1 = TA_cal + Timing_common

[0796] or RAR_window_delay1 = TA_cal + Timing_common + / - X

[0797] RAR_window_delay2 = TA_cal + Timing_common – TA

[0798] =0

[0799] or RAR_window_delay2 = TA_cal + Timing_common – TA + / - X

[0800] =X

[0801] The terminal device can determine \(K_{mac}\) based on the following formula.

[0802] \(K_{mac}=0\)

[0803] Or \(K_{mac}\) is equal to a smaller value, such as 1, 2, or 3, etc. For another example, \(K_{mac}=Y\).

[0804] The terminal device can determine \(K_{offset}\) based on the following formula.

[0805]

[0806] Or

[0807] Or

[0808] The terminal device can determine \(TA\) based on the following formula.

[0809] \(TA = TA_{cal}+Timing_{common}\)

[0810] Based on the above solution, the network device can implicitly indicate to the terminal device whether to compensate the feeding link, which can save transmission resources.

[0811] Based on the same technical concept as the above method, as Figure 18 shown, a device 1800 is provided. The device 1800 can execute each step performed by the terminal device and the network device side in the above method. To avoid repetition, it will not be elaborated here.

[0812] The device 1800 includes: a transceiver module 1810, a processing module 1820. Optionally, it further includes a storage module 1830; the processing module 1820 can be respectively connected to the storage module 1830 and the transceiver module 1810, and the storage module 1830 can also be connected to the transceiver module 1810. Among them, the processing module 1820 can be integrated with the storage module 1830. The transceiver module 1810 can also be called a transceiver, a transceiver unit, a transceiver device, etc. The processing module 1820 can also be called a processor, a processing board, a processing module, a processing device, etc. Optionally, the device for realizing the receiving function in the transceiver module 1810 can be regarded as a receiving unit, and the device for realizing the sending function in the transceiver module 1810 can be regarded as a sending unit, that is, the transceiver module 1810 includes a receiving unit and a sending unit. The transceiver module can sometimes also be called a transceiver, a transceiver unit, or a transceiver circuit, etc. The receiving unit can sometimes also be called a receiver, a receiver unit, or a receiving circuit, etc. The sending unit can sometimes also be called a transmitter, a transmitter unit, or a transmitting circuit, etc.

[0813] It should be understood that the transceiver module 1810 is used to perform the sending and receiving operations on the terminal device and network device sides in the above method embodiments, and the processing module 1820 is used to perform other operations on the terminal device and network device sides except for the sending and receiving operations in the above method embodiments. For example, in one implementation, the transceiver module 1810 is used to perform Figure 14 the receiving operation on the terminal device side or the sending operation on the network device side in step 1401 in, and / or the transceiver module 1810 is further used to perform other sending and receiving steps on the terminal device and network device sides in the embodiments of the present application. The processing module 1820 is used to perform Figure 14 the processing steps on the terminal device side in step 1402 in, and / or the processing module 1820 is used to perform other processing steps on the terminal device and network device sides in the embodiments of the present application.

[0814] The storage module 1830 is used to store computer programs;

[0815] Exemplarily, when the device 1800 executes each step performed by the terminal device in the above method, the transceiver module 1810 is used to receive the first information. The first information may be a time parameter, and for relevant descriptions, reference may be made to the method embodiments as shown in Figure 14 which will not be elaborated here.

[0816] In one design, the processing module 1820 is used to determine a timing offset based on the time parameter. Specifically, the processing module 1820 may be used to determine at least one of a first timing offset and a second timing offset. Optionally, the processing module 1820 may further be used to determine the delay start duration of the RAR window.

[0817] In one design, the time parameter includes the difference between the first timing offsets and a common timing advance value TA_common, and the TA_common is a parameter determined according to the round-trip time delay between the satellite and a reference point. Specifically, the processing module 1820 is used to determine the first timing offset based on the difference between the first timing offsets and the TA_common.

[0818] In one design, the time parameter includes the minimum round-trip time delay parameter Service_RTD_min of the serving link in the area covered by the satellite, the common timing advance value TA_common, and the duration of the RAR window. The TA_common is a parameter determined according to the round-trip time delay between the satellite and a reference point. Specifically, the processing module 1820 is used to determine the first timing offset based on the Service_RTD_min, the TA_common, and the duration of the RAR window.

[0819] In one design, the time parameters include the maximum round-trip delay parameter Service_RTD_max of the service link in the area covered by the satellite and the common timing advance value TA_common. The TA_common is a parameter determined according to the round-trip delay between the satellite and the reference point. The processing module 1820 is specifically configured to determine the first timing offset based on the Service_RTD_max and the TA_common.

[0820] In one design, the time parameters include the duration of the RAR window, the delay start duration of the RAR window, and the round-trip delay parameter Delay_compensated between the reference point and the network device. The processing module 1820 is specifically configured to determine the first timing offset based on the duration of the RAR window, the delay start duration of the RAR window, and the Delay_compensated.

[0821] In one design, the time parameters include the duration of the RAR window and the delay start duration of the RAR window. The processing module 1820 is specifically configured to determine the first timing offset based on the duration of the RAR window and the delay start duration of the RAR window.

[0822] In one design, the time parameters include the duration of the RAR window, the delay start duration of the RAR window, and the second timing offset. The processing module 1820 is specifically configured to determine the first timing offset based on the duration of the RAR window, the delay start duration of the RAR window, and the second timing offset.

[0823] In one design, the processing module 1820 is specifically configured to determine the first timing offset according to the time parameters and the adjustment parameter of the first timing offset. The adjustment parameter of the first timing offset is preset or indicated by the network device.

[0824] In one design, the time parameters include the round-trip delay parameter Delay_compensated between the reference point and the network device. The processing module 1820 is specifically configured to determine the second timing offset based on the Delay_compensated.

[0825] In one design, the time parameters include the round-trip delay parameter Feeder_RTD between the satellite and the network device and the common timing advance value TA_common. The TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The processing module 1820 is specifically configured to determine the second timing offset based on the Feeder_RTD and the TA_common.

[0826] In one design, the time parameters include the duration of the RAR window, the delay start duration of the RAR window, and the first timing offset. The processing module 1820 is specifically configured to determine a second timing offset based on the duration of the RAR window, the delay start duration of the RAR window, and the first timing offset.

[0827] In one design, the time parameters include the first timing offset and a common timing advance value TA_common, where TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The processing module 1820 is further configured to determine a round-trip delay parameter TA_cal of the service link based on the position information of the satellite. The processing module 1820 is specifically configured to determine a second timing offset based on the first timing offset, TA_cal, and TA_common.

[0828] In one design, the time parameters include the duration of the RAR window, the delay start duration of the RAR window, and a common timing advance value TA_common, where TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The processing module 1820 is further configured to determine a round-trip delay parameter TA_cal of the service link based on the position information of the satellite. The processing module 1820 is specifically configured to determine the second timing offset based on the duration of the RAR window, the delay start duration of the RAR window, TA_cal, and TA_common.

[0829] In one design, the processing module 1820 is further configured to determine the second timing offset according to the time parameters and an adjustment parameter of the second timing offset; the adjustment parameter of the second timing offset is preset or indicated by the network device.

[0830] In one design, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters include a round-trip delay parameter Delay_compensated between the reference point and the network device and a common timing advance value TA_common, where TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The processing module 1820 is further configured to determine a round-trip delay parameter TA_cal of the service link based on the position information of the satellite. The processing module 1820 is specifically configured to determine the delay start duration of the first RAR window based on TA_cal, TA_common, and Delay_compensated.

[0831] In one design, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters include the second timing offset and the common timing advance value TA_common, and the TA_common is determined according to the round-trip delay parameter between the satellite and the reference point. The processing module 1820 is further configured to determine the round-trip delay parameter TA_cal of the service link based on the position information of the satellite. Specifically, the processing module 1820 is configured to determine the delay start duration of the first RAR window based on the TA_cal, the TA_common, and the second timing offset.

[0832] In one design, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters include the round-trip delay parameter Feeder_RTD between the satellite and the network device. The processing module 1820 is further configured to determine the round-trip delay parameter TA_cal of the service link based on the position information of the satellite. Specifically, the processing module 1820 is configured to determine the delay start duration of the first RAR window based on the TA_cal and the Feeder_RTD.

[0833] In one design, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters include the first timing offset and the duration of the RAR window. The processing module 1820 is further configured to determine the delay start duration of the first RAR window based on the first timing offset and the duration of the RAR window.

[0834] In one design, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameters include the minimum round-trip delay parameter Service_RTD_min of the service link in the area covered by the satellite and the round-trip delay parameter Delay_compensated between the reference point and the network device. Specifically, the processing module 1820 is configured to determine the delay start duration of the first RAR window based on the Service_RTD_min and the Delay_compensated.

[0835] In one design, the processing module 1820 is specifically configured to determine the delay start duration of the first RAR window according to the time parameters and the adjustment parameter of the delay start duration of the RAR window. The adjustment parameter of the delay start duration of the RAR window is preset or indicated by the network device.

[0836] In a design, the delay start duration of the RAR window includes the delay start duration of the second RAR window. The processing module 1820 is specifically configured to determine the delay start duration of the second RAR window based on the delay start duration of the first RAR window and the timing advance value used by the terminal device; or, the processing module 1820 is specifically configured to determine the delay start duration of the second RAR window based on the delay start duration of the first RAR window, the timing advance value used, and the adjustment parameter of the delay start duration of the RAR window. The adjustment parameter of the delay start duration of the RAR window is preset or indicated by the network device.

[0837] In a design, the delay start duration of the RAR window includes the delay start duration of the second RAR window. The time parameter includes the delay start duration of the first RAR window. The processing module 1820 is specifically configured to determine the delay start duration of the second RAR window based on the delay start duration of the first RAR window and the timing advance value used; or, the processing module 1820 is specifically configured to determine the delay start duration of the second RAR window based on the delay start duration of the first RAR window, the timing advance value used, and the adjustment parameter of the delay start duration of the RAR window. The adjustment parameter of the delay start duration of the RAR window is preset or indicated by the network device.

[0838] In a design, the transceiver module 1810 is further configured to receive indication information. The indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, or the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link.

[0839] In a design, the time parameter includes the difference between the common timing value and the first timing offset. The common timing value is determined based on the round-trip delay of the feeder link. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the first timing offset based on the difference of the first timing offset and not based on the common timing value. When the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the first timing offset based on the difference of the first timing offset and the common timing value.

[0840] In a design, the time parameter includes the common timing value. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the second timing offset based on the common timing value; when the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the second timing offset based on 0 and not based on the common timing value.

[0841] In one design, the delay start duration of the RAR window includes the delay start duration of the first RAR window. The time parameter includes a common timing value, which is determined based on the round-trip delay of the feeder link. The processing module 1820 is further configured to determine the round-trip delay parameter TA_cal of the service link based on the position information of the satellite. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the delay start duration of the first RAR window based on the TA_cal and the common timing value; when the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the delay start duration of the first RAR window based on the TA_cal and the common timing value.

[0842] In one design, the delay start duration of the RAR window includes the delay start duration of the second RAR window. The time parameter includes a common timing value, which is determined based on the round-trip delay of the feeder link. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the delay start duration of the second RAR window based on the common timing value; when the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the delay start duration of the second RAR window based on the common timing value.

[0843] In one design, the time parameter includes a common timing value, which is determined based on the round-trip delay of the feeder link. The processing module 1820 is further configured to determine the round-trip delay parameter TA_cal of the service link based on the position information of the satellite. When the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the timing advance value to be used based on the TA_cal and not based on the common timing value; when the indication information is used to indicate that the network device has compensated for the round-trip delay of the feeder link, the processing module 1820 is specifically configured to determine the timing advance value to be used based on the TA_cal and the common timing value.

[0844] In one design, the time parameter includes the difference between the first timing offset and the second timing offset, and the processing module 1820 is specifically configured to determine the first timing offset based on the difference between the first timing offsets and not based on the second timing offset; or, the delay start duration of the RAR window includes the delay start duration of the first RAR window, and the time parameter includes the second timing offset; the processing module 1820 is further configured to determine the round-trip delay parameter TA_cal of the service link based on the position information of the satellite, and the processing module 1820 is specifically configured to determine the delay start duration of the first RAR window based on the TA_cal and the second timing offset; or, the delay start duration of the RAR window includes the delay start duration of the second RAR window, the time parameter includes the second timing offset, and the processing module 1820 is specifically configured to determine the delay start duration of the first RAR window based on the second timing offset; or, the time parameter includes the difference between the first timing offsets and a common timing value, the common timing value is determined based on the round-trip delay of the feeder link, and the processing module 1820 is specifically configured to determine the first timing offset based on the difference between the first timing offsets and the common timing value; or, the time parameter includes a common timing value, the common timing value is determined based on the round-trip delay of the feeder link, and the processing module 1820 is specifically configured to determine the second timing offset based on 0 and not based on the common timing value; or, the delay start duration of the RAR window includes the delay start duration of the first RAR window, the time parameter includes a common timing value, the common timing value is determined based on the round-trip delay of the feeder link; the processing module 1820 is further configured to determine the round-trip delay parameter TA_cal of the service link based on the position information of the satellite, and the processing module 1820 is specifically configured to determine the delay start duration of the first RAR window based on the TA_cal and the common timing value; or, the delay start duration of the RAR window includes the delay start duration of the second RAR window, the time parameter includes a common timing value, the common timing value is determined based on the round-trip delay of the feeder link; the processing module 1820 is specifically configured to determine the delay start duration of the second RAR window based on the common timing value.

[0845] In a design, the delay start duration of the RAR window includes the delay start duration of the first RAR window and the delay start duration of the second RAR window. The delay start duration of the second RAR window is determined based on the round-trip delay parameter Delay_compensated between the reference point and the network device. The time parameter includes the delay start duration of the second RAR window. Specifically, the processing module 1820 is configured to determine the second timing offset based on the delay start duration of the second RAR window; or, the processing module 1820 is specifically configured to determine the delay start duration of the first RAR window based on the delay start duration of the second RAR window and the used timing advance value.

[0846] When the device is a chip-like device or a circuit, the device may include a transceiver module and a processing module. Among them, the transceiver module may be an input / output circuit and / or a communication interface; the processing module is an integrated processor, a microprocessor, or an integrated circuit. The transceiver module can input data and output data, and the processing module can determine the output data according to the input data. For example, the transceiver module inputs the first information. The processing module can determine the output data, such as the timing offset, according to the input data.

[0847] Exemplarily, when the device 1800 executes the steps performed by the network device in the above method, the processing module 1820 is configured to generate the first information. The first information may be a time parameter. For relevant descriptions, reference may be made to the method embodiments as shown in Figure 14 and details are not described herein again. The transceiver module 1810 is configured to send the first information.

[0848] In a design, the transceiver module 1810 is further configured to send an indication information, where the indication information is used to indicate that the network device compensates for the round-trip delay of the feeder link, or the indication information is used to indicate that the network device does not compensate for the round-trip delay of the feeder link. For relevant descriptions, reference may be made to the method embodiments as shown in Figure 14 and details are not described herein again.

[0849] In a design, the transceiver module 1810 is further configured to send at least one of the adjustment parameter of the first timing offset, the adjustment parameter of the second timing offset, and the adjustment parameter of the delay start duration of the RAR window. For relevant descriptions, reference may be made to the method embodiments as shown in Figure 14 and details are not described herein again.

[0850] When the device is a chip - type device or a circuit, the device may include a transceiver module and a processing module. Among them, the transceiver module may be an input - output circuit and / or a communication interface; the processing module is an integrated processor, a microprocessor, or an integrated circuit. The transceiver module can input data and output data, and the processing module can determine the output data. For example, the processing module can generate a first piece of information. The transceiver module can output the first piece of information.

[0851] As Figure 8 As shown in the device 800 provided by the embodiment of the present application, it is used to implement the functions of the first network device side and the second network device side in the above - mentioned method. When the device is used to implement the function of the first network device in the above - mentioned method, the device may be an LMF, or a chip with a function similar to that of the LMF, or a device that can be used in combination with the LMF. When the device is used to implement the function of the second network device in the above - mentioned method, the device may be an access network device, or a chip with a function similar to that of the access network device, or a device that can be used in combination with the access network device.

[0852] The device 1900 includes at least one processor 1920, which is used to implement the functions of the network device and the terminal device side in the method provided by the embodiment of the present application. The device 1900 may also include a communication interface 1910. In the embodiment of the present application, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces, and is used to communicate with other devices through a transmission medium. For example, the communication interface 1910 is used for the device in the device 1900 to communicate with other devices. The processor 1920 can complete the functions of the processing module 1820 as Figure 18 shown, and the communication interface 1910 can complete the functions of the transceiver module 1810 as Figure 18 shown.

[0853] The device 1900 may also include at least one memory 1930, which is used to store program instructions and / or data. The memory 1930 is coupled to the processor 1920. The coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, and is used for information interaction between devices, units, or modules. The processor 1920 may cooperate with the memory 1930. The processor 1920 may execute the program instructions stored in the memory 1930. At least one of the at least one memories may be included in the processor.

[0854] In the embodiment of the present application, the specific connection medium between the above - mentioned communication interface 1910, processor 1920, and memory 1930 is not limited. In the embodiment of the present application Figure 19 it is shown that the memory 1930, processor 1920, and communication interface 1910 are connected through a bus 1940, and the busFigure 19 is represented by a thick line. The connection manners between other components are only for illustrative purposes and are not limited thereto. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 19 is only represented by a thick line in, but it does not mean that there is only one bus or one type of bus.

[0855] Figure 20 shows a schematic structural diagram of a simplified terminal device. For the convenience of understanding and illustration, Figure 20 in, the terminal device takes a mobile phone as an example. As Figure 20 shown, the terminal device includes a processor, a memory, a radio frequency circuit, an antenna, and an input / output device. The processor is mainly used for processing communication protocols and communication data, and controlling the terminal device, executing software programs, processing data of software programs, etc. The memory is mainly used for storing software programs and data. The radio frequency circuit is mainly used for the conversion between baseband signals and radio frequency signals and the processing of radio frequency signals. The processor can execute the software programs stored in the memory to enable the terminal device to execute the steps executed by the terminal device in the foregoing method embodiments, which will not be elaborated here. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. The input / output device, such as a touch screen, a display screen, a keyboard, etc., is mainly used for receiving data input by the user and outputting data to the user. It should be noted that some types of terminal devices may not have an input / output device.

[0856] When data needs to be sent, after the processor performs baseband processing on the data to be sent, it outputs a baseband signal to the radio frequency circuit, and the radio frequency circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For the convenience of illustration, Figure 20 only one memory and one processor are shown in. In an actual terminal device product, there may be one or more processors and one or more memories. The memory can also be referred to as a storage medium or a storage device, etc. The memory can be set independently of the processor or integrated with the processor. The embodiments of the present application do not limit this.

[0857] In the embodiments of the present application, the antenna and the radio frequency circuit with transceiver functions can be regarded as the transceiver module of the terminal device. As Figure 20 shown in, the transceiver module 2010 regards the processor with processing functions as the processing module of the terminal device. As Figure 20 shown in, the processing module 2020.

[0858] As another form of this embodiment, a computer-readable storage medium is provided, on which instructions are stored, and when the instructions are executed, the methods on the network device side and the terminal device side in the above method embodiment are executed.

[0859] As another form of this embodiment, a computer program product including instructions is provided, and when the instructions are executed by an electronic device (for example, a computer, a processor, or a device equipped with a processor, etc.), the electronic device is caused to execute the methods on the network device side and the terminal device side in the above method embodiment.

[0860] As another form of this embodiment, a communication system is provided, and the system may include a terminal device, the above at least one terminal device, and the above at least one network device.

[0861] It should be understood that the processor mentioned in the embodiments of the present invention may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0862] It should also be understood that the memory mentioned in the embodiments of the present invention can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM).

[0863] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) is integrated in the processor.

[0864] It should be noted that the memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.

[0865] It should be understood that in various embodiments of the present application, the magnitudes of the sequence numbers of the above processes do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

[0866] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0867] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0868] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

[0869] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place, or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0870] In addition, the functional units in each embodiment of this application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0871] When the above-mentioned function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs.

[0872] As described above, the above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method applied to a first communication device, characterized in that, it includes: receiving first information, where the first information includes a time parameter; the time parameter includes a second timing offset K_mac, and the second timing offset K_mac is used to indicate the delay for the configuration information received by the first communication device to take effect; determining the delay start duration of a random access response (RAR) window according to the second timing offset K_mac.

2. The method according to claim 1, characterized in that, the delay start duration of the RAR window is determined according to the second timing offset K_mac and the timing advance value used by the first communication device.

3. The method according to claim 2, characterized in that, the delay start duration of the RAR window satisfies the following formula: RAR_window_delay = TA + K_mac * slot_duration, where RAR_window_delay represents the delay start duration of the RAR window, TA represents the timing advance value used by the first communication device, and slot_duration represents a time unit.

4. The method according to claim 3, characterized in that, the time unit is 1 ms, and the delay start duration of the RAR window satisfies: RAR_window_delay = TA + K_mac.

5. The method according to any one of claims 2 to 4, characterized in that, the timing advance value used by the first communication device is determined according to a common timing advance value and the round-trip delay between the satellite and the first communication device.

6. The method according to claim 5, characterized in that, the timing advance value used by the first communication device is the sum of a common timing advance value, the round-trip delay between the satellite and the first communication device, an offset, and a correction value, where the correction value is indicated by the second communication device, and the offset is indicated by the second communication device or specified by the communication protocol.

7. The method according to claim 5 or 6, characterized in that, the time parameter further includes the common timing advance value.

8. The method according to any one of claims 1 to 7, characterized in that, the first information is carried in at least one of the following: a broadcast message, a radio resource control (RRC) message, a system information block.

9. The method according to any one of claims 1 to 8, characterized in that, it further includes: delaying the opening of the RAR window according to the delay start duration of the RAR window; or, delaying the opening of a random access contention resolution timer according to the delay start duration of the RAR window.

10. The method according to any one of claims 1 to 9, characterized in that, the second timing offset K_mac is related to the round-trip delay between the gateway station and the reference point.

11. The method according to any one of claims 1 to 10, characterized in that, the RAR window is used to receive a physical downlink control channel indicating at least one of the following: message 2 (Msg2), message B (MsgB), or a fallback RAR message.

12. The method according to any one of claims 1 to 11, wherein, the configuration information is Media Access Control (MAC) signaling.

13. A communication method applied to a second communication device, wherein, it includes: determining first information; sending the first information to a first communication device, the first information including a time parameter; wherein, the time parameter includes a second timing offset K_mac, and the second timing offset K_mac is used to determine the delay for the configuration information sent by the second communication device to take effect, and the second timing offset K_mac is used to determine the delay start duration of a Random Access Response (RAR) window.

14. The method according to claim 13, wherein, the delay start duration of the RAR window is determined according to the second timing offset K_mac and the timing advance value used by the first communication device.

15. The method according to claim 14, wherein, the delay start duration of the RAR window satisfies the following formula: RAR_window_delay = TA + K_mac * slot_duration, wherein, RAR_window_delay represents the delay start duration of the RAR window, TA represents the timing advance value used by the first communication device, and slot_duration represents a time unit.

16. The method according to claim 15, wherein, the time unit is 1 ms, and the delay start duration of the RAR window satisfies: RAR_window_delay = TA + K_mac.

17. The method according to any one of claims 14 to 16, wherein, the timing advance value used by the first communication device is determined according to a common timing advance value and the round-trip time delay between the satellite and the first communication device.

18. The method according to claim 17, wherein, the timing advance value used by the first communication device is the sum of a common timing advance value, the round-trip time delay between the satellite and the first communication device, an offset, and a correction value, wherein the correction value is indicated by the second communication device, and the offset is indicated by the second communication device or is specified by the communication protocol.

19. The method according to claim 17 or 18, wherein, the time parameter further includes the common timing advance value.

20. The method according to any one of claims 13 to 19, wherein, the first information is carried in at least one of the following: a broadcast message, a Radio Resource Control (RRC) message, a System Information Block.

21. The method according to any one of claims 13 to 20, wherein, the delay start duration of the RAR window is used to delay the opening of the RAR window; or, the delay start duration of the RAR window is used to delay the opening of a random access contention resolution timer.

22. The method according to any one of claims 13 to 21, wherein, the second timing offset K_mac is related to the round-trip time delay between the gateway station and the reference point.

23. The method according to any one of claims 13 to 22, wherein, the RAR window is used to receive a physical downlink control channel indicating at least one of the following: message 2 Msg2, message B MsgB, or a fallback RAR message.

24. The method according to any one of claims 13 to 23, wherein, the configuration information is media access control MAC signaling.

25. A communication device, wherein, it includes a unit or module for performing the method according to any one of claims 1 - 12.

26. A communication device, wherein, it includes a unit or module for performing the method according to any one of claims 13 - 24.

27. A communication device, wherein, it includes a processor, the processor is coupled to a memory storing a computer program, and the processor is configured to run the computer program such that the communication device performs the method according to any one of claims 1 - 12.

28. A communication device, wherein, it includes a processor, the processor is coupled to a memory storing a computer program, and the processor is configured to run the computer program such that the communication device performs the method according to any one of claims 13 - 24.

29. A computer - readable storage medium, wherein, the computer - readable storage medium stores computer - readable instructions, and when the computer - readable instructions are run on a computer, the method according to any one of claims 1 - 12 is performed; or, the method according to any one of claims 13 - 24 is performed.

30. A computer program product comprising instructions, wherein, when it runs on a computer, the method according to any one of claims 1 - 12 is performed; or, the method according to any one of claims 13 - 24 is performed.

Images