Effective duration reporting method and device and nonvolatile storage medium

Abstract

The invention discloses an effective duration reporting method and device and a nonvolatile storage medium. The method comprises the following steps: user equipment receives a system information block containing uplink synchronization effective duration, and the uplink synchronization effective duration is used for indicating the effective duration of ephemeris information and network time adjustment information; determining a time delay from reception of the system information block to completion of the random access procedure; the reported effective duration of the global satellite navigation system is adjusted according to the time delay, the adjusted effective duration of the global satellite navigation system is obtained, and the minimum value of the adjusted effective duration of the global satellite navigation system is smaller than the minimum value of the uplink synchronization effective duration; and reporting a radio resource control connection request message carrying the adjusted effective duration of the global satellite navigation system to a non-ground network of the Internet of Things. According to the method and the device, the technical problem that the effective duration reported by the UE is not matched with the uplink synchronization effective duration broadcasted by the network is solved.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a method, apparatus, and non-volatile storage medium for reporting the effective duration. Background Art

[0002] In the communication environment of the Internet of Things Non-Terrestrial Networking (IoT NTN), a User Equipment (UE) needs to synchronize signals from the Global Navigation Satellite System (GNSS) to ensure correct communication with the network. When the UE establishes a connection with the network or performs certain connection management operations, it needs to report the GNSS effective duration that it believes. This duration is carried by the Global Navigation Satellite System Validity Duration (Release 17) (abbreviated as GNSS-ValidityDuration-r17, where r17 represents the introduction in the 17th version of the 3rd Generation Partnership Project (3GPP) specification).

[0003] The GNSS effective duration reported by the UE depends on the uplink synchronization effective duration broadcast by the System Information Block Type 31 (SIB31). The value of the former should be less than that of the latter. However, the minimum value of the GNSS-ValidityDuration-r17 cell is 10 seconds, which is larger than the minimum value of 5 seconds of the Uplink Synchronization Validity Duration (Release 17) (abbreviated as ul-SyncValidityDuration-r17) cell that carries the uplink synchronization effective duration in SIB31. When the uplink synchronization effective duration broadcast by the IoT NTN network through SIB31 is between 5 seconds and 10 seconds, since the minimum value of the GNSS-ValidityDuration-r17 cell is 10 seconds, the UE cannot report a duration less than 10 seconds when reporting the GNSS effective duration. This results in a mismatch between the effective duration reported by the UE and the uplink synchronization effective duration broadcast by the network. The UE cannot respond to faster signal changes, which may lead to synchronization problems.

[0004] For the above problems, no effective solution has been proposed yet. Summary of the Invention

[0005] An embodiment of the present application provides a method, apparatus, and non - volatile storage medium for reporting the effective duration, so as to at least solve the technical problem that there is a mismatch between the effective duration reported by the UE and the uplink synchronization effective duration broadcast by the network.

[0006] According to one aspect of the embodiments of the present application, a method for reporting the effective duration is provided, including: a user equipment receives a system information block containing the uplink synchronization effective duration, where the uplink synchronization effective duration is used to indicate the effective duration of ephemeris information and network time adjustment information; determines the time delay from receiving the system information block until the random access procedure is completed; adjusts the reported global navigation satellite system (GNSS) effective duration according to the time delay to obtain an adjusted GNSS effective duration, where the minimum value of the adjusted GNSS effective duration is less than the minimum value of the uplink synchronization effective duration; and reports a radio resource control connection request message carrying the adjusted GNSS effective duration to the Internet of Things non - terrestrial network.

[0007] In some embodiments of the present application, the system information block carries an uplink synchronization effective duration cell and does not carry an epoch time cell. In the case where the system information block does not carry an epoch time cell, the minimum value of the uplink synchronization effective duration of the system information block is less than the minimum value of the GNSS effective duration. Here, the uplink synchronization effective duration cell is used to indicate the uplink synchronization effective duration, and the epoch time cell is used to specify the starting time point of the uplink synchronization effective duration and is an optional cell.

[0008] In some embodiments of the present application, the time delay is determined in the following manner: obtaining a first time from receiving the system information block to sending a random access preamble sequence; obtaining a second time from sending the random access preamble sequence to receiving a random access response; obtaining a third time from receiving the random access response to sending a radio resource control connection request message; and determining the sum of the first time, the second time, and the third time as the time delay.

[0009] In some embodiments of the present application, the effective duration of the global satellite navigation system to be reported is adjusted according to a time delay to obtain an adjusted effective duration of the global satellite navigation system, including: the user equipment evaluates the reliability in the random access process based on the uplink synchronization effective duration indicated by the field in the uplink synchronization effective duration cell, and obtains a reliability evaluation result; when the reliability evaluation result indicates that the uplink synchronization effective duration is not sufficient to cover the time required for the entire random access process, the user equipment adjusts the effective duration of the global satellite navigation system to be reported according to the time delay to obtain an adjusted effective duration of the global satellite navigation system, and sends a resynchronization request, where the resynchronization request is used to ensure that the uplink synchronization between the user equipment and the Internet of Things non-terrestrial network is completed within the adjusted effective duration of the global satellite navigation system.

[0010] In some embodiments of the present application, the user equipment adjusts the effective duration of the global satellite navigation system to be reported according to a time delay to obtain an adjusted effective duration of the global satellite navigation system, including: obtaining the uplink synchronization effective duration in the system information block; subtracting the internal delay of the user equipment from the uplink synchronization effective duration to obtain a preliminary effective duration of the global satellite navigation system, where the internal delay of the user equipment includes the timing advance time and the time consumption of the Doppler frequency offset; subtracting the time delay from the preliminary effective duration of the global satellite navigation system to obtain an adjusted effective duration of the global satellite navigation system.

