Device control method, and device and storage medium

Abstract

Provided in the present application are a device control method, and a device and a storage medium. The method comprises: a terminal device controlling by means of a first condition or a second condition the cancellation of triggered first reporting, wherein the first reporting is the reporting of a global navigation satellite system (GNSS) availability time, the first condition is a first medium access control (MAC) protocol data unit (PDU) not being transmitted by means of Msg3, the second condition is the first MAC PDU being transmitted by means of Msg3 in a random access process and the random access process being successful, the first MAC PDU is transmitted on an uplink channel, and the first MAC PDU includes a GNSS availability time report MAC control unit (CE).

Description

Device control method, device, and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a device control method and device, and a storage medium. Background Art

[0002] The random access procedure is a fundamental and important process in communications systems. Its objectives include establishing uplink synchronization, establishing a unique terminal identifier (Cell Radio Network Temporary Identifier, C-RNTI), and requesting the network to allocate uplink resources to the terminal. Therefore, the random access procedure is not only used for initial access, but also for accessing a new cell during handover, accessing after a radio link failure, and restoring uplink synchronization during uplink / downlink data transmission.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a device control method, a device, and a storage medium.

[0005] The device control method provided in the embodiment of the present application includes:

[0006] The terminal device controls the cancellation of a first report triggered by a first condition or a second condition, where the first report is a report of the effective time of the global navigation satellite system (GNSS); the first condition is that the first medium access control (MAC) protocol data unit (PDU) is not transmitted through message 3, and the second condition is that the first MAC PDU is transmitted through message 3 in a random access process and the random access process is successful, the first MAC PDU is transmitted on an uplink channel, and the first MAC PDU includes a GNSS effective time reporting MAC control unit (CE).

[0007] The terminal device provided in the embodiment of the present application includes:

[0008] A control unit is configured to control the cancellation of a triggered first report through a first condition or a second condition, wherein the first report is a report of the effective time of the global satellite navigation system GNSS; the first condition is that the first medium access control MAC protocol data unit PDU is not transmitted through message 3, and the second condition is that the first MAC PDU is transmitted through message 3 during the random access process and the random access process is successful, the first MAC PDU is transmitted on an uplink channel, and the first MAC PDU includes a GNSS effective time reporting MAC control unit CE.

[0009] The communication device provided in the embodiment of the present application may be the terminal device in the above-mentioned solution, and the communication device includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned device control method.

[0010] The chip provided in the embodiment of the present application is used to implement the above-mentioned device control method.

[0011] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned device control method.

[0012] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned device control method.

[0013] The computer program product provided in the embodiments of the present application includes computer program instructions, which enable a computer to execute the above-mentioned device control method.

[0014] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned device control method.

[0015] Through the above technical solution, the terminal device controls the cancellation of the triggered GNSS valid time reporting by judging whether the terminal device successfully executes the first condition or the second condition for reporting the GNSS valid time, thereby effectively controlling the cancellation of the GNSS valid time reporting and avoiding inconsistent understanding between the network device and the terminal device regarding the validity of the GNSS measurement. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application;

[0018] FIG2 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0019] FIG3 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0020] FIG4 is a schematic diagram of a non-terrestrial communication network (NTN) scenario based on a transparent transmission and forwarding satellite according to an embodiment of the present application;

[0021] FIG5 is a schematic diagram of an NTN scenario based on a regenerative forwarding satellite according to an embodiment of the present application;

[0022] FIG6 is a schematic diagram of an optional flow chart of four-step random access provided in an embodiment of the present application;

[0023] FIG7 is a schematic diagram of an optional flow chart of two-step random access provided in an embodiment of the present application;

[0024] FIG8 is an optional flowchart of a device control method provided in an embodiment of the present application;

[0025] FIG9 is an optional flow chart of a device control method provided in an embodiment of the present application;

[0026] FIG10 is an optional flow chart of a device control method provided in an embodiment of the present application;

[0027] FIG11 is an optional flow chart of a device control method provided in an embodiment of the present application;

[0028] FIG12 is a schematic diagram of an optional structure of a terminal device provided in an embodiment of the present application;

[0029] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0030] FIG14 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0031] FIG15 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0033] Communication system scenarios include terrestrial networks (TNs) and NTNs. NTNs typically use satellite communications to provide communication services to terrestrial users. Currently, NTN systems include NR-NTN and IoT-NTN, and other NTN systems may be added in the future.

[0034] Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application. As shown in Figure 1, communication system 100 may include terminal device 110 and network device 120. Network device 120 may communicate with terminal device 110 via an air interface. Multi-service transmission is supported between terminal device 110 and network device 120.

[0035] It should be understood that the embodiments of the present application are only illustrative of the communication system 100, but the embodiments of the present application are not limited thereto. That is, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems.

[0036] In the communication system 100 shown in Figure 1, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area and may communicate with the terminal device 110 (eg, UE) located within the coverage area.

[0037] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0038] The terminal device 110 can be used for device-to-device (D2D) communication.

[0039] The functional units in the communication system 100 may also establish connections and implement communication via next generation (NG) network interfaces.

[0040] Figure 1 exemplarily shows a base station, a core network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include other numbers of terminal devices within its coverage area, which is not limited in this embodiment of the present application.

[0041] NTN uses satellite communications to provide communications services to terrestrial users. Compared to terrestrial cellular networks, satellite communications offer many unique advantages. First, satellite communications are not restricted by user location. For example, conventional terrestrial communications cannot cover areas such as oceans, high mountains, and deserts where communications equipment cannot be deployed or where there is a sparse population. However, satellite communications, because a single satellite can cover a large area and orbits the Earth, theoretically every corner of the globe can be covered. Second, satellite communications have significant social value. Satellite communications can provide low-cost coverage in remote mountainous areas and poor, underdeveloped countries and regions, enabling people in these areas to enjoy advanced voice communications and mobile internet technologies, helping to narrow the digital divide with developed regions and promoting their development. Third, satellite communications offer long range, and the cost of communications does not increase significantly with increasing distance. Finally, satellite communications are highly stable and unaffected by natural disasters.

[0042] NTN technology can be combined with various communication systems. For example, NTN technology can be combined with the NR system to form an NR-NTN system. Another example is that NTN technology can be combined with the Internet of Things (IoT) system to form an IoT-NTN system. IoT-NTN systems can include NB-IoT-NTN systems and eMTC-NTN systems.

[0043] FIG2 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0044] As shown in Figure 2, a terminal device 201 and a satellite 202 are included, and wireless communication can be performed between the terminal device 201 and the satellite 202. The network formed between the terminal device 201 and the satellite 202 can also be referred to as an NTN. In the architecture of the communication system shown in Figure 2, the satellite 202 can have the function of a base station, and the terminal device 201 and the satellite 202 can communicate directly. In the system architecture, the satellite 202 can be referred to as a network device. In some embodiments of the present application, the communication system can include multiple network devices 1102, and each network device 1102 can include a different number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0045] FIG3 is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application.

[0046] As shown in Figure 3, it includes a terminal device 201, a satellite 202 and a base station 203. Wireless communication can be carried out between the terminal device 201 and the satellite 202, and communication can be carried out between the satellite 202 and the base station 203. The network formed between the terminal device 201, the satellite 202 and the base station 203 can also be referred to as an NTN. In the architecture of the communication system shown in Figure 3, the satellite 202 may not have the function of a base station, and the communication between the terminal device 201 and the base station 203 needs to be transferred through the satellite 202. In this system architecture, the base station 203 can be referred to as a network device. In some embodiments of the present application, the communication system may include multiple base stations 203, and each base station 203 may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application. The base station 203 can be the network device 120 in Figure 1.

