Method and apparatus for uplink synchronization, electronic device, chip and storage medium

Abstract

The present disclosure provides a method and device for uplink synchronization, electronic equipment, chip and storage medium, which relates to the technical field of communication protocol. The method comprises: starting a timer when receiving configuration information of a configured grant (CG) sent by a network device; and sending preset content to the network device on a physical uplink shared channel (PUSCH) of the CG when the timer reaches a timing value and there is no uplink content to be sent to the network device in the terminal. Thus, the problem of uplink out-of-sync caused by the terminal not sending uplink data for a long time under the CG configuration and the terminal being unable to measure the uplink timing can be avoided, thereby ensuring the accuracy and synchronization of data transmission between the terminal and the network device and improving the communication quality.

Description

Technical Field

[0001] This disclosure relates to the technical field of communication protocols, and in particular to an uplink synchronization method, apparatus, electronic device, chip, and storage medium. Background Technology

[0002] In wireless communication systems such as 5G New Radio (5G NR), in order to maintain the orthogonality of uplink transmission, reduce multiple access interference and multipath interference, and improve system performance and capacity, it is necessary to measure and adjust the uplink timing deviation between user equipment and base station to ensure uplink synchronization.

[0003] In 5G NR, base stations can measure uplink timing deviations using the Physical Uplink Shared Channel (PUSCH) transmitted by user equipment (UE). However, in semi-static PUSCH scenarios (configured grant, CG), UE needs to have service data or other data as uplink data before it can send the PUSCH. In this scenario, UEs may not send data to the base station for an extended period, preventing the base station from performing uplink timing adjustments and causing uplink synchronization issues for the UE. Therefore, an uplink synchronization method is needed to control the interval of uplink timing adjustments. Summary of the Invention

[0004] This disclosure aims to at least partially address one of the technical problems in the related art.

[0005] The first aspect of this disclosure provides a method for uplink synchronization, including:

[0006] Upon receiving configuration information for the configuration authorization CG sent by the network device, start the timer;

[0007] When the timer reaches its set value and there is no uplink content to be sent to the network device from the terminal, preset content is sent to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG.

[0008] A second aspect of this disclosure provides an uplink synchronization apparatus, comprising:

[0009] The startup module is used to start a timer upon receiving configuration information from the configuration authorization CG sent by the network device;

[0010] The sending module is configured to send preset content to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG when the timer reaches its set time value and there is no uplink content to be sent to the network device from the terminal.

[0011] A third aspect of this disclosure provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements the uplink synchronization method as proposed in the first aspect of this disclosure.

[0012] A fourth aspect of this disclosure provides a chip including processing circuitry configured to perform the uplink synchronization method proposed in a first aspect embodiment.

[0013] A fifth aspect of this disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the uplink synchronization method as described in the first aspect of this disclosure.

[0014] The uplink synchronization method, apparatus, electronic device, chip, and storage medium disclosed herein have the following beneficial effects:

[0015] In this embodiment of the disclosure, by using a timer to monitor the time interval of uplink timing measurement performed by the terminal under CG configuration, and sending simulated content to the network device when the maximum time interval is reached and the terminal has no uplink content to send, uplink timing deviation measurement can be performed. This can avoid the problem of uplink synchronization failure caused by the terminal not sending uplink data for a long time under CG configuration, which makes it impossible to measure the terminal's uplink timing. This ensures the accuracy and synchronization of data transmission between the terminal and the network device and improves communication quality.

[0016] Additional aspects and advantages of this disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this disclosure. Attached Figure Description

[0017] The above and / or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which:

[0018] Figure 1 This is a flowchart illustrating an uplink synchronization method provided in an embodiment of the present disclosure.

[0019] Figure 2 A flowchart illustrating an uplink synchronization method provided in another embodiment of this disclosure;

[0020] Figure 3 A flowchart illustrating an uplink synchronization method provided in another embodiment of this disclosure;

[0021] Figure 4 A flowchart illustrating an uplink synchronization method provided in another embodiment of this disclosure;