[0011] In some embodiments of the present application, the method further includes: immediately starting a timer after receiving the system information block, where the timer is used to measure the time delay; terminating the timer at the time point when the random access process is completed, and recording the time delay; storing the recorded time delay in the local database of the user equipment.

[0012] In some embodiments of the present application, the method further includes: determining the battery power status and power consumption of the user equipment; when reporting the second preset field carrying the adjusted effective duration of the global satellite navigation system to the Internet of Things non-terrestrial network, also carrying the battery power status and power consumption of the user equipment, where the battery power status and power consumption of the user equipment are used to indicate that the Internet of Things non-terrestrial network adjusts parameters according to the battery power status and power consumption of the user equipment to optimize network resource allocation.

[0013] According to another aspect of the embodiments of the present application, there is also provided a device for reporting the effective duration, including: a receiving module, configured to receive, by a user equipment, a system information block including the uplink synchronization effective duration, where the uplink synchronization effective duration is used to indicate the effective duration of ephemeris information and network time adjustment information; a determining module, configured to determine the time delay from receiving the system information block until the random access process is completed; an adjusting module, configured to adjust the reported effective duration of the global satellite navigation system according to the time delay to obtain an adjusted effective duration of the global satellite navigation system, where the minimum value of the adjusted effective duration of the global satellite navigation system is less than the minimum value of the uplink synchronization effective duration; and a reporting module, configured to report a radio resource control connection request message carrying the adjusted effective duration of the global satellite navigation system to the Internet of Things non-terrestrial network.

[0014] According to another aspect of the embodiments of the present application, there is also provided a non-volatile storage medium storing a program, where, when the program runs, it controls the device where the non-volatile storage medium is located to execute the above method for reporting the effective duration.

[0015] According to another aspect of the embodiments of the present application, there is also provided an electronic device including a memory and a processor, where the processor is configured to run the program stored in the memory, and when the program runs, it executes the above method for reporting the effective duration.

[0016] According to another aspect of the embodiments of the present application, there is also provided a computer program product including computer instructions, and when the computer instructions are executed by a processor, they implement the above method for reporting the effective duration.

[0017] In an embodiment of the present application, a user equipment receives a system information block including an uplink synchronization effective duration, where the uplink synchronization effective duration is used to indicate the effective duration of ephemeris information and network time adjustment information; determines the time delay from receiving the system information block until the random access procedure is completed; adjusts the reported global satellite navigation system effective duration according to the time delay to obtain an adjusted global satellite navigation system effective duration, where the minimum value of the adjusted global satellite navigation system effective duration is less than the minimum value of the uplink synchronization effective duration; and reports a radio resource control connection request message carrying the adjusted global satellite navigation system effective duration to the non-terrestrial network of the Internet of Things. By adjusting the reported global satellite navigation system effective duration according to the time delay to obtain an adjusted global satellite navigation system effective duration, and the minimum value of the adjusted global satellite navigation system effective duration is less than the minimum value of the uplink synchronization effective duration, the purpose that the effective duration reported by the UE is always less than the uplink synchronization effective duration is achieved, and the problem of mismatch between the effective duration reported by the UE and the uplink synchronization effective duration broadcast by the network is avoided. Furthermore, the technical problem of mismatch between the effective duration reported by the UE and the uplink synchronization effective duration broadcast by the network is solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and form a part of the present application. The illustrative embodiments and descriptions thereof of the present application are used to explain the present application and do not constitute an improper limitation to the present application. In the drawings:

[0019] Figure 1 is a hardware structure block diagram of a computer terminal for implementing a method for reporting an effective duration according to an embodiment of the present application;

[0020] Figure 2 is a flowchart of a method for reporting an effective duration according to an embodiment of the present application;

[0021] Figure 3 is a flowchart of another method for reporting an effective duration according to an embodiment of the present application;

[0022] Figure 4 is a schematic structural diagram of a device for reporting an effective duration according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0023] To enable those skilled in the art to better understand the solution of this application, the following will clearly and completely describe the technical solution in the embodiments of this application in combination with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the protection scope of this application.

[0024] The information collected in the embodiments of this application is information and data authorized by the user or fully authorized by all parties. Moreover, for the processing of relevant data such as collection, storage, use, processing, transmission, provision, disclosure, and application, all comply with the relevant laws, regulations, and standards of the relevant regions, necessary confidentiality measures are taken, it does not violate public order and good customs, and a corresponding operation entry is provided for the user to choose to authorize or reject the automated decision result; if the user chooses to reject, the expert decision-making process will be entered.

[0025] It should be noted that the terms "first", "second", etc. in the specification, claims, and the above-mentioned accompanying drawings of this application are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments of this application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device including a series of steps or units does not necessarily have to be limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products, or devices.

[0026] To better understand the embodiments of this application, the following technical terms involved in the embodiments of this application are explained as follows:

[0027] 3rd Generation Partnership Project (3GPP): 3GPP is a standardization organization whose main goal is to define the technical specifications for global 3G, 4G, and 5G mobile communication networks.

[0028] Internet of Things Non-Terrestrial Networking (IoT NTN): IoT NTN is a specific specification of 3GPP for Internet of Things devices to communicate in non-terrestrial networks (such as satellite networks). It aims to expand the connection capabilities of the Internet of Things and enable support for areas that cannot be covered by terrestrial networks, such as remote areas, oceans, and the air.

