A method, device and non-transitory computer readable medium for wireless communication

By determining the uplink loss state in the user equipment and obtaining new ephemeris information, the problem of ephemeris information failure caused by satellite movement is solved, the reliability of communication is improved, and the continuity of uplink data transmission is ensured.

CN118018100BActive Publication Date: 2024-12-06ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410355536.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-07-29
Publication Date
2024-12-06
Estimated Expiration
2041-07-29

AI Technical Summary

Technical Problem

In satellite communication scenarios, due to satellite movement, the ephemeris information obtained by user equipment (UE) fails, and uplink synchronization cannot be guaranteed, affecting the reliability of communication.

Method used

By determining that the user equipment is in an upward out-of-step state, obtain the ephemeris information using the medium access control layer (MAC) or wireless resource control (RRC), start the timer to obtain the ephemeris information, and obtain it successfully Restore uplink synchronization to ensure uplink data transmission.

Benefits of technology

It effectively solves the problem of uplink loss caused by the failure of ephemeris information, improves the reliability of communication, ensures uplink synchronization between user equipment and service nodes, and ensures the continuity of data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118018100B_ABST
    Figure CN118018100B_ABST
Patent Text Reader

Abstract

The present application provides a method, device and non-transitory computer-readable medium for wireless communication. The method for wireless communication includes: receiving, by a radio resource control (RRC) layer of a user equipment operating in a satellite network, ephemeris information carried in system information broadcast by a base station, the ephemeris information at least including satellite position information; starting a timer by the RRC layer of the user equipment upon receiving the system information; reacquiring, by the RRC layer of the user equipment, the ephemeris information carried in the system information according to the timeout of the timer; and when the ephemeris information carried in the system information is successfully acquired, notifying the medium access control (MAC) layer of the user equipment of uplink synchronization.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the Chinese patent application with application number "202110865071.8", application date "July 29, 2021", and title "Ephemeris information acquisition method, indication method, communication node and storage medium". Technical Field

[0002] The present application relates to the technical field of wireless communication networks, and for example, to a method for acquiring ephemeris information, an indication method, a communication node, and a storage medium. Background Art

[0003] In the satellite communication scenario, the base station broadcasts ephemeris information through system information to facilitate the user equipment (UE) to obtain the position of the satellite. The UE can obtain its own position through the Global Navigation Satellite System (GNSS). After obtaining its own position and the position of the satellite, it can calculate the distance between itself and the satellite, and calculate the uplink synchronization information required for the UE and the service node to maintain uplink synchronization, that is, the ephemeris information, such as the time advance. If the UE and the service node maintain uplink synchronization, the UE can send uplink data and the service node can successfully decode it. Otherwise, the UE will lose uplink synchronization and need to stop uplink transmission, and the service node will not be able to decode successfully.

[0004] Due to the movement of the satellite, the ephemeris information obtained by the UE will become invalid, and the satellite position and the distance between the UE and the satellite calculated by the UE will also become invalid. If the UE cannot obtain valid ephemeris information and cannot ensure uplink synchronization, the uplink data cannot be transmitted, affecting the reliability of communication. Summary of the invention

[0005] The present application provides a method for obtaining ephemeris information, an indication method, a communication node and a storage medium, so as to ensure uplink synchronization and improve the reliability of communication by obtaining ephemeris information.

[0006] The present application provides a method for obtaining ephemeris information, including:

[0007] Determining that the user equipment UE is in an uplink out-of-sync state;

[0008] In case of uplink loss of synchronization, obtain ephemeris information.

[0009] The embodiment of the present application also provides an indication method, including:

[0010] Sending ephemeris acquisition indication information, where the indication information is used to instruct the user equipment UE to determine that the UE is in an uplink desynchronization state, and to acquire ephemeris information in the case of uplink desynchronization.

[0011] An embodiment of the present application also provides a communication node, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned ephemeris information acquisition method or indication method when executing the program.

[0012] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the above-mentioned ephemeris information acquisition method or indication method is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 A flowchart of a method for obtaining ephemeris information provided by an embodiment;

[0014] Figure 2 A schematic diagram of obtaining ephemeris information provided by an embodiment;

[0015] Figure 3 A schematic diagram of another embodiment for obtaining ephemeris information;

[0016] Figure 4 A schematic diagram of another method of obtaining ephemeris information provided by an embodiment;

[0017] Figure 5 A schematic diagram of another method of obtaining ephemeris information provided by an embodiment;

[0018] Figure 6 A schematic diagram of the structure of a device for acquiring ephemeris information provided by an embodiment;

[0019] Figure 7 A schematic diagram of the hardware structure of a communication node provided by an embodiment. DETAILED DESCRIPTION

[0020] The present application is described below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should be noted that, in the absence of conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily. It should also be noted that, for ease of description, only the parts related to the present application rather than all structures are shown in the accompanying drawings.

[0021] In an embodiment of the present application, a method for acquiring ephemeris information is provided, which can be applied to UE. Figure 1 A flowchart of a method for obtaining ephemeris information is provided in an embodiment. Figure 1 As shown, the method provided in this embodiment includes step 110 and step 120.

[0022] In step 110, it is determined that the user equipment UE is in an uplink out-of-synchronization state.

[0023] In step 120, in case of uplink out-of-sync, ephemeris information is acquired.

[0024] In this embodiment, when the UE determines that it is in an uplink desynchronization state due to the failure of the ephemeris information, it obtains new ephemeris information. By obtaining the ephemeris information, a basis is provided for calculating the distance between the UE and the satellite and achieving uplink synchronization between the UE and the service node, thereby ensuring the transmission of uplink data. Among them, the state of uplink desynchronization can be discovered through the UE's medium access control layer (MAC) or radio resource control (RRC); the ephemeris information can be obtained through MAC or RRC.

[0025] In one embodiment, the method further comprises:

[0026] Step 112: Clear the Hybrid Automatic Repeat request (HARQ) cache through MAC, stop the uplink synchronization timer, and release the uplink resources.

[0027] In this embodiment, in the case of uplink desynchronization, the ephemeris information becomes invalid, and the related operations of uplink synchronization can be stopped through MAC to save resources.

[0028] In one embodiment, step 120 includes: obtaining ephemeris information via MAC or RRC.

[0029] In one embodiment, the method further includes: Step 122: starting a timer via MAC or RRC.

[0030] In this embodiment, MAC or RRC may start a timer, and the UE obtains the ephemeris information during the timer running.

[0031] In one embodiment, the start condition of the timer includes one of the following:

[0032] Determine through MAC that the uplink is out of sync due to the failure of ephemeris information;

[0033] Determine through RRC that the uplink synchronization is lost due to the failure of ephemeris information;

[0034] MAC indicates that RRC has lost uplink synchronization due to invalid ephemeris information;

[0035] MAC instructs RRC to obtain ephemeris information;

[0036] RRC indicates to MAC that the uplink is out of sync due to the failure of ephemeris information;

[0037] RRC instructs MAC to obtain ephemeris information.

[0038] In one embodiment, the stop condition of the timer includes: successfully acquiring ephemeris information through MAC or RRC.

[0039] In one embodiment, the method further includes: Step 130: if the timer times out, the acquisition of the ephemeris information fails.

[0040] In one embodiment, step 120 includes: monitoring a physical downlink control channel (PDCCH) scrambled by a system information-radio network temporary identity (SI-RNTI) through MAC, and receiving a corresponding physical downlink shared channel (PDSCH), where the PDSCH carries ephemeris information.

[0041] In one embodiment, step 120 includes: monitoring a PDCCH scrambled by a cell-radio network temporary identity (C-RNTI) through a MAC, wherein the PDCCH scrambled by the C-RNTI carries first indication information, and the first indication information is used to indicate that the PDCCH schedules a PDSCH carrying ephemeris information.

[0042] In one embodiment, step 120 includes: receiving a PDSCH carrying ephemeris information on a specific time-frequency resource through MAC; wherein the specific time-frequency resource is determined based on at least one of a starting position of a time domain, a time domain period, a time domain duration, a starting position of a frequency domain, a bandwidth, and a modulation and coding scheme (MCS).

[0043] In this embodiment, the specific time-frequency resources for receiving the PDSCH and related parameters thereof may be configured or indicated by the network side.

[0044] In one embodiment, step 120 includes: receiving, via MAC, a PDSCH carrying ephemeris information at a configured interval; wherein the interval is determined according to at least one of an interval period, a starting position of the interval, and an interval duration.

[0045] In this embodiment, the interval for receiving the PDSCH and its related parameters may be configured or indicated by the network side.

[0046] In one embodiment, the method further includes: Step 140: determining a Physical Random Access Channel (PRACH) resource for random access according to the PDCCH scrambled by the C-RNTI.

[0047] In this embodiment, based on the PRACH resources, the UE may initiate a random access (Random Access, RACH).

[0048] In one embodiment, the method further comprises:

[0049] Step 150: When the ephemeris information is successfully acquired, second indication information is sent to MAC via RRC, where the second indication information is used to indicate successful acquisition of the ephemeris information or uplink synchronization, or to instruct MAC to send a random access request to the target cell.

[0050] In one embodiment, the method further comprises:

[0051] Step 160: When the acquisition of ephemeris information fails, the RRC enters an idle state, or the RRC is instructed by MAC to initiate an RRC reestablishment process.

[0052] In one embodiment, the method further comprises:

[0053] Step 170: When the ephemeris information is successfully obtained, a random access request is sent to the target cell via MAC.

[0054] In one embodiment, the method further comprises:

[0055] Step 180: In the case of failure in obtaining ephemeris information, third indication information is sent to RRC via MAC, where the third indication information is used to instruct RRC to enter an idle state or to instruct RRC to initiate an RRC reconstruction process.

[0056] In one embodiment, the method further comprises:

[0057] Step 190: When the ephemeris information acquisition fails, the ephemeris information is acquired again, and an RRC reestablishment request is sent to the serving cell with uplink synchronization loss.

[0058] In one embodiment, the method further includes: Step 142: randomly selecting a PRACH resource within a configured time window.

[0059] In one embodiment, the method further includes: Step 144: randomly generating a time window, and selecting a PRACH resource within the generated time window.

[0060] In one embodiment, the method further includes: Step 146: generating a time window according to the service type, and selecting a PRACH resource within the time window corresponding to the current service type.

[0061] In one embodiment, the method further includes: Step 148: generating a start time according to the service type, and selecting a PRACH resource according to the start time.

[0062] In one embodiment, the method further includes: Step 102: receiving configuration information, the configuration information including at least one of the following:

[0063] Indication information for enabling the UE to obtain ephemeris information in the connected state; timer timing duration; PRACH time and frequency resources; PRACH cycle; PRACH starting position; PRACH repetition number; PRACH frequency domain position;

[0064] PDCCH time-frequency resources; PDCCH period; PDCCH starting position; PDCCH repetition times; PDCCH frequency domain position;

[0065] The time and frequency resources of the measurement gap; the period of the measurement gap; the starting position of the measurement gap; the duration of the measurement gap;

[0066] Specific time-frequency resources; the time domain starting position of specific time-frequency resources; the period of specific time-frequency resources; the duration of specific time-frequency resources; the frequency domain starting position of specific time-frequency resources; the bandwidth of specific time-frequency resources; the modulation and coding level MCS corresponding to the specific time-frequency resources;

[0067] Time window length; minimum granularity of the time window; value range of the time window length; minimum granularity of the time window associated with the business type; value range of the time window length associated with the business type; minimum granularity of the start time.

[0068] In an embodiment of the present application, an indication method is also provided, which can be applied to the network side, such as a base station.

[0069] The indication method provided in this embodiment includes step 210: sending ephemeris acquisition indication information, where the indication information is used to instruct the user equipment UE to determine that the UE is in an uplink desynchronization state and to acquire ephemeris information in the case of uplink desynchronization.

[0070] In this embodiment, the network side instructs the UE to obtain new ephemeris information when it is determined that it is in an uplink out-of-sync state due to invalid ephemeris information, so as to provide a basis for calculating the distance between the UE and the satellite and achieving uplink synchronization between the UE and the service node, thereby ensuring the transmission of uplink data.

[0071] In one embodiment, the method further includes: step 220: sending configuration information, wherein the configuration information includes at least one of the following: indication information for enabling the UE to obtain ephemeris information in a connected state; a timer timing duration; a time-frequency resource of the PRACH; a period of the PRACH; a starting position of the PRACH; a number of repetitions of the PRACH; a frequency domain position of the PRACH;

[0072] PDCCH time-frequency resources; PDCCH period; PDCCH starting position; PDCCH repetition times; PDCCH frequency domain position;

[0073] The time and frequency resources of the measurement gap; the period of the measurement gap; the starting position of the measurement gap; the duration of the measurement gap;