[0022] Figure 5 A flowchart illustrating an uplink synchronization method provided in another embodiment of this disclosure.

[0023] Figure 6 A schematic diagram of the structure of an uplink synchronization device provided in an embodiment of this disclosure;

[0024] Figure 7 A block diagram of an exemplary electronic device suitable for implementing embodiments of the present disclosure is shown;

[0025] Figure 8 This is a schematic diagram of the structure of a chip proposed in an embodiment of this disclosure. Detailed Implementation

[0026] Embodiments of this disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure.

[0027] The following description, with reference to the accompanying drawings, outlines an uplink synchronization method, apparatus, electronic device, chip, and storage medium according to embodiments of the present disclosure.

[0028] Figure 1 This is a flowchart illustrating an uplink synchronization method provided in an embodiment of the present disclosure.

[0029] This disclosure illustrates the example of the uplink synchronization method being configured in an uplink synchronization device. The uplink synchronization device can be applied to any electronic device or any chip, so that the electronic device or chip can perform timed transmission of uplink data to avoid uplink synchronization failure.

[0030] It should be noted that the uplink synchronization method proposed in this disclosure can be applied to small data transmission (SDT) scenarios based on configured grant (CG), or it can be extended to non-SDT scenarios.

[0031] like Figure 1 As shown, the uplink synchronization method may include the following steps:

[0032] Step 101: Upon receiving the configuration information of the configuration authorization CG sent by the network device, start the timer.

[0033] The timer (CG_SEND_TIMER) is set by the terminal (such as user equipment (UE)) to control the interval between when the terminal sends uplink content to network equipment (such as base station).

[0034] In this embodiment of the disclosure, the terminal can receive a Radio Resource Control (RRC) Release message sent by the network device (used to establish and maintain a communication connection between the terminal and the network device). The RRC Release message may carry configuration information of the Configured Grant (CG).

[0035] Understandably, CG configuration allows network devices to pre-configure transmission resources for terminals, enabling terminals to transmit data using the CG configuration information without real-time dynamic scheduling. However, since the RRC Release message does not contain Sounding Reference Signal (SRS) configuration, the terminal cannot send an SRS signal to the network device to measure the uplink timing deviation. Therefore, the terminal can only perform uplink timing deviation measurement by sending uplink content such as service data or signaling to the network device through the Physical Uplink Shared Channel (PUSCH).

[0036] Furthermore, since CG is a semi-static PUSCH, the terminal can periodically send CG PUSCH autonomously according to the CG configuration after the network device issues the CG configuration, or it can send uplink content through dynamic PUSCH scheduled by the network downlink control information (DCI). However, the CG-related protocol (i.e., 3GPP 38.214) stipulates that the terminal should not send CG PUSCH when there is no service data or other content to be transmitted. Therefore, if the terminal has not been scheduled for dynamic PUSCH by the network device for a long time, or has no data to be transmitted, it cannot send CG PUSCH to allow the network device to perform uplink timing deviation measurement on the terminal. This may lead to the risk of the terminal losing uplink synchronization, requiring the random access procedure to be re-initiated, which will increase the terminal's data latency.

[0037] Therefore, in this embodiment of the present disclosure, after receiving the CG configuration information sent by the base station, the terminal can start the timer it sets to control the interval between sending uplink content to the network device (such as the base station), so as to prevent the uplink timing deviation measurement from being unable to be performed for a long time and reduce the risk of uplink synchronization failure.

[0038] Step 102: When the timer reaches its set time and there is no uplink content to be sent to the network device from the terminal, the preset content is sent to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG.

[0039] The timer value refers to the maximum time interval between each transmission of uplink content to the network device and the next transmission. The timer value can be determined empirically or based on various factors, such as the uplink transmission frequency of the terminal's historical service data and the CG-SDT period size; this disclosure does not impose any limitations on this.

[0040] The preset content is used to simulate the service data or signaling sent by the terminal to the network device. It may have a specific identifier to indicate that the network device does not need to parse the content.