[0029] User Equipment (UE): UE is a key entity in the 3GPP standard, referring to any device that can communicate directly or indirectly with the network in a wireless communication network. UE can be a mobile phone, an Internet of Things device, a computer, etc., capable of executing wireless communication protocols and exchanging data with the network.

[0030] Global Navigation Satellite System (GNSS) Validity Duration Information Element: GNSS-ValidityDuration-r17 is an information element defined in the 3GPP R17 specification, used to indicate the duration of GNSS signals that the UE reports it believes to be valid. This can be the duration calculated by the UE after receiving and processing satellite signals.

[0031] System Information Block Type 31 (SIB31): SIB31 is a type of System Information Block (SIB) defined in the 3GPP R17 version, used to broadcast satellite navigation-related information to User Equipment (UE) to support positioning and uplink synchronization functions in non-terrestrial networks.

[0032] Uplink Synchronization Validity Duration (Release17) (ul-SyncValidityDuration-r17) Information Element: ul-SyncValidityDuration-r17 is an information element defined in the 3GPP R17 specification of SIB31 in the 3GPP R17 version, used as a reference for the UE to synchronize in the uplink to determine the availability of ephemeris information.

[0033] In the related art, the GNSS validity duration reported by the UE depends on the uplink synchronization validity duration broadcast in the System Information Block Type 31 (SIB31 for short). The value of the former should be less than that of the latter. However, the minimum value of the GNSS-ValidityDuration-r17 cell is 10 seconds, which is larger than the minimum value of 5 seconds of the Uplink Synchronization Validity Duration (Release17) (ul-SyncValidityDuration-r17 for short) cell that carries the uplink synchronization validity duration in SIB31. When the uplink synchronization validity duration broadcast by the IoT NTN network through SIB31 is between 5 seconds and 10 seconds, since the minimum value of the GNSS-ValidityDuration-r17 cell is 10 seconds, when the UE reports the GNSS validity duration, it cannot report a duration less than 10 seconds. This results in a mismatch between the validity duration reported by the UE and the uplink synchronization validity duration broadcast by the network, and the UE cannot respond to faster signal changes. Therefore, there is a technical problem that the validity duration reported by the UE does not match the uplink synchronization validity duration broadcast by the network. To solve this problem, relevant solutions are provided in the embodiments of the present application, which are described in detail below.

[0034] According to the embodiments of the present application, an embodiment of a method for reporting the validity duration is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. And although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0035] The method embodiments provided by the embodiments of the present application can be executed in a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal for implementing the method for reporting the validity duration is shown. As Figure 1 shown, the computer terminal 10 may include one or more (shown as 102a, 102b,..., 102n in the figure) processors 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a field programmable gate array FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may further include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports in the BUS bus), a network interface, a power supply, and / or a camera. Those of ordinary skill in the art can understand, Figure 1The structure shown is only schematic and does not limit the structure of the above-mentioned electronic device. For example, the computer terminal 10 may also include more or fewer components than those shown in Figure 1 or have a different configuration from that shown in Figure 1 .

[0036] It should be noted that one or more of the above-mentioned processors 102 and / or other data processing circuits can generally be referred to as "data processing circuits" herein. The data processing circuit can be embodied in software, hardware, firmware, or any combination thereof, in whole or in part. In addition, the data processing circuit can be a single independent processing module, or be incorporated in whole or in part into any one of the other elements in the computer terminal 10. As involved in the embodiments of the present application, the data processing circuit is a kind of processor control (such as the selection of a variable resistor terminal path connected to an interface).

[0037] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage devices corresponding to the method of reporting the effective duration in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the above-mentioned method of reporting the effective duration. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some instances, the memory 104 may further include a memory remotely provided with respect to the processor 102, and these remote memories can be connected to the computer terminal 10 through a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0038] The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the computer terminal 10. In one instance, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station and thus can communicate with the Internet. In one instance, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0039] The display can be, for example, a touch-screen liquid crystal display (LCD), which enables a user to interact with the user interface of the computer terminal 10.

[0040] Under the above operating environment, an embodiment of a method for reporting the effective duration is provided in an embodiment of the present application. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. And although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0041] As Figure 2 shown, it is a flowchart of a method for reporting the effective duration provided according to an embodiment of the present application, including:

[0042] Step S202, the user equipment receives a system information block containing the effective duration of uplink synchronization, and the effective duration of uplink synchronization is used to indicate the effective duration of ephemeris information and Network Time Adjustment (NTA) information.

[0043] In the technical solution provided in step S202, the system information block carries an uplink synchronization effective duration cell and does not carry an epoch time cell. In the case where the system information block does not carry an epoch time cell, the minimum value of the uplink synchronization effective duration of the system information block is less than the minimum value of the effective duration of the global satellite navigation system. Among them, the uplink synchronization effective duration cell is used to indicate the uplink synchronization effective duration, and the epoch time cell is used to specify the starting time point of the uplink synchronization effective duration, which is an optional cell. Ephemeris information is the key data provided to the user equipment (UE) in the global satellite navigation system (GNSS) for positioning and time synchronization. It contains detailed parameters describing the satellite orbit position, including the position, speed, acceleration of the satellite in space, and the shape and attitude of the orbit. Ephemeris information is usually calculated by a control center on the earth and uploaded to the satellite, and the satellite then broadcasts it to the UE. After receiving the ephemeris information, the UE can use these data to calculate the precise position of the satellite and perform positioning and time synchronization based on this. Network Time Adjustment information (NTA) is data used to adjust the time synchronization difference between the UE and the network side. In a non-terrestrial network (NTN), such as a satellite network, due to the long distance and high latency of signal transmission, there may be a significant time offset between the UE and the network side (non-terrestrial network (NTN)). The NTA information is sent to the UE through broadcast or point-to-point signaling to help the UE adjust its local clock to achieve more precise synchronization with the network. The NTA information usually includes the time offset and the rate of change of the time offset, as well as timeliness information. After receiving the NTA information, the UE will adjust its local clock according to these parameters to reduce the time difference with the network side and ensure more precise time synchronization in specific communication scenarios, such as uplink data transmission, timing synchronization, etc.

