Time domain parameter determination method, terminal device and network device

Abstract

Provided in an embodiment of the present invention are a time domain parameter determination method, a terminal device and a network device, applied to the technical field of communications, the embodiments of the present invention comprising: receiving configuration information sent by a network device, the configuration information comprising: a time domain parameter reference value and at least one time domain parameter offset value; and determining a time domain parameter according to the configuration information.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a time domain parameter determination method, terminal equipment and network equipment. Background Art

[0002] In a non-terrestrial network (NTN), for a scenario where a cell contains multiple satellite beams, since the satellite broadcasts the time slot offset K to the terminal device, offset When the timing advance (TA) is set, a K signal needs to be broadcast for each satellite beam. offset or TA, but due to K offset and TA have a wide range of values, and each K offset The TA configuration requires more bit fields, and this configuration method requires greater signaling overhead. Summary of the invention

[0003] An embodiment of the present invention provides a time domain parameter determination method, a terminal device and a network device. By configuring the network device to the terminal device (configuring and sending a time domain parameter reference value and at least one time domain parameter offset value), the signaling overhead can be reduced for a scenario where a cell contains multiple satellite beams, or for a scenario where a satellite serves multiple terminal devices.

[0004] An embodiment of the present invention provides a time domain parameter determination method, a terminal device and a network device. The network device can indicate a time domain parameter reference value and at least one time domain parameter offset value to the terminal device, and determine the time domain parameters accordingly. In this way, multiple different time domain parameters can be configured through a smaller bit domain, and such a configuration method can reduce signaling overhead.

[0005] In a first aspect, a method for determining a time domain parameter is provided, comprising: receiving configuration information sent by a network device; determining a time domain parameter according to the configuration information, wherein the configuration information comprises: a time domain parameter reference value and at least one time domain parameter offset value.

[0006] In a second aspect, a method for determining a time domain parameter is provided, comprising: sending configuration information to a terminal device, the configuration information being used to determine the time domain parameter, the configuration information comprising: a time domain parameter reference value and at least one time domain parameter offset value.

[0007] In a third aspect, a terminal device is provided, including:

[0008] A receiving module, used to receive configuration information sent by a network device, the configuration information including: a time domain parameter reference value and at least one time domain parameter offset value

[0009] The processing module is used to determine the time domain parameters according to the configuration information.

[0010] In a fourth aspect, a network device is provided, including:

[0011] The sending module is used to send configuration information to the terminal device, where the configuration information is used to determine the time domain parameters, and the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

[0012] In a fifth aspect, a terminal device is provided, including:

[0013] A receiver, used for receiving configuration information sent by a network device;

[0014] The processor is used to determine the time domain parameter according to the configuration information, where the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

[0015] In a sixth aspect, a network device is provided, including:

[0016] The transmitter is used to send configuration information to the terminal device, where the configuration information is used to determine the time domain parameters, and the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

[0017] In the seventh aspect, a computer-readable storage medium is provided, comprising: computer instructions, which, when executed on a computer, enable the computer to execute a method as described in the first aspect or any optional implementation of the first aspect, or to execute a method as described in the second aspect or any optional implementation of the second aspect.

[0018] In an eighth aspect, a computer program product is provided, comprising computer instructions. When the computer program product runs on a computer, the computer executes the computer instructions so that the computer executes a method as described in the first aspect or any optional implementation of the first aspect, or executes a method as described in the second aspect or any optional implementation of the second aspect.

[0019] In the ninth aspect, a chip is provided, which is coupled to a memory in a terminal device, so that the chip calls program instructions stored in the memory during operation, so that the terminal device executes a method such as the first aspect or any optional implementation method of the first aspect, or so that the network device executes the second aspect or any optional implementation method of the second aspect.

[0020] In the time domain parameter determination method provided in an embodiment of the present invention, a network device can send configuration information to a terminal device, where the configuration information includes a time domain parameter reference value and at least one time domain parameter offset value, so that the terminal device can determine the time domain parameters based on the configuration information. For a scenario where a cell includes multiple satellite beams, or for a scenario where a satellite serves multiple terminal devices, the terminal device can determine the corresponding multiple time domain parameters, so that multiple different time domain parameters can be configured through a smaller bit domain. Therefore, such a configuration method can reduce signaling overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1A A schematic diagram of the architecture of a wireless communication system provided by an embodiment of the present invention;

[0022] Figure 1B A schematic diagram of the architecture of a wireless communication system provided by an embodiment of the present invention Figure 2 ;

[0023] Figure 1C A schematic diagram of the architecture of a wireless communication system provided by an embodiment of the present invention Figure 3 ;

[0024] Figure 2 A schematic diagram of a satellite network architecture for transparent forwarding provided by an embodiment of the present invention;

[0025] Figure 3 A schematic diagram of a satellite network architecture for regeneration and forwarding provided by an embodiment of the present invention;

[0026] Figure 4 A timing relationship in an NTN system provided by an embodiment of the present invention;

[0027] Figure 5 A second timing relationship in an NTN system provided by an embodiment of the present invention;

[0028] Figure 6 A schematic diagram of a regeneration and forwarding NTN architecture provided by an embodiment of the present invention;

[0029] Figure 7 A schematic diagram of a transparent forwarding NTN architecture provided by an embodiment of the present invention;

[0030] Figure 8 A schematic diagram of a flow chart of a method for determining time domain parameters provided by an embodiment of the present invention;

[0031] Fig. 9 A schematic diagram of the structure of a terminal device provided by an embodiment of the present invention;

[0032] Fig.10 A schematic diagram of the structure of a network device provided by an embodiment of the present invention;

[0033] Fig.11 A schematic diagram of the hardware structure of a terminal device provided in an embodiment of the present invention;

[0034] Fig.12 A schematic diagram of the hardware structure of a satellite provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0035] The technical solutions in the embodiments of the present invention will be described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0036] In the embodiments of the present invention, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present invention should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0037] 1. Background of NTN

[0038] Among the related technologies, 3GPP is studying NTN technology, which generally uses satellite communication to provide communication services to ground users. Compared with ground cellular network communication, satellite communication has the following advantages:

[0039] First of all, satellite communications are not restricted by the user's geographical location. For example, general land communications cannot cover oceans, mountains, deserts and other areas where communication equipment cannot be set up or where there is no communication coverage due to sparse population. For satellite communications, since one satellite can cover a larger area and satellites can orbit the earth, in theory every corner of the earth can be covered by satellite communications.

[0040] Secondly, satellite communications have great social value. Satellite communications can be covered at a relatively low cost in remote mountainous areas, poor and backward countries or regions, so that people in these areas can enjoy advanced voice communications and mobile Internet technologies, which is conducive to narrowing the digital divide with developed regions and promoting the development of these regions.

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

[0042] According to the different orbital altitudes, communication satellites can be divided into low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, geostationary Earth orbit (GEO) satellites, high elliptical orbit (HEO) satellites, etc. At present, the main research is on LEO and GEO.

[0043] 1.LEO

[0044] The altitude of low-orbit satellites ranges from 500km to 1500km, and the corresponding orbital period is about 1.5 hours to 2 hours. The signal propagation delay of single-hop communication between user equipment and satellite is generally less than 20ms. The maximum satellite visibility time is 20 minutes. The signal propagation distance is short, the link loss is small, and the transmission power requirement for user terminals is not high.

[0045] 2. GEO

[0046] Geosynchronous orbit satellites have an orbital altitude of 35786km and a rotation period around the earth of 24 hours. The signal propagation delay of single-hop communication between user equipment and satellite is generally 250ms.

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

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

[0049] Figure 1A One 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.

[0050] For example, Figure 1B This is a schematic diagram of another communication system architecture provided in 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.

[0051] For example, Figure 1C This is a schematic diagram of another communication system architecture provided in 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.

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

[0053] Optionally, Figure 1A-Figure 1C The 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.

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

[0055] The terminal device can be a station (STAION, 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.

[0056] 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.).

[0057] In the embodiment of the present application, the terminal device can 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 a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

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

[0059] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment may be an evolutionary base station (evolutional node B, referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro-micro base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

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

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

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

[0063] 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-1B Taking the communication system shown as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment described in the embodiments of the present invention, which will not be repeated here; the communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited to the embodiments of the present application.

[0064] The technical solution of the embodiment of the present invention 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.

[0065] Optionally, the embodiment of the present invention may be applied to a non-terrestrial network (NTN) system, or may be applied to a terrestrial network (TN) system.

[0066] The communication system in the embodiment of the present invention can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0067] Optionally, the communication system in the embodiment of the present invention can be applied to unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present invention can also be applied to licensed spectrum, where the licensed spectrum can also be considered as an unshared spectrum.

[0068] 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 there can be three relationships. 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.

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