[0041] In this embodiment of the disclosure, when the timer reaches its timing value and there is no uplink content to be sent to the network device, it indicates that the terminal has not performed uplink timing deviation measurement for a long time. Therefore, in order to avoid the terminal losing uplink synchronization, preset content can be used to simulate the uplink content that the terminal needs to send to the network device, and sent to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG, so that the network device can use the signal of the preset content to measure the uplink timing deviation of the terminal.

[0042] In this embodiment, upon receiving configuration information for the Configuration Authorization Channel (CG) sent by the network device, a timer is first started. Then, when the timer reaches its set time and there is no uplink content to be sent to the network device from the terminal, preset content is sent to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG. Thus, by using a timer to monitor the time interval for uplink timing measurements performed by the terminal under the CG configuration, and by sending simulated content to the network device when the maximum time interval is reached and the terminal has no uplink content to send, uplink timing deviation measurement can be performed. This avoids the problem of uplink synchronization failure caused by the terminal not sending uplink data for extended periods under the CG configuration, preventing uplink timing measurement. This ensures the accuracy and synchronization of data transmission between the terminal and the network device, improving communication quality.

[0043] Figure 2 This is a flowchart illustrating an uplink synchronization method provided in an embodiment of the present disclosure, as shown below. Figure 2 As shown, the uplink synchronization method may include the following steps:

[0044] Step 201: Upon receiving the configuration information of the configuration authorization CG sent by the network device, determine the period of the CG based on the configuration information of the CG.

[0045] The CG period is the time interval at which network devices send authorization information to terminals, and terminals can perform uplink transmission at the corresponding frequency according to the authorization information.

[0046] It is understandable that CG allocates specific uplink resources (such as time or frequency) to the terminal, and the configuration information of CG specifies the exact location and size of these uplink resources. Therefore, the period of CG can be obtained from the configuration information.

[0047] Step 202: Determine the timing value of the timer based on the period of CG.

[0048] The timer's timing value is n times the period of CG, where n is a natural number.

[0049] It should be noted that since the terminal can send the uplink content to be transmitted within each CG cycle to the network device, when the timer value is an integer multiple of the CG cycle, the terminal can determine whether there is content to be sent within a complete cycle when the timer value is reached. This will not lead to the situation where the cycle has not ended when the timer reaches the timer value, resulting in the incorrect judgment that there is no uplink content to be sent.

[0050] In this embodiment of the disclosure, n times the period of CG can be determined as the timing value of the timer. The specific value of n can be determined according to the period of CG. For example, when the period of CG is large, n can take a small value, and when the period of CG is small, n can take a large value, so that the timing value of the timer is neither too large nor too small.

[0051] Alternatively, n can be determined to be equal to 1 if the period of CG is greater than a threshold.

[0052] The threshold can be determined based on experience, and this disclosure does not impose any restrictions on it.

[0053] Alternatively, n can be determined to be greater than 1 if the period of CG is less than or equal to the threshold.

[0054] In this embodiment of the disclosure, the value of n can be determined by judging the relationship between the period of CG and the preset threshold, which can make the setting of timing value more reasonable, and optimize resource utilization while ensuring the timeliness of uplink timing measurement.

[0055] Step 203: Start the timer. When the timer reaches its set time and there is no uplink content to be sent to the network device from the terminal, send the preset content to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG.

[0056] For detailed data on step 203 above, please refer to other embodiments of this disclosure, which will not be repeated here.

[0057] It should be noted that the timer's timing value controls the interval between two uplink transmissions from the terminal to the network device. Therefore, after the timer is started, it needs to be reset every time a terminal sends uplink content to the network device. Thus, when the timer reaches its timing value, it can be confirmed that no uplink transmissions from the terminal to the network device have occurred within the corresponding time period. If the terminal still has no uplink content to send to the network device at this point, it can send preset content to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG.

[0058] In this embodiment, the period of the CG is determined based on its configuration information, and then the timer value is determined based on the CG's period. This improves the rationality of the timer value setting, thereby increasing resource utilization and enhancing the orderliness and efficiency of uplink synchronization.

[0059] Figure 3 This is a flowchart illustrating an uplink synchronization method provided in an embodiment of the present disclosure, as shown below. Figure 3 As shown, the uplink synchronization method may include the following steps:

[0060] Step 301: Upon receiving the configuration information of the configuration authorization CG sent by the network device, start the timer.

[0061] For detailed data on step 301 above, please refer to other embodiments of this disclosure, which will not be repeated here.

[0062] Step 302: After sending uplink content to the network device, restart the timer.

[0063] In this embodiment of the disclosure, after the timer is started, the terminal may generate uplink content such as service data or signaling that needs to be sent to the network device before the timer reaches its set time. In this case, uplink timing deviation measurement can be performed by sending this uplink content to the network device. At this point, the timer can be restarted to recalculate the latest time to send the next uplink content to the network device.

[0064] It should be noted that the uplink content can be any of the following: uplink content sent through the dynamically scheduled Physical Uplink Shared Channel (PUSCH), or uplink content sent through the CG PUSCH.

[0065] In this embodiment, since the CG is a semi-static PUSCH, after the network device issues the CG configuration, the terminal can autonomously and periodically send uplink content through the CG PUSCH according to the CG configuration. Alternatively, uplink content can also be sent through a dynamic PUSCH scheduled by the network DCI. Therefore, the uplink content sent by the terminal to the network device can be uplink content sent through a dynamically scheduled Physical Uplink Shared Channel (PUSCH), or it can be uplink content sent through the CG PUSCH.

[0066] In this embodiment, by restarting the timer after the terminal sends uplink content to the network device, it can be ensured that there are no events of the terminal sending uplink content to the network device within the time period when the timer reaches the timer value, thus avoiding unnecessary uplink timing deviation measurements and improving resource utilization.

[0067] Figure 4 This is a flowchart illustrating an uplink synchronization method provided in an embodiment of the present disclosure, as shown below. Figure 4 As shown, the uplink synchronization method may include the following steps:

[0068] Step 401: Upon receiving the configuration information of the configuration authorization CG sent by the network device, start the timer.

[0069] For detailed data on step 401 above, please refer to other embodiments of this disclosure, which will not be repeated here.

[0070] Step 402: If the transmission time of the Physical Uplink Shared Channel (PUSCH) of the CG is reached, determine whether there is uplink content in the terminal to be sent to the network device.

[0071] The transmission time refers to the time during which the terminal is allowed to periodically send data to the network device, based on the CG cycle.

[0072] In this embodiment of the disclosure, after the timer is started, since there may be multiple CG cycles before the timer reaches its timing value, it is possible to determine whether there is uplink content in the terminal to be sent to the network device in the current cycle each time the transmission time of the Physical Uplink Shared Channel (PUSCH) of the CG is reached, thus ensuring that the content in the terminal can be sent to the network device in a timely manner.

[0073] Step 403: If there is uplink content to be sent to the network device in the terminal, send the uplink content on the CG PUSCH.

[0074] In this embodiment of the disclosure, after the transmission time of the CG PUSCH is reached and it is determined that there is uplink content to be sent to the network device in the terminal, the uplink content can be sent to the network device on the CG PUSCH.

[0075] Step 404: Restart the timer.

[0076] In this embodiment of the disclosure, while the network device receives the uplink content, it can perform an uplink timing deviation measurement based on the uplink content to maintain uplink synchronization. Then, the timer can be restarted to recalculate the latest time to send the next uplink content to the network device.

[0077] Optionally, if there is no uplink content to be sent to the network device in the terminal, it can be determined whether the timer has expired. Then, if the timer has not expired, the preset content is not sent on the CG PUSCH.

[0078] In this embodiment of the disclosure, if it is determined that there is no uplink content to be sent to the network device at the current transmission time, it is first determined whether the timer has expired. If the timer has not expired, it can be determined that there is no risk of uplink synchronization failure at this time, so no preset content will be generated to simulate uplink data. Furthermore, according to the constraints in the CG-related protocol, that is, the terminal does not send CG PUSCH when there is no data content to be sent, the terminal will not send preset content (or any other content) on the CG PUSCH, and the timer will continue to count down.