[0044] In some embodiments of the present application:

[0045] The user equipment receives a system information block (e.g., SIB31) containing the uplink synchronization validity duration. In this application, it specifically refers to a system information block that does not carry an epoch time cell (e.g., the epochTime-r17 cell) and carries an uplink synchronization validity duration cell (e.g., the ul-SyncValidityDuration-r17 cell). epochTime-r17 is a cell defined in SIB31 in 3GPP Release 17. The parameter of this cell is used to indicate the start time point of the validity duration of ephemeris information and network time adjustment (NTA) information, that is, from which system frame and subframe these information are valid. It helps the UE determine when to start applying this information. This cell is an optional cell, that is, it can be chosen to carry or not carry this cell.

[0046] When not carrying epochTime-r17, the epoch time will be considered as the start time of the downlink subframe of the SI message carrying SIB31 transmitted at the end of the SI window (the SI window refers to the time window for system information (SI) transmission). That is to say, if the system information block does not contain the epochTime-r17 cell, then the user equipment (UE) considers the start point of the uplink synchronization valid time as the start time of the downlink subframe of the last transmitted SIB31(-NB) message within the current SI window. The value range of the uplink synchronization validity duration carried by the ul-SyncValidityDuration-r17 cell in the system information block is 16 enumerated values from 5 seconds to 900 seconds, representing the validity duration of ephemeris information and NTA information after the system frame and subframe indicated by the epochTime-r17 cell. The 16 enumerated values are {s5, s10, s15, s20, s25, s30, s35, s40, s45, s50, s55, s60, s120, s180, s240, s900; where s represents seconds, for example, s5 represents 5 seconds}. It can be seen that at this time, the minimum value of the uplink synchronization validity duration is 5 seconds.

[0047] Step S204, determine the time delay from receiving the system information block until the random access process is completed.

[0048] In the technical solution provided in step S204, the time delay is determined as follows: obtaining a first time from receiving the system information block to transmitting the random access preamble sequence; obtaining a second time from transmitting the random access preamble sequence to receiving the random access response; obtaining a third time from receiving the random access response to transmitting the radio resource control connection request message; and determining the sum of the first time, the second time, and the third time as the time delay. By accurately measuring the time of each stage in the random access process, the time delay required for the entire process can be accurately evaluated, providing data support for adjusting the effective duration of the global satellite navigation system and ensuring effective synchronization between the user equipment and the non-terrestrial network of the Internet of Things.

[0049] After receiving the system information block, a timer is immediately started, and the timer is used to measure the time delay; the timer is terminated at the time point when the random access process is completed, and the time delay is recorded; the recorded time delay is stored in the local database of the user equipment. The above-mentioned first time, second time, and third time can also be obtained from the local database. By using the timer to measure the time delay, the execution of the random access process can be monitored in real time, providing accurate data basis for subsequent adjustment of the effective duration of the global satellite navigation system. At the same time, storing the time delay in the local database facilitates the management of device status and the analysis of historical data, contributing to the optimization and fault troubleshooting of the non-terrestrial network of the Internet of Things. For example, by analyzing the time delay records in the local database, network operators can identify the bottlenecks affecting the random access efficiency, and thus optimize the network configuration targetedly to improve the overall performance.

[0050] In some embodiments of the present application:

[0051] When the UE receives the System Information Block SIB31 containing the uplink synchronization validity duration cell (e.g., the ul-SyncValidityDuration-r17 cell), it immediately starts a dedicated timer, which is used to record the time consumed from receiving SIB31 to completing the random access procedure. From the moment the UE receives SIB31, record the time point when the random access preamble is sent. This time difference is the time from receiving SIB31 to sending the preamble, denoted as the first time. After the UE sends the preamble, it waits to receive the Random Access Response (RAR). Record the time point from when the UE sends the preamble to receiving the RAR. This time difference is the second time, representing the time consumed by the UE from sending the preamble to receiving the RAR. After receiving the RAR, the UE prepares and sends a Radio Resource Control (RRC) connection request message. Record the time point from receiving the RAR to sending the RRC connection request. This time difference is the third time, indicating the delay of the UE from receiving the RAR to sending the RRC connection request. When the UE finishes sending the RRC connection request message, terminate the above dedicated timer and record the timestamp at this time. The time delay is calculated as the end time of the timer minus the start time, which is the total time consumed for completing the random access procedure. The random access procedure is a mechanism that allows a User Equipment (UE) to establish an initial connection with the network or restore a lost connection. For the IoT NTN (Internet of Things in Non-Terrestrial Networks) environment, this process is particularly crucial because it involves time synchronization and frequency calibration between the UE and a satellite base station at a long distance to ensure the reliability and efficiency of subsequent data transmission. The random access procedure generally includes the following steps: sending a random access preamble, receiving a random access response (RAR), sending a connection request, and completing connection establishment. The calculated total time delay is stored in the local database of the UE for subsequent GNSS validity duration adjustment.