[0074] Specific time-frequency resources; the time domain starting position of specific time-frequency resources; the period of specific time-frequency resources; the duration of specific time-frequency resources; the frequency domain starting position of specific time-frequency resources; the bandwidth of specific time-frequency resources; the modulation and coding level MCS corresponding to the specific time-frequency resources;

[0075] Time window length; minimum granularity of the time window; value range of the time window length; minimum granularity of the time window associated with the business type; value range of the time window length associated with the business type; minimum granularity of the start time.

[0076] The following is an example to illustrate the process of obtaining ephemeris information.

[0077] Example 1

[0078] This example describes the process of MAC detecting uplink desynchronization and obtaining ephemeris information through RRC.

[0079] In the satellite scenario, the base station broadcasts ephemeris information through system information to facilitate UE to obtain the position of the satellite. The UE can obtain its own position through GNSS. After the UE obtains its own position and the position of the satellite, it can calculate the distance between itself and the satellite, and based on this, calculate the ephemeris information required for the UE and the base station to maintain uplink synchronization, such as the time advance. If the UE and the base station maintain uplink synchronization, the UE can send uplink data and the base station can successfully decode it. Otherwise, the UE will lose uplink synchronization and need to stop uplink transmission, and the base station cannot successfully decode it.

[0080] If the ephemeris information obtained by the UE may become invalid due to the movement of the satellite, the satellite position calculated by the UE and the distance between the UE and the satellite will become invalid, and the ephemeris information calculated by the UE will also become invalid. If the UE wants to resume uplink data transmission, it needs to re-acquire the ephemeris information and recalculate the UE's ephemeris information. However, for the UE in the Internet of Things (IoT), it is not possible to send and receive data at the same time, nor can it receive system information and downlink proprietary data at the same time. A special time is required to receive ephemeris information. The solution is as follows:

[0081] When the ephemeris information of the UE is invalid, the ephemeris information needs to be acquired again. For example, after acquiring the ephemeris information each time, the UE starts a timer. If the timer times out, the corresponding ephemeris information is invalid. In this case, the UE acquires the ephemeris information again.

[0082] Figure 2 FIG. 1 is a schematic diagram of obtaining ephemeris information provided by an embodiment. Figure 2 As shown, the MAC of the UE finds that the uplink is out of sync, indicates it to the RRC, and the RRC obtains the ephemeris information. If the RRC obtains the ephemeris information successfully, it indicates the uplink synchronization to the MAC, and the MAC can initiate the RACH process; if the RRC fails to obtain the ephemeris information, the RRC performs the operation of returning to the idle (IDLE) state, or initiates the RRC reconstruction process.

[0083] The specific process is as follows:

[0084] The base station broadcasts the indication bit enabling the UE to read the ephemeris information in the connected state in the system information or configures it in the RRC message, that is, the indication information for enabling the UE to obtain the ephemeris information in the connected state. If the base station enables this function, the UE re-reads the ephemeris information after the ephemeris information becomes invalid.

[0085] Step 1: When MAC finds that the UE uplink is out of synchronization due to invalid ephemeris information, MAC will clear the HARQ buffer, stop all uplink synchronization-related timers, and release uplink resources, such as the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH).

[0086] step2a: MAC instructs RRC that the UE uplink is out of sync due to invalid ephemeris information, or MAC instructs RRC to obtain ephemeris information. After RRC receives the instruction from MAC, RRC starts the timer. While the timer is running, RRC obtains the ephemeris information. If RRC successfully obtains the ephemeris information while the timer is running, RRC stops the timer. RRC can indicate to MAC that the ephemeris information has been successfully obtained or indicate uplink synchronization, or instruct MAC to initiate RACH. If the timer times out, RRC performs the operation of returning to the IDLE state, or initiates the RRC reconstruction process.

[0087] step2b: MAC instructs RRC that the UE uplink is out of sync due to the invalidity of ephemeris information, or MAC instructs RRC to obtain ephemeris information, and MAC starts the timer. RRC receives the ephemeris information indicated by MAC that the UE uplink is out of sync, and RRC obtains the ephemeris information. If RRC successfully obtains the ephemeris information during the timer operation, RRC indicates to MAC that the ephemeris information is successfully obtained or indicates uplink synchronization, or instructs MAC to initiate RACH. If MAC receives an instruction from RRC while the timer is running, MAC will stop the timer. If the timer times out, MAC indicates uplink out of sync to RRC, etc. After receiving the instruction, RRC executes the operation to return to the IDLE state, or initiates the RRC reconstruction process.

[0088] Step 2c: MAC instructs RRC that the UE uplink is out of synchronization due to the failure of ephemeris information, or MAC instructs RRC to obtain ephemeris information. After RRC receives the MAC instruction, RRC obtains the ephemeris information. If RRC successfully obtains the ephemeris information, RRC indicates to MAC that the ephemeris information or uplink synchronization has been successfully obtained, or instructs MAC to initiate RACH.

[0089] Step 3: If RRC indicates that the ephemeris information is successfully obtained, or RRC instructs MAC to initiate RACH, and the UE maintains uplink synchronization, MAC will initiate the RACH process based on the configured PRACH resources.

[0090] Among them, step 2a, step 2b and step 2c are executed one by one. The base station can broadcast the timing duration of the timer in the system information or configure it in the RRC message. The base station will broadcast the time and frequency resources of PRACH in the system information or configure it in the RRC message, including: the period, starting position, number of repetitions, frequency domain position, etc. of PRACH. The PRACH is used to send to the base station after the UE successfully reads the ephemeris information.

[0091] Example 2

[0092] This example describes the process of MAC detecting uplink desynchronization and obtaining ephemeris information.

[0093] When the ephemeris information of the UE is invalid, the ephemeris information needs to be acquired again. For example, after acquiring the ephemeris information each time, the UE starts a timer. If the timer times out, the corresponding ephemeris information is invalid. In this case, the UE acquires the ephemeris information again.

[0094] Figure 3 Another schematic diagram of obtaining ephemeris information provided by an embodiment is as follows: Figure 3 As shown in the figure, MAC finds that the uplink is out of sync, and MAC obtains the ephemeris information. If the ephemeris information is obtained successfully, MAC initiates the RACH process. If the ephemeris information is obtained unsuccessfully, MAC instructs RRC to perform the operation of returning to the IDLE state, or initiates the RRC reconstruction process.

[0095] The specific process is as follows:

[0096] The base station broadcasts the indication bit enabling the UE to read the ephemeris information in the connected state in the system information or configures it in the RRC message, that is, the indication information for enabling the UE to obtain the ephemeris information in the connected state. If the base station enables this function, the UE re-reads the ephemeris information after the ephemeris information becomes invalid.

