Wireless communication method, terminal device and network device

Abstract

The embodiment of the invention provides a wireless communication method, terminal equipment and network equipment. The method comprises the following steps: the terminal equipment acquires a first uplink synchronous timer; wherein the first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first serving cell group, the first serving cell group comprises at least one serving cell, and the first uplink synchronization timer is used for maintaining uplink synchronization of the at least one serving cell in the first serving cell group. Therefore, the problem of how to control the uplink synchronization of the serving cell in the NTN system is solved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, a terminal device, and a network device. Background Art

[0002] Non Terrestrial Network (NTN) generally uses satellite communication to provide communication services to ground users. Compared with ground cellular network communication, satellite communication has many unique advantages. First, satellite communication is not restricted by the user's region. Secondly, satellite communication has great social value. Thirdly, satellite communication has a long distance, and the cost of communication does not increase significantly as the communication distance increases; finally, satellite communication has high stability and is not restricted by natural disasters. In the NTN system, how to control the uplink synchronization of the service cell is a technical problem that needs to be solved urgently in this application. Summary of the invention

[0003] The embodiments of the present application provide a wireless communication method, a terminal device and a network device, thereby solving the problem of how to control the uplink synchronization of a serving cell in an NTN system.

[0004] In a first aspect, a wireless communication method is provided, including: a terminal device obtains a first uplink synchronization timer; wherein, the first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain uplink synchronization of at least one service cell in the first service cell group.

[0005] In a second aspect, a wireless communication method is provided, including: a network device configures a first uplink synchronization timer to a terminal device; wherein the first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain uplink synchronization of at least one service cell in the first service cell group.

[0006] In a third aspect, a terminal device is provided, comprising: a communication unit, used to obtain a first uplink synchronization timer; wherein the first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain uplink synchronization of at least one service cell in the first service cell group.

[0007] In a fourth aspect, a network device is provided, comprising: a communication unit, used to configure a first uplink synchronization timer for a terminal device; wherein the first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain uplink synchronization of at least one service cell in the first service cell group.

[0008] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein 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 execute the method in the first aspect or its implementation manners.

[0009] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein 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 execute the method in the second aspect or its implementation manners.

[0010] In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects or any of their implementations.

[0011] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes a method as described in any one of the first to second aspects or in each of their implementations.

[0012] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to second aspects or any of their implementations.

[0013] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method of any one of the first to second aspects or any of their implementations.

[0014] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects or in each of their implementations.

[0015] Through the technical solution of the first aspect or the second aspect, the terminal device can maintain the uplink synchronization of at least one serving cell in the first serving cell group through the first uplink synchronization timer, thereby solving the problem of how to control the uplink synchronization of the serving cell in the NTN system. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1AA schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0017] Figure 1B A schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0018] Figure 1C A schematic diagram of the architecture of another communication system provided in an embodiment of the present application;

[0019] Figure 2 A schematic diagram of a timing relationship in an NTN system provided in an embodiment of the present application;

[0020] Figure 3 A schematic diagram of another timing relationship in an NTN system provided in an embodiment of the present application;

[0021] Figure 4 An interactive flow chart of a wireless communication method provided in one embodiment of the present application;

[0022] Figure 5 A schematic block diagram of a terminal device 500 according to an embodiment of the present application is shown;

[0023] Figure 6 A schematic block diagram of a network device 600 according to an embodiment of the present application is shown;

[0024] Figure 7 is a schematic structural diagram of a communication device 700 provided in an embodiment of the present application;

[0025] Figure 8 is a schematic structural diagram of a device according to an embodiment of the present application;

[0026] Fig. 9 It is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0028] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0029] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0030] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0031] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0032] Optionally, the embodiments of the present application may be applied to an NTN system, or to a terrestrial network (TN) system.

[0033] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0034] The terminal device can be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0035] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).

[0036] In the embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, or a wireless terminal device in smart home, etc. The terminal device involved in the embodiment of the present application may also be referred to as a terminal, a user equipment (UE), an access terminal device, a vehicle terminal, an industrial control terminal, a UE unit, a UE station, a mobile station, a mobile station, a remote station, a remote terminal device, a mobile device, a UE terminal device, a wireless communication device, a UE agent, or a UE device, etc. The terminal device may also be fixed or mobile.

[0037] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0038] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.

[0039] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0040] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0041] For example, Figure 1A The following is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. Figure 1A As shown, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices located in the coverage area.

[0042] Figure 1AOne network device and two terminal devices are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0043] For example, Figure 1B This is a schematic diagram of another communication system architecture provided by an embodiment of the present application. Figure 1B , including a terminal device 1101 and a satellite 1102, the terminal device 1101 and the satellite 1102 can communicate wirelessly. The network formed between the terminal device 1101 and the satellite 1102 can also be called NTN. Figure 1B In the architecture of the communication system shown, the satellite 1102 may have the function of a base station, and the terminal device 1101 and the satellite 1102 may communicate directly. In the system architecture, the satellite 1102 may be referred to as a network device. Optionally, the communication system may include multiple network devices 1102, and each network device 1102 may include other number of terminal devices within its coverage area, which is not limited in the embodiment of the present application.

[0044] For example, Figure 1C This is a schematic diagram of another communication system architecture provided by an embodiment of the present application. Figure 1C , including terminal equipment 1201, satellite 1202 and base station 1203, terminal equipment 1201 and satellite 1202 can communicate wirelessly, and satellite 1202 and base station 1203 can communicate. The network formed by terminal equipment 1201, satellite 1202 and base station 1203 can also be called NTN. Figure 1C In the architecture of the communication system shown, the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be transferred through the satellite 1202. In this system architecture, the base station 1203 can be called a network device. Optionally, the communication system may include multiple network devices 1203, and each network device 1203 may include other number of terminal devices within its coverage area, which is not limited in the embodiment of the present application.

[0045] It should be noted that Figure 1A-Figure 1C The system to which the present application is applicable is only illustrated in the form of an example. Of course, the method shown in the embodiment of the present application can also be applied to other systems, such as 5G communication system, LTE communication system, etc., and the embodiment of the present application does not make specific limitations on this.

[0046] Optionally, Figure 1A-Figure 1CThe wireless communication system shown may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but this is not limited in the embodiments of the present application.

[0047] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1A Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0048] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0049] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0050] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0051] Optionally, the indication information in the embodiment of the present application includes at least one of physical layer signaling such as DCI, Radio Resource Control (RRC) signaling and Media Access Control Control Element (MAC CE).

[0052] Optionally, the high-level parameters or high-level signaling in the embodiment of the present application include at least one of RRC signaling and MAC CE.