[0052] Step S206, adjust the reported GNSS validity duration according to the time delay to obtain the adjusted GNSS validity duration.

[0053] In the technical solution provided in step S206, the minimum value of the adjusted GNSS validity duration (the minimum value refers to the minimum value) is less than the minimum value of the uplink synchronization validity duration.

[0054] In the technical solution provided in step S206, there are various ways to adjust the effective duration of the global navigation satellite system (GNSS) to be reported according to the time delay to obtain the adjusted effective duration of the GNSS. For example, the user equipment evaluates the reliability in the random access process based on the uplink synchronization effective duration indicated by the field in the uplink synchronization effective duration cell, and obtains a reliability evaluation result. When the reliability evaluation result indicates that the uplink synchronization effective duration is not sufficient to cover the time required for the entire random access process, the user equipment adjusts the effective duration of the GNSS to be reported according to the time delay to obtain the adjusted effective duration of the GNSS, and sends a resynchronization request. The resynchronization request is used to ensure uplink synchronization between the user equipment and the Internet of Things non-terrestrial network within the adjusted effective duration of the GNSS. By evaluating the reliability of the random access process, the effective duration of the GNSS can be actively adjusted. When it is detected that the uplink synchronization effective duration may not be sufficient to cover the entire random access process, the user equipment will send a resynchronization request to ensure synchronization within the effective duration, avoiding synchronization failure caused by a too narrow time window, and improving the stability of the Internet of Things non-terrestrial network and the user experience. For example, in areas with poor satellite network coverage, by actively adjusting the effective duration, the probability of successful synchronization can be increased to ensure the continuity of data transmission.

[0055] It should be noted that there are various ways for the user equipment to adjust the effective duration of the GNSS to be reported according to the time delay to obtain the adjusted effective duration of the GNSS in the above steps. For example, obtain the uplink synchronization effective duration in the system information block; subtract the internal delay of the user equipment from the uplink synchronization effective duration to obtain a preliminary effective duration of the GNSS, where the internal delay of the user equipment includes the timing advance time and the time consumption of the Doppler frequency offset; subtract the time delay from the preliminary effective duration of the GNSS to obtain the adjusted effective duration of the GNSS. By accurately calculating and subtracting these three periods of time, it can be ensured that the adjusted GNSS effective duration more accurately reflects the time window during which the UE can rely on GNSS information for effective synchronization, which is particularly important for ensuring efficient and accurate synchronization between the UE and the network in the IoT NTN environment.

[0056] In some embodiments of the present application:

[0057] After receiving a system information block (e.g., SIB31) containing an uplink synchronization validity duration cell (e.g., ul-SyncValidityDuration-r17), the UE parses and evaluates the uplink synchronization validity duration. Based on this duration, the UE calculates whether it is sufficient to cover the time required for the entire random access procedure, including but not limited to Preamble transmission, RAR reception, RRC connection request transmission, and possible additional processing time. The UE can implement a simple algorithm to determine the reliability evaluation result: compare the uplink synchronization validity duration with the time delay measured in step S204. If the remaining validity duration after subtracting the time delay from the uplink synchronization validity duration is below a preset threshold (e.g., not sufficient to ensure the completion of the entire random access procedure), it is determined that the reliability of the random access procedure is insufficient. If the reliability evaluation result indicates that the uplink synchronization validity duration is not sufficient to cover all the time requirements of the random access procedure, the UE will send a resynchronization request to the network. This request can be sent together with the RRC message, and the request contains the adjusted GNSS validity duration to ensure that the UE can successfully complete the uplink synchronization with the satellite network within this duration. The resynchronization request may also include the requirement for additional time resources so that the UE can complete the synchronization operation within a more generous time window.

[0058] When adjusting the GNSS validity duration, the UE extracts the uplink synchronization validity duration carried by the ul-SyncValidityDuration-r17 cell from the received SIB31, which is the validity duration of the ephemeris information and the NTA information. The UE also needs to consider its own internal time delay, including the time consumption for calculating the Timing Advance (TA) and the Doppler frequency offset. These internal time delays can be estimated through historical data or device performance parameters. First, subtract the UE internal time delay from the uplink synchronization validity duration to obtain the preliminary GNSS validity duration. Then, further subtract the time delay measured in step S204 from the preliminary GNSS validity duration to obtain the final adjusted GNSS validity duration.

[0059] Another optional implementation: The UE can also implement a dynamic adjustment strategy to adjust the GNSS active duration regularly or on demand according to the current network conditions and location information. For example, when the UE is moving rapidly or at the network edge, more frequent adjustments may be required to adapt to the changing communication environment. Using the time delays and other relevant parameters (such as network configuration updates, UE moving speed, etc.) stored in the local database, the UE can make more accurate adjustments to the GNSS active duration, improving the random access success rate and overall communication quality. Referring to the value of the ul-SyncValidityDuration-r17 cell, the values of the above time delays, as well as the time consumption of the Timing Advance (TA for short) and Doppler frequency offset, are usually 2s. Then, the value of the adjusted GNSS-ValidityDuration-r17 cell is {s3, s8, s10, s13, s18, s20, s23, s28, s30, s33, s38, s40, s43, s48, s50, s53, s58...}, where s represents seconds. It can be seen that the minimum value of the adjusted GNSS-ValidityDuration-r17 cell is 3 seconds, and the minimum value of the adjusted GNSS-ValidityDuration-r17 cell is less than the minimum value of the uplink synchronization active duration (the minimum value refers to the minimum value).