[0097] Step 1: When MAC finds that the UE is out of uplink synchronization due to invalid ephemeris information, MAC will clear the HARQ Buffer, stop all uplink synchronization-related timers, and release uplink resources, including PUCCH, PUSCH, etc.

[0098] Step 2a: UE obtains ephemeris information. When the UE loses uplink synchronization due to the failure of ephemeris information, the UE's MAC starts a timer. While the timer is running, the MAC monitors the PDCCH encrypted by SI-RNTI and receives the corresponding PDSCH, which carries the ephemeris information. During the timer, if the MAC successfully monitors the PDCCH related to SI-RNTI, it stops the timer. If the timer times out, the MAC indicates that the RRC failed to obtain the ephemeris information.

[0099] Step 2b: UE obtains ephemeris information. When the UE loses uplink synchronization due to invalid ephemeris information, the UE's MAC starts a timer. While the timer is running, the MAC monitors the PDCCH encrypted by C-RNTI. During the timer, if the MAC successfully monitors the PDCCH encrypted by C-RNTI and the PDCCH carries an indication bit, indicating that the PDCCH schedules the PDSCH carrying ephemeris information, the timer is stopped. If the timer times out, the MAC indicates that the RRC failed to obtain the ephemeris information.

[0100] Step 2c: UE obtains ephemeris information. When the UE loses uplink synchronization due to invalid ephemeris information, MAC starts a timer. While the timer is running, MAC receives PDSCH on a specific time-frequency resource, and the PDSCH carries ephemeris information. While the timer is running, if the UE successfully receives PDSCH on a specific time-frequency resource, the UE will stop the timer. MAC indicates that RRC has successfully obtained ephemeris information. If the timer times out, MAC indicates that RRC has failed to obtain ephemeris information.

[0101] step2d: UE obtains ephemeris information. When the UE loses uplink synchronization due to invalid ephemeris information, MAC starts the timer. While the timer is running, MAC receives PDSCH in the interval (Gap) configured by the base station, and the PDSCH carries the ephemeris information. In the Gap, the UE will not monitor PDCCH in the uplink search space (USS), but only detect PDSCH. While the timer is running, if MAC successfully receives PDSCH in the Gap, MAC will stop the timer. MAC indicates that RRC has successfully obtained ephemeris information. If the timer times out, MAC indicates that RRC has failed to obtain ephemeris information.

[0102] Step 2e: The UE also receives the PRACH resources configured by the base station. The UE monitors the C-RNTI scrambled PDCCH, and the PDCCH carries a dedicated PRACH resource, which is used by the UE to initiate the RACH process after acquiring synchronization.

[0103] Step 3: If MAC indicates that the ephemeris information is successfully obtained and the UE maintains uplink synchronization, MAC will initiate the RACH process based on the configured PRACH resources.

[0104] Among them, step 2a, step 2b, step 2c and step 2d are executed one by one. The base station broadcasts the timer duration in the system information or configures it in the RRC message. The base station broadcasts the PRACH time and frequency resources in the system information or configures it in the RRC message, including: the period, starting position, number of repetitions and / or frequency domain position of the PRACH, etc. The PRACH is used by the UE to send the ephemeris information to the base station after successfully reading it.

[0105] The base station will broadcast the time and frequency resources of PDCCH in the system information or configure it in the RRC message, including: the period, starting position, number of repetitions and / or frequency domain position of PDCCH, etc. The PDCCH is used for monitoring when the UE reads the ephemeris information. PDCCH includes machine type communication physical downlink control channel (Machine Type Communication Physical Downlink Control Channel, MPDCCH), narrowband physical downlink control channel (Narrowband Physical Downlink Control Channel, NPDCCH) and / or PDCCH, etc.

[0106] The base station will broadcast the time and frequency resources of the GAP in the system information or configure them in the RRC message, including: the period, starting position and / or duration of the Gap.

[0107] The base station will broadcast in the system information or configure specific time-frequency resources in the RRC message or PDCCH, including the starting position in the time domain, the time domain period, the time domain duration, the starting position in the frequency domain, the bandwidth and / or MCS, etc.

[0108] Example 3

[0109] This example describes the process of RRC detecting uplink out-of-sync and obtaining ephemeris information.

[0110] When the ephemeris information of the UE is invalid, the ephemeris information needs to be acquired again. For example, after acquiring the ephemeris information each time, the UE starts a timer. If the timer times out, the corresponding ephemeris information is invalid. In this case, the UE acquires the ephemeris information again.

[0111] Figure 4 FIG. 1 is another schematic diagram of obtaining ephemeris information provided by an embodiment. Figure 4 As shown, RRC finds that the ephemeris information is invalid, and RRC obtains the ephemeris information. If the acquisition is successful, RRC instructs MAC, and MAC initiates the RACH process. If the acquisition fails, RRC performs the operation of returning to the IDLE state, or initiates the RRC reconstruction process.

[0112] The specific process is as follows:

[0113] The base station will broadcast in the system information or configure in the RRC message an indication bit that enables the UE to read the ephemeris information in the connected state, that is, indication information for enabling the UE to obtain the ephemeris information in the connected state. If the base station enables this function, the UE will re-read the ephemeris information after the ephemeris information becomes invalid.

[0114] Step 1: When RRC finds that the UE uplink is out of synchronization due to the failure of ephemeris information, RRC obtains the ephemeris information.

[0115] Step 2: When RRC obtains the ephemeris information, RRC starts the timer. During the timer, RRC obtains the ephemeris information. If RRC successfully obtains the ephemeris information during the timer, RRC stops the timer. RRC can indicate the successful acquisition of ephemeris information to MAC or indicate uplink synchronization. If the timer times out, RRC performs the operation of returning to the IDLE state or initiates the RRC reconstruction process.

[0116] Step 3: If MAC indicates that the ephemeris information is successfully obtained and the UE maintains uplink synchronization, MAC will initiate the RACH process based on the configured PRACH resources.

[0117] The base station will broadcast the timer duration in the system information or configure it in the RRC message. The base station will broadcast the PRACH time and frequency resources in the system information or configure it in the RRC message, including: the period, starting position, number of repetitions and / or frequency domain position of the PRACH, which is used by the UE to send to the base station after successfully reading the ephemeris information.

[0118] The base station will broadcast the time-frequency resources of the Gap in the system information or configure them in the RRC message, including: the period, starting position and / or duration of the Gap.

[0119] Example 4

[0120] This example describes the process of RRC detecting uplink desynchronization and obtaining ephemeris information through MAC.