[0070] In the description of the embodiments of the present invention, the term "corresponding" may indicate that there is a direct or indirect correspondence between two things, or an association relationship between the two things, or a relationship of indication and being indicated, configuration and being configured, and the like.

[0071] Optionally, the indication information in the embodiment of the present invention includes at least one of physical layer signaling such as downlink control information (Downlink Control Information, DCI), radio resource control (Radio Resource Control, RRC) signaling and media access control element (Media Access Control Control Element, MAC CE).

[0072] Optionally, the high-layer parameters or high-layer signaling in the embodiment of the present invention include at least one of Radio Resource Control (RRC) signaling and Media Access Control Control Element (MAC CE).

[0073] Currently, there are two types of satellite network architectures considered by 3GPP: one is a satellite network architecture with transparent payload, and the other is a satellite network architecture with regenerative payload.

[0074] A satellite network (i.e., NTN network) may include the following network elements:

[0075] (1) At least one gateway: used to connect the satellite and terrestrial public networks;

[0076] (2) Feeder link: a link used for communication between the gateway and the satellite;

[0077] (3) Service link: the link used for communication between the terminal equipment and the satellite;

[0078] (4) Satellite: Based on the functions it provides, it can be divided into two types: transparent forwarding and regenerative forwarding. For satellites with transparent forwarding, it only provides the functions of wireless frequency filtering, frequency conversion and amplification. It only provides transparent forwarding of signals and does not change the waveform signal it forwards. For satellites with regenerative forwarding, in addition to providing the functions of wireless frequency filtering, frequency conversion and amplification, it can also provide demodulation / decoding, routing / conversion, encoding / modulation functions. It has some or all of the functions of a base station;

[0079] (5) Intersatellite link: exists in the regeneration and forwarding network architecture.

[0080] For example, Figure 2 The schematic diagram of a satellite network architecture with transparent forwarding includes: 5G access network (NG-RAN), 5G core network (5G CN) and data network composed of user equipment (UE), base station (gNB), satellite and ground gateway (NTN gateway). UE and gNB are connected through the new radio (NR) Uu interface (i.e., universal user network interface), base station and 5G core network (5G CN) are connected through the NG interface, and 5G core network and data network (data network) are connected through the N6 interface. Among them, the satellite and the ground gateway form a remote radio unit (RRU). During the data transmission between UE and gNB, it will be forwarded by the satellite and ground gateway. The satellite and ground gateway do not perform protocol stack processing on the data during the forwarding process, thereby realizing transparent forwarding.

[0081] For example, Figure 3The figure is a schematic diagram of a satellite network architecture for regeneration and forwarding, including: NG-RAN, 5G CN and data network composed of UE, satellite and ground gateway. The UE is connected to the satellite through the NR Uu interface, the satellite is connected to the 5GCN through the NG interface, and the 5G core network is connected to the data network through the N6 interface. Among them, the satellite and the ground gateway are connected through the NG interface (i.e. NG overSRI) running on the signal rate indicator (SRI) interface. When the UE transmits data, it will be forwarded by the satellite. The satellite will process the data through the protocol stack during the forwarding process, thereby realizing regeneration and forwarding.

[0082] 2. Timing relationship of NTN system

[0083] In terrestrial communication systems, the propagation delay of signal communication is usually less than 1ms. In NTN systems, due to the long communication distance between terminal equipment and satellites (or network equipment), 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.

[0084] In the NTN system, as in the NR system, the user equipment (UE) 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, the terminal device needs to consider the round trip time (RTT) and transmit in advance during uplink transmission so that the signal can arrive at the base station side in time slot n of the uplink on the base station side. Specifically, the timing relationship in the NTN system may include two situations, as follows: Figure 4 and Figure 5 shown.

[0085] Case 1: Figure 4 As shown in the figure, like the NR system, the downlink time slot and uplink time slot of the network device are aligned, but the downlink time slot of the terminal device is not aligned with the uplink time slot of the terminal device. In order to align the uplink transmission of the terminal device with the uplink time slot of the network device, the terminal device needs to use a larger TA value. When performing uplink transmission, a larger offset value also needs to be introduced. For example, Figure 4 In some cases, the TA value can also be used to determine K offset value.

[0086] It should be noted that, in the accompanying drawings in the embodiments of the present invention, the downlink time slot of the network device or the timing corresponding to the downlink time slot is represented in the drawing as gNB DL; the uplink time slot of the network device or the timing corresponding to the uplink time slot is represented in the drawing as gNB UL; the downlink time slot of the terminal device or the timing corresponding to the downlink time slot is represented in the drawing as UE DL; the uplink time slot of the terminal device or the timing corresponding to the uplink time slot is represented in the drawing as UE UL.

[0087] Optionally, there is an offset value between a downlink timeslot of the network device and an uplink timeslot of the network device.

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

[0089] 3. Timing relationship of NR system

[0090] The timing relationship in the existing NR system is as follows:

[0091] 1) Physical Downlink Shared Channel (PDSCH) reception timing: When the UE is scheduled to receive PDSCH by downlink control information (DCI), the DCI includes K 0 The instructions for this K 0 For example, if the scheduling DCI is received on time slot n, the time slot allocated for PDSCH transmission is time slot n. Among them, K 0 It is determined according to the subcarrier spacing of PDSCH, μ PDSCH and μ PDCCH Used to determine the subcarrier spacing configured for PDSCH and PDCCH respectively. 0 The value range is 0 to 32.

[0092] 2) DCI-scheduled physical uplink shared channel (PUSCH) transmission timing: When the UE is scheduled by DCI to send PUSCH, the DCI includes K 2 The instructions for this K 2For example, if the scheduling DCI is received on time slot n, the time slot allocated for PUSCH transmission is time slot n. Among them, K 2 It is determined according to the subcarrier spacing of PDSCH, μ PUSCH and μ PDCCH Used to determine the subcarrier spacing configured for PUSCH and PDCCH respectively. 2 The value range is 0 to 32.

[0093] 3) Transmission timing of PUSCH scheduled by random access response (RAR) grant: For the time slot scheduled by RAR grant for PUSCH transmission, if the UE initiates physical random access channel (PRACH) transmission, and the UE receives the end position of the physical downlink shared channel (PDSCH) including the corresponding RAR grant message in time slot n, then the UE shall transmit the PUSCH in time slot n+K. 2 +Δ, where K 2 and Δ are agreed upon in the agreement.

[0094] 4) The transmission timing of HARQ-ACK feedback information on the physical uplink control channel (PUCCH) is as follows: for the time slot of PUCCH transmission, if the end position of a PDSCH reception is in time slot n or the end position of a PDCCH reception indicating a semi-persistent scheduling (SPS) PDSCH release is in time slot n, the terminal device should transmit the corresponding HARQ-ACK feedback information on the PUCCH resources in time slot n+K1.

[0095] Among them, the hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback information includes: ACK information, or NACK information; K1 is the number of time slots, and the number of time slots can be indicated by the HARQ feedback timing indication (PDSCH-to-HARQ-timing-indicator) information field in the DCI format, or the number of time slots is provided by the HARQ feedback timing set (such as the dl-DataToUL-ACK parameter). When K1=0, the last time slot corresponding to the PUCCH transmission overlaps with the time slot of the PDSCH reception, or the last time slot corresponding to the PUCCH transmission overlaps with the time slot of the PDCCH reception indicating the SPS PDSCH release.

[0096] 5) MAC CE activation timing: When the HARQ-ACK information corresponding to the PDSCH including the MAC CE command is transmitted in time slot n, the corresponding behavior indicated by the MAC CE command and the downlink configuration assumed by the UE should be transmitted from time slot n. The first time slot after the Indicates the number of time slots included in each subframe under the subcarrier spacing configuration μ.

[0097] 6) CSI transmission timing on PUSCH: The CSI transmission timing on PUSCH is the same as the transmission timing of DCI-scheduled PUSCH transmission in general.

[0098] 7) CSI reference resource timing: For the CSI reference resource reporting CSI in uplink time slot n′, it is based on the single downlink time slot nn. CSI_ref Certainly, among them, μ DL and μ UL They are the subcarrier spacing configurations for downlink and uplink, respectively. CSI_ref The value of depends on the type of CSI reporting.

[0099] 8) Aperiodic SRS transmission timing: If a UE receives a DCI triggering the transmission of an aperiodic SRS in time slot n, the UE The non-periodic SRS in each triggered SRS resource set is transmitted, where k is configured by the high-level parameter slotOffset in each triggered SRS resource set and is determined according to the subcarrier spacing corresponding to the triggered SRS transmission, μ SRS and μ PDCCH They are respectively the subcarrier spacing configuration of the triggered SRS transmission and the PDCCH carrying the triggering command.

[0100] 4. Timing Enhancement of NTN System