[0060] Step S208: Report the radio resource control connection request message carrying the adjusted GNSS active duration to the non-terrestrial network of the Internet of Things.

[0061] In the technical solution provided in step S208, in order to optimize network resource allocation, the battery power status and power consumption of the user equipment can be determined; when reporting the second preset field carrying the adjusted GNSS active duration to the non-terrestrial network of the Internet of Things, the battery power status and power consumption of the user equipment are carried at the same time, where the battery power status and power consumption of the user equipment are used to instruct the non-terrestrial network of the Internet of Things to perform parameter adjustment according to the battery power status and power consumption of the user equipment, optimizing network resource allocation. By reporting the battery power status and power consumption of the user equipment, the non-terrestrial network of the Internet of Things can optimize resource allocation according to the actual status of the device. For example, for a device with a low battery level, the network can preferentially allocate resources to ensure that it can complete the random access process in time. At the same time, by adjusting communication parameters such as power control and frequency band selection, power consumption can be reduced, the battery life of the device can be extended, and the user experience and overall performance of the network are improved.

[0062] In some embodiments of the present application:

[0063] UE devices regularly monitor their battery charge status and current power consumption. This information can be obtained through the power management module and power consumption monitoring mechanism inside the device. The monitoring frequency can be dynamically adjusted according to the device status and network requirements. For example, in the case of low battery charge or high power consumption, the monitoring frequency should be higher to update the network in a timely manner. After adjusting the effective duration of the Global Navigation Satellite System (GNSS), the UE integrates the adjusted duration information, along with the battery charge status and power consumption, into the Radio Resource Control (RRC) connection request message (the RRC connection request message can specifically be defined as any one of the RRC connection setup complete message, RRC connection reconfiguration complete message, RRC connection re-establishment complete message, and RRC connection resume complete message. However, the GNSS-ValidityDuration-r17 information element is mandatory in the RRC connection setup complete message and optional in the other three). This is achieved by adding or modifying existing information elements (IEs) in the RRC message. For example, a new information element can be defined that contains fields representing the remaining battery charge percentage and the current power consumption level. The battery charge status and power consumption of the device can be encoded into specific information elements, which need to comply with the encoding rules of 3GPP (or other applicable standards) for easy parsing and processing on the network side.

[0064] The UE sends the RRC connection request message carrying the adjusted GNSS effective duration, as well as the battery charge and power consumption status, to the Internet of Things Non-Terrestrial Network (IoT NTN) through its uplink. This step is completed in the final stage of the random access procedure, that is, after successfully receiving the Random Access Response (RAR), the UE sends the RRC connection request to the target network. After receiving the RRC connection request message from the UE, the IoT NTN parses the GNSS effective duration, battery charge status, and power consumption information carried in it. Based on this information, the network side (i.e., the IoT NTN side) can optimize resource allocation, such as priority adjustment, power control strategy modification, frequency band selection, etc., to adapt to the actual status of the UE. For UEs with low battery charge, the IoT NTN may preferentially allocate resources to ensure that they can complete the random access procedure in a timely manner, while adjusting communication parameters to reduce power consumption, such as by reducing the UE transmission power or selecting a low-power consumption frequency band for communication. The IoT NTN network responds to the UE's requirements by adjusting the uplink parameters according to the UE's battery charge status and power consumption. This may include adjusting the TA timing window, sending power control instructions, providing communication strategies more suitable for low-power devices, etc. The response from the network side can be immediate or can be adjusted in the next system information update cycle or at the RRC reconfiguration opportunity.

[0065] Through the technical solution of the present application, the user equipment can adjust the reported value of the effective duration of the global satellite navigation system according to the actual time required for the random access process, ensuring that the random access is completed within the limited uplink synchronization effective duration, avoiding the uplink synchronization failure caused by time delay, and improving the synchronization efficiency and data transmission reliability of the Internet of Things non-terrestrial network. The problem of the conflict between the effective duration of the global satellite navigation system and the uplink synchronization effective duration is solved. For example, in satellite communication, considering the signal transmission delay, the user equipment can accurately calculate the time delay and adjust the effective duration of the global satellite navigation system accordingly, effectively avoiding the expiration of the synchronization window and ensuring the timely transmission of data.

[0066] The embodiment of the present application also provides a flowchart of another method for reporting the effective duration, as Figure 3As shown in the figure, the process of reporting the valid duration in the related art is presented. First, the user equipment (UE) reads broadcast messages such as SIB1 (carrying ephemeris, NTA, and its valid duration). Then, the UE calculates the TA and Doppler spectrum and performs pre-compensation. Next, the UE goes through the random access process. In the last RRC connection establishment completion message during the random access process, the UE reports the GNSS valid duration to the NW (i.e., the Network, referring to the communication network). This GNSS valid duration is not adjusted and there will be the technical problems proposed in this application. The GNSS valid duration reported by the UE depends on the uplink synchronization valid duration broadcast by System Information Block Type 31 (abbreviated as SIB31). The former value should be less than the latter value. However, the minimum value of the GNSS-ValidityDuration-r17 cell is 10 seconds, which is larger than the minimum value of 5 seconds of the Uplink Synchronization Validity Duration (Release 17) (abbreviated as ul-SyncValidityDuration-r17) cell carrying the uplink synchronization valid duration in SIB31. When the uplink synchronization valid duration broadcast by the IoT NTN network through SIB31 is between 5 seconds and 10 seconds, since the minimum value of the GNSS-ValidityDuration-r17 cell is 10 seconds, the UE cannot report a duration less than 10 seconds when reporting the GNSS valid duration. This results in a mismatch between the valid duration reported by the UE and the uplink synchronization valid duration broadcast by the network. This application optimizes the process in the related art. By determining the time delay from receiving the system information block to completing the random access process and adjusting the reported Global Navigation Satellite System (GNSS) valid duration based on the time delay, the adjusted GNSS valid duration is obtained. Among them, the minimum value of the adjusted GNSS valid duration is less than the minimum value of the uplink synchronization valid duration, solving this problem and effectively avoiding the problem of valid time conflicts, ensuring the timely transmission of data.