[0121] When the ephemeris information of the UE is invalid, the ephemeris information needs to be acquired again. For example, after acquiring the ephemeris information each time, the UE starts a timer. If the timer times out, the corresponding ephemeris information is invalid. In this case, the UE acquires the ephemeris information again.

[0122] Figure 5 FIG. 1 is a schematic diagram of another method of obtaining ephemeris information provided by an embodiment. Figure 5 As shown, RRC finds that the ephemeris information is invalid and instructs MAC to obtain the ephemeris information. If the acquisition is successful, MAC initiates the RACH process to indicate that RRC has successfully obtained the ephemeris information. If the acquisition of ephemeris information fails, MAC indicates that RRC has failed to obtain the information, and RRC performs the operation of returning to the IDLE state or initiates the RRC reconstruction process.

[0123] The specific process is as follows:

[0124] The base station will broadcast in the system information or configure in the RRC message an indication bit that enables the UE to read the ephemeris information in the connected state, that is, indication information for enabling the UE to obtain the ephemeris information in the connected state. If the base station enables this function, the UE will re-read the ephemeris information after the ephemeris information becomes invalid.

[0125] Step 1: When RRC finds that the UE uplink is out of synchronization due to the failure of ephemeris information, RRC obtains the ephemeris information.

[0126] step2a: When RRC obtains ephemeris information, RRC starts the timer and instructs MAC to obtain ephemeris information, or the ephemeris information fails, causing the UE to lose uplink synchronization. When MAC receives the instruction, MAC will clear the HARQ Buffer, stop all uplink synchronization-related timers, and release uplink resources, including PUCCH and PUSCH. MAC starts to monitor the SI-RNTI-wrapped PDCCH and receives the corresponding PDSCH, which carries the ephemeris information. If MAC successfully monitors the SI-RNTI-wrapped PDCCH, MAC indicates that RRC has successfully obtained the ephemeris information. During the timer operation, if RRC receives that MAC has successfully obtained the ephemeris information, RRC will stop the timer. If the timer times out, RRC executes the operation of returning to the IDLE state, or initiates the RRC reconstruction process.

[0127] step2b: When RRC obtains ephemeris information, RRC starts the timer. And instructs MAC to obtain ephemeris information, or the ephemeris information fails, causing the UE to lose uplink synchronization. When MAC receives the indication, MAC will clear the HARQ Buffer, stop all uplink synchronization-related timers, and release uplink resources, including PUCCH and PUSCH. MAC starts to monitor the PDCCH with C-RNTI. If MAC successfully monitors the PDCCH with C-RNTI, and the PDCCH carries an indication bit, indicating that the PDCCH schedules the PDSCH carrying ephemeris information, MAC instructs RRC to successfully obtain the ephemeris information. During the timer operation, if RRC receives the information that MAC has successfully obtained the ephemeris information, RRC will stop the timer. If the timer times out, RRC executes the operation of returning to the IDLE state, or initiates the RRC reconstruction process.

[0128] step2c: When RRC obtains ephemeris information, RRC starts the timer. And instructs MAC to obtain ephemeris information, or the ephemeris information fails, causing the UE to lose uplink synchronization. When MAC receives the instruction, MAC will clear the HARQ Buffer, stop all uplink synchronization-related timers, and release uplink resources, including PUCCH and PUSCH. MAC starts to receive PDSCH on specific time-frequency resources, and the PDSCH carries ephemeris information. If the UE successfully receives PDSCH on specific time-frequency resources, MAC indicates that RRC has successfully obtained ephemeris information. During the timer operation, if RRC receives that MAC has successfully obtained ephemeris information, RRC will stop the timer. If the timer times out, RRC executes the operation of returning to the IDLE state, or initiates the RRC reconstruction process.

[0129] step2d: When RRC obtains ephemeris information, RRC starts the timer. And instructs MAC to obtain ephemeris information, or the ephemeris information fails, causing the UE to lose uplink synchronization. When MAC receives the indication, MAC will clear the HARQ Buffer, stop all uplink synchronization-related timers, and release uplink resources, including PUCCH and PUSCH. MAC receives PDSCH on the Gap configured by the base station, and the PDSCH carries ephemeris information. Within the Gap, the UE will not listen to PDCCH on the USS, but only detect PDSCH. During the timer operation, if RRC receives an indication from MAC that it has successfully obtained the ephemeris information, RRC will stop the timer. If the timer times out, RRC executes the operation of returning to the IDLE state, or initiates the RRC reconstruction process.

[0130] Step 2e: The UE also receives the PRACH resources configured by the base station. The UE monitors the C-RNTI-wrapped PDCCH, which carries the dedicated PRACH resources for the UE to initiate the RACH process after acquiring synchronization.

[0131] Step 3: If MAC indicates that the ephemeris information is successfully obtained and the UE maintains uplink synchronization, MAC will initiate the RACH process based on the configured PRACH resources.

[0132] Among them, step 2a, step 2b, step 2c and step 2d are executed one by one. The base station broadcasts the timer duration in the system information or configures it in the RRC message. The base station broadcasts the PRACH time and frequency resources in the system information or configures it in the RRC message, including: the period, starting position, number of repetitions and / or frequency domain position of the PRACH, etc. The PRACH is used by the UE to send the ephemeris information to the base station after successfully reading it.

[0133] The base station will broadcast in the system information or configure specific time-frequency resources in the RRC message or PDCCH, including the starting position in the time domain, the time domain period, the time domain duration, the starting position in the frequency domain, the bandwidth and / or MCS, etc.

[0134] Example 5

[0135] This example describes the process of triggering RRC reestablishment due to ephemeris information failure.

[0136] During the RRC reestablishment process, the UE will perform cell selection, select the target cell, read the system information of the target cell, and send an RRC reestablishment request message. However, if the signal quality of the original cell has not deteriorated due to the failure to obtain the ephemeris information, the UE can still select the original cell. In addition, the UE needs to re-acquire the ephemeris information instead of other system information. In this example, the RRC reestablishment process is simplified.

[0137] Due to the failure to obtain ephemeris information, the RRC reestablishment process is triggered, and the UE selects the original cell (i.e., the cell with uplink synchronization loss). If the system information of the original cell is valid, the system information includes, for example, the master system information block (MIB), the system information block (Systym Information Block) such as SIB1 and SIB2, etc., but does not include the system information carrying ephemeris information), in this case, the UE does not receive the paging message caused by the system information update, and the UE will apply the saved information and will not re-acquire it.