[0047] It should be understood that the satellites 202 include, but are not limited to, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, geostationary Earth orbit (GEO) satellites, and high elliptical orbit (HEO) satellites. Satellites can use multiple beams to cover the ground. For example, a satellite can form dozens or even hundreds of beams to cover the ground. In other words, a single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers, thereby ensuring satellite coverage and improving the system capacity of the entire satellite communication system.

[0048] In order to ensure satellite coverage and improve the system capacity of the entire satellite communication system, satellites use multiple beams to cover the ground. A satellite can form dozens or even hundreds of beams to cover the ground; a satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0049] It should be noted that Figures 1 to 3 illustrate the systems to which this application applies only by way of example. The methods described in the embodiments of this application are also applicable to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the associated objects are in an "or" relationship. It should also be understood that the term "indication" in the embodiments of this application can be direct, indirect, or indicate an associated relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; or it can mean that A and B have an associated relationship. It should also be understood that the term "corresponding" in the embodiments of this application can mean that two objects have a direct or indirect correspondence relationship, an associated relationship, or a relationship between an indicator and the indicated, a configuration and the configured, and so on. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit its specific implementation method. For example, predefined can refer to a definition in a protocol. It should also be understood that in the embodiments of the present application, the “protocol” can refer to a standard protocol in the field of communications, such as an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0050] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0051] Satellites can be categorized as either transparent payload or regenerative payload based on their functionality. Transparent payload satellites only provide radio frequency filtering, frequency conversion, and amplification, transparently forwarding signals without altering the waveform of the signal being forwarded. Regenerative payload satellites, in addition to providing radio frequency filtering, frequency conversion, and amplification, can also provide demodulation / decoding, routing / conversion, and encoding / modulation, embodying some or all of the functions of a base station.

[0052] An NTN network may include one or more gateways, feeder links, service links, satellites, and inter-satellite links (ISLs). Gateways facilitate communication between satellites and terrestrial public networks, between gNBs on satellites and the core network, or between gNB distributed units (DUs) on satellites and gNB central units (CUs) on the ground. Feeder links are the communication links between gateways and satellites. Service links are the communication links between terminal devices and satellites. Satellites can be categorized into transparent forwarding and regenerative forwarding based on their functionality. Transparent forwarding provides only radio frequency filtering, frequency conversion, and amplification, transparently forwarding signals without altering the waveform of the forwarded signal. Regenerative forwarding, in addition to radio frequency filtering, frequency conversion, and amplification, can also provide demodulation / decoding, routing / conversion, and encoding / modulation, emulating some or all of the functions of a base station. Inter-satellite links are the communication links between satellites in a regenerative forwarding network architecture.

[0053] FIG4 and FIG5 are schematic diagrams showing NTN scenarios based on transparent forwarding satellites and regenerative forwarding satellites, respectively.

[0054] As shown in Figure 4 , for an NTN scenario based on transparent forwarding satellites, gateway 401 and satellite 402 communicate via a feeder link, and satellite 402 and terminal 403 can communicate via a service link. Gateway 401 is connected to data network 404. As shown in Figure 5 , for an NTN scenario based on regenerative forwarding satellites, satellites 402 and 405 communicate via an inter-satellite link, gateway 401 and satellite 402 or satellite 405 communicate via a feeder link, and satellite 402 and terminal 403 can communicate via a service link.

[0055] LTE random access process

[0056] In the LTE system, the random access process can be triggered by the following events:

[0057] Establishing a wireless connection when the UE initially accesses: The UE changes from the idle state (i.e., RRC_IDLE state) of the Radio Resource Control (RRC) to the connected state (i.e., RRC_CONNECTED state); wherein, in the RRC_IDLE state, no RRC connection is established, and in the RRC_CONNECTED state, an RRC connection is established;

[0058] RRC connection reestablishment process: to enable the UE to reestablish the radio connection after a radio link failure;

[0059] Handover: The UE needs to establish uplink synchronization with the new cell;

[0060] In the RRC_CONNECTED state, downlink (DL) data arrives, and the uplink (UL) is out of synchronization.

[0061] In the RRC_CONNECTED state, UL data arrives, and the UL is out of synchronization or there are no Physical Uplink Control Channel (PUCCH) resources for sending a Scheduling Request (SR);

[0062] SR failed;

[0063] Synchronous reconfiguration request from RRC.

[0064] In the related art, the following two random access modes are supported: a contention-based random access mode shown in FIG. 2 and a non-contention-based random access mode shown in FIG. 3 .

[0065] The contention-based random access process, as shown in Figure 2, includes the following four steps:

[0066] In step S601, the terminal device sends a random access preamble (Preamble) to the network device via message 1 (Msg1).

[0067] The terminal device selects a physical random access channel (PRACH) resource and sends the selected preamble on the selected PRACH resource; based on the preamble, the base station can estimate the uplink timing and the size of the uplink grant required by the terminal device to transmit Msg3.

[0068] Step S602: The network device sends message 2 (message 2, Msg2) to the terminal device.

[0069] After the network device detects that a terminal device has sent a Preamble, it sends a Random Access Response (RAR) to the terminal device through Msg2 to inform the terminal device of the uplink resource information that can be used when sending Msg3, allocate a temporary Radio Network Temporary Identity (RNTI) to the terminal device, and provide the terminal device with a time advance command (time advance command), etc.

[0070] After sending Msg1, the terminal device opens a RAR time window (ra-ResponseWindow) and monitors the physical downlink control channel (PDCCH) scrambled by the random access RNTI (RA-RNTI) within the RAR time window. In LTE, the calculation formula of RA-RNTI is shown in the following formula (1): RA_RNTI = 1 + t_id + 10 * f_id Formula (1);

[0071] Among them, t_id is the first subframe index (index) of PRACH transmission (0≤t_id<10); f_id is the frequency domain index corresponding to PRACH in the subframe (0≤f_id<6); among them, PRACH resources are numbered in order from low to high in the frequency domain.

[0072] For eMTC UE, RA-RNTI is calculated as shown in the following formula (2): RA_RNTI=1+t_id+10*f_id+60*(SFN_id mod(Wmax / 10)) Formula (2);

[0073] Where t_id is the index of the first subframe transmitted by the PRACH (0≤t_id<10); f_id is the frequency domain index corresponding to the PRACH in this subframe (0≤f_id<6); PRACH resources are numbered sequentially in the frequency domain from low to high. SFN_id is the system frame number (SFN) of the first PRACH transmission. Wmax is the maximum RAR window length supported by eMTC, which is 400 subframes.

[0074] For NB-IoT UE, RA-RNTI is calculated as shown in the following formula (3): RA_RNTI=1+floor(SFN_id / 4)+256*carrier_id Formula (3);

[0075] SFN_id is the first SFN index of PRACH transmission, carrier_id is the UL carrier index corresponding to PRACH transmission, and the carrier identifier (carrier_id) corresponding to the anchor carrier is 0.

[0076] For NB-IoT UE in TDD mode, the calculation of RA-RNTI is shown in the following formula (4): RA_RNTI=1+floor(SFN_id / 4)+256*(H_SFN mod 2) Formula (4);

[0077] SFN_id is the first SFN index transmitted by PRACH, and H_SFN is the first hyperframe system frame number (H-SFN) transmitted by PRACH.

[0078] From the above RA-RNTI calculation formula, it can be seen that RA-RNTI is related to the PRACH time-frequency resources used by the UE to send Msg1.

[0079] After the terminal device successfully receives the RA-RNTI-scrambled PDCCH, it can obtain the Physical Downlink Shared Channel (PDSCH) scheduled by the PDCCH. Among them, the PDCCH contains the RAR, which specifically contains the following information: subheader, RAPID, payload, uplink (UL) grant and Temporary cell RNTI (Cell RNTI, C-RNTI); among them, the RAR subheader contains the BI, which is used to indicate the backoff time for retransmitting Msg1; the RAPID in the RAR is the preamble index received by the network response; the RAR payload contains the TAG, which is used to adjust the uplink timing; the UL grant is used to schedule the uplink resource indication of Msg3; Temporary C-RNTI: used to scramble the PDCCH of Msg4 (initial access).