[0053] To facilitate a better understanding of the embodiments of the present application, the following first introduces the uplink timing advance adjustment in the NR system, the timing relationship of the NTN system, and the uplink timing advance adjustment of the NTN system:

[0054] 1. Uplink Timing Advance Adjustment in NR System

[0055] 1. Timing Advance (TA) and Timing Advance Group (TAG):

[0056] TA is used for uplink transmission of terminal devices, which means that the terminal device sends data packets in advance according to corresponding instructions.

[0057] In the LTE-A version (Release, Rel) 11, due to the proposal of carrier aggregation, different carriers supported by the terminal device (including one primary carrier and the rest are auxiliary carriers) are allowed to have different TA values, so the concept of Timing Advance Group (TAG) is introduced.

[0058] In the TN system, the terminal device can have one or more TAGs, where a TAG refers to a group of service cells configured by RRC. For the uplink configuration corresponding to the group of service cells, the same timing reference cell and the same TA value are used. If a TAG includes the MAC entity of a special cell (SpCell), it is considered to be a primary TAG (Primary Timing Advance Group, PTAG), otherwise it is considered to be a secondary TAG (Secondary Timing Advance Group, STAG). Among them, SpCell refers to: in the DC scenario, according to the master cell group (Master Cell Group, MCG) or secondary cell group (Secondary Cell Group, SCG) associated with the MAC entity, SpCell corresponds to the primary cell (Primary Cell, PCell) in the MCG or the primary secondary cell (Primary Secondary Cell, PSCell) in the SCG. In other scenarios, SpCell refers to PCell.

[0059] 2. Uplink synchronization timer, timing advance command (TAC) MAC CE and timing advance adjustment:

[0060] The network equipment will configure high-level parameters such as timeAlignmentTimer through RRC to maintain uplink timing synchronization. Each TAG is configured with an uplink synchronization timer timeAlignmentTimer to control how long the MAC entity will consider the uplink of the service cell associated with the TAG to be timing synchronized.

[0061] When timeAlignmentTimer expires, if timeAlignmentTimer is associated with PTAG, then

[0062] (1) Clear all Hybrid Automatic Repeat Request (HARQ) buffers of all serving cells;

[0063] (2) If a physical uplink control channel (PUCCH) is configured, instruct the RRC to release the PUCCH of all serving cells;

[0064] (3) If a channel sounding reference signal (SRS) is configured, instruct the RRC to release the SRS of all serving cells;

[0065] (4) Clear any preconfigured downlink transmissions and preconfigured uplink grants;

[0066] (5) Clear any Physical Uplink Shared Channel (PUSCH) resources used for semi-persistent Channel State Information (CSI) reporting;

[0067] (6) All running timeAlignmentTimers are considered expired;

[0068] (7) Keep N of all tags TA .

[0069] When timeAlignmentTimer expires, if timeAlignmentTimer is associated with STAG, then for all serving cells belonging to the STAG:

[0070] (1) Clear all HARQ buffers;

[0071] (2) If PUCCH is configured, instruct RRC to release PUCCH;

[0072] (3) If SRS is configured, instruct RRC to release SRS;

[0073] (4) Clear any preconfigured downlink transmissions and preconfigured uplink grants;

[0074] (5) Clear any PUSCH resources used for semi-persistent CSI reporting;

[0075] (6) Keep the N of the STAG TA .

[0076] The terminal device can adjust the timing advance according to the TAC MAC CE sent by the network device. TA has been applied to the TA adjustment process associated with the TAG, then the TAC and N TA To adjust the TA associated with the TAG, and start or restart the timeAlignmentTimer associated with the indicated TAG. The TAC MAC CE includes 2 bits of TAG identification (Identity, ID) indication information and 6 bits of TAC indication information, and the TAC indication information is used to adjust the TA associated with the TAG. TA The value is also used to adjust the TA associated with the TAG, N TA The value is related to the subcarrier spacing of the first uplink transmission of the terminal device after receiving the Random Access Response (RAR).

[0077] As an example but not a limitation, the TA adjustment process of the terminal device is as follows:

[0078] The terminal device is provided with a timing advance offset value NTA,offset corresponding to a service cell; for example, the terminal device may be provided with the timing advance offset value of the service cell by a network device through a parameter n-TimingAdvanceOffset. If the terminal device is not provided with the parameter n-TimingAdvanceOffset corresponding to the service cell, the terminal device determines a default timing advance offset value for the service cell according to a protocol such as TS 38.133.

[0079] For the transmission of Msg1 or MsgA in the random access response process, the terminal device shall TA =N TA,offset *T c Determine TA; where T c =1 / (Δf max *N f ), Δf max=480000Hz, N f =4096. TA Indicates the timing advance during uplink transmission.

[0080] For uplink transmissions other than Msg1 or MsgA transmissions in the random access response process, the terminal device TA =(N TA +N TA,offset )*T c Determine the TA;

[0081] Among them, the TAC indicated in the RAR received by the terminal device is T A In this case, according to the T A Determine the N in TAG TA =T A *16*64 / 2 μ , where T A =0,1,2……3846.

[0082] In other cases, TAC T A , according to the T A Adjust N TA , where N TA_old Indicates the current adjustment N TA , N TA_new Represents the adjusted N TA , N TA_new =N TA_old +(T A -31)*16*64 / 2 μ , where T A =0,1,2...63; μ represents the subcarrier spacing configuration, and μ corresponds to a subcarrier spacing of 2 μ *15kHz.

[0083] 2. Timing relationship of NTN system

[0084] In the TN system, the propagation delay of signal communication is usually less than 1ms. In the NTN system, due to the long communication distance between the terminal equipment and the satellite, the propagation delay of signal communication is very large, ranging from tens of milliseconds to hundreds of milliseconds, which is related to the satellite orbit height and the type of satellite communication service. In order to handle the relatively large propagation delay, the timing relationship of the NTN system needs to be enhanced relative to the NR system.

[0085] In the NTN system, like the NR system, the terminal device needs to consider the impact of TA when performing uplink transmission. Since the propagation delay in the system is large, the range of TA values ​​is also relatively large. When the terminal device is scheduled to perform uplink transmission in time slot n, considering the round-trip propagation delay, the uplink transmission is performed in advance, so that the signal can reach the network device side in time slot n. Specifically, the timing relationship in the NTN system may include two situations, as follows: Figure 2 and Figure 3 shown.