[0138] The RRC reestablishment process is triggered by the failure to obtain the ephemeris information. The UE re-acquires the ephemeris information. If the ephemeris information is successfully obtained within a certain period of time, the UE sends an RRC reestablishment request message. Otherwise, the UE will enter the idle state.

[0139] Example 6

[0140] This example describes the process of resolving preamble conflicts.

[0141] When a UE needs to initiate uplink data, for example, a UE in ILDE state is called, a UE in ILDE state makes a call, a UE in inactive state (INACTIVE) wants to restore the connection, or a UE in connected state wants to restore the link, etc., in this case, it is necessary to calculate the position of the satellite based on the ephemeris information, and then estimate the time information between the UE and the satellite, such as the uplink advance, and finally initiate the RACH process. Ephemeris information is sent periodically through system information. If multiple UEs want to initiate RACH in the interval between two ephemeris information transmissions, these UEs will read the ephemeris information at the next ephemeris information transmission time, and send PRACH at the next closest PRACH time. Then these UEs may have Preamble conflicts and PRACH congestion.

[0142] Here's how to resolve the conflict:

[0143] The base station enables the UE to avoid PRACH congestion through system information or RRC message configuration, and instructs the UE through the fourth indication information. When enabled, the method for resolving the conflict is as follows:

[0144] Method 1: The UE randomly selects PRACH resources within the time window. The base station configures the length of a time window through system information or RRC message, and the time window is long enough to include multiple PRACH transmission resources, including frequency domain, time domain and Preamble. After the UE reads the ephemeris information, it selects the starting time of the time window as the time of the first available PRACH resource according to the time window configured by the base station. The window length of the time window is configured by the base station. The UE determines the available PRACH transmission resources within the time window, the UE randomly selects one of these PRACH transmission resources, and then sends the PRACH. Or the UE determines the possible PRACH transmission resources within the time window, the UE first randomly selects a time in the time domain, then randomly selects a frequency domain resource in the frequency domain, and finally randomly selects a preamble.

[0145] Method 2: The UE randomly generates a time window and selects a PRACH resource within the time window. The base station configures the minimum granularity of a time window and the range of values ​​of the window length of the time window, such as the maximum window length and the minimum window length, through system information or RRC messages. When the UE generates a random number for the window length of the time window within the range of values ​​of the window length according to the minimum granularity of the time window configured by the base station, the window length of the time window is the product of the minimum granularity and the random number of the window length. After the UE reads the ephemeris information, it selects the starting time of the time window as the time at which the first available PRACH resource is located. The window length of the time window is generated by the above UE. The UE determines the PRACH transmission resources available within the time window, the UE randomly selects one of these PRACH transmission resources, and then sends the PRACH. Or the UE determines the possible PRACH transmission resources within the time window, the UE first randomly selects a time in the time domain, then randomly selects a frequency domain resource in the frequency domain, and finally randomly selects a preamble.

[0146] Method 3: The UE generates time windows of different lengths according to the service type, and then selects PRACH resources within the time window. The base station configures the parameters of multiple time windows through system information or RRC messages, including the minimum granularity and the value range of the window length. Each parameter is associated with one or more service types. For example, the value range of time window 1 corresponds to the main call, the value range of time window 2 corresponds to the called party, and the value range of time window 3 corresponds to the connection state recovery link. After the UE reads the ephemeris information, it selects the corresponding time window parameter according to its own service type, and generates a random number for the time window length within the value range of the window length. The window length of the time window is the product of the minimum granularity and the random number of the window length. After the UE reads the ephemeris information, it selects the starting time of the time window as the time of the first available PRACH resource. The window length of the time window is generated by the above UE. The UE determines the PRACH transmission resources available in the time window, and the UE randomly selects one of these PRACH transmission resources, and then sends the PRACH. Or the UE determines the possible PRACH transmission resources within the time window. The UE first randomly selects a time in the time domain, then randomly selects a frequency domain resource in the frequency domain, and finally randomly selects a preamble.

[0147] Method 4: The UE generates a time start time according to the service type and selects PRACH resources. The base station configures a minimum granularity of the time start time through system information or RRC message. The UE calculates the time start time according to the service type. For example, the time start time of the connection state recovery link is 0*minimum granularity, the time start time of the called party is 1*minimum granularity, and the time start time of the main call is 2*minimum granularity. After the UE reads the ephemeris information, it selects the PRACH sending resource after the start time according to the generated time start time, and then sends the PRACH.

[0148] The embodiment of the present application also provides a device for acquiring ephemeris information. Figure 6 FIG. 1 is a schematic diagram of a structure of an apparatus for acquiring ephemeris information provided by an embodiment. Figure 6 As shown, the ephemeris information acquisition device includes:

[0149] The out-of-synchronization determination module 310 is configured to determine whether the user equipment UE is in an uplink out-of-synchronization state;

[0150] The information acquisition module 320 is configured to acquire ephemeris information in case of uplink loss of synchronization.

[0151] The ephemeris information acquisition device of this embodiment acquires new ephemeris information when it is determined that the uplink is out of sync due to the failure of the ephemeris information. By acquiring the ephemeris information, a basis is provided for calculating the distance between the UE and the satellite and achieving uplink synchronization between the UE and the service node, thereby ensuring the transmission of uplink data.

[0152] In one embodiment, the device further comprises:

[0153] The front-end operation module is configured to clear the HARQ buffer through the MAC, stop the uplink synchronization timer, and release the uplink resources.

[0154] In one embodiment, the information acquisition module 320 is configured to: acquire ephemeris information via MAC or RRC.

[0155] In one embodiment, the device further includes: starting a timer via MAC or RRC.

[0156] In one embodiment, the start condition of the timer includes one of the following:

[0157] Determine through MAC that the uplink is out of sync due to the failure of ephemeris information;

[0158] Determine through RRC that the uplink synchronization is lost due to the failure of ephemeris information;

[0159] MAC indicates that RRC has lost uplink synchronization due to invalid ephemeris information;

[0160] MAC instructs RRC to obtain ephemeris information;

[0161] RRC indicates to MAC that the uplink is out of sync due to the failure of ephemeris information;

[0162] RRC instructs MAC to obtain ephemeris information.

[0163] In one embodiment, the stop condition of the timer includes: successfully acquiring ephemeris information through MAC or RRC.

[0164] In one embodiment, the device further comprises: a failure module, configured to fail to obtain the ephemeris information if the timer times out.

[0165] In one embodiment, the information acquisition module 320 is configured to: monitor the PDCCH scrambled by SI-RNTI through MAC, and receive the corresponding PDSCH, where the PDSCH carries the ephemeris information.