[0067] The embodiment of this application also provides a schematic structural diagram of a device for reporting the valid duration, as Figure 4 shown, including:

[0068] A receiving module 402, configured to receive, by the user equipment, a system information block containing the uplink synchronization valid duration, where the uplink synchronization valid duration is used to indicate the valid duration of ephemeris information and network time adjustment information.

[0069] A determining module 404, configured to determine the time delay from receiving the system information block to completing the random access process.

[0070] The determination module 404 is further configured to obtain a first time from receiving the system information block to transmitting the random access preamble sequence; obtain a second time from transmitting the random access preamble sequence to receiving the random access response; obtain a third time from receiving the random access response to transmitting the radio resource control connection request message; and determine the sum of the first time, the second time, and the third time as the time delay.

[0071] The adjustment module 406 is configured to adjust the reported effective duration of the global navigation satellite system according to the time delay to obtain an adjusted effective duration of the global navigation satellite system, where the minimum value of the adjusted effective duration of the global navigation satellite system is less than the minimum value of the uplink synchronization effective duration.

[0072] The adjustment module 406 is further configured to evaluate the reliability in the random access procedure based on the uplink synchronization effective duration indicated by the field in the uplink synchronization effective duration cell to obtain a reliability evaluation result; when the reliability evaluation result indicates that the uplink synchronization effective duration is not sufficient to cover the time required for the entire random access procedure, the user equipment adjusts the reported effective duration of the global navigation satellite system according to the time delay to obtain an adjusted effective duration of the global navigation satellite system, and sends a resynchronization request, where the resynchronization request is used to ensure that the uplink synchronization between the user equipment and the non-terrestrial network of the Internet of Things is completed within the adjusted effective duration of the global navigation satellite system.

[0073] The adjustment module 406 is further configured to obtain the uplink synchronization effective duration in the system information block; subtract the internal delay of the user equipment from the uplink synchronization effective duration to obtain a preliminary effective duration of the global navigation satellite system, where the internal delay of the user equipment includes the timing advance time and the time consumption of the Doppler frequency offset; and subtract the time delay from the preliminary effective duration of the global navigation satellite system to obtain an adjusted effective duration of the global navigation satellite system.

[0074] The reporting module 408 is configured to report a radio resource control connection request message carrying the adjusted effective duration of the global navigation satellite system to the non-terrestrial network of the Internet of Things.

[0075] It should be noted that Figure 4 the device for reporting the effective duration shown is used to execute Figure 2 the method for reporting the effective duration shown, so Figure 2 the relevant explanations in the method for reporting the effective duration in

[0076] It should be noted that each module in the above device for reporting the effective duration can be a program module (for example, a set of program instructions that implement a specific function), or a hardware module. For the latter, it can be presented in the following forms, but not limited to: the manifestation of each of the above modules is a processor, or the functions of each of the above modules are implemented by a processor.

[0077] The embodiment of the present application also provides a non-volatile storage medium. The non-volatile storage medium includes a stored program. When the program runs, it controls the device where the non-volatile storage medium is located to execute the above method for reporting the effective duration. For example, the user equipment receives a system information block including the uplink synchronization effective duration, and the uplink synchronization effective duration is used to indicate the effective duration of ephemeris information and network time adjustment information; determines the time delay from receiving the system information block to completing the random access process; adjusts the reported global satellite navigation system effective duration according to the time delay to obtain an adjusted global satellite navigation system effective duration, where the minimum value of the adjusted global satellite navigation system effective duration is less than the minimum value of the uplink synchronization effective duration; and reports a radio resource control connection request message carrying the adjusted global satellite navigation system effective duration to the non-terrestrial network of the Internet of Things.

[0078] The embodiment of the present application also provides an electronic device. The electronic device includes a processor, and the processor is used to run a program. When the program runs, it executes the above method for reporting the effective duration. For example, the user equipment receives a system information block including the uplink synchronization effective duration, and the uplink synchronization effective duration is used to indicate the effective duration of ephemeris information and network time adjustment information; determines the time delay from receiving the system information block to completing the random access process; adjusts the reported global satellite navigation system effective duration according to the time delay to obtain an adjusted global satellite navigation system effective duration, where the minimum value of the adjusted global satellite navigation system effective duration is less than the minimum value of the uplink synchronization effective duration; and reports a radio resource control connection request message carrying the adjusted global satellite navigation system effective duration to the non-terrestrial network of the Internet of Things.

[0079] According to another aspect of the embodiments of the present application, there is also provided a computer program product, including a computer program which, when executed by a processor, implements the method for reporting the effective duration as described above. For example, a user equipment receives a system information block including an uplink synchronization effective duration, where the uplink synchronization effective duration is used to indicate the effective duration of ephemeris information and network time adjustment information; determines a time delay from receiving the system information block until the random access procedure is completed; adjusts the reported global satellite navigation system effective duration according to the time delay to obtain an adjusted global satellite navigation system effective duration, where the minimum value of the adjusted global satellite navigation system effective duration is less than the minimum value of the uplink synchronization effective duration; and reports a radio resource control connection request message carrying the adjusted global satellite navigation system effective duration to the Internet of Things non-terrestrial network.