[0086] Case 1: If Figure 2 As shown in the figure, like the NR system, the downlink time slot and uplink time slot on the network device side are aligned. Accordingly, in order to align the uplink transmission of the terminal device with the uplink time slot on the network device side, the terminal device needs to use a larger TA value. When performing uplink transmission, a larger offset value such as Koffset also needs to be introduced. Among them, Koffset can be determined based on the TA value.

[0087] Case 2: If Figure 3 As shown in the figure, there is an offset value between the downlink time slot and the uplink time slot on the network device side. In this case, if you want to align the uplink transmission of the terminal device with the uplink time slot on the network device side, the terminal device only needs to use a smaller TA value. However, in this case, the network device may need additional scheduling complexity to handle the corresponding scheduling timing.

[0088] 3. NTN system uplink timing advance adjustment

[0089] In the NTN system, the uplink timing advance adjustment includes at least one of the following schemes:

[0090] (1) The network device indicates a common TA (or the location information of the reference point) to the terminal device, and the terminal device performs uplink timing advance adjustment according to the common TA (or the location information of the reference point);

[0091] (2) The network device indicates a public TA (or the location information of the reference point) to the terminal device. The terminal device obtains the TA on its own according to its own Global Navigation Satellite System (GNSS) capability and the public TA (or the location information of the reference point), and makes an advance adjustment to the uplink timing.

[0092] (3) The terminal device obtains TA based on its own GNSS capability and adjusts the uplink timing in advance.

[0093] As described above, in the NTN system, how to control the uplink synchronization of the serving cell is a technical problem to be solved in this application. In order to solve this technical problem, this application implements the uplink synchronization of the serving cell by configuring an uplink synchronization timer in the terminal device.

[0094] The technical solution of this application will be described in detail below:

[0095] Figure 4 An interactive flow chart of a wireless communication method provided in an embodiment of the present application, such as Figure 4 As shown, the method includes:

[0096] Step S410: The network device configures a first uplink synchronization timer for the terminal device.

[0097] Among them, the first uplink synchronization timer corresponds to the first TAG, the first TAG corresponds to the first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain the uplink synchronization of at least one service cell in the first service cell group.

[0098] Optionally, the wireless communication method may be applied to an NTN system or a TN system, and this application does not impose any limitation on this.

[0099] Optionally, the first uplink synchronization timer may be carried in the RRC configuration information, or may be configured through DCI or MACCE signaling, which is not limited in the present application.

[0100] Optionally, the network device can configure one or more TAGs for the terminal device, and the first TAG is a TAG configured by the network device for the terminal device. The first TAG refers to a group of service cells configured by RRC. For the uplink configuration corresponding to the group of service cells, the same timing reference cell and the same TA value are used.

[0101] It should be understood that, according to the definition of the first TAG, the first TAG corresponding to the first service cell group can also be understood as the first TAG is associated with the first service cell group. The first TAG corresponding to the first service cell group is also described as the first TAG and the first service cell group have a corresponding relationship, and this application does not limit this.

[0102] It should be understood that the network device can configure an uplink synchronization timer for each TAG, and the first uplink synchronization timer is the uplink synchronization timer configured by the network device for the first TAG. The first uplink synchronization timer corresponding to the first TAG is also described as the first uplink synchronization timer having a corresponding relationship with the first TAG, and this application does not limit this.

[0103] Optionally, the first uplink synchronization timer may be used to control how long the MAC entity considers that the uplink of the service cell associated with the first TAG is timed synchronized.

[0104] Optionally, if the first uplink synchronization timer expires, for the at least one serving cell included in the first serving cell group, the behavior of the terminal device includes at least one of the following, but is not limited to:

[0105] (1) Clear all HARQ buffers.

[0106] (2) If PUCCH is configured, instruct RRC to release PUCCH.

[0107] (3) If a sounding reference signal SRS is configured, instruct RRC to release the SRS.

[0108] (4) Clear any preconfigured downlink transmissions and preconfigured uplink grants.

[0109] (5) Clear any PUSCH resources used for semi-persistent CSI reporting.

[0110] For example, when the first uplink synchronization timer expires, if the first uplink synchronization timer is associated with PTAG, then

[0111] (1) Clear all HARQ buffers of all serving cells;

[0112] (2) If PUCCH is configured, instruct RRC to release PUCCH of all serving cells;

[0113] (3) If SRS is configured, instruct RRC to release the SRS of all serving cells;

[0114] (4) Clear any preconfigured downlink transmissions and preconfigured uplink grants;

[0115] (5) Clear any PUSCH resources used for semi-persistent CSI reporting;

[0116] (6) All running uplink synchronization timers are considered expired;

[0117] (7) Keep N of all tags TA .

[0118] For another example, when the first uplink synchronization timer expires, if the first uplink synchronization timer is associated with a STAG, then for all serving cells belonging to the STAG:

[0119] (1) Clear all HARQ buffers;

[0120] (2) If PUCCH is configured, instruct RRC to release PUCCH;

[0121] (3) If SRS is configured, instruct RRC to release SRS;

[0122] (4) Clear any preconfigured downlink transmissions and preconfigured uplink grants;

[0123] (5) Clear any PUSCH resources used for semi-persistent CSI reporting;

[0124] (6) Keep the N of the STAG TA .

[0125] Based on this, in order to prevent the problem that the first uplink synchronization timer is easily expired, optionally, the validity period of the first uplink synchronization timer is configured to be infinite.

[0126] It should be understood that the infinity here is also described as infinite. The validity period of the first uplink synchronization timer is configured as infinity and is also described as the terminal device expecting the value configured for the first uplink synchronization timer to be infinite or infinite. Alternatively, the terminal device does not expect the value configured for the first uplink synchronization timer to be other values ​​except infinite or infinite, and the present application does not limit this.

[0127] In summary, in the present application, the terminal device can maintain the uplink synchronization of at least one service cell in the first service cell group through the first uplink synchronization timer. Thereby solving the problem of how to control the uplink synchronization of the service cell in the NTN system. Furthermore, in some optional embodiments, since the validity period of the first uplink synchronization timer is configured to be infinite, the first uplink synchronization timer will not expire, and accordingly, the MAC entity will not think that the uplink timing of the first service cell group corresponding to the first uplink synchronization timer is out of sync, thereby avoiding clearing all HARQ caches, releasing PUCCH, releasing SRS, clearing pre-configured downlink transmissions, pre-configured uplink authorizations and PUSCH resources for semi-continuous CSI reporting.