[0166] In one embodiment, the information acquisition module 320 is configured to: monitor the C-RNTI-scrambled PDCCH through MAC, where the C-RNTI-scrambled PDCCH carries first indication information, and the first indication information is used to indicate that the PDCCH schedules the PDSCH carrying ephemeris information.

[0167] In one embodiment, the information acquisition module 320 is configured to: receive a PDSCH carrying ephemeris information on a specific time-frequency resource through a MAC; wherein the specific time-frequency resource is determined based on at least one of a starting position of a time domain, a time domain period, a time domain duration, a starting position of a frequency domain, a bandwidth, and an MCS.

[0168] In one embodiment, the information acquisition module 320 is configured to: receive a PDSCH carrying ephemeris information at a configured interval through MAC; wherein the interval is determined according to at least one of an interval period, a starting position of the interval, and an interval duration.

[0169] In one embodiment, the device further includes: a resource determination module, configured to determine a PRACH resource for random access according to the PDCCH scrambled by the C-RNTI.

[0170] In one embodiment, the device further comprises:

[0171] The first indication module is configured to send second indication information to MAC through RRC when the ephemeris information is successfully acquired, wherein the second indication information is used to indicate successful acquisition of the ephemeris information or uplink synchronization, or to instruct the MAC to send a random access request to the target cell.

[0172] In one embodiment, the device further comprises:

[0173] The second indication module is configured to, when the ephemeris information acquisition fails, cause the RRC to enter an idle state, or to instruct the RRC to initiate an RRC reconstruction process through MAC.

[0174] In one embodiment, the device further comprises:

[0175] The access request module is configured to send a random access request to the target cell through MAC when the ephemeris information is successfully acquired.

[0176] In one embodiment, the device further comprises:

[0177] The third indication module is configured to send third indication information to the RRC through the MAC when the acquisition of the ephemeris information fails, wherein the third indication information is used to instruct the RRC to enter an idle state or to instruct the RRC to initiate an RRC reconstruction process.

[0178] In one embodiment, the device further comprises:

[0179] The reacquisition module is configured to reacquire the ephemeris information when the ephemeris information acquisition fails, and send an RRC reestablishment request to the serving cell with uplink synchronization loss.

[0180] In one embodiment, the apparatus further includes: a resource selection module configured to randomly select a PRACH resource within a configured time window.

[0181] In one embodiment, the device further includes: a resource selection module, configured to: randomly generate a time window, and select a PRACH resource within the generated time window.

[0182] In one embodiment, the device further includes: a resource selection module, configured to: generate a time window according to a service type, and select a PRACH resource within the time window corresponding to the current service type.

[0183] In one embodiment, the device further includes: a resource selection module, configured to: generate a start time according to a service type, and select a PRACH resource according to the start time.

[0184] In one embodiment, the device further includes: a configuration receiving module, configured to receive configuration information, wherein the configuration information includes at least one of the following:

[0185] Indication information for enabling the UE to obtain ephemeris information in the connected state; timer timing duration; PRACH time and frequency resources; PRACH cycle; PRACH starting position; PRACH repetition number; PRACH frequency domain position;

[0186] PDCCH time-frequency resources; PDCCH period; PDCCH starting position; PDCCH repetition times; PDCCH frequency domain position;

[0187] The time and frequency resources of the measurement gap; the period of the measurement gap; the starting position of the measurement gap; the duration of the measurement gap;

[0188] Specific time-frequency resources; the time domain starting position of specific time-frequency resources; the period of specific time-frequency resources; the duration of specific time-frequency resources; the frequency domain starting position of specific time-frequency resources; the bandwidth of specific time-frequency resources; the modulation and coding level MCS corresponding to the specific time-frequency resources;

[0189] Time window length; minimum granularity of the time window; value range of the time window length; minimum granularity of the time window associated with the business type; value range of the time window length associated with the business type; minimum granularity of the start time.

[0190] The ephemeris information acquisition device proposed in this embodiment and the ephemeris information acquisition method proposed in the above embodiment belong to the same inventive concept. The technical details not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as executing the ephemeris information acquisition method.

[0191] The present application also provides an indication device. The device includes:

[0192] The indication module is configured to send ephemeris acquisition indication information, wherein the indication information is used to instruct the user equipment UE to determine that the UE is in an uplink desynchronization state and to acquire ephemeris information in the case of uplink desynchronization.

[0193] The ephemeris information acquisition device of this embodiment instructs the UE to acquire new ephemeris information when it is determined that the UE is in an uplink out-of-sync state due to the failure of the ephemeris information, thereby providing a basis for calculating the distance between the UE and the satellite and achieving uplink synchronization between the UE and the service node, thereby ensuring the transmission of uplink data.

[0194] In one embodiment, the device further comprises:

[0195] The configuration module is configured to send configuration information, wherein the configuration information includes at least one of the following:

[0196] Indication information for enabling the UE to obtain ephemeris information in the connected state; timer timing duration; PRACH time and frequency resources; PRACH cycle; PRACH starting position; PRACH repetition number; PRACH frequency domain position;

[0197] PDCCH time-frequency resources; PDCCH period; PDCCH starting position; PDCCH repetition times; PDCCH frequency domain position;

[0198] The time and frequency resources of the measurement gap; the period of the measurement gap; the starting position of the measurement gap; the duration of the measurement gap;

[0199] Specific time-frequency resources; the time domain starting position of specific time-frequency resources; the period of specific time-frequency resources; the duration of specific time-frequency resources; the frequency domain starting position of specific time-frequency resources; the bandwidth of specific time-frequency resources; the modulation and coding level MCS corresponding to the specific time-frequency resources;

[0200] Time window length; minimum granularity of the time window; value range of the time window length; minimum granularity of the time window associated with the business type; value range of the time window length associated with the business type; minimum granularity of the start time.

[0201] The ephemeris information acquisition device proposed in this embodiment and the ephemeris information acquisition method proposed in the above embodiment belong to the same inventive concept. The technical details not described in detail in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as executing the ephemeris information acquisition method.

[0202] An embodiment of the present application also provides a communication node, which may be a UE or a network side node. Figure 7 A hardware structure diagram of a communication node provided by an embodiment is shown in FIG. Figure 7 As shown, the communication node provided in the present application includes a memory 52, a processor 51, and a computer program stored in the memory and executable on the processor. When the processor 51 executes the program, the above-mentioned ephemeris information acquisition method or indication method is implemented.