[0080] If the terminal device receives a PDCCH scrambled by RAR-RNTI and the RAR contains the preamble index sent by itself, the terminal device considers that the random access response has been successfully received.

[0081] Step S603: The terminal device sends Msg3 in the uplink resources specified by the RAR message.

[0082] Msg3 is primarily used to inform the network device of the event that triggered the RACH process. For example, if it is an initial random access event, the Msg3 will carry the terminal device ID and establishment cause; if it is an RRC reestablishment event, the Msg3 will carry the terminal device ID and establishment cause in the connected state.

[0083] At the same time, the ID carried in Msg3 can resolve the contention conflict in step S204.

[0084] Step S604: The network device sends Msg4 to the terminal device.

[0085] Msg4 includes a contention resolution message and allocates uplink transmission resources to the terminal device.

[0086] Msg4 has two functions: one is to resolve contention conflicts, and the other is for the network to transmit RRC configuration messages to the terminal. There are two ways to resolve contention conflicts: one is that if the UE carries C-RNTI in Msg3, Msg4 uses C-RNTI to scramble the PDCCH carrying Msg4. The other is that if the UE does not carry C-RNTI in Msg3, such as initial access, the temporary cell radio network temporary identifier (Temporary C-RNTI, TC-RNTI) is used to scramble the PDCCH. The conflict is resolved by the UE receiving the PDSCH of Msg4 and matching the common control channel (CCCH) service data unit (SDU) in the PDSCH.

[0087] When the terminal device receives Msg4 sent by the network device, it will detect whether the terminal device specific temporary identifier (TC-RNTI or C-RNTI) sent by the terminal device in Msg3 is included in the contention resolution message sent by the base station. If it is included, it indicates that the random access process of the terminal device is successful. Otherwise, it is considered that the random process has failed, and the terminal device needs to initiate the random access process again from the first step.

[0088] The process of the non-contention-based random access method is shown in Figure 7 and includes the following three steps:

[0089] Step S701: The network device sends an allocated random access Preamble to the terminal device.

[0090] Step S702: The terminal device sends a random access Preamble to the network device via Msg1.

[0091] Based on non-contention random access, PRACH time domain resources and preamble can be specified by the network device.

[0092] Step S703: The network device sends Msg2 to the terminal device.

[0093] After the network device detects that a terminal device has sent a Preamble, it sends a RAR to the terminal device through Msg2.

[0094] After the terminal device sends Msg1, it opens a random access response time window and monitors the RA-RNTI scrambled PDCCH within the random access response time window. For the description of the random access response, please refer to the description in step S202.

[0095] For non-contention-based random access, the random access process ends after the terminal device successfully receives Msg2.

[0096] In IoT NTN (i.e., scenarios where NB-IoT and eMTC are connected to NTN), the Global Navigation Satellite System (GNSS) measurement module and communication module of the IoT terminal cannot operate simultaneously (Simultaneous GNSS and NTN NINACTIVEB-IoT / eMTC operation is not assumed). In NTN, IoT terminals can only perform GNSS measurements to obtain location information in RRC IDLE or RRC INACTIVE states, and the GNSS module cannot be activated in RRC connected state. Therefore, the UE must first obtain its own GNSS position using the GNSS module before entering the RRC connected state. The UE can determine the validity period of the GNSS position based on its own conditions (such as the UE's mobility) and report the remaining validity period of the GNSS position to the network during RRC connection establishment / RRC re-establishment / RRC connection recovery. For a UE in the RRC connected state, if its GNSS position expires, since the UE cannot perform GNSS operations in the RRC connected state, the UE cannot perform timing advance (TA) compensation based on a valid GNSS position, and therefore needs to return to the RRC IDLE state.

[0097] In the IoT NTN enhancement, IoT terminals connected to the NTN will be able to perform GNSS measurements in the RRC connected state. However, the UE's GNSS measurement module and communication module cannot be operated simultaneously. To address this, the following two trigger mechanisms are introduced for GNSS measurements of connected UEs:

[0098] Trigger mechanism 1. GNSS measurement triggered by the base station: The base station triggers the UE to perform GNSS measurement by sending a GNSS measurement MAC CE. After receiving the MAC CE, the UE performs GNSS measurement within a given gap period.

[0099] Trigger mechanism 2: UE-autonomously triggered GNSS measurement: The UE can perform GNSS measurement in the DRX inactive state (whether and when to trigger depends on the UE implementation), or the UE starts a timer when the GNSS position fails, and the UE performs GNSS measurement during the timer.

[0100] If the UE completes the GNSS measurement during the gap period or while the timer is running, the UE reports the validity period of the GNSS position obtained this time to the base station through the MAC CE (i.e., GNSS validity duration reporting). On the one hand, it notifies the base station that the UE has completed the GNSS measurement so that the base station can resume communication with the UE; on the other hand, it can assist the base station in deciding to trigger the UE to perform GNSS measurement before the GNSS position expires.

[0101] In the related art, for GNSS valid time reporting, according to the current protocol, a UE in an RRC connected state triggers a GNSS valid time reporting after each GNSS measurement is completed. For GNSS valid time reporting that has been triggered and not canceled, if the UE has a physical uplink shared channel (PUSCH) resource available for new transmission in the current TTI and the PUSCH resource can carry a GNSS valid time reporting MAC CE (GNSS Validity Duration Report MAC control element), the UE uses the PUSCH resource to report the GNSS valid time reporting; otherwise, the UE triggers random access. When the UE sends a MAC PDU and the MAC PDU contains a GNSS valid time reporting MAC CE, the UE cancels all GNSS valid time reporting. The current mechanism has the following two problems:

[0102] 1. If the UE triggers the random access process due to the lack of PUSCH resources for transmitting the GNSS valid time reporting MAC CE, and the UE transmits the GNSS valid time reporting MAC CE through Msg3 PUSCH during the random access process, due to the risk of conflict in the random access process, if the UE cancels the GNSS valid time reporting after completing the Msg3 PUSCH transmission, and the UE subsequently fails to resolve the contention, and since the completion of GNSS measurement is the only condition for the UE to trigger the GNSS valid time reporting, the UE will not have the opportunity to trigger the GNSS valid time reporting again until the current GNSS position expires. The base station does not know when the UE's GNSS position will expire and therefore does not know when to trigger the UE to perform GNSS measurement.

[0103] 2. Based on the current protocol, for a UE that triggers GNSS effective time reporting, the UE will determine whether there is a PUSCH resource that can transmit the GNSS effective time reporting MAC CE in each TTI. If not, random access will be triggered, which will cause the UE to frequently trigger unnecessary random access procedures.

[0104] Therefore, the above problems need to be solved from the standard level.

[0105] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0106] The present application provides a device control method, which is applied to a terminal device, as shown in FIG8 , including:

[0107] S801. The terminal device controls the cancellation of the triggered first report through the first condition or the second condition, and the first report is the report of the GNSS effective time; the first condition is that the first MAC PDU is not transmitted through message 3, and the second condition is that the first MAC PDU is transmitted through message 3 during the random access process and the random access process is successful, the first MAC PDU is transmitted on the uplink channel, and the first MAC PDU includes the GNSS effective time reporting MAC CE.

[0108] In the embodiment of the present application, the terminal device completes the GNSS measurement and triggers the first report, i.e., the first reporting process. The first report is a report of the GNSS validity time. The first report can also be understood as sending the remaining GNSS measurement validity duration to the network device. That is, the first report is used to provide the base station with the remaining validity time of the GNSS position obtained by the terminal device this time. For example, the first report can be used to notify the base station side that the terminal device has completed the GNSS measurement. The first report can also be used by the base station to trigger the terminal device to perform GNSS measurement before the GNSS position of this GNSS measurement expires.