[0101] The PDSCH reception timing in the NR system is only affected by the timing of the downlink receiving side and is not affected by the large transmission round-trip delay in the NTN system. Therefore, the NTN system can reuse the PDSCH reception timing in the NR system.

[0102] For other timings affected by the interaction between downlink reception and uplink transmission, in order to work properly in the NTN system, or to overcome the large transmission delay in the NTN system, the timing relationship needs to be enhanced. A simple solution is to introduce an offset parameter K in the system. offset , and apply the parameter to the relevant timing relationship.

[0103] (A) DCI-scheduled PUSCH (including CSI transmitted on PUSCH) transmission timing: If the scheduled DCI is received on time slot n, the time slot allocated for PUSCH transmission is time slot

[0104] (B) RAR grant-scheduled PUSCH transmission timing: For the time slot scheduled by RAR grant for PUSCH transmission, the UE transmits the PUSCH in time slot n+K. 2 +Δ+K offset The PUSCH is transmitted on the

[0105] (C) Transmission timing of HARQ-ACK on PUCCH: For the time slot of PUCCH transmission, the UE should transmit HARQ-ACK in time slot n+K. 1 +K offset The corresponding HARQ-ACK information is transmitted on the PUCCH resources within the HARQ-ACK channel.

[0106] (D) MAC CE activation timing: When the HARQ-ACK information corresponding to the PDSCH including the MAC CE command is transmitted in time slot n, the corresponding behavior indicated by the MAC CE command and the downlink configuration assumed by the UE should be activated from time slot n. It takes effect from the first time slot after the NTN, where X may be determined by the UE capability of the NTN and the value may not be 3.

[0107] (E) CSI reference resource timing: For uplink time slot n ′ The CSI reference resource for reporting CSI is based on a single downlink time slot Sure.

[0108] (F) Aperiodic SRS transmission timing: If a UE receives a DCI triggering the transmission of an aperiodic SRS in time slot n, the UE The non-periodic SRS in each triggered SRS resource set is transmitted.

[0109] 5. Determination of NTN initial TA

[0110] There may be two types of UEs in NTN, one is UE without positioning capability, and the other is UE with positioning capability.