[0203] The communication node may further include a memory 52; the processor 51 in the communication node may be one or more, Figure 7 A processor 51 is taken as an example; the memory 52 is used to store one or more programs; the one or more programs are executed by the one or more processors 51, so that the one or more processors 51 implement the ephemeris information acquisition method or indication method as described in the embodiments of the present application.

[0204] The communication node further comprises: a communication device 53 , an input device 54 and an output device 55 .

[0205] The processor 51, memory 52, communication device 53, input device 54 and output device 55 in the communication node may be connected via a bus or other means. Figure 7 The example of connecting through bus is taken in the following.

[0206] The input device 54 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the communication node. The output device 55 may include a display device such as a display screen.

[0207] The communication device 53 may include a receiver and a transmitter. The communication device 53 is configured to perform information transmission and reception communication according to the control of the processor 51.

[0208] The memory 52, as a computer-readable storage medium, can be configured to store software programs, computer executable programs and modules, such as the program instructions / modules corresponding to the ephemeris information acquisition method described in the embodiment of the present application (for example, the out-of-sync determination module 310 and the information acquisition module 320 in the ephemeris information acquisition device). The memory 52 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the communication node, etc. In addition, the memory 52 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 52 may further include a memory remotely arranged relative to the processor 51, and these remote memories may be connected to the communication node via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0209] The embodiment of the present application also provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the ephemeris information acquisition method or indication method described in any of the embodiments of the present application is implemented. The ephemeris information acquisition method includes: determining that the user equipment UE is in an uplink out-of-sync state; in the case of uplink out-of-sync, obtaining ephemeris information. The indication method includes: sending ephemeris acquisition indication information, wherein the indication information is used to instruct the user equipment UE to determine that the UE is in an uplink out-of-sync state, and obtain ephemeris information in the case of uplink out-of-sync.

[0210] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (Random Access Memory, RAM), a read-only memory (Read Only Memory, ROM), an erasable programmable read-only memory (ErasableProgrammable Read Only Memory, EPROM), a flash memory, an optical fiber, a portable CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination of the above. The computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, a device or a device or used in combination with it.

[0211] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to: electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0212] The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the above.

[0213] The computer program code for performing the operation of the present application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and also conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on the remote computer, or completely on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).

[0214] The above description is merely an exemplary embodiment of the present application and is not intended to limit the protection scope of the present application.

[0215] It will be appreciated by those skilled in the art that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.

[0216] In general, various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software that can be executed by a controller, microprocessor or other computing device, although the present application is not limited thereto.

[0217] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0218] The block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions. A computer program may be stored in a memory. The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to read-only memory (ROM), random access memory (RAM), optical memory devices and systems (digital versatile discs (DVD) or compact disks (CD), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FGPAs) and processors based on multi-core processor architectures.

[0219] By way of exemplary and non-limiting examples, a detailed description of exemplary embodiments of the present application has been provided above. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, but will not depart from the scope of the present application. Therefore, the proper scope of the present application will be determined according to the claims.

Claims

1. A method for wireless communication, comprising: Receiving, by a radio resource control RRC layer of a user equipment operating in a satellite network, ephemeris information carried in system information broadcast by a base station, the ephemeris information including at least satellite position information; The RRC layer of the user equipment starts a timer upon receiving the system information; The RRC layer of the user equipment reacquires the ephemeris information carried in the system information according to expiration of the timer; as well as When the ephemeris information carried in the system information is successfully acquired, the RRC layer notifies the medium access control MAC layer of the user equipment to implement uplink synchronization.

2. The method according to claim 1, comprising: The RRC layer of the user equipment determines uplink desynchronization based on expiration of the timer.

3. The method according to claim 2, comprising: In response to the uplink desynchronization, the MAC layer of the user equipment clears a HARQ buffer.

4. The method according to claim 3, further comprising at least one of the following: The MAC layer of the user equipment stops all timers related to the uplink synchronization; The MAC layer of the user equipment releases uplink resources on an uplink channel, where the uplink channel includes a physical uplink control channel or a physical uplink shared channel.

5. The method according to claim 1, comprising: An uplink transmission process is enabled when the MAC layer is notified of the uplink synchronization implementation.

6. A device implemented as a user equipment, the user equipment being configured to operate in a satellite network for wireless communication, the device implemented as the user equipment comprising a memory and one or more processors, the memory storing a computer program executable on the processor, the processor being configured to: Receiving ephemeris information carried in system information broadcast by a base station, the ephemeris information at least including satellite position information; Starting a timer upon receiving the system information; Reacquiring the ephemeris information carried in the system information according to the timeout of the timer; as well as When the ephemeris information carried in the system information is successfully acquired, the medium access control MAC layer uplink synchronization of the user equipment is notified.

7. The device according to claim 6, wherein: The one or more processors are configured to: An uplink out-of-sync is determined based on expiration of the timer.

8. The device according to claim 7, wherein: The one or more processors are configured to: In response to the uplink desynchronization, a HARQ buffer is cleared.

9. The device according to claim 8, wherein: The one or more processors are configured to: Stop all timers related to the uplink synchronization; and / or Uplink resources on an uplink channel are released, where the uplink channel includes a physical uplink control channel or a physical uplink shared channel.

10. The device according to claim 6, wherein: The one or more processors are configured to: An uplink transmission process is enabled when the MAC layer is notified of the uplink synchronization implementation.

11. A non-transitory computer-readable medium carrying instructions, wherein when the instructions are executed by at least one processor, the following operations are implemented, including: Receiving ephemeris information carried in system information broadcast by a base station, the ephemeris information at least including satellite position information; Starting a timer upon receiving the system information; Reacquiring the ephemeris information carried in the system information according to the timeout of the timer; as well as When the ephemeris information carried in the system information is successfully acquired, the medium access control MAC layer uplink synchronization of the user equipment is notified.

12. The non-transitory computer readable medium of claim 11, wherein: The operations also include: An uplink out-of-sync is determined based on expiration of the timer.

13. The non-transitory computer readable medium of claim 12, wherein: The operations also include: In response to the uplink desynchronization, a HARQ buffer is cleared.

14. The non-transitory computer readable medium of claim 13, wherein: The operations also include at least one of the following: Stop all timers related to the uplink synchronization; Uplink resources on an uplink channel are released, where the uplink channel includes a physical uplink control channel or a physical uplink shared channel.

15. The non-transitory computer readable medium of claim 11, wherein: The operations also include: An uplink transmission process is enabled when the MAC layer is notified of the uplink synchronization implementation.