[0109] If the triggered first reporting process is not canceled, the terminal device performs the first reporting. The terminal device performing the first reporting can be understood as the terminal device sending the first MAC PDU to the network device via an uplink channel. The first MAC PDU includes a GNSS valid time reporting MAC CE. In this embodiment of the present application, the uplink channel carrying the first MAC PDU may be a PUSCH.

[0110] In an embodiment of the present application, the upper layer of the terminal device instructs the MAC layer to report the remaining GNSS measurement valid time. The MAC layer generates a GNSS valid time reporting MAC CE based on the remaining GNSS measurement valid time, and includes the GNSS valid time reporting MAC CE in the first MAC PDU and sends the first MAC PDU to the network device through the uplink channel.

[0111] The uplink resources used to transmit the first MAC PDU include the following two types:

[0112] A first uplink resource, an uplink resource carrying other uplink transmissions except message 3;

[0113] The second uplink resource, the uplink resource carrying message 3.

[0114] If the uplink resource used for the first MAC PDU is the first uplink resource, the first MAC PDU is not transmitted through message 3.

[0115] If the uplink resource used for the first MAC PDU is the second uplink resource, the terminal device initiates a random access process and the first MAC PDU is transmitted through message 3 of the random access process.

[0116] After executing the triggered first report, the terminal device determines whether to cancel the first report. In this embodiment of the present application, the terminal device controls the cancellation of the triggered first report through a first condition or a second condition. The first condition is that the first MAC PDU is not transmitted through message 3, and the second condition is that the first MAC PDU passes through message 3 of the random access process and the random access process is successful.

[0117] It can be understood that the first condition and the second condition are used to determine whether the terminal device successfully executes GNSS valid time reporting.

[0118] For the first condition, if the first MAC PDU is not transmitted through message 3, the GNSS effective time reporting is successfully executed.

[0119] For the second condition, if the first MAC PDU passes message 3 of the random access process and the random access process is successful, the GNSS effective time reporting is successfully executed.

[0120] The successful execution of the GNSS effective time reporting can be understood as the successful sending of the remaining GNSS measurement effective time to the network device.

[0121] In the related technology, when the transmitted MAC PDU includes the GNSS valid time reporting MAC CE, the triggered first report is canceled, that is, when the terminal device determines that it has transmitted the first MAC PDU, it cancels the triggered first report, and does not care whether the GNSS valid time report is successfully executed, that is, it does not care whether the network side successfully receives the remaining GNSS measurement valid time, resulting in the following inconsistent understanding of the validity of the GNSS measurement between the network device and the terminal device: the terminal device executes the first report, that is, transmits the first MAC PDU and cancels the first report based on the transmission of the first MAC PDU, and the network device does not receive the remaining GNSS measurement valid time of the terminal device due to the conflict of random access between different terminal devices.

[0122] In an embodiment of the present application, the terminal device controls the cancellation of the triggered GNSS valid time reporting by determining whether the terminal device successfully executes the first condition or the second condition for reporting the GNSS valid time, thereby effectively controlling the cancellation of the GNSS valid time reporting and avoiding inconsistent understanding between the network device and the terminal device regarding the validity of the GNSS measurement.

[0123] In some embodiments, if the terminal device meets the first condition or the second condition, the triggered first report is canceled.

[0124] If the terminal device meets the first condition, that is, the first MAC PDU is not transmitted through message 3, the triggered first report is canceled.

[0125] If the terminal device meets the second condition, that is, the first MAC PDU is transmitted through message 3 in the random access process and the random access process is successful, the triggered first report is canceled.

[0126] Optionally, if the MAC entity of the terminal device considers or determines that the first condition or the second condition is met, the triggered first report is canceled.

[0127] In an embodiment of the present application, when it is determined based on the first condition or the second condition that the GNSS effective time is successfully reported to the network device, the triggered first report is canceled, thereby canceling the first report when the terminal device determines that it has successfully reported the GNSS effective time to the network device, ensuring that the terminal device cancels the reporting of the remaining GNSS measurement effective time to the network device when the network device receives the remaining GNSS measurement effective time.

[0128] In some embodiments, if the terminal device does not meet the first condition and does not meet the second condition, the triggered first report is not canceled.

[0129] In an embodiment of the present application, the terminal device does not meet the first condition and does not meet the second condition, which can be understood as the first MAC PDU is transmitted through message 3 in the random access process and the random access process fails. In this case, the first MAC PDU is transmitted through message 3 in the random access process and the random access process fails. The triggered first report is not canceled.

[0130] In the embodiment of the present application, the first MAC PDU is transmitted through message 3 in the random access process, and the failure of the random access process can be understood as the terminal device not receiving message 4 of this random access process, or the contention resolution of this random access fails.

[0131] When the terminal device executes the triggered first report and determines based on the first condition and the second condition that the triggered first report is not canceled, the terminal device continues to execute the triggered first report until the GNSS position of this GNSS measurement expires or the terminal device satisfies the first condition or the second condition. In an embodiment of the present application, if the terminal device does not satisfy the first condition or the second condition before the GNSS position of this GNSS measurement expires, the terminal device cancels the triggered first report.

[0132] In some embodiments, if the terminal device meets the first condition or the second condition, the triggered first report is canceled.

[0133] If the terminal device satisfies the first condition or the second condition, the triggered first report is canceled, which can be replaced by the description: when the terminal device satisfies the first condition or the second condition, or at the moment of determining that the terminal device satisfies the first condition or the second condition, the triggered first report is canceled.

[0134] In an embodiment of the present application, the terminal device cancels the triggered first report when it determines that the first condition or the second condition is met.

[0135] In an embodiment of the present application, the terminal device may also cancel the triggered first report after a first time period after determining that the first condition or the second condition is met, wherein the size of the first time period may be set according to actual needs.

[0136] In some embodiments, the random access procedure being successful includes one or more of the following:

[0137] A. Successfully complete the random access procedure;

[0138] B. The MAC entity of the terminal device determines that the conflict is successfully resolved;

[0139] C. The MAC entity receives a first indication from a lower layer, where the first indication is used to indicate reception of a first physical downlink control channel (PDCCH), where the first PDCCH is scrambled using a cell radio network temporary identifier (C-RNTI) of the terminal device;

[0140] D. The MAC entity receives a second indication from a lower layer, where the second indication is used to indicate reception of a second PDCCH, where the second PDCCH is scrambled using the C-RNTI of the terminal device, and includes a newly transmitted uplink grant;

[0141] E. The MAC entity receives a third indication from a lower layer, where the third indication is used to indicate reception of a third PDCCH, where the third PDCCH is scrambled using the C-RNTI of the terminal device, and where the third PDCCH indicates a new uplink transmission;

[0142] F. The MAC entity receives a fourth indication from a lower layer, where the fourth indication is used to indicate reception of a fourth PDCCH, where the fourth PDCCH is scrambled using the C-RNTI of the terminal device, and where the fourth PDCCH indicates a newly transmitted uplink authorization or downlink allocation.

[0143] In the embodiment of the present application, the description method of the success of the random access process may include one or more description methods from A to F above.

[0144] For description method A, if a MAC PDU is transmitted through message 3 and the MAC PDU contains a GNSS validity duration report MAC CE (GNSS Validity Duration Report MAC control element), when the UE successfully completes the random access procedure or the random access procedure is successfully completed (the Random Access procedure is successfully completed), the triggered GNSS validity duration report is cancelled.

[0145] For description method B, if a MAC PDU is transmitted through message 3 and the MAC PDU contains a GNSS validity duration report MAC CE (GNSS Validity Duration Report MAC control element), when the UE's MAC entity determines that the conflict resolution is successful (the MAC entity considers Contention Resolution successful), the triggered GNSS validity duration report is canceled.