[0128] As described above, in the TN system, the terminal device can start or restart the uplink synchronization timer when receiving the TAC MAC CE, and how to start, restart or stop the first uplink timer in the NTN system is the issue to be discussed next, and as described above, in the TN system, the TAC MAC CE includes: TAG ID and TAC indication information, and in the NTN system, the present application can enhance the TAC MAC CE, or propose other information to achieve TA adjustment, frequency deviation information determination, etc., and these contents will be described in detail through the following embodiments:

[0129] Example 1

[0130] Optionally, when the terminal device receives the first indication information, the terminal device starts or restarts the first uplink synchronization timer. The first indication information is associated with the first TAG or the first uplink synchronization timer.

[0131] It should be understood that the first indication information is used to trigger the terminal device to start or restart the first uplink synchronization timer.

[0132] It should be understood that the first indication information is associated with the first TAG or the first uplink synchronization timer, which may mean: the first indication information is associated with the first TAG. Since the first TAG is associated with the first uplink synchronization timer, the first indication information can be used to trigger the terminal device to start or restart the first uplink synchronization timer.

[0133] It should be understood that the association of the first indication information with the first uplink synchronization timer may mean that the first indication information is used to trigger the terminal device to start or restart the first uplink synchronization timer. The association of the first indication information with the first uplink synchronization timer is also described as the first indication information and the first uplink synchronization timer having an associated relationship, or the first indication information corresponds to the first uplink synchronization timer, or the first indication information and the first uplink synchronization timer having a corresponding relationship, and the present application does not impose any restrictions on this.

[0134] It should be understood that, as described above, the first TAG corresponds to the first uplink synchronization timer, and the first indication information is used to trigger the terminal device to start or restart the first uplink synchronization timer. Therefore, the first indication information can be said to be associated with the first TAG. Of course, the first indication information associated with the first TAG is also described as the first indication information and the first TAG having an associated relationship, or the first indication information corresponds to the first TAG, or the first indication information and the first TAG have a corresponding relationship, and this application does not limit this.

[0135] Optionally, the first indication information is used to determine at least one of the following information:

[0136] (1)TA information.

[0137] (2) Frequency deviation information.

[0138] (3)TA change information.

[0139] (4) Frequency deviation change information.

[0140] (5) Timing offset Koffset information.

[0141] (6) Time reference information.

[0142] (7) Location information of reference points.

[0143] (8) Identification of the first TAG.

[0144] It should be understood that, for any first information or combination of information in (1) to (8) above, the so-called first indication information is used to determine the first information or combination of information, which means that the first indication information is used to indicate the first information or combination of information; or, the first indication information is used to indicate other information, and the other information is used to determine the first information or combination of information. This application does not impose any restrictions on this.

[0145] Optionally, the TA information in the above item (1) includes at least one of the following information: cell common TA, beam common TA, and feedback link (feedlink) TA.

[0146] Optionally, the cell common TA may be a common TA of a serving cell associated with the first TAG.

[0147] Optionally, the cell common TA may be a common TA between serving cells corresponding to the first TAG and other TAGs.

[0148] Optionally, the beam-common TA may be a common TA corresponding to a first beam of a service cell associated with the first TAG, wherein the first beam includes one or more beams.

[0149] Optionally, the beam-common TA may be a common TA between different beams, and one TAG may correspond to one or more beams.

[0150] Optionally, when the TA information is a cell-common TA or a beam-common TA, after the terminal device obtains the TA information, the terminal device may adjust the uplink timing in advance according to the TA information and the terminal device's own GNSS capability; or, the terminal device may adjust the uplink timing in advance according to the TA information. Of course, even if the terminal device obtains the TA information, it may not need to use the TA information, but adjust the uplink timing in advance according to its own GNSS capability, and this application does not limit this.

[0151] It should be understood that the above feedback link can be Figure 1C The feedback link between the satellite and the base station is shown.

[0152] Optionally, the terminal device may determine the TA between the terminal device and the base station based on the feedback link TA. The application does not limit how to determine the TA.

[0153] Optionally, the frequency deviation information in the above item (2) is configured by the network device to the terminal device, for example, a common frequency deviation for a service cell associated with the first TAG. Optionally, the frequency deviation information indicates a Doppler shift. Optionally, the frequency deviation information indicates a frequency deviation between a receiving frequency of the terminal device and a transmitting frequency of the network device. For example: if the network device sends or receives a signal at a carrier frequency of 2 GHz, and the frequency deviation information is 1 Khz, the terminal device receives or sends the signal at 2 GHz + 1 Khz = 2.001 GHz.

[0154] Optionally, the TA change information in the above item (3) is used to measure the change of TA in a unit time, wherein the unit of the unit time may be milliseconds, seconds, time slots, etc., which is not limited in the present application. For example, the TA change information is TA drift.

[0155] Optionally, the TA change information may be the change information of the TA information mentioned in item (1), namely, the change information of the cell common TA, the change information of the beam common TA, the change information of the feedback link TA, etc.

[0156] Optionally, if the terminal device has acquired the cell common TA information before the current moment, the terminal device may determine the current cell common TA information according to the cell common TA information before the current moment and the change information of the cell common TA.

[0157] Optionally, after the terminal device obtains the current cell public TA information, the terminal device may adjust the uplink timing in advance according to the current cell public TA information and the terminal device's own GNSS capability; or, the terminal device may adjust the uplink timing in advance according to the current cell public TA information. Of course, even if the terminal device obtains the current cell public TA information, it may not need to use the current cell public TA information, but adjust the uplink timing in advance according to its own GNSS capability, and this application does not limit this.

[0158] Optionally, if the terminal device has acquired the beam-common TA information before the current moment, the terminal device may determine the current beam-common TA information according to the beam-common TA information before the current moment and the change information of the beam-common TA.

[0159] Optionally, after the terminal device obtains the current beam-common TA information, the terminal device may adjust the uplink timing in advance according to the current beam-common TA information and the terminal device's own GNSS capability; or, the terminal device may adjust the uplink timing in advance according to the current beam-common TA information. Of course, even if the terminal device obtains the current beam-common TA information, it does not need to use the current beam-common TA information, but adjusts the uplink timing in advance according to its own GNSS capability, and this application does not impose any restrictions on this.

[0160] Optionally, if the terminal device has acquired the feedback link TA before the current moment, the terminal device can determine the current feedback link TA based on the feedback link TA before the current moment and the change information of the feedback link TA. Optionally, the terminal device can determine the TA between the terminal device and the base station based on the feedback link TA.

[0161] Optionally, the frequency deviation change information in item (4) above is used to measure the change of the frequency deviation information within a unit time, or the frequency deviation change information is Doppler shift change information, which is used to measure the change of the Doppler shift information within a unit time. The unit of the unit time can be milliseconds, seconds, time slots, etc., and this application does not limit this. For example, the frequency deviation change information is frequency deviation drift.