[0111] For UEs without positioning capability, the satellite will locate the nearest point within the coverage area of ​​the satellite ground based on the perigee (i.e. Figure 6 The signal transmission delay between the reference point in the broadcast and the base station broadcasts a common TA, as follows Figure 6 As shown, it is a schematic diagram of a regenerative forwarding NTN architecture, where public TA = 2*d0 / c; d0 is the distance between the satellite and the perigee; d1 is the distance between the satellite and the terminal device.

[0112] like Figure 7 As shown in the figure, for the transparent forwarding NTN architecture diagram, TA = 2*(d0+d0_F) / c. When the UE sends the preamble, it uses the public TA broadcast by the network for compensation. The network indicates a UE-specific TA adjustment value to the UE in the RAR, so that the initial TA of the UE is the cumulative result of the public TA broadcast and the UE-specific TA indicated in the RAR. Among them, d0 is the satellite distance to the perigee (that is, the closest point within the coverage range of the satellite on the ground, that is, Figure 7 d0_F is the distance between the satellite and the ground network equipment; d1 is the distance between the satellite and the terminal equipment.

[0113] Based on the current progress of 3GPP on NTN standardization, offset The following conclusions have been drawn based on the configuration:

[0114] For the initial random access result, the network can configure the cell-level K by broadcasting. offset Or satellite beam level K offset .

[0115] For a connected UE, the network can configure a dedicated K for the UE through RRC signaling or MAC. offset .

[0116] If the network does not configure a UE-specific K offset , then the UE uses the broadcast K offset .

[0117] Based on the current understanding, the network mainly refers to TA to configure K offset For example, K for network broadcast offset , the network needs to configure K_offset based on the maximum TA supported by the cell or a satellite beam; for UE-specific K offset, the network can refer to the UE's TA configuration K offset .

[0118] In addition, for each UE with GNSS positioning capability, a random access request needs to be sent based on the common TA for TA compensation during the initial random access process. Based on the description in the current communication protocol TR38.821, each satellite beam corresponds to at least one ground reference point, that is, at least one common TA needs to be broadcast for each satellite beam.

[0119] For a scenario where a cell contains multiple satellite beams, since the network broadcasts multiple K offset The most intuitive way is to configure a K for each satellite beam. offset and a public TA, and since K offset and TA have a wide range of values, and each K offset The TA configuration requires more bit fields, and this configuration method requires relatively large signaling overhead. How to reduce the configuration signaling overhead is a problem that needs to be solved.

[0120] In order to solve the above problem, an embodiment of the present invention provides a time domain parameter determination method, and a network device can send configuration information to a terminal device, where the configuration information includes a time domain parameter reference value and at least one time domain parameter offset value, so that the terminal device can determine the time domain parameters based on the configuration information. For a scenario where a cell contains multiple satellite beams, or for a scenario where a satellite serves multiple terminal devices, the terminal device can determine the corresponding multiple time domain parameters, so that multiple different time domain parameters can be configured through a smaller bit domain. Therefore, such a configuration method can reduce signaling overhead.

[0121] Embodiment 1

[0122] like Figure 8 As shown, an embodiment of the present invention provides a method for determining time domain parameters, including:

[0123] 801. The network device sends configuration information to the terminal device.

[0124] The configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

[0125] Optionally, the time domain parameters may include the following:

[0126] Case 1: The time domain parameter can be K offset ;

[0127] In this case 1, the time domain parameter reference value is K offset The reference value, which can be recorded as K in this embodiment offset_ref; the time domain parameter offset value is K offset The offset value of at least one time domain parameter can be expressed as: delteK offset _i;

[0128] Among them, 0<=i<N, and N is greater than or equal to 0.

[0129] Optionally, in this embodiment of the present invention, if the time domain parameter is the K offset , then determine the time domain resource position of the uplink transmission according to the time domain parameters.

[0130] Case 2: The time domain parameter may be a common TA.

[0131] In case 2, the time domain parameter reference value is the reference value of the common TA, which can be recorded as commonTA_ref in this embodiment; the time domain parameter offset value is the offset value of the common TA, and the above at least one time domain parameter offset value can be expressed as: delte common TA_i.

[0132] Optionally, at least one time domain parameter offset value corresponds to at least one object, and one time domain parameter offset value corresponds to one or more objects; wherein, the at least one object is at least one beam, or the at least one object is at least one terminal device.

[0133] Optionally, the network device in the embodiment of the present invention may be a base station or a satellite, and the beam may refer to a base station beam or a satellite beam. When the network device in the embodiment of the present invention is a base station, the beam refers to a base station beam; when the network device in the embodiment of the present invention is a satellite, the beam refers to a satellite beam.

[0134] Optionally, in an embodiment of the present invention, if the time domain parameter is the common TA, TA compensation is performed when sending a random access request during a random access process according to the time domain parameter.

[0135] Optionally, in an embodiment of the present invention, if the time domain parameter is the common TA, it is applied to a terminal device without positioning capability.

[0136] Optionally, the random access process includes: a four-step random access process, and / or a two-step random access process.

[0137] The network device may send the configuration information in at least one of the following ways:

[0138] (a) configuration information (time domain parameter reference value and at least one time domain parameter offset value) is sent via broadcast;

[0139] (b) The time domain parameter reference values ​​are sent via broadcast;

[0140] (c) If at least one time domain parameter offset value corresponds to at least one beam, the at least one time domain parameter offset value is sent via broadcast or multicast:

[0141] (d) If at least one time domain parameter offset value corresponds to at least one terminal device, then at least one time domain parameter offset value is sent via multicast or via dedicated signaling.

[0142] The dedicated signaling may be MAC CE signaling or RRC signaling.

[0143] 802. The terminal device determines time domain parameters according to the configuration information.

[0144] Depending on the configuration information, the implementation of 802 may vary. The following is a detailed description:

[0145] (1) An implementation manner of configuration information: the time domain parameter reference value is a time domain parameter reference value shared by at least one object; and the at least one time domain parameter offset value includes a time domain parameter offset value corresponding to each object.

[0146] With respect to the implementation of the configuration information in (1) above, the implementation of 802 includes: determining the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value;

[0147] Among them, the first time domain parameter offset value is one of at least one time domain parameter offset value; the first time domain parameter offset value corresponds to the beam where the terminal device is located, or the first time domain parameter offset value corresponds to the terminal device.

[0148] Optionally, determining the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value includes: calculating the sum of the time domain parameter reference value and the first time domain parameter offset value to obtain the time domain parameter.

[0149] Optionally, determining the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value includes: calculating the difference between the time domain parameter reference value and the first time domain parameter offset value to obtain the time domain parameter.

[0150] Optionally, for a transparent forwarding non-terrestrial communication NTN architecture, the time domain parameter reference value is determined according to a first round-trip time (RTT) and a second RTT;

[0151] The first RTT is: the RTT between the first reference point and the network device, and the uplink time domain and the downlink time domain of the first reference point are aligned.

[0152] The second RTT is: the RTT between the network device and a ground reference point within the cell where the terminal device is located.

[0153] Among them, the network equipment is a non-ground network equipment that provides services to the terminal equipment.

[0154] Optionally, the time domain parameter reference value is the sum of the first RTT and the second RTT.

[0155] Optionally, for the regeneration and forwarding NTN architecture, the time domain parameter reference value corresponds to a second RTT, the second RTT is the RTT between the network device and a ground reference point within the cell where the terminal device is located, and the network device is a non-ground network device that provides services to the terminal device.

[0156] (2) Another implementation manner of the configuration information: the time domain parameter reference value is a time domain parameter corresponding to the first object; each of the at least one time domain offset value is an offset value of a time domain parameter corresponding to at least one other object relative to the time domain parameter reference value;

[0157] The at least one other object is an object other than the first object among all the objects.

[0158] In this embodiment, the above-mentioned all objects refer to all beams of the satellite, or the above-mentioned all objects refer to all beams served by the satellite.

[0159] Regarding the implementation of the configuration information (2) above, one implementation of 802 includes:

[0160] If the terminal device corresponds to the first object, the time domain parameter reference value is determined as the time domain parameter.

[0161] The above-mentioned terminal device corresponding to the first object may include: the terminal device is a first terminal device, or the terminal device is located in a first beam.

[0162] Optionally, the time domain parameter reference value is a time domain parameter corresponding to the first terminal device. In this case, when the terminal device is determined to be the first terminal device, the time domain parameter reference value is determined to be the time domain parameter.

[0163] Optionally, the time domain parameter reference value is a time domain parameter corresponding to the first beam. In this case, when it is determined that the terminal device is located in the first beam, it can be determined that the time domain parameter reference value is the time domain parameter.

[0164] With respect to the implementation of the configuration information in (2), another implementation of 802 includes: if the terminal device corresponds to the second object, determining the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value;

[0165] Among them, the first time domain parameter offset value is one of at least one time domain parameter offset value; the first time domain parameter offset value corresponds to the satellite beam where the terminal device is located, or the first time domain parameter offset value corresponds to the terminal device; wherein the second object is one of at least one other object.

[0166] Optionally, the time domain parameter reference value is a time domain parameter corresponding to the first terminal device. In this case, when determining that the terminal device is the second terminal device, it is necessary to determine the time domain parameter based on the time domain parameter reference value and the first time domain parameter offset value. In this case, the first time domain parameter offset value is the time domain parameter offset value corresponding to the second terminal device.

[0167] Optionally, the time domain parameter reference value is the time domain parameter corresponding to the first beam. In this case, when determining that the terminal device is located in the second beam, it is necessary to determine the time domain parameter based on the time domain parameter reference value and the first time domain parameter offset value. In this case, the first time domain parameter offset value is the time domain parameter offset value corresponding to the second beam.

[0168] In the time domain parameter determination method provided in an embodiment of the present invention, a network device can send configuration information to a terminal device, where the configuration information includes a time domain parameter reference value and at least one time domain parameter offset value, so that the terminal device can determine the time domain parameters based on the configuration information. For a scenario where a cell includes multiple satellite beams, or for a scenario where a satellite serves multiple terminal devices, the terminal device can determine the corresponding multiple time domain parameters, and in this way, multiple different time domain parameters can be configured through a smaller bit domain. Therefore, such a configuration method can reduce signaling overhead.

[0169] In order to more clearly illustrate the time domain parameter determination method provided by an embodiment of the present invention, the embodiments of the present invention will be introduced below based on the case where at least one time domain parameter offset value corresponds to at least one satellite beam (involving the following embodiments 2 to 5), and the case where at least one time domain parameter offset value corresponds to at least one terminal device (involving the following embodiments 6 to 9).

[0170] Embodiment 2

[0171] K for satellite beam level offset Configuration method:

[0172] Network device configuration a K offset Reference value K offset _ref, and configure a delta K for each satellite beam i offset _i, then the K corresponding to satellite beam i offset K offset _ref and delte K offset The sum of _i.

[0173] The specific implementation process is as follows:

[0174] First, the network equipment configures a K for each satellite beam. offset , the K offset Used to determine the time domain resource location of UE uplink transmission. The network device configures the K offset The method is as follows:

[0175] a) Configure a time domain parameter reference value K offset , denoted as K offset _ref. For example:

[0176] For the transparent forwarding NTN architecture, the K offset _ref corresponds to the sum of the RTT between the first reference point and the serving satellite and the RTT between the serving satellite and a ground reference point (within the ground coverage of the cell). The uplink timing (UL timing) and the downlink timing (DL timing) at the first reference point are aligned.

[0177] For the regenerative forwarding NTN architecture, the K offset _ref corresponds to the RTT between the serving satellite and a ground reference point (within the cell's ground coverage).

[0178] b) For each satellite beam i, configure a time domain parameter offset value, denoted as delte K offset _i, the delte K offset _i represents the K corresponding to satellite beam i offset Relative to K offset _ref increment. Where 0 is greater than or equal to i,

[0179] And i<N, N is the number of satellite beams contained in the cell, and the beam index is 0 to N-1.

[0180] Then, based on the network device configuration, the terminal device uses the K corresponding to the satellite beam where it is located. offset That is, if the terminal device is located in satellite beam i, and the network does not configure the terminal device with a terminal device-specific K offset , then the terminal device uses K offset K offset _ref and delte K offset The sum of _i.

[0181] For example, it is assumed that the cell where the current terminal device is located includes three satellite beams. The following table 1 shows a configuration K for each satellite beam: offset Schematic diagram of the network. Among them, the network equipment can be configured by broadcasting: a time domain Koffset _ref, time domain parameter offset value delte K for satellite beam 0 offset _0, time domain parameter offset value delte K for satellite beam 1 offset _1. Time domain parameter offset value delte K for satellite beam 2 offset _2. Then, correspondingly, when the terminal device is located in satellite beam 0, the K of the terminal device located in satellite beam 0 is determined. offset _0=K offset _ref+delteK offset _0; when the terminal device is located in satellite beam 1, determine the K of the terminal device located in satellite beam 1 offset _1=K offset _ref+delte K offset _1; when the terminal device is located in satellite beam 0, determine the K of the terminal device located in satellite beam 2 offset _2=K offset _ref+delte K offset _2.

[0182] Table 1

[0183]

[0184] Embodiment 3

[0185] K for satellite beam level offset Configuration method:

[0186] The network device configures a K for satellite beam 0 offset K offset _0, and configure a delta K for each satellite beam i (where i>0) offset _i, then the K corresponding to satellite beam i offset K offset _0 and delte K offset The sum of _i.

[0187] The specific implementation process is as follows:

[0188] First, the network equipment configures a K for each satellite beam. offset , the K offset It is used to determine the time domain resource location of the terminal device uplink transmission. The network device configures the K offset The method is as follows:

[0189] a) For satellite beam 0, configure K offset , denoted as K offset _0.

[0190] b) For each satellite beam i, configure a K offset Offset value, denoted as delte K offset _i, the delteK offset _i represents the K corresponding to satellite beam i offset Relative to K offset _0. Where 0<i<N, N is the number of satellite beams contained in the cell.

[0191] Then, based on the network device configuration, the terminal device uses the K corresponding to the satellite beam where it is located. offset That is, if the terminal device is located in satellite beam i, and the network device does not configure the terminal device with a terminal device-specific K offset , then the terminal device uses K offset for:

[0192] a) If the terminal device is located in beam 0, the K used by the terminal device offset K is broadcast by network devices offset _0;

[0193] b) Otherwise, if the terminal device is located in beam i (i is not equal to 0), the K used by the terminal device is offset K offset _0 and delte K offset The sum of _i.

[0194] For example, assuming that the cell where the current terminal device is located includes three satellite beams, the following Table 2 shows a configuration K for each satellite beam: offset Schematic diagram of the network equipment. The network equipment can be configured by broadcasting: the time domain parameter K for satellite beam 0 offset _0, time domain parameter offset value delte K for satellite beam 1 offset _1. Time domain parameter offset value delte K for satellite beam 2 offset _2. Then, correspondingly, when the terminal device is located in satellite beam 0, the time domain parameter K located in satellite beam 0 is determined. offset _0; when the terminal device is located in satellite beam 1, determine the K of the terminal device located in satellite beam l offset _1=K offset _0+delte K offset _1; when the terminal device is located in satellite beam 0, determine the K of the terminal device located in satellite beam 2 offset _2=K offset _0+delte K offset _2.

[0195] Table 2

[0196]

[0197] Embodiment 4

[0198] Configuration method of common TA at satellite beam level:

[0199] The network device is configured with a common TA reference value common TA_ref, and a delta common TA i is configured for each satellite beam i. The common TA corresponding to satellite beam i is the sum of common TA_ref and delta commonTA_i.

[0200] The specific implementation process is as follows:

[0201] First, the network device configures a common TA for each satellite beam, and the common TA is used for TA compensation when the terminal device without positioning capability transmits msg1 (four-step random access) / msgA (two-step random access) during the random access process. The method for the network device to configure the common TA is as follows:

[0202] a) Configure a common TA reference value, denoted as common TA_ref. For example:

[0203] For the transparent forwarding NTN architecture, the common TA_ref corresponds to the sum of the RTT between the first reference point and the serving satellite and the RTT between the serving satellite and a ground reference point (within the ground coverage of the cell). The UL timing and DL timing at the first reference point are aligned.

[0204] For the regenerative forwarding NTN architecture, the common TA_ref corresponds to the RTT between the serving satellite and a ground reference point (within the ground coverage of the cell).

[0205] c) For each satellite beam i, a common TA offset value is configured, denoted as delta common TA_i, where delta common TA_i represents the increment of the common TA corresponding to satellite beam i relative to common TA_ref, where 0 is greater than or equal to i, and i<N, where N is the number of satellite beams contained in the cell.

[0206] Then, for a terminal device without positioning capability, if the terminal device initiates a random access process, the terminal device uses the common TA corresponding to the satellite beam where it is located based on the network device configuration. That is, if the terminal device is located in satellite beam i, and the terminal device currently has no valid TA available, the terminal device uses the public TA corresponding to satellite beam i to send msgl / msg3. The public TA corresponding to satellite beam i is the sum of common TA_ref and delta common TA_i.

[0207] Exemplarily, assuming that the cell where the current terminal device is located includes 3 satellite beams, the following Table 3 is a schematic diagram of configuring common TA for each satellite beam. Among them, the network device can be configured by broadcasting: a time domain common TA_ref, a time domain parameter offset value delta common TA_0 for satellite beam 0, a time domain parameter offset value delta common TA_1 for satellite beam 1, and a time domain parameter offset value delta commonTA_2 for satellite beam 2. Then correspondingly, when the terminal device is located in satellite beam 0, it is determined that commonTA_0 of the terminal device located in satellite beam 0 is equal to common TA_ref+delta common TA_0; when the terminal device is located in satellite beam 1, it is determined that common TA_1 of the terminal device located in satellite beam 1 is equal to common TA_ref+delta common TA_1; when the terminal device is located in satellite beam 2, it is determined that common TA_2 of the terminal device located in satellite beam 2 is equal to common TA_ref+deltacommon TA_2.

[0208] Table 3

[0209]

[0210] Embodiment 5

[0211] Configuration method of common TA at satellite beam level:

[0212] The network device configures a common TA common TA_0 for satellite beam 0, and configures a delta common TA_i for each satellite beam i (where i>0). The common TA corresponding to satellite beam i is the sum of common TA_0 and delta common TA_i.

[0213] The specific implementation process is as follows:

[0214] First, the network device configures a common TA for each satellite beam, and the common TA is used for TA compensation when the terminal device without positioning capability transmits msg1 (i.e., four-step random access process) / msgA (i.e., two-step random access process) during the random access process. The method for the network device to configure the common TA is as follows:

[0215] a) For satellite beam 0, configure a common TA, denoted as common TA_0.

[0216] b) For each satellite beam i, a common TA offset value is configured, denoted as delta common TA_i, where delta common TA_i represents the increment of the common TA corresponding to satellite beam i relative to common TA_0, where 0<i<N, and N is the number of satellite beams included in the cell.

[0217] Then, for a terminal device without positioning capability, if the terminal device initiates a random access process, the terminal device uses the common TA corresponding to the satellite beam where it is located based on the network device configuration. That is, if the terminal device is located in satellite beam i, and the terminal device currently has no valid TA available, the terminal device uses the public TA corresponding to satellite beam i to send msgl / msg3. Among them, the public TA corresponding to satellite beam i is:

[0218] a) If i=0, common TA_0 is used.

[0219] b) Otherwise, the sum of common TA_0 and delta common TA_i is used.

[0220] Exemplarily, assuming that the cell where the current terminal device is located includes 3 satellite beams, the following Table 4 is a schematic diagram of configuring common TA for each satellite beam. Among them, the network device can be configured by broadcasting: time domain parameter common TA_0 for satellite beam 0, time domain parameter offset value delta common TA_1 for satellite beam 1, and time domain parameter offset value delta common TA_2 for satellite beam 2. Then correspondingly, when the terminal device is located in satellite beam 0, the time domain parameter commonTA_0 located in satellite beam 0 is determined; when the terminal device is located in satellite beam 1, the common TA_1 of the terminal device located in satellite beam 1 is determined to be = commonTA_0 + delta common TA_1; when the terminal device is located in satellite beam 0, the commonTA_2 of the terminal device located in satellite beam 2 is determined to be = common TA_0 + deltacommon TA_2.

[0221] Table 4

[0222]

[0223] Embodiment 6

[0224] K for terminal equipment level offset Configuration method:

[0225] Network device configuration a K offset Reference value K offset _ref, and configure a delte K for each terminal device i offset _i, then the K corresponding to terminal device i offset K offset _ref and delte K offset The sum of _i.

[0226] The specific implementation process is as follows:

[0227] First, the network device configures a K for each terminal device. offset , the K offset Used to determine the time domain resource location of UE uplink transmission. The network device configures the K offset The method is as follows:

[0228] d) Configure a time domain parameter reference value K offset , denoted as K offset _ref. For example:

[0229] For the transparent forwarding NTN architecture, the K offset _ref corresponds to the sum of the RTT between the first reference point and the serving satellite and the RTT between the serving satellite and a ground reference point (within the ground coverage of the cell). The uplink timing (UL timing) and downlink timing (DL timing) at the first reference point are aligned.

[0230] For the regenerative forwarding NTN architecture, the K offset _ref corresponds to the RTT between the serving satellite and a ground reference point (within the cell's ground coverage).

[0231] e) For each terminal device i, configure a time domain parameter offset value, denoted as delte K offset _i, the delte K offset _i indicates the K corresponding to terminal device i offset Relative to K offset _ref increment. Where 0 is greater than or equal to i, and i<N, where N is the number of terminal devices contained in the cell.

[0232] Then, the terminal device uses the K corresponding to its current terminal device based on the network device configuration. offset That is, if the current terminal device is terminal device i, and the network device does not configure a dedicated K for the current terminal device offset , then the K used by the terminal device offset K offset _ref and delte K offset The sum of _i.

[0233] For example, assuming that the satellite serves three terminal devices, the following table 5 shows a configuration K for each terminal device: offset Schematic diagram of the network. Among them, the network equipment can be configured by broadcasting: a time domain K offset _ref, time domain parameter offset value delte K for terminal device 0 offset _0, time domain parameter offset value delteK for terminal device 1 offset _1. Time domain parameter offset value delte K for terminal device 2 offset _2. Then correspondingly, when the current terminal device is terminal device 0, determine the K of terminal device 0 offset _0=K offset _ref+delte K offset _0; when the current terminal device is terminal device 1, determine the K of terminal device 1 offset _1=K offset _ref+delte K offset _1; when the current terminal device is terminal device 0, determine the K of terminal device 2 offset _2=K offset _ref+delte K offset _2.

[0234] Table 5

[0235]

[0236] Embodiment 7

[0237] K for terminal equipment level offset Configuration method:

[0238] The network device configures a time domain parameter K for terminal device 0 offset , denoted as K offset _0, and configure a delte K for each terminal device i (where i>0) offset _i, then the K corresponding to terminal device i offset K offset _0 and delte Koffset The sum of _i.

[0239] The specific implementation process is as follows:

[0240] First, the network device configures a K for each terminal device. offset , the K offset It is used to determine the time domain resource location of the terminal device uplink transmission. The network device configures the K offset The method is as follows:

[0241] c) For terminal device 0, configure K offset , denoted as K offset _0.

[0242] d) For each terminal device i, configure a K offset Offset value, denoted as delte K offset _i, the delteK offset _i indicates the K corresponding to terminal device i offset Relative to K offset _0. Where 0<i<N, N is the number of terminal devices contained in the cell.

[0243] Then, the terminal device uses the K corresponding to its own terminal device based on the network device configuration. offset That is, if the current terminal device is terminal device i, and the network device does not have a K exclusive to the terminal device offset , then the K used by the terminal device offset for:

[0244] c) If the current terminal device is terminal device 0, then the K used by the current terminal device offset K is broadcast by network devices offset _0;

[0245] d) Otherwise, if the current terminal device is terminal device i (i is not equal to 0), then the K used by the current terminal device is offset K offset _0 and delte K offset The sum of _i.