[0146] For description method C, if a MAC PDU is transmitted through message 3 and the MAC PDU contains a GNSS valid time report MAC CE (GNSS Validity Duration Report MAC control element), the MAC entity receives an indication of a PDCCH received from the lower layer and the PDCCH is scrambled using the cell radio network temporary identifier C-RNTI of the terminal device (the notification of a reception of a PDCCH transmission is received from lower layer and the PDCCH transmission is addressed to the C-RNTI), the triggered GNSS valid duration report is canceled.

[0147] For description method D, if a MAC PDU is transmitted through message 3 and the MAC PDU contains a GNSS valid duration report MAC CE (GNSS Validity Duration Report MAC control element), the MAC entity receives an indication of PDCCH reception from the lower layer and the PDCCH is scrambled using the C-RNTI of the terminal device, and the PDCCH contains a new uplink grant (the notification of a reception of a PDCCH transmission is received from lower layer and the PDCCH transmission is addressed to the C-RNTI and contains an UL grant for a new transmission), the triggered GNSS valid duration report is canceled.

[0148] For description method E, if a MAC PDU is transmitted through message 3 and the MAC PDU contains a GNSS valid time report MAC CE (GNSS Validity Duration Report MAC control element), the MAC entity receives an indication of a PDCCH received from the lower layer and the PDCCH is scrambled using the C-RNTI of the terminal device, and the PDCCH indicates a new transmission (the notification of a reception of a PDCCH transmission is received from lower layer and the PDCCH transmission is addressed to the C-RNTI and contains a new transmission), the triggered GNSS valid duration report is canceled.

[0149] For description method F, if a MAC PDU is transmitted through message 3 and the MAC PDU contains a GNSS valid time report MAC CE (GNSS Validity Duration Report MAC control element), the MAC entity receives an indication of PDCCH reception from the lower layer and the PDCCH is scrambled using the C-RNTI of the terminal device, and the PDCCH indicates a new uplink grant or downlink assignment (the notification of a reception of a PDCCH transmission is received from lower layer and the PDCCH transmission is addressed to the C-RNTI and contains an UL grant or DL ​​assignment for a new transmission), the triggered GNSS valid duration report is canceled.

[0150] In some embodiments, as shown in FIG9 , the device control method provided by the embodiment of the present application includes:

[0151] S901. If there is a first uplink resource in the current transmission time interval TTI, the terminal device transmits the first MAC PDU through the first uplink resource, the first uplink resource is used for new transmission and the first uplink resource can carry the GNSS effective time reporting MAC CE.

[0152] After the terminal device completes the GNSS measurement, it triggers the first report. If the first uplink resource exists in the current TTI, the terminal device generates a GNSS validity duration report MAC CE to transmit the first MAC PDU through the first uplink resource. The first uplink resource can be understood as the uplink resources allocated for new transmission for this TTI in the current transmission time interval (UL resources allocated for new transmission for this TTI), and the uplink resource can carry the GNSS validity duration report MAC CE (can accommodate the GNSS Validity Duration Report MAC control element).

[0153] Optionally, the first uplink resource is a PUSCH resource.

[0154] In some embodiments, as shown in FIG10 , the device control method provided by the embodiment of the present application includes:

[0155] S1001. If the first uplink resource does not exist in the current TTI, the terminal device initiates a random access procedure; the first uplink resource is used for new transmission and the first uplink resource can carry the GNSS effective time reporting MAC CE.

[0156] After the terminal device completes the GNSS measurement, it triggers the first report and initiates a random access process when there is no first uplink resource in the current TTI, so as to transmit the first MAC PDU through message 3 in the random access process.

[0157] In the embodiment of the present application, the random access process initiated by the terminal device is a contention-based four-step random access process, and the GNSS valid time reporting MAC CE is transmitted through Msg3 during the random access process.

[0158] In some embodiments, the first uplink resource does not exist in the current TTI, including:

[0159] There are no uplink resources for new transmission in the current TTI; or,

[0160] There are uplink resources for new transmission in the current TTI, but the uplink resources cannot carry the GNSS valid time reporting MAC CE.

[0161] The terminal device determines that there is no uplink resource for new transmission in the current TTI, or that there is an uplink resource for new transmission in the current TTI but the uplink resource cannot carry the GNSS valid time reporting MAC CE, and determines that there is no first uplink resource in the current TTI.

[0162] Based on the device control method shown in FIG10 , the conditions for the terminal device to initiate the random access process further include one or more of the following:

[0163] Condition A: The terminal device is not currently performing a random access procedure;

[0164] Condition B: the terminal device is not currently performing a first random access procedure, and the first random access procedure is triggered by the first report;

[0165] Condition C: The terminal device does not currently have a second random access process in progress, and the second random access process is triggered by the MAC layer or the radio resource control RRC layer.

[0166] As shown in FIG11 , the device control method provided in the embodiment of the present application includes:

[0167] S1101. If the first uplink resource does not exist in the current TTI and the terminal device meets the third condition, the terminal device initiates a random access process; the first uplink resource is used for new transmission and the first uplink resource can carry the GNSS effective time reporting MAC CE.

[0168] The third condition includes one of condition A, condition B, and condition C.

[0169] For condition A, the terminal device determines that there is no first uplink resource on the current TTI and there is no random access process in progress, and initiates a random access process to transmit the GNSS effective time reporting MAC CE through message 3 in the random access process.

[0170] For condition B, the terminal device determines that there is no first uplink resource on the current TTI and there is no ongoing random access process triggered by the first report, and initiates a random access process to transmit the GNSS effective time report MAC CE through message 3 in the random access process.

[0171] For condition C, the terminal device determines that there is no first uplink resource on the current TTI and there is no ongoing random access process triggered by the MAC layer or RRC layer, and initiates a random access process to transmit the GNSS effective time reporting MAC CE through message 3 in the random access process.

[0172] In related technologies, for a terminal device that triggers GNSS effective time reporting, the terminal device will determine whether there are uplink resources capable of transmitting the GNSS effective time reporting MAC CE in each TTI. If not, a random access process will be triggered, which will cause the terminal device to frequently trigger unnecessary random access processes.

[0173] In the device control method provided in the embodiment of the present application, if the terminal device triggers the GNSS effective time reporting, and there are no uplink resources for new transmission in the current TTI or the uplink resources currently used for new transmission are insufficient to carry the GNSS effective time reporting MAC CE, the terminal device will only trigger the random access process if the UE has no ongoing random access process or no ongoing random access process triggered based on the GNSS effective time reporting or no ongoing random access process triggered based on the MAC layer or RRC layer, which can effectively avoid the triggering of unnecessary random access processes.

[0174] It should be noted that the device control method shown in FIG. 11 provided in the embodiment of the present application can be implemented in conjunction with the device control method shown in FIG. 8 or can be implemented independently.

[0175] In one example, a triggering condition for triggering the random access procedure is: the first uplink resource does not exist in the current TTI. A cancellation condition for triggering the GNSS effective time reporting includes: the first MAC PDU is transmitted via the first uplink resource, or the first MAC PDU is transmitted via message 3 during the random access procedure and the random access procedure is successful.

[0176] In this case, when the first uplink resource exists in the current TTI, the terminal device transmits the first MAC PDU through the first uplink resource, and cancels the triggered GNSS effective time report based on the transmission of the first MAC PDU and the cancellation condition of the triggered GNSS effective time report. When the first uplink resource does not exist in the current TTI, the terminal device triggers the random access process, transmits the first MAC PDU through message 3 in the random access process, and cancels the triggered GNSS effective time report if the random access process is successful.

[0177] In one example, the triggering condition for triggering the random access procedure includes: the first uplink resource does not exist in the current TTI and there is no ongoing random access procedure or the first random access procedure or the second random access procedure. The cancellation condition for triggering the GNSS effective time reporting includes: the first MAC PDU is transmitted.