[0162] Optionally, if the terminal device has acquired the frequency offset information before the current moment, the terminal device may determine the current frequency offset information based on the frequency offset information before the current moment and the frequency offset change information.

[0163] Optionally, the Koffset information in item (5) above can be obtained based on Figure 2 Optionally, the unit of Koffset may be milliseconds, seconds, time slots, etc. Optionally, the unit of the indicated Koffset may be milliseconds, and the terminal device converts the unit of Koffset from milliseconds to time slots according to the subcarrier spacing configuration. For example, the indicated Koffset is 20 milliseconds, and the terminal device determines that Koffset is 40 time slots based on the configured subcarrier spacing of 30 kHz.

[0164] Optionally, the time reference information in the above item (6) is absolute time information, and the network device configures the same time reference information for all terminal devices.

[0165] Optionally, the location information of the reference point in item (7) above may be the location information of the satellite or the location information of the base station, or the location information of a certain point between the link of the satellite and the base station, and this application does not impose any restrictions on this.

[0166] Optionally, after the terminal device obtains the location information of the reference point, the terminal device may adjust the uplink timing in advance according to the location information of the reference point and the GNSS capability of the terminal device itself; or, the terminal device may adjust the uplink timing in advance according to the location information of the reference point. Of course, even if the terminal device obtains the location information of the reference point, it may not need to use the location information of the reference point, but adjust the uplink timing in advance according to its own GNSS capability, and this application does not limit this.

[0167] Optionally, the identifier of the first TAG in item (8) can be used to trigger the terminal device to start or restart the first uplink synchronization timer.

[0168] Optionally, the first indication information is carried in at least one of the following: system message, RRC signaling, MAC CE, DCI, RS.

[0169] It should be understood that since the first indication information can be carried in at least one of the following: system message, RRC signaling, MAC CE, DCI, RS, when the terminal device receives the first indication information, the first uplink synchronization timer is started or restarted, which is also described as: when the terminal device receives at least one of the system message, RRC signaling, MAC CE, DCI, RS carrying the first indication information, the first uplink synchronization timer is started or restarted. This application does not impose any restrictions on this.

[0170] As an example but not limitation, the first indication information includes an identifier of the first TAG. When the terminal device receives a system message, RRC signaling, MAC CE, DCI or RS carrying the first indication information, the terminal device starts or restarts the first uplink synchronization timer.

[0171] In summary, in this embodiment, when the terminal device receives the first indication information associated with the first TAG or the first uplink synchronization timer, it can start or restart the first uplink synchronization timer, thereby avoiding the situation where the first uplink synchronization timer cannot be updated and expires. Correspondingly, the MAC entity will not think that the uplink timing of the first service cell group corresponding to the first uplink synchronization timer is out of sync, thereby avoiding clearing all HARQ caches, releasing PUCCH, releasing SRS, clearing pre-configured downlink transmissions, pre-configured uplink authorizations and PUSCH resources for semi-continuous CSI reporting.

[0172] Example 2

[0173] Optionally, when the terminal device receives the second indication information, the terminal device starts or restarts the first uplink synchronization timer. The second indication information is associated with the first TAG or the first uplink synchronization timer, and the second indication information is carried in the TAC MAC CE.

[0174] It should be understood that, since the second indication information is carried in the TAC MAC CE, when the terminal device receives the second indication information, the terminal device starts or restarts the first uplink synchronization timer. It is also described as: when the terminal device receives the TAC MAC CE, the terminal device starts or restarts the first uplink synchronization timer.

[0175] It should be understood that the second indication information is used to trigger the terminal device to start or restart the first uplink synchronization timer.

[0176] It should be understood that the second indication information is associated with the first TAG or the first uplink synchronization timer, which may mean: the second indication information is associated with the first TAG. Since the first TAG is associated with the first uplink synchronization timer, the second indication information can be used to trigger the terminal device to start or restart the first uplink synchronization timer.

[0177] It should be understood that the association of the second indication information with the first uplink synchronization timer may mean that the second indication information is used to trigger the terminal device to start or restart the first uplink synchronization timer. The association of the second indication information with the first uplink synchronization timer is also described as the second indication information having an associated relationship with the first uplink synchronization timer, or the second indication information corresponds to the first uplink synchronization timer, or the second indication information having a corresponding relationship with the first uplink synchronization timer, and the present application does not impose any restrictions on this.

[0178] It should be understood that, as described above, the first TAG corresponds to the first uplink synchronization timer, and the second indication information is used to trigger the terminal device to start or restart the first uplink synchronization timer. Therefore, the second indication information can be said to be associated with the first TAG. Of course, the association of the second indication information with the first TAG is also described as the second indication information having an associated relationship with the first TAG, or the second indication information corresponds to the first TAG, or the second indication information has a corresponding relationship with the first TAG, and this application does not limit this.

[0179] In an implementable manner, the second indication information includes an identifier of the first TAG and first TAC information. The first TAC information is used by the terminal device to adjust the TA associated with the first TAG. Alternatively, the first TAC information is not used by the terminal device to adjust the TA associated with the first TAG.

[0180] Optionally, when the first TAC information is used by the terminal device to adjust the TA associated with the first TAG, the terminal device may adjust the TA associated with the first TAG according to the first TAC information, or may adjust the TA associated with the first TAG according to the first TAC information and the terminal device's own GNSS. This application does not impose any restrictions on this.

[0181] Optionally, when the first TAC information is not used for the terminal device to adjust the TA associated with the first TAG, the terminal device may adjust the TA associated with the first TAG according to the terminal device's own GNSS, and this application does not impose any restrictions on this.

[0182] It should be understood that the first TAC information is not used by the terminal device to adjust the TA associated with the first TAG, and can also be described as the first TAC information being ignored.

[0183] Optionally, whether the first TAC information is used by the terminal device to adjust the TA associated with the first TAG is preset or configured by the network device, and this application does not impose any restrictions on this.

[0184] In another achievable manner, the second indication information is used to determine at least one of the following information:

[0185] (1)TA information.

[0186] (2) Frequency deviation information.

[0187] (3)TA change information.

[0188] (4) Frequency deviation change information.

[0189] (5) Timing offset Koffset information.

[0190] (6) Time reference information.

[0191] (7) Location information of reference points.

[0192] (8) Identification of the first TAG.

[0193] Among them, for the explanation of the above 8 items of information, please refer to the explanation of the 8 items of information determined by the first indication information in Example 1, and this application will not go into details.