[0079] In this embodiment, upon reaching the transmission time of the Physical Uplink Shared Channel (PUSCH), it is first determined whether the terminal has uplink content to be sent to the network device. Then, if the terminal has uplink content to be sent to the network device, the uplink content is transmitted on the CG PUSCH, and the timer is restarted. Therefore, by initializing the timer after the uplink content to be sent to the network device from the terminal at the transmission time of the CG PUSCH, timely synchronization between terminal data and network device can be ensured. Furthermore, it guarantees that no event occurs during the timer's timeout period, preventing unnecessary uplink timing deviation measurements and improving resource utilization.

[0080] Figure 5 This is a flowchart illustrating an uplink synchronization method provided in one embodiment of this disclosure. Figure 5 As shown, the uplink synchronization method may include the following steps:

[0081] First, after the User Equipment (UE) receives the CG-SDT configuration from the base station, the UE can start the timer (CG_SEND_TIMER).

[0082] The timer length can be set to N times the CG-SDT period (the specific value of N can be determined based on the CG-SDT period; for example, if the CG-SDT period is large, then N should be a smaller value, and if the CG-SDT period is small, then N can be a larger value). After the timer is started, once the UE sends any data to the base station (this can be data sent via dynamic PUSCH scheduled by the base station, or service data sent autonomously by the UE when the CG-SDT PUSCH transmission time arrives), the base station can measure the UE's uplink timing deviation based on the data sent by the UE. There is no risk of uplink synchronization failure, and the timer will restart, i.e., begin counting again.

[0083] Therefore, in Figure 5 In this process, after starting the timer, it can be determined whether the UE has sent a dynamic PUSCH to the base station (i.e., whether the UE has been scheduled by the base station to send a dynamic PUSCH and send uplink content to the base station). If the UE has sent a dynamic PUSCH to the base station, the timer (CG_SEND_TIMER) is restarted. Alternatively, if the UE has not sent a dynamic PUSCH to the base station, it can be further determined whether the UE has service data to send to the base station when the CG-SDT PUSCH transmission time arrives.