[0178] In this case, when the first uplink resource exists in the current TTI, the terminal device transmits the first MAC PDU through the first uplink resource, and cancels the triggered GNSS effective time reporting based on the transmission of the first MAC PDU. When the first uplink resource does not exist in the current TTI and there is no ongoing random access procedure or the first random access procedure or the second random access procedure, the terminal device triggers the random access procedure, transmits the first MAC PDU through message 3 in the random access procedure, and cancels the triggered GNSS effective time reporting based on the transmission of the first MAC PDU.

[0179] In one example, a triggering condition for triggering a random access procedure includes: the absence of a first uplink resource in a current TTI and no ongoing random access procedure, the first random access procedure, or the second random access procedure. A cancellation condition for triggering a GNSS valid time report includes: the transmission of a first MAC PDU via a first uplink resource, or the transmission of the first MAC PDU via message 3 during a random access procedure and the success of the random access procedure.

[0180] In this case, when the first uplink resource exists in the current TTI, the terminal device transmits the first MAC PDU through the first uplink resource, and cancels the triggered GNSS effective time report based on the transmission of the first MAC PDU and the cancellation condition of the triggered GNSS effective time report. When the first uplink resource does not exist in the current TTI and there is no ongoing random access process or the first random access process or the second random access process, the terminal device triggers the random access process, transmits the first MAC PDU through message 3 in the random access process, and cancels the triggered GNSS effective time report if this random access is successful.

[0181] The device control method provided in the embodiments of the present application is described below through multiple embodiments.

[0182] Example 1

[0183] For the triggered GNSS effective time reporting, the cancellation conditions of the GNSS effective time reporting are: the UE transmits a GNSS effective time reporting MAC CE through a PUSCH other than Msg3; or the UE transmits a GNSS effective time reporting MAC CE through a Msg3 PUSCH, and the UE successfully completes the random access.

[0184] For the first embodiment, if the UE triggers a GNSS validity duration report, when condition one (i.e., the first condition) or condition two (i.e., the second condition) is met (or at the moment when condition one or condition two is met), all triggered GNSS validity duration reports are canceled.

[0185] The first condition is defined as: when the UE or MAC entity transmits a MAC PDU, and the MAC PDU includes a GNSS Validity Duration Report MAC control element (MAC CE), and the MAC PDU is not transmitted through Msg3;

[0186] The second condition is defined as one of the following:

[0187] Definition A: If the UE or MAC entity transmits a MAC PDU via Msg3, and the MAC PDU contains a GNSS Validity Duration Report MAC control element, then when the UE or MAC entity successfully completes random access;

[0188] Definition B: If the UE or MAC entity transmits a MAC PDU via Msg3, and the MAC PDU contains a GNSS Validity Duration Report MAC control element, then the UE or MAC entity considers that the contention resolution is successful;

[0189] Definition C: If the UE or MAC entity transmits a MAC PDU via Msg3, and the MAC PDU contains a GNSS Validity Duration Report MAC control element, then when the UE or MAC entity receives a PDCCH reception indication from the physical layer, and the PDCCH is scrambled with the UE's C-RNTI, and the PDCCH indicates a newly transmitted UL grant;

[0190] Definition D: If the UE or MAC entity transmits a MAC PDU via Msg3, and the MAC PDU contains a GNSS Validity Duration Report MAC control element, then when the UE or MAC entity receives a PDCCH reception indication from the physical layer, and the PDCCH is scrambled with the UE's C-RNTI, and the PDCCH indicates a new uplink transmission;

[0191] Definition E: If a UE or MAC entity transmits a MAC PDU via Msg3 and the MAC PDU contains a GNSS Validity Duration Report MAC control element, then when the UE or MAC entity receives a PDCCH reception indication from the physical layer and the PDCCH is scrambled using the UE's C-RNTI;

[0192] Definition F: If the UE or MAC entity transmits a MAC PDU via Msg3, and the MAC PDU contains a GNSS Validity Duration Report MAC control element, then when the UE or MAC entity receives a PDCCH reception indication from the physical layer, and the PDCCH is scrambled using the UE's C-RNTI, and the PDCCH indicates a new uplink transmission or a new downlink transmission.

[0193] Embodiment 1 can be applied to, but not limited to, the following examples.

[0194] Example 1

[0195] For NB-IoT terminals, narrowband low complexity UEs (BL UEs) or UEs in enhanced coverage of NTN networks, the upper layer may send an indication to report the remaining GNSS measurement validity time.

[0196] If the GNSS valid time reporting process is triggered but not cancelled:

[0197] If the MAC entity has uplink resources allocated for new transmission in the current TTI, and if, as a result of the logical channel priority, the allocated UL resources can accommodate the GNSS validity period report MAC control element and its subheader, then indicate the multiplexing and assembly process for generating the GNSS validity period report MAC control element; otherwise, initiate the random access process.

[0198] That is to say, for the GNSS effective time reporting that has been triggered and not canceled, if the UE has uplink resources available for new transmission in the current TTI and the uplink resources can carry the GNSS effective time reporting MAC CE, the UE uses the uplink resources to report the GNSS effective time reporting; otherwise, the UE triggers the random access process.

[0199] If the UE sends a MAC PDU containing a GNSS valid time reporting MAC CE and the transmission is not Msg3, all triggered GNSS valid time reports will be deleted.

[0200] If a MAC PDU is transmitted via Msg3 and the MAC PDU contains a GNSS valid time reporting MAC CE, all triggered GNSS valid time reports will be deleted when the random access procedure is successfully completed.

[0201] Example 2

[0202] For NB-IoT terminals, BL UEs or UEs in the enhanced coverage of the NTN network, the upper layer may send an indication to report the remaining GNSS measurement validity time.

[0203] If the GNSS valid time reporting process is triggered but not cancelled:

[0204] If the MAC entity has uplink resources allocated for new transmission in the current TTI, and if, as a result of the logical channel priority, the allocated UL resources can accommodate the GNSS validity period report MAC control element and its subheader, then indicate the multiplexing and assembly process for generating the GNSS validity period report MAC control element; otherwise, initiate the random access process.

[0205] If the UE sends a MAC PDU containing a GNSS valid time reporting MAC CE and the transmission is not Msg3, all triggered GNSS valid time reports will be deleted.

[0206] If a MAC PDU is transmitted via Msg3 and the MAC PDU contains a GNSS valid time reporting MAC CE, when the MAC entity considers that the contention resolution is successful, all triggered GNSS valid time reports will be deleted.

[0207] Example 3

[0208] For NB-IoT terminals, BL UEs or UEs in the enhanced coverage of the NTN network, the upper layer may send an indication to report the remaining GNSS measurement validity time.

[0209] If the GNSS valid time reporting process is triggered but not cancelled:

[0210] If the MAC entity has uplink resources allocated for new transmission in the current TTI, and if, as a result of the logical channel priority, the allocated UL resources can accommodate the GNSS validity period report MAC control element and its subheader, then indicate the multiplexing and assembly process for generating the GNSS validity period report MAC control element; otherwise, initiate the random access process.

[0211] If the UE sends a MAC PDU containing a GNSS valid time reporting MAC CE and the transmission is not Msg3, all triggered GNSS valid time reports will be deleted.

[0212] If a MAC PDU is transmitted via Msg3 and the MAC PDU contains a GNSS valid time reporting MAC CE, when a PDCCH transmission reception indication is received from the lower layer, and the PDCCH transmission is scrambled with the UE's C-RNTI, and the PDCCH includes a newly transmitted UL grant, all triggered GNSS valid time reports will be deleted.

[0213] Example 4

[0214] For NB-IoT terminals, BL UEs or UEs in the enhanced coverage of the NTN network, the upper layer may send an indication to report the remaining GNSS measurement validity time.