[0194] As an example but not limitation, the second indication information includes an identifier of the first TAG. When the terminal device receives the TAC MAC CE carrying the second indication information, the terminal device starts or restarts the first uplink synchronization timer.

[0195] In summary, in this embodiment, the terminal device can start or restart the first uplink synchronization timer according to the second indication information, that is, the TAC MAC CE here. Further, the TAC indication information in the TAC MAC CE can be used to adjust the timing in advance, or the TAC indication information in the TAC MAC CE can be not used to adjust the timing in advance, thereby improving the flexibility of the timing in advance adjustment. Alternatively, the terminal device reuses the mechanism of restarting or starting the first uplink synchronization timer by TAC MAC CE, and enhances TAC MAC CE for new requirements such as NTN network, for example, determining at least one of the above 8 items of information through TAC MAC CE.

[0196] Example 3

[0197] Optionally, when the terminal device receives the third indication information, the terminal device starts, restarts or stops the first uplink synchronization timer according to the third indication information, wherein the third indication information is associated with the first TAG or the first uplink synchronization timer.

[0198] Optionally, the third indication information is used to indicate starting, restarting, or stopping the first uplink synchronization timer.

[0199] It should be understood that the third indication information is associated with the first TAG or the first uplink synchronization timer, which may mean: the third indication information is associated with the first TAG. Since the first TAG is associated with the first uplink synchronization timer, the third indication information can be used to instruct the terminal device to start, restart or stop the first uplink synchronization timer.

[0200] It should be understood that the association of the third indication information with the first uplink synchronization timer may mean that the third indication information is used to instruct the terminal device to start or restart the first uplink synchronization timer. The association of the third indication information with the first uplink synchronization timer is also described as the third indication information having an associated relationship with the first uplink synchronization timer, or the third indication information corresponds to the first uplink synchronization timer, or the third indication information has a corresponding relationship with the first uplink synchronization timer, and the present application does not impose any restrictions on this.

[0201] It should be understood that, as described above, the first TAG corresponds to the first uplink synchronization timer, and the third indication information is used to instruct the terminal device to start or restart the first uplink synchronization timer. Therefore, the third indication information can be said to be associated with the first TAG. Of course, the third indication information associated with the first TAG is also described as the third indication information having an associated relationship with the first TAG, or the third indication information corresponds to the first TAG, or the third indication information has a corresponding relationship with the first TAG, and this application does not limit this.

[0202] Optionally, the third indication information is carried in at least one of the following: system message, RRC signaling, MAC CE, DCI, RS, but not limited thereto. For example: the third indication information is 2-bit information at a fixed position in the RRC signaling. When the 2-bit information is "00", it indicates starting the first uplink synchronization timer. When the 2-bit information is "01", it indicates restarting the first uplink synchronization timer. When the 2-bit information is "10", it indicates stopping the first uplink synchronization timer. For another example: the third indication information includes 1-bit information. When the 1-bit information is a first preset value such as "1", it indicates starting or restarting the first uplink synchronization timer. Or, when the 1-bit information is a second preset value such as "0", it indicates stopping the first uplink synchronization timer. For another example: the third indication information includes a first parameter configuration. When the first parameter configuration is received, it indicates starting or restarting the first uplink synchronization timer.

[0203] It should be understood that since the third indication information can be carried in at least one of the following items: system message, RRC signaling, MAC CE, DCI, RS, when the terminal device receives the third indication information, the first uplink synchronization timer is started, restarted or stopped according to the third indication information. It is also described as: when the terminal device receives at least one of the system message, RRC signaling, MAC CE, DCI, RS carrying the third indication information, the first uplink synchronization timer is started, restarted or stopped according to the third indication information. This application does not impose any restrictions on this.

[0204] As an example but not limitation, the third indication information includes an identifier of the first TAG and 1-bit indication information. When the terminal device receives a system message, RRC signaling, MAC CE, DCI or RS carrying the first indication information, if the 1-bit indicates a first preset value, the terminal device starts or restarts the first uplink synchronization timer; or, if the 1-bit indicates a second preset value, the terminal device stops the first uplink synchronization timer.

[0205] In summary, in this embodiment, when the terminal device receives the third indication information associated with the first TAG or the first uplink synchronization timer, it can start, restart or stop the first uplink synchronization timer according to the third indication information, thereby avoiding the situation where the first uplink synchronization timer cannot be updated and expires. Correspondingly, the MAC entity will not believe that the uplink timing of the first service cell group corresponding to the first uplink synchronization timer is out of sync, thereby avoiding the situation where all HARQ caches, PUCCH release, SRS release, pre-configured downlink transmission, pre-configured uplink authorization and PUSCH resources used for semi-continuous CSI reporting are cleared.

[0206] Embodiment 4

[0207] Optionally, the terminal device may determine to start, restart or stop the first uplink synchronization timer.

[0208] Optionally, the terminal device may adjust the TA associated with the first TAG according to the GNSS of the terminal device, but is not limited thereto.

[0209] Optionally, the terminal device may start, restart or stop the first uplink synchronization timer after adjusting the TA associated with the first TAG according to the GNSS of the terminal device, but is not limited to this.

[0210] Optionally, the terminal device may send fourth indication information to the network device, where the fourth indication information is used to determine at least one of the following information:

[0211] (1) Identification of the first TAG.

[0212] (2) The first uplink synchronization timer has been started.

[0213] (3) The first uplink synchronization timer has been restarted.

[0214] (4) The first uplink synchronization timer has been stopped.

[0215] Optionally, the identifier of the first TAG may be used to indicate that the first uplink synchronization timer has been started, restarted, or stopped.

[0216] As an example but not limitation, the third indication information includes an identifier of the first TAG and 1-bit indication information. If the 1-bit indicates a first preset value, such as "1", it indicates that the terminal device has started or restarted the first uplink synchronization timer; or, if the 1-bit indicates a second preset value, such as "0", it indicates that the terminal device has stopped the first uplink synchronization timer.

[0217] In summary, in this embodiment, the terminal device can report the fourth indication information to the network device so that the network device and the terminal device have a consistent understanding of how long the MAC entity will consider the uplink of the service cell associated with the first TAG to be timed synchronized, thereby facilitating the network device to perform uplink scheduling on the terminal device.

[0218] Figure 5 FIG. 5 shows a schematic block diagram of a terminal device 500 according to an embodiment of the present application. Figure 5 As shown, the terminal device 500 includes: a communication unit 510, which is used to obtain a first uplink synchronization timer. The first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain uplink synchronization of at least one service cell in the first service cell group.

[0219] Optionally, the validity period of the first uplink synchronization timer is configured to be infinite.