[0246] For example, assuming that the cell where the current terminal device is located includes 3 terminal devices, the following table 6 shows a method for configuring K for each terminal device: offset Schematic diagram of the network device. The network device can be configured by broadcasting: the time domain parameter K of the terminal device 0 offset _0, time domain parameter offset value delte K for terminal device 1 offset _1. Time domain parameter offset value delte K for terminal device 2 offset_2. Then correspondingly, when the current terminal device is terminal device 0, the time domain parameter K at terminal device 0 is determined offset _0; when the current terminal device is terminal device 1, determine the K of terminal device 1 offset _1=K offset _0+delte K offset _1; when the current terminal device is terminal device 2, determine the K of terminal device 2 offset _2=K offset _0+delte K offset _2.

[0247] Table 6

[0248]

[0249] Embodiment 8

[0250] Configuration method of common TA at terminal device level:

[0251] The network device is configured with a common TA reference value common TA_ref, and a delta common TAi is configured for each terminal device i. The common TA corresponding to the terminal device i is the sum of common TA_ref and delta commonTA_i.

[0252] The specific implementation process is as follows:

[0253] First, the network device configures a common TA for each terminal device, and the common TA is used for TA compensation when the terminal device without positioning capability transmits msg1 (four-step random access) / msgA (two-step random access) during the random access process. The method for the network device to configure the common TA is as follows:

[0254] b) Configure a common TA reference value, denoted as common TA_ref. For example:

[0255] For the transparent forwarding NTN architecture, common TA_ref corresponds to the sum of the RTT between the first reference point and the serving satellite and the RTT between the serving satellite and a ground reference point (within the ground coverage of the cell). The UL timing and DL timing at the first reference point are aligned.

[0256] For the regenerative forwarding NTN architecture, the common TA_ref corresponds to the RTT between the serving satellite and a ground reference point (within the ground coverage of the cell).

[0257] c) For each terminal device i, a common TA offset value is configured, denoted as delta common TA_i, where delta common TA_i represents the increment of the common TA corresponding to the terminal device i relative to the common TA_ref.

[0258] Then, for a terminal device without positioning capability, if the terminal device initiates a random access process, the terminal device uses the common TA corresponding to the terminal device it is in based on the network device configuration. That is, if the terminal device is located at terminal device i, and the terminal device currently has no valid TA available, the terminal device uses the public TA corresponding to terminal device i to send msg1 / msg3. Among them, the public TA corresponding to the terminal device i is the sum of common TA_ref and delta common TA_i.

[0259] Exemplarily, assuming that the cell where the current terminal device is located includes 3 terminal devices, the following Table 7 is a schematic diagram of configuring common TA for each terminal device. Among them, the network device can be configured by broadcasting: a time domain parameter reference value common TA_ref, a time domain parameter offset value delta common TA_0 for terminal device 0, a time domain parameter offset value delta common TA_1 for terminal device 1, and a time domain parameter offset value delta common TA_2 for terminal device 2. Then correspondingly, when the current terminal device is terminal device 0, the time domain parameter common TA_0 corresponding to terminal device 0 is determined to be common TA_ref+delta common TA_0; when the current terminal device is terminal device 1, the time domain parameter common TA_1 corresponding to terminal device 1 is determined to be common TA_ref+delta common TA_1; when the current terminal device is terminal device 0, the time domain parameter common TA_2 corresponding to terminal device 2 is determined to be commonTA_ref+delta common TA_2.

[0260] Table 7

[0261]

[0262] Embodiment 9

[0263] Configuration method of common TA at terminal device level:

[0264] The network device configures a common TA common TA_0 for terminal device 0, and configures a delta common TA_i for each terminal device i (where i>0), then the common TA corresponding to terminal device i is the sum of common TA_0 and delta common TA_i.

[0265] The specific implementation process is as follows:

[0266] First, the network device configures a common TA for each terminal device, and the common TA is used for TA compensation when the terminal device without positioning capability transmits msg1 (i.e., four-step random access process) / msgA (i.e., two-step random access process) during the random access process. The method for the network device to configure the common TA is as follows:

[0267] c) For terminal device 0, configure a common TA, denoted as common TA_0.

[0268] d) For each terminal device i, a common TA offset value is configured, recorded as delta common TA_i, where delta common TA_i represents the increment of the common TA corresponding to the terminal device i relative to common TA_0, where 0<i<N, N is the number of terminal devices included in the cell.

[0269] Then, for a terminal device without positioning capability, if the terminal device initiates a random access process, the terminal device uses the common TA corresponding to its own terminal device based on the network device configuration. That is, if the current terminal device is terminal device i, and the terminal device currently has no valid TA, msg1 / msg3 is sent using the public TA corresponding to terminal device i. The public TA corresponding to the terminal device i is:

[0270] c) If i=0, common TA_0 is used.

[0271] d) Otherwise, the sum of common TA_0 and delta common TA_i is used.

[0272] Exemplarily, assuming that the cell where the current terminal device is located includes 3 terminal devices, as shown in Table 8 below, is a schematic diagram of configuring common TA for each terminal device. Among them, the network device can be configured by broadcasting: time domain parameter common TA_0 for terminal device 0, time domain parameter offset value delta common TA_1 for terminal device 1, and time domain parameter offset value delta common TA_2 for terminal device 2. Then correspondingly, when the current terminal device is terminal device 0, the time domain parameter common TA_0 corresponding to terminal device 0 is determined; when the current terminal device is terminal device 1, the time domain parameter common TA_1 corresponding to terminal device 1 is determined to be common TA_0+delta common TA_1; when the terminal device is located at terminal device 0, the time domain parameter common TA_2 corresponding to terminal device 2 is determined to be common TA_0+delta common TA_2.

[0273] Table 8

[0274]

[0275] The configuration method in the embodiment of the present invention can be applicable to the scenario where a cell contains multiple satellite beams, or the scenario where the satellite serves multiple terminal devices. Such a configuration method can configure multiple different time domain parameters through fewer bit domains, thereby reducing signaling overhead.

[0276] like Fig. 9 As shown, a terminal device is provided, including:

[0277] Receiving module 901, used to receive configuration information sent by the network device;

[0278] The processing module 902 is used to determine a time domain parameter according to configuration information, where the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

[0279] Optionally, at least one time domain parameter offset value corresponds to at least one object, and one time domain parameter offset value corresponds to one or more objects;

[0280] Among them, at least one object is at least one beam, or at least one object is at least one terminal device.

[0281] Optionally, the time domain parameter reference value is a time domain parameter reference value shared by at least one object;

[0282] The at least one time-domain parameter offset value includes a time-domain parameter offset value corresponding to each object.

[0283] Optionally, the processing module 902 is specifically configured to determine the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value;

[0284] Among them, the first time domain parameter offset value is one of at least one time domain parameter offset value; the first time domain parameter offset value corresponds to the beam where the terminal device is located, or the first time domain parameter offset value corresponds to the terminal device.

[0285] Optionally, for a transparent forwarding non-terrestrial communication NTN architecture, the time domain parameter reference value is determined according to the first round-trip delay RTT and the second RTT;

[0286] The first RTT is: the RTT between the first reference point and the network device, and the uplink time domain and the downlink time domain of the first reference point are aligned;

[0287] The second RTT is: the RTT between the network device and a ground reference point within the cell where the terminal device is located.

[0288] Among them, the network equipment is a non-ground network equipment that provides services to the terminal equipment.

[0289] Optionally, the time domain parameter reference value is the sum of the first RTT and the second RTT.

[0290] Optionally, for the regeneration and forwarding NTN architecture, the time domain parameter reference value corresponds to a second RTT, the second RTT is the RTT between the network device and a ground reference point within the cell where the terminal device is located, and the network device is a non-ground network device that provides services to the terminal device.

[0291] Optionally, the time domain parameter reference value is a time domain parameter corresponding to the first object;

[0292] Each of the at least one time domain offset value is: an offset value of a time domain parameter corresponding to at least one other object relative to a time domain parameter reference value; wherein the at least one other object is an object other than the first object among all objects.

[0293] Optionally, the processing module 902 is specifically configured to determine the time domain parameter reference value as the time domain parameter if the terminal device corresponds to the first object.

[0294] Optionally, the processing module 902 is specifically configured to determine the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value if the terminal device corresponds to the second object;

[0295] Wherein, the first time domain parameter offset value is one of at least one time domain parameter offset value;

[0296] The first time domain parameter offset value corresponds to the satellite beam where the terminal device is located, or the first time domain parameter offset value corresponds to the terminal device; the second object is one of at least one other object.

[0297] Optionally, the processing module 902 is specifically configured to calculate the sum of the time domain parameter reference value and the first time domain parameter offset value to obtain the time domain parameter.