[0084] It should be noted that after the UE sends the dynamic PUSCH to the base station and restarts the timer, in the new timing cycle, it is still necessary to determine whether the UE has service data to send to the base station when the CG-SDT PUSCH transmission time arrives. Therefore, in Figure 5 The flowchart connection method has been simplified, connecting the processes for both cases where the UE sends a dynamic PUSCH to the base station and cases where it does not send a dynamic PUSCH to the base station to the same node (i.e. Figure 5 The diamond-shaped indicator indicates that the next step can be to determine whether the current time is the time when the CG-SDT PUSCH is sent.

[0085] Because the timer's duration is longer than the CG-SDT period, each time the UE reaches the CG-SDT PUSCH transmission time, it first checks if the UE has any service data to send. If so, it sends the corresponding service data on the CG-SDT PUSCH and restarts CG_SEND_TIMER. If the UE has no service data, it checks if CG_SEND_TIMER has timed out (i.e.,...). Figure 5If the CG_SEND_TIMER in the protocol has expired, and the timer has expired, in order to ensure that the UE does not lose uplink synchronization, simulated service data is sent on the CG-SDT PUSCH for the base station to measure the UE's uplink timing. If the CG_SEND_TIMER has not expired, the CG-SDT PUSCH is not sent to maintain the protocol constraint that "the UE does not send the CG-SDT PUSCH when there is no service data".

[0086] It should be noted that, regardless of whether the timer restarts or the timer hasn't reached its set time, it's necessary to continue monitoring whether the UE has sent data to the base station. Therefore, in Figure 5 In the flowchart shown, after determining that the CG-SDT PUSCH transmission time has not yet arrived (restarting the timer, sending the simulated service data, or confirming that the timer has not expired), the process can return to determine whether the UE has sent data to the base station, thus... Figure 5 As shown, the uplink synchronization method provided in this embodiment is a cyclic process.

[0087] To implement the above embodiments, this disclosure also proposes an uplink synchronization device.

[0088] Figure 6 This is a schematic diagram of the uplink synchronization device provided in an embodiment of the present disclosure.

[0089] like Figure 6 As shown, the uplink synchronization device 600 may include:

[0090] The startup module 601 is used to start a timer upon receiving configuration information of the configuration authorization CG sent by the network device;

[0091] The sending module 602 is used to send preset content to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG when the timer reaches the set time value and there is no uplink content to be sent to the network device in the terminal.

[0092] Optionally, the startup module 601 can also be used for:

[0093] Determine the CG cycle based on the CG configuration information;

[0094] Based on the period of CG, determine the timing value of the timer, where the timing value of the timer is n times the period of CG, and n is a natural number.

[0095] Optionally, the startup module 601 can also be used for:

[0096] If the period of CG is greater than the threshold, then n is determined to be equal to 1; or,

[0097] If the period of CG is less than or equal to the threshold, then n is determined to be greater than 1.

[0098] Optionally, the startup module 601 can also be used for:

[0099] Restart the timer after sending uplink content to the network device.

[0100] Optionally, the uplink content can be any of the following: uplink content transmitted via the dynamically scheduled Physical Uplink Shared Channel (PUSCH) or uplink content transmitted via the CG PUSCH.

[0101] Optionally, the startup module 601 can also be used for:

[0102] If the transmission time of the Physical Uplink Shared Channel (PUSCH) of the CG is reached, determine whether there is uplink content in the terminal to be sent to the network device.

[0103] If there is uplink content to be sent to the network device at the terminal, send the uplink content on the CG PUSCH.

[0104] Restart the timer.

[0105] Optionally, the startup module 601 can also be used for:

[0106] If there is no uplink content to be sent to the network device in the terminal, determine whether the timer has timed out;

[0107] If the timer has not expired, do not send the preset content on the CG PUSCH.

[0108] The functions and specific implementation principles of the modules described in this embodiment can be found in the above method embodiments, and will not be repeated here.

[0109] The uplink synchronization apparatus of this disclosure first uses a timer to monitor the time interval for uplink timing measurement performed by the terminal under CG configuration. When the maximum time interval is reached and the terminal has no uplink content to send, simulated content is sent to the network device to perform uplink timing deviation measurement. This can avoid the problem of uplink synchronization failure caused by the terminal not sending uplink data for a long time under CG configuration, which makes it impossible to measure the terminal's uplink timing. This ensures the accuracy and synchronization of data transmission between the terminal and the network device and improves communication quality.

[0110] To implement the above embodiments, this disclosure also proposes an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the uplink synchronization method proposed in the foregoing embodiments of this disclosure.

[0111] Figure 7 A block diagram of an exemplary electronic device suitable for implementing embodiments of the present disclosure is shown. Figure 7 The electronic device 12 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0112] like Figure 7 As shown, the electronic device 12 is represented in the form of a general-purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, system memory 28, and bus 18 connecting different system components (including system memory 28 and processing unit 16).

[0113] Bus 18 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. Examples of these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0114] Electronic device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by electronic device 12, including volatile and non-volatile media, removable and non-removable media.

[0115] Memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and / or cache memory 32. Electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 may be used to read and write non-removable, non-volatile magnetic media (… Figure 7 Not shown; usually referred to as a "hard drive"). Although Figure 7Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disc drive for reading and writing to a removable non-volatile optical disc (e.g., a compact disc read-only memory (CD-ROM), a digital video disc read-only memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 via one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of this disclosure.

[0116] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 42 typically perform the functions and / or methods described in the embodiments of this disclosure.

[0117] Electronic device 12 can also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), and with one or more devices that enable a user to interact with electronic device 12, and / or with any device that enables electronic device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via input / output (I / O) interface 22. Furthermore, electronic device 12 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 20. As shown, network adapter 20 communicates with other modules of electronic device 12 via bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0118] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing the methods mentioned in the foregoing embodiments.

[0119] To implement the above embodiments, this disclosure also proposes a chip, including: the chip includes processing circuitry configured to perform the graphics rendering method as provided in the foregoing embodiments.