[0220] Optionally, the method further includes: a processing unit 520, configured to start or restart a first uplink synchronization timer when the communication unit receives the first indication information, wherein the first indication information is associated with the first TAG or the first uplink synchronization timer.

[0221] Optionally, the first indication information is used to determine at least one of the following information:

[0222] TA information.

[0223] Frequency deviation information.

[0224] TA change information.

[0225] Frequency deviation change information.

[0226] Timing offset Koffset information.

[0227] Time reference information.

[0228] The location information of the reference point.

[0229] The identifier of the first tag.

[0230] Optionally, the first indication information is carried in at least one of the following: system message, RRC signaling, MAC CE, DCI, RS.

[0231] Optionally, the method further includes: a processing unit 520, configured to start or restart the first uplink synchronization timer when the communication unit receives the second indication information, wherein the second indication information is associated with the first TAG or the first uplink synchronization timer, and the second indication information is carried in the timing advance command TAC MAC CE.

[0232] Optionally, the second indication information includes an identifier of the first TAG and first TAC information, wherein the first TAC information is used by the terminal device to adjust the TA associated with the first TAG, or the first TAC information is not used by the terminal device to adjust the TA associated with the first TAG.

[0233] Optionally, whether the first TAC information is used by the terminal device to adjust the TA associated with the first TAG is preset or configured by the network device.

[0234] Optionally, the second indication information is used to determine at least one of the following information:

[0235] TA information.

[0236] Frequency deviation information.

[0237] TA change information.

[0238] Frequency deviation change information.

[0239] Timing offset Koffset information.

[0240] Time reference information.

[0241] The location information of the reference point.

[0242] The identifier of the first tag.

[0243] Optionally, the method further includes: a processing unit 520, configured to start, restart or stop the first uplink synchronization timer according to the third indication information when the communication unit receives the third indication information, wherein the third indication information is associated with the first TAG or the first uplink synchronization timer.

[0244] Optionally, the third indication information is used to indicate starting, restarting, or stopping the first uplink synchronization timer.

[0245] Optionally, the third indication information is carried in at least one of the following: system message, RRC signaling, MAC CE, DCI, RS.

[0246] Optionally, the TA information includes at least one of the following information: cell common TA, beam common TA, and feedback link TA.

[0247] Optionally, the processing unit 520 is further configured to: adjust the TA associated with the first TAG according to the TA information, or adjust the TA associated with the first TAG according to the TA information and a global navigation satellite system GNSS of the terminal device.

[0248] Optionally, the method further includes: a processing unit 520, configured to determine whether to start, restart or stop the first uplink synchronization timer.

[0249] Optionally, the communication unit 510 is further configured to send fourth indication information to the network device, where the fourth indication information is used to determine at least one of the following information:

[0250] The identifier of the first tag.

[0251] The first uplink synchronization timer has been started.

[0252] The first uplink synchronization timer has been restarted.

[0253] The first uplink synchronization timer has been stopped.

[0254] Optionally, the processing unit 520 is further configured to adjust the TA associated with the first TAG according to the GNSS of the terminal device.

[0255] Optionally, the communication unit 510 is specifically used to: obtain a first uplink synchronization timer according to RRC configuration information of the network device.

[0256] Optionally, the first uplink synchronization timer is used to maintain uplink synchronization of at least one serving cell in the first serving cell group, including:

[0257] If the first uplink synchronization timer expires, for at least one serving cell, the actions of the terminal device include at least one of the following:

[0258] Clear all HARQ buffers.

[0259] If PUCCH is configured, instruct RRC to release PUCCH.

[0260] If SRS is configured, instruct RRC to release SRS.

[0261] Clears any preconfigured downlink transmissions and preconfigured uplink grants.

[0262] Clear any PUSCH resources used for semi-persistent CSI reporting.

[0263] Optionally, the terminal device is a terminal device in an NTN.

[0264] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0265] It should be understood that the terminal device 500 according to the embodiment of the present application may correspond to the present application. Figure 4 The terminal device in the corresponding method embodiment, and the above and other operations and / or functions of each unit in the terminal device 500 are respectively to achieve the above Figure 4 For the sake of brevity, the corresponding processes of the terminal device in the corresponding method embodiment will not be repeated here.

[0266] Figure 6 FIG. 6 shows a schematic block diagram of a network device 600 according to an embodiment of the present application. Figure 6 As shown, the network device 600 includes: a communication unit 610, configured to configure a first uplink synchronization timer for a terminal device. The first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain uplink synchronization of at least one service cell in the first service cell group.

[0267] Optionally, the validity period of the first uplink synchronization timer is configured to be infinite.

[0268] Optionally, the communication unit 610 is further configured to send first indication information to the terminal device, wherein the first indication information is used to trigger the terminal device to start or restart a first uplink synchronization timer, and the first indication information is associated with the first TAG or the first uplink synchronization timer.

[0269] Optionally, the first indication information is used to determine at least one of the following information:

[0270] TA information.

[0271] Frequency deviation information.

[0272] TA change information.

[0273] Frequency deviation change information.

[0274] Timing offset Koffset information.

[0275] Time reference information.

[0276] The location information of the reference point.

[0277] The identifier of the first tag.

[0278] Optionally, the first indication information is carried in at least one of the following: system message, RRC signaling, MAC CE, DCI, RS.

[0279] Optionally, the communication unit 610 is further configured to send second indication information to the terminal device, wherein the second indication information is used to trigger the terminal device to start or restart the first uplink synchronization timer. The second indication information is associated with the first TAG or the first uplink synchronization timer, and the second indication information is carried in the TAC MAC CE.

[0280] Optionally, the second indication information includes an identifier of the first TAG and first TAC information, wherein the first TAC information is used by the terminal device to adjust the TA associated with the first TAG, or the first TAC information is not used by the terminal device to adjust the TA associated with the first TAG.

[0281] Optionally, whether the first TAC information is used by the terminal device to adjust the TA associated with the first TAG is preset or configured by the network device.

[0282] Optionally, the second indication information is used to determine at least one of the following information:

[0283] TA information.

[0284] Frequency deviation information.

[0285] TA change information.

[0286] Frequency deviation change information.

[0287] Timing offset Koffset information.

[0288] Time reference information.

[0289] The location information of the reference point.

[0290] The identifier of the first tag.

[0291] Optionally, the communication unit 610 is further configured to send third indication information to the terminal device, wherein the third indication information is used to instruct the terminal device to start, restart or stop the first uplink synchronization timer according to the third indication information, and the third indication information is associated with the first TAG or the first uplink synchronization timer.