[0298] Optionally, the time domain parameter is the time slot offset K offset ;

[0299] Optionally, the time domain parameter is a common timing advance TA.

[0300] Optionally, the processing module 902 is further configured to determine the time domain parameter according to the configuration information, and if the time domain parameter is K offset , the time domain resource position of the uplink transmission is determined according to the time domain parameters; if the time domain parameters are common TA, TA compensation is performed when sending a random access request during the random access process according to the time domain parameters.

[0301] Optionally, if the time domain parameter is a public TA, it is applied to terminal devices without positioning capability.

[0302] Optionally, the random access process includes: a four-step random access process, and / or a two-step random access process.

[0303] Optionally, the time domain parameter reference value is sent via broadcast.

[0304] Optionally, if at least one time domain parameter offset value corresponds to at least one beam, the at least one time domain parameter offset value is sent via broadcast or multicast.

[0305] Optionally, if at least one time domain parameter offset value corresponds to at least one terminal device, the at least one time domain parameter offset value is sent via multicast or via dedicated signaling.

[0306] Optionally, the network device is a satellite.

[0307] like Fig.10 As shown, a network device is provided, including:

[0308] The sending module 1001 is used to send configuration information to the terminal device, where the configuration information is used to determine the time domain parameters, and the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

[0309] Optionally, at least one time domain parameter offset value corresponds to at least one object, and one time domain parameter offset value corresponds to one or more objects;

[0310] Among them, at least one object is at least one beam, or at least one object is at least one terminal device.

[0311] Optionally, the time domain parameter reference value is a time domain parameter reference value corresponding to each object;

[0312] At least one time domain parameter offset value is a time domain parameter offset value corresponding to each object.

[0313] Optionally, for the transparent forwarding NTN architecture, the time domain parameter reference value is determined according to the first RTT and the second RTT;

[0314] The first RTT is: the RTT between the first reference point and the network device, and the uplink time domain and the downlink time domain of the first reference point are aligned;

[0315] The second RTT is: the RTT between the network device and a ground reference point within the cell where the terminal device is located.

[0316] Among them, the network equipment is a non-ground network equipment that provides services to the terminal equipment.

[0317] Optionally, the time domain parameter reference value is the sum of the first RTT and the second RTT.

[0318] Optionally, for the regeneration and forwarding NTN architecture, the time domain parameter reference value corresponds to a second RTT, the second RTT is the RTT between the network device and a ground reference point within the cell where the terminal device is located, and the network device is a non-ground network device that provides services to the terminal device.

[0319] Optionally, the time domain parameter is the time slot offset K offset ;

[0320] or,

[0321] The time domain parameter is the timing advance TA.

[0322] Optionally, the time domain parameter reference value is sent via broadcast.

[0323] Optionally, if at least one time domain parameter offset value corresponds to at least one beam, the at least one time domain parameter offset value is sent via broadcast or multicast;

[0324] If at least one time domain parameter offset value corresponds to at least one terminal device, then the at least one time domain parameter offset value is sent via multicast or via dedicated signaling.

[0325] Optionally, the network device is a satellite.

[0326] An embodiment of the present invention further provides a terminal device, comprising: a memory storing executable program code;

[0327] a processor coupled to the memory;

[0328] The processor calls the executable program code stored in the memory to execute the time domain parameter determination method executed by the terminal device in the embodiment of the present invention.

[0329] An embodiment of the present invention further provides a network device, comprising: a memory storing executable program code;

[0330] a processor coupled to the memory;

[0331] The processor calls the executable program code stored in the memory to execute the time domain parameter determination method executed by the network device in the embodiment of the present invention.

[0332] For example, Fig.11 The figure shows a terminal device provided in an embodiment of the present invention, which includes: a radio frequency (RF) circuit 1110, a memory 1120, a processor 1130 and other components. Among them, the RF circuit 1110 includes a receiver 1111 and a transmitter 1112. Those skilled in the art can understand that Fig.11 The structure of the terminal device shown in the figure does not constitute a limitation on the terminal device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0333] The RF circuit 1110 can be used for receiving and sending signals during the process of sending and receiving information or making calls. In particular, after receiving the downlink information of the base station, it is sent to the processor 1130 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit 1110 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (LNA), a duplexer, etc. In addition, the RF circuit 1110 can also communicate with the network and other devices through wireless communication. The above-mentioned wireless communication can use any communication standard or protocol, including but not limited to the global system of mobile communication (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), long term evolution (LTE), email, short messaging service (SMS), etc.

[0334] The memory 1120 can be used to store software programs and modules. The processor 1130 executes various functional applications and data processing of the terminal device by running the software programs and modules stored in the memory 1120. The memory 1120 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the terminal device (such as audio data, a phone book, etc.), etc. In addition, the memory 1120 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0335] The processor 1130 is the control center, which uses various interfaces and lines to connect various parts of the entire terminal device, and executes various functions of the terminal device and processes data by running or executing software programs and / or modules stored in the memory 1120, and calling data stored in the memory 1120, so as to monitor the terminal device as a whole. Optionally, the processor 1130 may include one or more processing units; preferably, the processor 1130 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application programs, etc., and the modem processor mainly processes wireless communications. It can be understood that the above-mentioned modem processor may not be integrated into the processor 1130.

[0336] In the embodiment of the present invention, the RF circuit 1110 (specifically, it may be a receiver 1111) is used to receive configuration information sent by a network device;

[0337] The processor 1130 is configured to determine a time domain parameter according to configuration information, where the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

[0338] Optionally, at least one time domain parameter offset value corresponds to at least one object, and one time domain parameter offset value corresponds to one or more objects;

[0339] Among them, at least one object is at least one beam, or at least one object is at least one terminal device.

[0340] Optionally, the time domain parameter reference value is a time domain parameter reference value shared by at least one object;

[0341] The at least one time-domain parameter offset value includes a time-domain parameter offset value corresponding to each object.

[0342] Optionally, the processor 1130 is specifically configured to determine the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value;

[0343] Among them, the first time domain parameter offset value is one of at least one time domain parameter offset value; the first time domain parameter offset value corresponds to the beam where the terminal device is located, or the first time domain parameter offset value corresponds to the terminal device.

[0344] Optionally, for a transparent forwarding non-terrestrial communication NTN architecture, the time domain parameter reference value is determined according to the first round-trip delay RTT and the second RTT;

[0345] The first RTT is: the RTT between the first reference point and the network device, and the uplink time domain and the downlink time domain of the first reference point are aligned;

[0346] The second RTT is: the RTT between the network device and a ground reference point within the cell where the terminal device is located.

[0347] Among them, the network equipment is a non-ground network equipment that provides services to the terminal equipment.

[0348] Optionally, the time domain parameter reference value is the sum of the first RTT and the second RTT.

[0349] Optionally, for the regeneration and forwarding NTN architecture, the time domain parameter reference value corresponds to a second RTT, the second RTT is the RTT between the network device and a ground reference point within the cell where the terminal device is located, and the network device is a non-ground network device that provides services to the terminal device.

[0350] Optionally, the time domain parameter reference value is a time domain parameter corresponding to the first object;

[0351] Each of the at least one time domain offset value is: an offset value of a time domain parameter corresponding to at least one other object relative to a time domain parameter reference value; wherein the at least one other object is an object other than the first object among all objects.

[0352] Optionally, the processor 1130 is specifically configured to determine the time domain parameter reference value as the time domain parameter if the terminal device corresponds to the first object.

[0353] Optionally, the processor 1130 is specifically configured to determine the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value if the terminal device corresponds to the second object;

[0354] Wherein, the first time domain parameter offset value is one of at least one time domain parameter offset value;

[0355] The first time domain parameter offset value corresponds to the satellite beam where the terminal device is located, or the first time domain parameter offset value corresponds to the terminal device; the second object is one of at least one other object.

[0356] Optionally, the processor 1130 is specifically configured to calculate the sum of the time domain parameter reference value and the first time domain parameter offset value to obtain the time domain parameter.

[0357] Optionally, the time domain parameter is the time slot offset K offset ;

[0358] Optionally, the time domain parameter is a common timing advance TA.

[0359] Optionally, the processor 1130 is further configured to determine the time domain parameter according to the configuration information, if the time domain parameter is K offset , the time domain resource position of the uplink transmission is determined according to the time domain parameters; if the time domain parameters are common TA, TA compensation is performed when sending a random access request during the random access process according to the time domain parameters.

[0360] Optionally, if the time domain parameter is a public TA, it is applied to terminal devices without positioning capability.

[0361] Optionally, the random access process includes: a four-step random access process, and / or a two-step random access process.

[0362] Optionally, the time domain parameter reference value is sent via broadcast.

[0363] Optionally, if at least one time domain parameter offset value corresponds to at least one beam, the at least one time domain parameter offset value is sent via broadcast or multicast.