[0120] Figure 8 This is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. See also... Figure 8 The diagram shown is a schematic representation of the structure of chip 800, but is not limited to this.

[0121] Chip 800 includes processing circuitry 801, which is configured to perform any of the above methods.

[0122] In some embodiments, the chip 800 further includes one or more interface circuits 802. Optionally, the interface circuit 802 is connected to the memory 803, and the interface circuit 802 can be used to receive signals from the memory 803 or other devices, and the interface circuit 802 can be used to send signals to the memory 803 or other devices. For example, the interface circuit 802 can read instructions stored in the memory 803 and send the instructions to the processing circuit 801.

[0123] In some embodiments, the interface circuit 802 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processing circuit 801 performs other steps.

[0124] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.

[0125] In some embodiments, chip 800 further includes one or more memories 803 for storing instructions. Optionally, all or part of the memories 803 may be located outside of chip 800.

[0126] To implement the above embodiments, this disclosure also proposes a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the uplink synchronization method as proposed in the foregoing embodiments of this disclosure.

[0127] The technical solution disclosed herein can ensure timely synchronization between terminal data and network devices, and guarantee that there are no events where the terminal sends uplink content to the network device within the time period when the timer reaches the timer value, thereby avoiding unnecessary uplink timing deviation measurements and improving resource utilization.

[0128] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0129] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0130] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of preferred embodiments of this disclosure includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as will be understood by those skilled in the art to which embodiments of this disclosure pertain.

[0131] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0132] It should be understood that various parts of this disclosure can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0133] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0134] Furthermore, the functional units in the various embodiments of this disclosure can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0135] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present disclosure.

Claims

1. A method for uplink synchronization, characterized in that, include: Upon receiving configuration information for the configuration authorization CG sent by the network device, start the timer; When the timer reaches its set time and there is no uplink content to be sent to the network device from the terminal, preset content is sent to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG. The preset content is used to simulate the uplink content that the terminal needs to send to the network device.

2. The method as described in claim 1, characterized in that, Before starting the timer, the following is also included: The cycle of the CG is determined based on the configuration information of the CG; The timing value of the timer is determined based on the period of the CG, wherein the timing value of the timer is n times the period of the CG, and n is a natural number.

3. The method as described in claim 2, characterized in that, Determining the timing value of the timer based on the period of the CG includes at least one of the following: If the period of the CG is greater than the threshold, then n is determined to be equal to 1; If the period of the CG is less than or equal to the threshold, then n is determined to be greater than 1.

4. The method as described in claim 1, characterized in that, Following the start timer, the following is also included: When uplink content is sent to the network device, the timer is restarted.

5. The method as described in claim 4, characterized in that, The uplink content is any one of the following: uplink content transmitted via the dynamically scheduled Physical Uplink Shared Channel (PUSCH) or uplink content transmitted via the CG PUSCH.

6. The method according to any one of claims 1-5, characterized in that, Following the start timer, the following is also included: When the transmission time of CG PUSCH is reached, determine whether the terminal has uplink content to be sent to the network device; If there is uplink content to be sent to the network device in the terminal, the uplink content is sent on the CG PUSCH; Restart the timer.

7. The method as described in claim 6, characterized in that, After determining whether the terminal has uplink content to be sent to the network device, the method further includes: If there is no uplink content to be sent to the network device in the terminal, determine whether the timer has timed out; If the timer does not expire, the preset content will not be sent on the CG PUSCH.

8. An uplink synchronization device, characterized in that, The device includes: The startup module is used to start a timer upon receiving configuration information from the configuration authorization CG sent by the network device; The sending module is configured to send preset content to the network device on the Physical Uplink Shared Channel (PUSCH) of the CG when the timer reaches its set value and there is no uplink content to be sent to the network device from the terminal. The preset content is used to simulate the uplink content that the terminal needs to send to the network device.

9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements the uplink synchronization method as described in any one of claims 1-7.

10. A chip, characterized in that, The chip includes processing circuitry configured to perform the uplink synchronization method as described in any one of claims 1-7.

11. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the uplink synchronization method as described in any one of claims 1-7.

Images