[0292] Optionally, the third indication information is carried in at least one of the following: system message, RRC signaling, MAC CE, DCI, RS.

[0293] Optionally, the TA information includes at least one of the following information: cell common TA, beam common TA, and feedback link TA.

[0294] Optionally, the TA information is used to adjust the TA associated with the first TAG.

[0295] Optionally, the communication unit 610 is further configured to receive fourth indication information, where the fourth indication information is used to determine at least one of the following information:

[0296] The identifier of the first tag.

[0297] The first uplink synchronization timer has been started.

[0298] The first uplink synchronization timer has been restarted.

[0299] The first uplink synchronization timer has been stopped.

[0300] Optionally, the communication unit 610 is specifically configured to:

[0301] The first uplink synchronization timer is configured to the terminal device through RRC configuration information.

[0302] Optionally, the first uplink synchronization timer is used to maintain uplink synchronization of at least one serving cell in the first serving cell group, including:

[0303] If the first uplink synchronization timer expires, for at least one serving cell, the network device assumes that the behavior of the terminal device includes at least one of the following:

[0304] Clear all HARQ buffers.

[0305] If PUCCH is configured, instruct RRC to release PUCCH.

[0306] If SRS is configured, instruct RRC to release SRS.

[0307] Clears any preconfigured downlink transmissions and preconfigured uplink grants.

[0308] Clear any PUSCH resources used for semi-persistent CSI reporting.

[0309] Optionally, the network device is a network device in an NTN.

[0310] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0311] It should be understood that the network device 600 according to the embodiment of the present application may correspond to a method embodiment on the network device side, and the above and other operations and / or functions of each unit in the network device 600 are respectively for implementing the corresponding processes of the network device in the method embodiment on the network device side. For the sake of brevity, they will not be repeated here.

[0312] Figure 7 It is a schematic structural diagram of a communication device 700 provided in an embodiment of the present application. Figure 7 The communication device 700 shown includes a processor 710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0313] Alternatively, if Figure 7 As shown, the communication device 700 may further include a memory 720. The processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0314] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0315] Alternatively, if Figure 7 As shown, the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

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

[0317] Optionally, the communication device 700 may specifically be a network device of an embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0318] Optionally, the communication device 700 may specifically be a terminal device of an embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0319] Figure 8 It is a schematic structural diagram of the device of an embodiment of the present application. Figure 8 The device 800 shown includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0320] Alternatively, if Figure 8 As shown, the apparatus 800 may further include a memory 820. The processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application.

[0321] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

[0322] Optionally, the apparatus 800 may further include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0323] Optionally, the apparatus 800 may further include an output interface 840. The processor 810 may control the output interface 840 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

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

[0325] Optionally, the apparatus may be applied to a terminal device in an embodiment of the present application, and the apparatus may implement corresponding processes implemented by the terminal device in each method in an embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0326] Optionally, the device mentioned in the embodiments of the present application may also be a chip, for example, a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.

[0327] Fig. 9 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. Fig. 9 As shown, the communication system 900 includes a terminal device 910 and a network device 920 .

[0328] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device or base station in the above method. For the sake of brevity, they are not repeated here.

[0329] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. 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.

[0330] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example 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.

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

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

[0333] Optionally, the computer-readable storage medium can be applied to the network device or base station in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0334] 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 are not repeated here.

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

[0336] Optionally, the computer program product can be applied to the network device or base station in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0337] 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 are not repeated here.

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

[0339] Optionally, the computer program can be applied to the network device or base station in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device or base station in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0340] 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 are not repeated here.

[0341] Those of ordinary skill 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 to be beyond the scope of this application.

[0342] Those skilled in the art can 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.

[0343] In the several embodiments provided in the present 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, 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.

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

[0345] 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.

[0346] 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. In view of such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform 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.

[0347] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device obtains a first uplink synchronization timer; Among them, the first uplink synchronization timer corresponds to the first timing advance group TAG, the first TAG corresponds to the first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain the uplink synchronization of at least one service cell in the first service cell group.

2. The method according to claim 1, characterized in that Also includes: When the terminal device receives the first indication information, the terminal device starts or restarts the first uplink synchronization timer; The first indication information is associated with the first TAG or the first uplink synchronization timer.

3. The method according to claim 2, characterized in that The first indication information is carried in at least one of the following: a system message, a radio resource control RRC signaling, a media access control control element MAC CE, downlink control information DCI, and a reference signal RS.

4. A wireless communication method, characterized in that: include: The network device configures a first uplink synchronization timer for the terminal device; Among them, the first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain uplink synchronization of at least one service cell in the first service cell group.

5. The method according to claim 4, characterized in that Also includes: The network device sends first indication information to the terminal device; Among them, the first indication information is used to trigger the terminal device to start or restart the first uplink synchronization timer; the first indication information is associated with the first TAG or the first uplink synchronization timer.

6. The method according to claim 5, characterized in that The first indication information is carried in at least one of the following: a system message, a radio resource control RRC signaling, a media access control control element MAC CE, downlink control information DCI, and a reference signal RS.

7. A terminal device, characterized in that: include: A communication unit, configured to obtain a first uplink synchronization timer; Among them, the first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain uplink synchronization of at least one service cell in the first service cell group.

8. The terminal device according to claim 7, characterized in that: Also includes: a processing unit, configured to start or restart the first uplink synchronization timer when the communication unit receives the first indication information; The first indication information is associated with the first TAG or the first uplink synchronization timer.

9. The terminal device according to claim 8, characterized in that: The first indication information is carried in at least one of the following: a system message, a radio resource control RRC signaling, a media access control control element MAC CE, downlink control information DCI, and a reference signal RS.

10. A network device, characterized in that: include: A communication unit, configured to configure a first uplink synchronization timer for a terminal device; Among them, the first uplink synchronization timer corresponds to a first TAG, the first TAG corresponds to a first service cell group, the first service cell group includes at least one service cell, and the first uplink synchronization timer is used to maintain uplink synchronization of at least one service cell in the first service cell group.

11. The network device according to claim 10, characterized in that: The communication unit is further used to send first indication information to the terminal device; Among them, the first indication information is used to trigger the terminal device to start or restart the first uplink synchronization timer; the first indication information is associated with the first TAG or the first uplink synchronization timer.

12. The network device according to claim 11, characterized in that: System messages, radio resource control RRC signaling, media access control control element MAC CE, downlink control information DCI, reference signal RS.

13. A terminal device, characterized in that: include: 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 3.

14. A network device, characterized in that: include: 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 as claimed in any one of claims 4 to 6.

Images