[0364] Optionally, if at least one time domain parameter offset value corresponds to at least one terminal device, the at least one time domain parameter offset value is sent via multicast or via dedicated signaling.

[0365] Optionally, the network device is a satellite.

[0366] For example, Fig.12 As shown, the network device in the embodiment of the present invention may be a satellite, and the satellite includes:

[0367] The transmitter 1200 is used to send configuration information to the terminal device, where the configuration information is used to determine the time domain parameters, and the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

[0368] Optionally, at least one time domain parameter offset value corresponds to at least one object, and one time domain parameter offset value corresponds to one or more objects;

[0369] Among them, at least one object is at least one beam, or at least one object is at least one terminal device.

[0370] Optionally, the time domain parameter reference value is a time domain parameter reference value corresponding to each object;

[0371] At least one time domain parameter offset value is a time domain parameter offset value corresponding to each object.

[0372] Optionally, for the transparent forwarding NTN architecture, the time domain parameter reference value is determined according to the first RTT and the second RTT;

[0373] The first RTT is: the RTT between the first reference point and the network device, and the uplink time domain and the downlink time domain of the first reference point are aligned;

[0374] The second RTT is: the RTT between the network device and a ground reference point within the cell where the terminal device is located.

[0375] Among them, the network equipment is a non-ground network equipment that provides services to the terminal equipment.

[0376] Optionally, the time domain parameter reference value is the sum of the first RTT and the second RTT.

[0377] Optionally, for the regeneration and forwarding NTN architecture, the time domain parameter reference value corresponds to a second RTT, the second RTT is the RTT between the network device and a ground reference point within the cell where the terminal device is located, and the network device is a non-ground network device that provides services to the terminal device.

[0378] Optionally, the time domain parameter is the time slot offset K offset ;

[0379] or,

[0380] The time domain parameter is the timing advance TA.

[0381] Optionally, the time domain parameter reference value is sent via broadcast.

[0382] Optionally, if at least one time domain parameter offset value corresponds to at least one beam, the at least one time domain parameter offset value is sent via broadcast or multicast;

[0383] If at least one time domain parameter offset value corresponds to at least one terminal device, then the at least one time domain parameter offset value is sent via multicast or via dedicated signaling.

[0384] The embodiment of the present invention further provides a computer-readable storage medium, including: computer instructions, which, when executed on a computer, enable the computer to execute various processes of the terminal device in the above method embodiment.

[0385] The embodiment of the present invention further provides a computer-readable storage medium, including: computer instructions, which, when executed on a computer, enable the computer to execute various processes of the network device in the above method embodiment.

[0386] An embodiment of the present invention further provides a computer program product, including computer instructions. When the computer program product runs on a computer, the computer runs the computer instructions, so that the computer executes each process of the terminal device in the above method embodiment.

[0387] An embodiment of the present invention further provides a computer program product, including computer instructions. When the computer program product runs on a computer, the computer runs the computer instructions, so that the computer executes each process of the network device in the above method embodiment.

[0388] An embodiment of the present invention further provides a chip, which is coupled to a memory in a terminal device, so that the chip calls program instructions stored in the memory during operation, so that the terminal device executes various processes of the terminal device in the above method embodiment.

[0389] An embodiment of the present invention further provides a chip, which is coupled to a memory in a network device, so that the chip calls program instructions stored in the memory during operation, so that the network device executes various processes of the network device in the above method embodiment.

[0390] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.

[0391] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

Claims

1. A method for determining time domain parameters, the method being executed by a terminal device, characterized in that: The method comprises: Receiving configuration information sent by a network device, the configuration information including: a time domain parameter reference value and at least one time domain parameter offset value; According to the configuration information, time domain parameters are determined.

2. The method according to claim 1, characterized in that: The at least one time domain parameter offset value corresponds to at least one object, and one time domain parameter offset value corresponds to one or more objects; The at least one object is at least one beam, or the at least one object is at least one terminal device; The time domain parameter reference value is a time domain parameter reference value shared by the at least one object; The at least one time domain parameter offset value includes a time domain parameter offset value corresponding to each object; The step of determining the time domain parameters according to the configuration information includes: Determining the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value; The first time domain parameter offset value is one of the at least one time domain parameter offset value; the first time domain parameter offset value corresponds to the beam where the terminal device is located, or the first time domain parameter offset value corresponds to the terminal device.

3. The method according to claim 2, characterized in that For a transparent forwarding non-terrestrial communication NTN architecture, the time domain parameter reference value is determined according to the first round-trip delay RTT and the second RTT; The first RTT is: the RTT between the first reference point and the network device, and the uplink time domain and the downlink time domain of the first reference point are aligned; The second RTT is: the RTT between the network device and a ground reference point within the cell where the terminal device is located; Wherein, the network device is a non-terrestrial network device that provides services to the terminal device; and / or For the regeneration and forwarding NTN architecture, the time domain parameter reference value corresponds to a second RTT, the second RTT is the RTT between the network device and a ground reference point within the cell where the terminal device is located, and the network device is a non-ground network device that provides services to the terminal device.

4. The method according to claim 1 or 2, characterized in that: The time domain parameter reference value is a time domain parameter corresponding to the first object; Each of the at least one time domain offset value is: an offset value of a time domain parameter corresponding to at least one other object relative to the time domain parameter reference value; wherein the at least one other object is an object other than the first object among all objects; wherein: The determining of the time domain parameters according to the configuration information includes: If the terminal device corresponds to the first object, determining the time domain parameter reference value as the time domain parameter; or The determining of the time domain parameters according to the configuration information includes: If the terminal device corresponds to a second object, the time domain parameter is determined according to the time domain parameter reference value and the first time domain parameter offset value; wherein the first time domain parameter offset value is one of the at least one time domain parameter offset value; the first time domain parameter offset value corresponds to the satellite beam where the terminal device is located, or the first time domain parameter offset value corresponds to the terminal device; the second object is one of the at least one other object.

5. The method according to claim 2, characterized in that: The determining the time domain parameter according to the time domain parameter reference value and the first time domain parameter offset value includes: The sum of the time domain parameter reference value and the first time domain parameter offset value is calculated to obtain the time domain parameter.

6. A method for determining time domain parameters, the method being executed by a network device, characterized in that: The method comprises: Configuration information is sent to a terminal device, where the configuration information is used to determine a time domain parameter, and the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

7. The method according to claim 6, characterized in that The at least one time domain parameter offset value corresponds to at least one object, and one time domain parameter offset value corresponds to one or more objects; The at least one object is at least one beam, or the at least one object is at least one terminal device; The time domain parameter reference value corresponds to the time domain parameter reference value of each object; The at least one time domain parameter offset value is a time domain parameter offset value corresponding to each object.

8. The method according to claim 7, characterized in that For the transparent forwarding NTN architecture, the time domain parameter reference value is determined according to the first RTT and the second RTT; The first RTT is: the RTT between the first reference point and the network device, and the uplink time domain and the downlink time domain of the first reference point are aligned; The second RTT is: the RTT between the network device and a ground reference point within the cell where the terminal device is located; Wherein, the network device is a non-terrestrial network device that provides services to the terminal device; and / or For the regeneration and forwarding NTN architecture, the time domain parameter reference value corresponds to a second RTT, which is the RTT between the network device and a ground reference point within the cell where the terminal device is located, and the network device is a non-ground network device that provides services to the terminal device.

9. The method according to any one of claims 6 to 8, characterized in that: The time domain parameter is the time slot offset K offset ; or, The time domain parameter is the timing advance TA.

10. The method according to any one of claims 6 to 9, characterized in that: The time domain parameter reference value is sent via broadcasting; If the at least one time domain parameter offset value corresponds to at least one beam, the at least one time domain parameter offset value is sent by broadcast or multicast; If the at least one time domain parameter offset value corresponds to at least one terminal device, the at least one time domain parameter offset value is sent via multicast or via dedicated signaling.

11. A terminal device, characterized in that: include: A receiving module, used for receiving configuration information sent by a network device; The processing module is used to determine the time domain parameter according to the configuration information, wherein the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

12. A network device, characterized in that: include: The sending module is used to send configuration information to the terminal device, where the configuration information is used to determine the time domain parameters, and the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

13. A terminal device, characterized in that: include: A receiver, used for receiving configuration information sent by a network device; The processor is used to determine the time domain parameter according to the configuration information, wherein the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

14. A network device, characterized in that: include: A transmitter is used to send configuration information to a terminal device, wherein the configuration information is used to determine a time domain parameter, and the configuration information includes: a time domain parameter reference value and at least one time domain parameter offset value.

15. A computer-readable storage medium, characterized in that: include: Computer instructions, when the computer instructions are executed on a processor, enable the processor to implement the method according to any one of claims 1 to 5, or implement the method according to any one of claims 6 to 10.

Images