[0215] If the GNSS valid time reporting process is triggered but not cancelled:

[0216] If the MAC entity has uplink resources allocated for new transmission in the current TTI, and if, as a result of the logical channel priority, the allocated UL resources can accommodate the GNSS validity period report MAC control element and its subheader, then indicate the multiplexing and assembly process for generating the GNSS validity period report MAC control element; otherwise, initiate the random access process.

[0217] If the UE sends a MAC PDU containing a GNSS valid time reporting MAC CE and the transmission is not Msg3, all triggered GNSS valid time reports will be deleted.

[0218] If a MAC PDU is transmitted via Msg3 and the MAC PDU contains a GNSS valid time reporting MAC CE, when a PDCCH transmission reception indication is received from the lower layer and the PDCCH transmission is scrambled using the UE's C-RNTI, all triggered GNSS valid time reports will be deleted.

[0219] Example 5

[0220] For NB-IoT terminals, BL UEs or UEs in the enhanced coverage of the NTN network, the upper layer may send an indication to report the remaining GNSS measurement validity time.

[0221] If the GNSS valid time reporting process is triggered but not cancelled:

[0222] If the MAC entity has uplink resources allocated for new transmission in the current TTI, and if, as a result of the logical channel priority, the allocated UL resources can accommodate the GNSS validity period report MAC control element and its subheader, then indicate the multiplexing and assembly process for generating the GNSS validity period report MAC control element; otherwise, initiate the random access process.

[0223] If the UE sends a MAC PDU containing a GNSS valid time reporting MAC CE and the transmission is not Msg3, all triggered GNSS valid time reports will be deleted.

[0224] If a MAC PDU is transmitted via Msg3 and the MAC PDU contains a GNSS valid time reporting MAC CE, when a PDCCH transmission reception indication is received from the lower layer, and the PDCCH transmission is scrambled using the UE's C-RNTI, and the PDCCH includes a newly transmitted UL grant or downlink allocation, all triggered GNSS valid time reports will be deleted.

[0225] Embodiment 1 of the present application provides a method for UE to cancel GNSS effective time reporting. In the case of transmitting GNSS effective time reporting MAC CE via Msg3 PUSCH, the UE cancels the triggered GNSS effective time reporting when random access is successful. This can effectively solve the problem that the UE cannot report the GNSS effective time to the base station due to the failure of UE random GNSS effective time reporting access.

[0226] Example 2

[0227] If the UE triggers GNSS effective time reporting and the UE has no PUSCH resources for new transmission in the current TTI or the current PUSCH resources for new transmission are insufficient to carry the GNSS effective time reporting MAC CE, the UE triggers the random access procedure only when there is no random access procedure in progress.

[0228] For the second embodiment, if the UE triggers GNSS effective time reporting, and the UE has no PUSCH resources for new transmission in the current TTI or the current PUSCH resources for new transmission are insufficient to carry the GNSS effective time reporting MAC CE, then if condition three is met, the UE triggers the random access process. Among them:

[0229] The third condition is defined as one of the following:

[0230] Definition 1: The UE is not currently performing a random access procedure;

[0231] Definition 2: The UE is not currently performing a first random access procedure, and the first random access procedure is triggered by a GNSS valid time report;

[0232] Definition 3: The UE does not currently have a first random access procedure in progress. The first random access procedure is triggered by the MAC layer or RRC layer of the UE.

[0233] The second embodiment can be applied to, but not limited to, the following examples.

[0234] Example 1

[0235] For NB-IoT terminals, narrowband low complexity UEs (BL UEs) or UEs in enhanced coverage of NTN networks, the upper layer may send an indication to report the remaining GNSS measurement validity time.

[0236] If the GNSS valid time reporting process is triggered but not cancelled:

[0237] If the MAC entity has uplink resources allocated for new transmission in the current TTI, and if, as a result of the logical channel priority, the allocated UL resources can accommodate the GNSS validity period report MAC control element and its subheader, it indicates the multiplexing and assembly process for generating the GNSS validity period report MAC control element; otherwise, if the UE is not performing a random access procedure, the UE triggers the random access procedure.

[0238] If the UE sends a MAC PDU and the MAC PDU contains a GNSS valid time reporting MAC CE, all triggered GNSS valid time reports will be deleted.

[0239] Example 2

[0240] For NB-IoT terminals, narrowband low complexity UEs (BL UEs) or UEs in enhanced coverage of NTN networks, the upper layer may send an indication to report the remaining GNSS measurement validity time.

[0241] If the GNSS valid time reporting process is triggered but not cancelled:

[0242] If the MAC entity has uplink resources allocated to the new transmission for the current TTI, and if, as a result of the logical channel priority, the allocated UL resources can accommodate the GNSS valid time report MAC control element and its subheader, a multiplexing and assembly process is indicated, which is used to generate the GNSS valid time report MAC control element; otherwise, if the UE is not executing a first random access process, the first random access process is a random access process triggered based on the GNSS valid time report, and the UE triggers the random access process.

[0243] If the UE sends a MAC PDU and the MAC PDU contains a GNSS valid time reporting MAC CE, all triggered GNSS valid time reports will be deleted.

[0244] Example 2

[0245] For NB-IoT terminals, narrowband low complexity UEs (BL UEs) or UEs in enhanced coverage of NTN networks, the upper layer may send an indication to report the remaining GNSS measurement validity time.

[0246] If the GNSS valid time reporting process is triggered but not cancelled:

[0247] If the MAC entity has uplink resources allocated to the new transmission for the current TTI, and if, as a result of the logical channel priority, the allocated UL resources can accommodate the GNSS validity period report MAC control element and its subheader, then a multiplexing and assembly process is indicated, which is used to generate the GNSS validity period report MAC control element; otherwise, if the UE is not performing a second random access procedure, the second random access procedure is a random access procedure triggered by the MAC sublayer or the RRC sublayer, and the UE triggers the random access procedure.

[0248] If the UE sends a MAC PDU and the MAC PDU contains a GNSS valid time reporting MAC CE, all triggered GNSS valid time reports will be deleted.

[0249] Embodiment 2 of the present application provides a method for triggering random access by reporting a GNSS effective time, which can effectively avoid unnecessary triggering of random access by a UE.

[0250] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0251] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0252] FIG12 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. As shown in FIG12 , the terminal device 1200 includes:

[0253] The control unit 1201 is configured to control the cancellation of the triggered first report through a first condition or a second condition, where the first report is a report of the effective time of the global satellite navigation system GNSS; the first condition is that the first media access control MAC protocol data unit PDU is not transmitted through message 3, and the second condition is that the first MAC PDU is transmitted through message 3 during the random access process and the random access process is successful, the first MAC PDU is transmitted on the uplink channel, and the first MAC PDU includes the GNSS effective time reporting MAC control unit CE.

[0254] In some embodiments, if the terminal device meets the first condition or the second condition, the triggered first report is canceled.

[0255] In some embodiments, if the terminal device meets the first condition or the second condition, the triggered first report is canceled.

[0256] In some embodiments, the random access procedure being successful includes one or more of the following:

[0257] Successfully completing the random access procedure;

[0258] The MAC entity of the terminal device determines that the conflict is successfully resolved;

[0259] The MAC entity receives a first indication from a lower layer, where the first indication is used to indicate reception of a first physical downlink control channel (PDCCH), where the first PDCCH is scrambled using a cell radio network temporary identifier (C-RNTI) of the terminal device;

[0260] The MAC entity receives a second indication from a lower layer, where the second indication is used to indicate reception of a second PDCCH, where the second PDCCH is scrambled using the C-RNTI of the terminal device, and the second PDCCH includes a newly transmitted uplink grant;