[0080] In the above embodiments of the present application, the descriptions of the respective embodiments have their own emphases. For parts not detailed in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

[0081] In several embodiments provided by the present application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are merely illustrative. For example, the division of the units can be a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of units or modules can be in an electrical or other form.

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

[0083] In addition, the functional units in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0084] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the related technology, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The foregoing storage medium includes: various media that can store program codes, such as USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks, or optical discs.

[0085] The foregoing are only the preferred embodiments of this application. It should be noted that for those of ordinary skill in the art, without departing from the principle of this application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of this application.

Claims

1. A method for reporting effective duration, characterized in that, including: The user equipment receives a system information block including an uplink synchronization valid duration, which is used to indicate the valid duration of ephemeris information and network time adjustment information; determine the time delay from receiving the system information block until the random access procedure is completed; adjust the reported valid duration of the global satellite navigation system according to the time delay to obtain an adjusted valid duration of the global satellite navigation system, wherein the minimum value of the adjusted valid duration of the global satellite navigation system is less than the minimum value of the uplink synchronization valid duration; report a radio resource control connection request message carrying the adjusted valid duration of the global satellite navigation system to the Internet of Things non-terrestrial network.

2. The method according to claim 1, wherein The system information block carries an uplink synchronization valid duration cell and does not carry an epoch time cell. When the system information block does not carry the epoch time cell, the minimum value of the uplink synchronization valid duration in the system information block is less than the minimum value of the valid duration of the global satellite navigation system, wherein the uplink synchronization valid duration cell is used to indicate the uplink synchronization valid duration, and the epoch time cell is used to specify the starting time point of the uplink synchronization valid duration and is an optional cell.

3. The method according to claim 1, wherein The time delay is determined in the following manner: obtain a first time from receiving the system information block to sending a random access preamble; obtain a second time from sending the random access preamble to receiving a random access response; obtain a third time from receiving the random access response to sending a radio resource control connection request message; determine the sum of the first time, the second time, and the third time as the time delay.

4. The method according to claim 2, wherein The adjusting the reported valid duration of the global satellite navigation system according to the time delay to obtain an adjusted valid duration of the global satellite navigation system includes: The user equipment evaluates the reliability in the random access procedure based on the uplink synchronization valid duration indicated by the field in the uplink synchronization valid duration cell to obtain a reliability evaluation result; When the reliability evaluation result indicates that the uplink synchronization valid duration is not sufficient to cover the time required for the entire random access procedure, the user equipment adjusts the reported valid duration of the global satellite navigation system according to the time delay to obtain the adjusted valid duration of the global satellite navigation system and sends a resynchronization request, wherein the resynchronization request is used to ensure that the uplink synchronization between the user equipment and the Internet of Things non-terrestrial network is completed within the adjusted valid duration of the global satellite navigation system.

5. The method according to claim 4, characterized in that, The user equipment adjusts the reported valid duration of the global satellite navigation system according to the time delay to obtain the adjusted valid duration of the global satellite navigation system, including: obtain the uplink synchronization valid duration in the system information block; subtract the internal delay of the user equipment from the uplink synchronization valid duration to obtain a preliminary valid duration of the global satellite navigation system, wherein the internal delay of the user equipment includes timing advance time and time consumption of Doppler frequency offset; Subtract the time delay from the effective duration of the preliminary global satellite navigation system to obtain the adjusted effective duration of the global satellite navigation system.

6. The method according to claim 1, characterized in that The method further includes: Immediately start a timer after receiving the system information block, where the timer is used to measure the time delay; Terminate the timer at the time point when the random access procedure is completed and record the time delay; Store the recorded time delay in the local database of the user equipment.

7. The method according to claim 1, wherein The method further includes: Determine the battery power status and power consumption of the user equipment; When reporting the second preset field carrying the adjusted effective duration of the global satellite navigation system to the Internet of Things non-terrestrial network, also carry the battery power status and power consumption of the user equipment, where the battery power status and power consumption of the user equipment are used to instruct the Internet of Things non-terrestrial network to perform parameter adjustment according to the battery power status and power consumption of the user equipment to optimize network resource allocation.

8. A device for reporting the effective duration, characterized in that, It includes: A receiving module, configured to receive, by the user equipment, a system information block including an uplink synchronization effective duration, where the uplink synchronization effective duration is used to indicate the effective duration of ephemeris information and network time adjustment information; A determination module, configured to determine the time delay from receiving the system information block to the completion of the random access procedure; An adjustment module, configured to adjust the reported effective duration of the global satellite navigation system according to the time delay to obtain the adjusted effective duration of the global satellite navigation system, where the adjusted effective duration of the global satellite navigation system is less than the uplink synchronization effective duration; A reporting module, configured to report a radio resource control connection request message carrying the adjusted effective duration of the global satellite navigation system to the Internet of Things non-terrestrial network.

9. A non-volatile storage medium, characterized in that, A program is stored in the non-volatile storage medium, where when the program runs, it controls the device where the non-volatile storage medium is located to execute the method for reporting the effective duration according to any one of claims 1 to.

10. An electronic device, characterized in that, It includes: A memory and a processor, where the processor is configured to run the program stored in the memory, and when the program runs, it executes the method for reporting the effective duration according to any one of claims 1 to.

11. A computer program product comprising computer instructions, characterized in that, When the computer instruction is executed by the processor, it implements the method for reporting the effective duration according to any one of claims 1 to.

Images