[0261] The MAC entity receives a third indication from a lower layer, where the third indication is used to indicate reception of a third PDCCH, where the third PDCCH is scrambled using the C-RNTI of the terminal device, and where the third PDCCH indicates a new uplink transmission;

[0262] The MAC entity receives a fourth indication from a lower layer, where the fourth indication is used to indicate reception of a fourth PDCCH, where the fourth PDCCH is scrambled using the C-RNTI of the terminal device, and where the fourth PDCCH indicates a newly transmitted uplink authorization or downlink allocation.

[0263] In some embodiments, the terminal device 1200 further includes:

[0264] The communication unit is configured to transmit the first MAC PDU through the first uplink resource if there is a first uplink resource in the current transmission time interval TTI, the first uplink resource is used for new transmission and the first uplink resource can carry the GNSS effective time reporting MAC CE.

[0265] In some embodiments, the terminal device 1200 further includes:

[0266] The initiating unit is configured to initiate the random access process if there is no first uplink resource in the current TTI; the first uplink resource is used for new transmission and the first uplink resource can carry the GNSS effective time reporting MAC CE.

[0267] In some embodiments, the first uplink resource does not exist in the current TTI, including:

[0268] There are no uplink resources for new transmission in the current TTI; or,

[0269] There are uplink resources for new transmission in the current TTI, but the uplink resources cannot carry the GNSS valid time reporting MAC CE.

[0270] In some embodiments, the conditions for initiating the random access procedure further include one or more of the following:

[0271] The terminal device has no random access process currently in progress;

[0272] The terminal device is not currently performing a first random access process, and the first random access process is triggered by the first report;

[0273] The terminal device does not currently have a second random access process in progress, and the second random access process is triggered by the MAC layer or the radio resource control RRC layer.

[0274] The control unit and the initiating unit in the terminal device can be implemented by a processor in the terminal device, and the communication unit can be implemented by a transceiver in the terminal device.

[0275] Those skilled in the art should understand that the relevant description of the above-mentioned terminal device in the embodiment of the present application can be understood by referring to the relevant description of the device control method in the embodiment of the present application.

[0276] FIG13 is a schematic structural diagram of a communication device 1300 provided in an embodiment of the present application. The communication device can be a terminal device. The communication device 1300 shown in FIG13 includes a processor 1310, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0277] Optionally, as shown in FIG13 , the communication device 1300 may further include a memory 1320. The processor 1310 may call and execute a computer program from the memory 1320 to implement the method in the embodiment of the present application.

[0278] The memory 1320 may be a separate device independent of the processor 1310 , or may be integrated into the processor 1310 .

[0279] Optionally, as shown in FIG13 , the communication device 1300 may further include a transceiver 1330 , and the processor 1310 may control the transceiver 1330 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0280] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0281] Optionally, the communication device 1300 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0282] Figure 14 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1400 shown in Figure 14 includes a processor 1410, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0283] Optionally, as shown in FIG14 , the chip 1400 may further include a memory 1420 , wherein the processor 1410 may call and execute a computer program from the memory 1420 to implement the method in the embodiment of the present application.

[0284] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0285] Optionally, the chip 1400 may further include an input interface 1430. The processor 1410 may control the input interface 1430 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0286] Optionally, the chip 1400 may further include an output interface 1440. The processor 1410 may control the output interface 1440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0287] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0288] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0289] FIG15 is a schematic block diagram of a communication system 1500 provided in an embodiment of the present application. As shown in FIG15 , the communication system 1500 includes a terminal device 1510 and a network device 1520 .

[0290] Among them, the terminal device 1510 can be used to implement the corresponding functions implemented by the terminal device in the above method, which will not be repeated here.

[0291] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0292] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0293] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0294] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0295] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0296] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0297] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0298] The embodiment of the present application also provides a computer program.

[0299] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0300] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0301] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0302] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0304] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0305] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling 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 method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0306] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A device control method, the method comprising: The terminal device controls the cancellation of the triggered first report through the first condition or the second condition, where the first report is a report of the global satellite navigation system GNSS effective time; The first condition is that the first media access control MAC protocol data unit PDU is not transmitted through message 3, the second condition is that the first MAC PDU is transmitted through message 3 in the random access process and the random access process is successful, the first MAC PDU is transmitted on the uplink channel, and the first MAC PDU includes the GNSS effective time reporting MAC control unit CE.

2. The method according to claim 1, wherein If the terminal device meets the first condition or the second condition, the triggered first report is canceled.

3. The method according to claim 2, wherein: If the terminal device meets the first condition or the second condition, the triggered first report is canceled.

4. The method according to any one of claims 1 to 3, wherein: The success of the random access procedure includes one or more of the following: Successfully completing the random access procedure; The MAC entity of the terminal device determines that the conflict is successfully resolved; The MAC entity receives a first indication from a lower layer, where the first indication is used to indicate reception of a first physical downlink control channel (PDCCH), where the first PDCCH is scrambled using a cell radio network temporary identifier (C-RNTI) of the terminal device; The MAC entity receives a second indication from a lower layer, where the second indication is used to indicate reception of a second PDCCH, where the second PDCCH is scrambled using the C-RNTI of the terminal device, and the second PDCCH includes a newly transmitted uplink grant; The MAC entity receives a third indication from a lower layer, where the third indication is used to indicate reception of a third PDCCH, where the third PDCCH is scrambled using the C-RNTI of the terminal device, and where the third PDCCH indicates a new uplink transmission; The MAC entity receives a fourth indication from a lower layer, where the fourth indication is used to indicate reception of a fourth PDCCH, where the fourth PDCCH is scrambled using the C-RNTI of the terminal device, and where the fourth PDCCH indicates a newly transmitted uplink authorization or downlink allocation.

5. The method according to any one of claims 1 to 4, wherein: The method further comprises: If there is a first uplink resource in the current transmission time interval TTI, the terminal device transmits the first MAC PDU through the first uplink resource, the first uplink resource is used for new transmission and the first uplink resource can carry the GNSS effective time reporting MAC CE.

6. The method according to any one of claims 1 to 5, wherein: The method further comprises: If the first uplink resource does not exist in the current TTI, the terminal device initiates the random access process; the first uplink resource is used for new transmission and the first uplink resource can carry the GNSS effective time reporting MAC CE.

7. The method according to claim 6, wherein: The first uplink resource does not exist in the current TTI, including: There are no uplink resources for new transmission in the current TTI; or, There are uplink resources for new transmission in the current TTI, but the uplink resources cannot carry the GNSS valid time reporting MAC CE.

8. The method according to claim 6 or 7, wherein: The conditions for the terminal device to initiate the random access process also include one or more of the following: The terminal device has no random access process currently in progress; The terminal device is not currently performing a first random access process, and the first random access process is triggered by the first report; The terminal device does not currently have a second random access process in progress, and the second random access process is triggered by the MAC layer or the radio resource control RRC layer.

9. A terminal device comprising: a control unit configured to control cancellation of a triggered first report according to a first condition or a second condition, wherein the first report is a report of a global satellite navigation system GNSS effective time; The first condition is that the first media access control MAC protocol data unit PDU is not transmitted through message 3, the second condition is that the first MAC PDU is transmitted through message 3 during the random access process and the random access process is successful, the first MAC PDU is transmitted on the physical uplink shared channel PUSCH, and the first MAC PDU includes the GNSS effective time reporting MAC control unit CE.

10. A terminal device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 8.

11. A chip, comprising: The processor is configured to call and execute a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 8.

12. A computer-readable storage medium for storing a computer program, wherein the execution of the computer program enables a computer to execute the method according to any one of claims 1 to 8.

13. A computer program product comprising computer program instructions, wherein execution of the computer program instructions causes a computer to perform the method according to any one of claims 1 to 8.

14. A computer program, wherein the execution of the computer program enables a computer to execute the method according to any one of claims 1 to 8.

Images