Wireless communication method, terminal device and network device

Abstract

The invention provides a wireless communication method, terminal equipment and network equipment. The method comprises: a terminal device determines a collision fuzzy period for uplink transmission according to relative motion information between a network device and the terminal device, the collision fuzzy period being configured to not perform uplink transmission. Or, the method comprises the following steps: the network equipment determines a collision fuzzy period for downlink receiving according to the relative motion information between the network equipment and the terminal equipment, and the collision fuzzy period is configured to not perform downlink receiving. In the embodiment of the invention, the relative motion information between the network equipment and the terminal equipment is introduced to determine the collision fuzzy period for uplink transmission, so that a large amount of waste of resources is avoided under the condition of avoiding collision between uplink transmission and downlink reception.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment and network equipment. Background Art

[0002] Non-terrestrial networks (NTN) refer to networks that use non-terrestrial platforms such as satellites and drones to provide communication services. Due to the rapid movement of satellites relative to the ground, for terminal devices that are far away from network devices, uplink transmission and downlink reception between them and network devices may cause resource collisions and conflicts due to time advance (TA) mismatch (or TA mismatch), thus affecting communication performance. Summary of the invention

[0003] The present application provides a wireless communication method, terminal equipment and network equipment. The following introduces various aspects involved in the present application.

[0004] In a first aspect, a method for wireless communication is provided, comprising: a terminal device determines a collision ambiguity period for uplink transmission based on relative motion information between a network device and the terminal device, wherein the collision ambiguity period is configured to not perform uplink transmission.

[0005] In a second aspect, a method for wireless communication is provided, comprising: a network device determines a collision ambiguity period for downlink reception based on relative motion information between the network device and a terminal device, wherein the collision ambiguity period is configured to not perform downlink reception.

[0006] According to a third aspect, a terminal device is provided, comprising: a processing unit, configured to determine a collision ambiguity period for uplink transmission based on relative motion information between a network device and the terminal device, wherein the collision ambiguity period is configured to not perform uplink transmission.

[0007] In a fourth aspect, a network device is provided, comprising: a processing unit, configured to determine a collision ambiguity period for downlink reception based on relative motion information between the network device and a terminal device, wherein the collision ambiguity period is configured to not perform downlink reception.

[0008] In a fifth aspect, a terminal device is provided, comprising a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the terminal device executes the method described in the first aspect.

[0009] In a sixth aspect, a network device is provided, comprising a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the network device executes the method described in the second aspect.

[0010] In a seventh aspect, a device is provided, comprising a processor, configured to call a program from a memory so that the device executes a method as described in any one of the first aspect or the second aspect.

[0011] In an eighth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect or the second aspect.

[0012] In a ninth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

[0013] In a tenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method as described in the first aspect or the second aspect.

[0014] In an eleventh aspect, a computer program is provided, wherein the computer program enables a computer to execute the method as described in the first aspect or the second aspect.

[0015] In this application, the relative motion information between the network device and the terminal device is introduced to determine the collision ambiguity period for uplink transmission, thereby avoiding a large waste of resources while avoiding the collision between uplink transmission and downlink reception. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 2 is a diagram showing an example of a system architecture of a wireless communication system applicable to an embodiment of the present application.

[0017] Figure 2 Schematic diagram of collision between uplink transmission and downlink reception.

[0018] Figure 3 A flowchart of a wireless communication method according to an embodiment of the present application is shown.

[0019] Figure 4 A flowchart of a wireless communication method according to another embodiment of the present application is shown.

[0020] Figure 5 A flow chart of determining collision ambiguity periods for uplink transmission and downlink reception for a terminal device and a network device, respectively.

[0021] Figure 6 for Figure 3A schematic diagram of a possible specific implementation of the method shown.

[0022] Figure 7 for Figure 6 A schematic diagram of a collision between uplink transmission and downlink reception in the method shown.

[0023] Figure 8 Schematic diagram of a collision ambiguity period set for an uplink transmission interval when a network device and a terminal device move towards each other.

[0024] Fig. 9 Schematic diagram of a collision ambiguity period set for an uplink transmission interval when a network device and a terminal device are moving away from each other.

[0025] Fig.10 for Figure 4 A schematic diagram of a possible specific implementation of the method shown.

[0026] Fig.11 for Fig.10 A schematic diagram of a collision between uplink transmission and downlink reception in the method shown.

[0027] Fig.12 Schematic diagram of a collision ambiguity period set for a downlink reception interval when a network device and a terminal device move towards each other.

[0028] Fig.13 Schematic diagram of a collision ambiguity period set for a downlink reception interval when a network device and a terminal device are moving away from each other.

[0029] Fig.14 A schematic diagram of the structure of a terminal device according to an embodiment of the present application.

[0030] Fig.15 A schematic diagram of the structure of a network device according to an embodiment of the present application.

[0031] Fig.16 A schematic diagram of a device for communication according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0033] Wireless communication system

[0034] Figure 11 is an example diagram of the system architecture of a wireless communication system 100 to which an embodiment of the present application can be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide network coverage for a specific geographical area, and may communicate with the terminal device 120 located in the coverage area. The terminal device 120 may access a network, such as a wireless network, through the network device 110. Typically, the network device 110 is responsible for managing wireless resources and communicating with the terminal device 120. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0035] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0036] The terminal device in the embodiment of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiment of the present application can be a mobile phone, a tablet computer, a laptop, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a scheduling entity, which provides sidelink signals between terminal devices in vehicle to everything (V2X) or device to device (D2D). For example, a cellular phone and a car communicate with each other using a sidelink signal. Cellular phones and smart home devices communicate without relaying communication signals through a base station.

[0037] The network device in the embodiment of the present application may be a device for communicating with a terminal device. The network device may be, for example, an access network device or a wireless access network device. For example, the network device may be a base station. The base station may broadly cover the following various names, or replace them with the following names: Node B, evolved Node B (eNB), next generation Node B (gNB), relay station, access point, transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), home base station, network controller, access node, wireless node, access point (access point, AP), transmission node, transceiver node, base band unit (base band unit, BBU), remote radio unit (remote radio unit, RRU), active antenna unit (active antenna unit, AAU), radio head (remote radio head, RRH), central unit (central unit, CU), distributed unit (distributed unit, DU), positioning node, etc. The base station may be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof.

[0038] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device includes a CU and a DU. The gNB may also include an AAU.

[0039] The network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.

[0040] It should be understood that all or part of the functions of the communication device in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).

[0041] NTN

[0042] NTN can provide communication services to users in a non-terrestrial way. That is, it can communicate with terminal devices through non-terrestrial network devices such as satellites (SAT) and UAS platforms. Since the NTN network transmits data through space-based or air-based platforms, it has unique advantages.

[0043] For example, for terrestrial network communications, communication equipment cannot be set up in scenes such as oceans, mountains, and deserts. Or, considering the construction and operation costs of communication equipment, terrestrial communications usually do not cover sparsely populated areas. Compared with terrestrial network communications, NTN communication networks are not restricted by geography. In theory, satellites can orbit the earth, so every corner of the earth can be covered by satellite communications. In addition, the area that non-terrestrial network equipment can cover is much larger than the area covered by terrestrial communication equipment, that is, NTN cells can cover a larger range.

[0044] However, due to factors such as rapid movement relative to the ground, orbital altitude, signal interference, and capacity and energy consumption limitations, NTN networks often face higher latency and more severe Doppler frequency shift, which in turn creates more challenges for NTN networks.

[0045] HD-FDDRedcapUEs

[0046] The reduced capability terminal device of Half-Duplex Frequency Division Duplex (HD-FDD) is a special terminal device in the NR network. On the one hand, the terminal device adopts half-duplex mode and frequency division duplex (HD-FDD) mode for communication. In HD-FDD mode, the terminal device is allowed to transmit and receive at different frequencies at different times, but the terminal device cannot receive downlink data when sending uplink data, and cannot send uplink data when receiving downlink data. On the other hand, Redcap UE type terminal devices, that is, reduced capability terminal devices, are low-complexity terminal types formed by cutting out terminal devices in the NR system, also known as lightweight terminal devices. The purpose of reducing capabilities is to meet the terminal-specific requirements in mid-end IoT application scenarios such as industrial wireless sensors, video surveillance, and wearable devices, and to reduce complexity, cost, and power consumption by reducing terminal air interface capabilities.

[0047] TA

[0048] TA is generally used for uplink transmission of terminal devices. In order for the uplink data of the terminal device to reach the network device at the expected time, the RF transmission delay caused by the distance is estimated to send the uplink data in advance. From the perspective of the terminal device, the essence of TA is a negative offset between the start time of receiving the downlink data and the time of transmitting the uplink data. The network device can control the time when the uplink data from different terminal devices arrives at the network device by properly controlling the offset of each terminal device. For terminal devices that are far away from the network device, due to the larger transmission delay, it is necessary to send the uplink data in advance compared to terminal devices that are closer to the network device.

[0049] Collision

[0050] Collision conflict refers to the issues that require further study for HD-FDD RedCap UEs proposed in the 3GPP RAN#116 meeting. The two collision conflict situations described in case 3 and case 4 are mainly caused by TA mismatch in the NTN scenario. Case 3 refers to the collision conflict between the semi-statically configured downlink reception and the semi-statically configured uplink transmission, and case 4 refers to the collision conflict between the dynamically scheduled downlink reception and the dynamically scheduled uplink transmission.

[0051] As mentioned above, the uplink (UL) transmission and downlink (DL) transmission between the terminal device and the network device may cause a collision conflict due to TA mismatch. To this end, in the embodiment of the present application, it is proposed to set a collision ambiguity period (or collision ambiguity interval) to reduce the probability of a collision conflict between uplink transmission and downlink reception due to TA mismatch. Hereinafter, the collision conflict is also referred to as collision or conflict.

[0052] As an example, Figure 2 As shown, the terminal device will report a TA report to the network device, for example, reporting a TA report based on a certain period. The TA report includes, for example, a TA value. The network device will determine, based on the TA report, that a collision occurs between the uplink transmission UL8 and the downlink reception DL4, so the network device may not configure or schedule the downlink reception at the position of the downlink reception DL4 to avoid a collision between the downlink reception DL4 and the uplink transmission UL8. In fact, on the terminal device side, the uplink transmission UL8 collides with the downlink reception DL2, which is caused by the mismatch between the TA value in the TA report and the actual required time advance. Hereinafter, this situation will be referred to as a TA mismatch (or TA mismatch).

[0053] To solve this problem, the network device can proactively avoid potential collisions based on the TA report and the maximum TA mismatch value. Figure 2 As shown in FIG. 1 , the maximum TA mismatch value is between -2ms and +2ms. Therefore, when the network device schedules the uplink transmission UL8, it can avoid scheduling the downlink reception of the terminal device on the downlink reception DL2, DL3, DL4, DL5, and DL6 that may collide with the uplink transmission UL8. However, this will lead to a waste of resources in the NTN network because a large amount of resources are reserved.

[0054] We call the above-mentioned period from -2ms to +2ms, or the period of downlink reception DL2 to DL6, a collision ambiguity period. The shorter the collision ambiguity period, the more flexible the uplink scheduling and / or downlink scheduling. For the convenience of illustration, UL0 to UL9 and DL0 to DL9 in the embodiment of the present application correspond to different subframes, so their lengths can usually be 1ms.

[0055] To this end, an embodiment of the present application provides a method for wireless communication, which can introduce relative motion information between a network device and a terminal device to determine a collision ambiguity period for uplink transmission. While avoiding collisions between uplink transmission and downlink reception, it avoids a large amount of waste of resources and thereby avoids a decrease in throughput of a single terminal device.

[0056] In an embodiment of the present application, in the event that an uplink transmission collides with a downlink reception, the collision ambiguity period may be set for the uplink transmission, that is, the collision ambiguity period is set in the uplink transmission interval (or, the uplink transmission part), which is equivalent to canceling the uplink transmission where the collision occurs; or, the collision ambiguity period may also be set for the downlink reception, that is, the collision ambiguity period is set in the downlink reception interval (or, the downlink reception part), which is equivalent to canceling the downlink reception where the collision occurs. Figure 2 The example shown is to set the collision ambiguity period in downlink reception.

[0057] Optionally, the collision ambiguity period for uplink transmission may be determined by the terminal device, or the collision ambiguity period for downlink reception may be determined by the network device. Figure 3 and Figure 4 These two situations are described separately.

[0058] In the embodiment of the present application, the terminal device is, for example, a lightweight terminal device in a half-duplex frequency division duplex mode; the network device is, for example, a network device arranged on a non-ground platform in an NTN network.

[0059] Figure 3 A flowchart of a wireless communication method provided in an embodiment of the present application. Figure 3, in step 310, the terminal device determines a collision ambiguity period for uplink transmission according to the relative motion information between the network device and the terminal device.

[0060] The collision ambiguity period can be understood as a time period during which a collision may occur between uplink transmission and downlink reception. In other words, the uplink transmission and downlink reception may collide during the collision ambiguity period.

[0061] The collision ambiguity period for uplink transmission is configured to not perform uplink transmission, thereby avoiding collision between uplink transmission and downlink reception.

[0062] In an embodiment of the present application, when determining the collision ambiguity period, the relative movement between the network device and the terminal device is introduced, thereby optimizing the coverage of the collision ambiguity period, shortening the collision ambiguity period, reducing the occupation of time and frequency resources caused by collision avoidance, improving resource utilization, and reducing the frequency of TA reports reported by terminal devices.

[0063] For example, after determining the collision position based on the TA report (ie, the TA reported by the terminal device), and then combining the relative motion information, the position and length of the collision ambiguity period set in the uplink transmission interval can be determined.

[0064] The relative motion information may be used, for example, to determine a change in the distance and / or a moving direction of the network device relative to the terminal device.

[0065] In some implementations, the relative motion information includes one or more of the following: location information of the terminal device; location information of the network device; moving speed of the terminal device; moving speed of the network device.

[0066] It can be understood that since the network devices in the NTN network are usually set on non-ground platforms such as satellites, the movement speed of the network devices is much greater than the movement speed of the terminal devices. Therefore, the movement of the terminal devices can be ignored in the embodiments of the present application, that is, the movement speed of the network devices is considered to be the relative movement speed between the network devices and the terminal devices.

[0067] In some implementations, in step 310, the terminal device may determine a correction value of the collision position based on the relative motion information between the network device and the terminal device, and determine the collision ambiguity period based on the correction value of the collision position. The collision position is a position where the uplink transmission and the downlink reception collide based on the TA report, or the collision position is determined without considering the relative motion between the network device and the terminal device, such as the aforementioned Figure 2 The uplink transmission UL8 or downlink reception DL4 shown in FIG. The collision position can also be referred to as the collision point center expected by the terminal device.

[0068] In some implementations, the correction value of the collision position is a ratio between a change in the distance between the network device and the terminal device and a signal transmission speed within a predetermined period of time.

[0069] The predetermined duration may be, for example, the period of the terminal device reporting the TA report, that is, the time interval between two consecutive TA reports reported by the terminal device. The signal transmission speed refers to the transmission speed of uplink data and / or downlink data between the network device and the terminal device, which may be, for example, the speed of light, denoted as c.

[0070] The distance change between the network device and the terminal device may be, for example, the difference between the initial distance between the network device and the terminal device and the new distance between the network device and the terminal device after a predetermined period of time.

[0071] In some implementations, the correction value of the collision position is: Alternatively, the correction value can also be expressed as in It can represent the change in distance between the network device and the terminal device.

[0072] The above △TA is the correction value of TA, is the position of the network device in the coordinate system, is the position of the terminal device in the coordinate system, is the moving speed of the network device, T is the predetermined time, and c is the speed of light. The coordinate system may be, for example, a Cartesian coordinate system. As an example, the coordinate system is a Cartesian coordinate system established with the position of the terminal device as the coordinate. In this case, the position coordinate of the terminal device may be the origin coordinate or 0.

[0073] Optionally, the terminal device may receive configuration information sent by the network device, wherein the configuration information includes priority information of uplink transmission and downlink reception and / or ephemeris information of the network device, and the ephemeris information includes, for example, information of the location of the network device and / or the movement speed of the network device.

[0074] In cases such as telemedicine and emergency alarm, the priority of uplink transmission may be higher than the priority of downlink reception; in applications such as sensor networks and cameras, the priority of downlink reception may be higher than the priority of uplink transmission.

[0075] The terminal device can obtain its own location information through GPS, etc. And its location information Report to the network device, for example, by reporting the location signaling (Location Report). If the priority of uplink transmission is higher than the priority of downlink reception, the terminal device may not perform the above operation; if the priority of downlink reception is higher than the priority of uplink transmission, the terminal device performs the above operation. For example, after receiving the configuration information sent by the network device, the terminal device may Location information of network devices The speed of the network device The time interval T between two adjacent TA reports and other information can be used to estimate the correction value of the collision position. Specifically, the position information of the terminal device can be used to estimate the correction value of the collision position. and location information of network devices Calculate the initial distance between the two Then, according to the movement speed of the network device Calculate the new distance between the two after a TA report cycle: Finally, the difference between the initial distance between the network device and the terminal device and the new distance after one TA report cycle is calculated, and the difference is divided by the speed of light c to obtain the correction value of the collision position. Afterwards, the terminal device may determine the collision ambiguity period according to the correction value in combination with the direction of relative movement between the network device and the terminal device.

[0076] It can be understood that if the collision ambiguity period has been determined based on the collision position determined by the TA report and the maximum TA mismatch value, such as the aforementioned Figure 2 If the collision ambiguity period is shown in , the terminal device can modify (or reconfigure) the collision ambiguity period in the uplink transmission interval according to the correction value of the collision position, thereby optimizing the range of the collision ambiguity period to improve resource utilization. Of course, in some cases, the terminal device may not modify the collision ambiguity period.

[0077] For example, when the correction value of the collision position is less than the threshold, the terminal device may determine the collision ambiguity period based on the collision position before correction, that is, the collision position determined based on the TA report, such as the aforementioned Figure 2 After the terminal device determines the correction value, if the correction value is less than the threshold, the terminal device may not modify the collision ambiguity period using the correction value.

[0078] For another example, when the correction value of the collision position is greater than or equal to the threshold, the terminal device may determine the collision ambiguity period based on the collision position determined by the TA report and the correction value of the collision position, for example, different from the aforementioned Figure 2After determining the correction value, if the correction value is greater than the threshold, the terminal device needs to use the correction value to correct the original collision ambiguity period, such as the aforementioned Figure 2 The collision blur period shown in is modified to optimize the range of the collision blur period.

[0079] In some implementations, when the network device and the terminal device move toward each other, the collision ambiguity period is [TA0-△TA, TA0]; when the network device and the terminal device move away from each other, the collision ambiguity period is [TA0, TA0+△TA], where TA0 is the collision position and △TA is the correction value of the collision position.

[0080] There are two cases of relative motion between the network device and the terminal device. One case is that the network device and the terminal device move toward each other. At this time, the distance between the network device and the terminal device gradually decreases, so the collision ambiguity period can be set to [TA0-△TA, TA0]; the other case is that the network device and the terminal device move away from each other. At this time, the distance between the network device and the terminal device gradually increases, so the collision ambiguity period can be set to [TA0, TA0+△TA]. Here, TA0 is the collision position estimated based on the TA report, or the collision position determined without considering the relative motion between the network device and the terminal device.

[0081] In some implementations, when the first angle is less than 90°, the network device and the terminal device move toward each other; when the first angle is greater than 90°, the network device and the terminal device move away from each other. The first angle is the angle between the direction of movement of the network device and the distance between the network device and the terminal device. For example, in a Cartesian coordinate system established with the position of the terminal device as the origin, the angle between the direction of movement of the network device and the line between the position of the network device and the position of the terminal device is the first angle. When the first angle is greater than 90°, it indicates that the network device and the terminal device are moving away from each other, that is, the distance between the network device and the terminal device is increasing rapidly; when the first angle is less than 90°, it indicates that the network device and the terminal device are moving toward each other, that is, the distance between the network device and the terminal device is decreasing rapidly.

[0082] In some implementations, the terminal device also needs to send the location information of the terminal device to the network device. The location information of the terminal device can be used by the network device to determine the collision ambiguity period for downlink reception, and the collision ambiguity period for downlink reception is configured not to perform downlink reception. The location information of the terminal device can also be used by the network device to establish a corresponding coordinate system to facilitate the representation of information such as the location and speed of the network device and the terminal device.

[0083] In some implementations, the terminal device may periodically report its location information; or, the terminal device may send updated location information to the network device when its location information changes, for example, when its location changes within a predetermined time interval, the terminal device may send updated location information to the network device. The updated location information may be reported, for example, via location update signaling (Location Update).

[0084] The above describes the process of a terminal device determining a collision ambiguity period for uplink transmission. The following describes the process of a network device determining a collision ambiguity period for downlink reception.

[0085] Figure 4 A flowchart of a wireless communication method provided in an embodiment of the present application. Figure 4 In step 410, the network device determines a collision ambiguity period for downlink reception according to the relative motion information between the network device and the terminal device.

[0086] The collision ambiguity period can be understood as a time period during which a collision may occur between uplink transmission and downlink reception. In other words, the uplink transmission and downlink reception may collide during the collision ambiguity period.

[0087] The collision ambiguity period for downlink reception is configured to not perform downlink reception, thereby avoiding collision between uplink transmission and downlink reception.

[0088] In an embodiment of the present application, when determining the collision ambiguity period, the relative movement between the network device and the terminal device is introduced, thereby optimizing the coverage of the collision ambiguity period, shortening the collision ambiguity period, reducing the occupation of time and frequency resources caused by collision avoidance, improving resource utilization, and reducing the frequency of TA reports reported by terminal devices.

[0089] For example, after determining the collision position based on the TA report (ie, the TA reported by the terminal device), and then combining the relative motion information, the position and length of the collision ambiguity period set in the downlink reception interval can be determined.

[0090] The relative motion information may be used, for example, to determine a change in the distance and / or a moving direction of the network device relative to the terminal device.

[0091] In some implementations, the relative motion information includes one or more of the following: location information of the terminal device; location information of the network device; moving speed of the terminal device; moving speed of the network device.

[0092] It can be understood that since the network devices in the NTN network are usually set on non-ground platforms such as satellites, the movement speed of the network devices is much greater than the movement speed of the terminal devices. Therefore, the movement of the terminal devices can be ignored in the embodiments of the present application, that is, the movement speed of the network devices is considered to be the relative movement speed between the network devices and the terminal devices.

[0093] In some implementations, in step 410, the network device may determine a correction value of the collision position based on the relative motion information between the network device and the terminal device, and determine the collision ambiguity period based on the correction value of the collision position. The collision position is a position where the uplink transmission and the downlink reception collide based on the TA report, or the collision position is determined without considering the relative motion between the network device and the terminal device, such as the aforementioned Figure 2 The uplink transmission UL8 or downlink reception DL4 shown in FIG. The collision position can also be referred to as the collision point center expected by the terminal device.

[0094] In some implementations, the correction value of the collision position is a ratio between a change in the distance between the network device and the terminal device and a signal transmission speed within a predetermined period of time.

[0095] The predetermined duration may be, for example, the period of the terminal device reporting the TA report, that is, the time interval between two consecutive TA reports reported by the terminal device. The signal transmission speed refers to the transmission speed of uplink data and / or downlink data between the network device and the terminal device, which may be, for example, the speed of light, denoted as c.

[0096] The distance change between the network device and the terminal device may be, for example, the difference between the initial distance between the network device and the terminal device and the new distance between the network device and the terminal device after a predetermined period of time.

[0097] In some implementations, the correction value of the collision position is: Alternatively, the correction value can also be expressed as in It can represent the change in distance between the network device and the terminal device.

[0098] The above △TA is the correction value of TA, is the position of the network device in the coordinate system, is the position of the terminal device in the coordinate system, is the moving speed of the network device, T is the predetermined time, and c is the speed of light. The coordinate system may be, for example, a Cartesian coordinate system. As an example, the coordinate system is a Cartesian coordinate system established with the position of the terminal device as the coordinate. In this case, the position coordinate of the terminal device may be the origin coordinate or 0.

[0099] Optionally, the network device may receive the location information of the terminal device reported by the terminal device. In this way, the collision ambiguity period for downlink reception may be determined by using the location information reported by the terminal device and combining the priority information of uplink transmission and downlink reception and / or the ephemeris information of the network device. The ephemeris information may include, for example, the location of the network device and / or the movement speed of the network device.

[0100] In cases such as telemedicine and emergency alarm, the priority of uplink transmission may be higher than the priority of downlink reception; in applications such as sensor networks and cameras, the priority of downlink reception may be higher than the priority of uplink transmission.

[0101] For example, the network device can calculate the direction and speed of relative movement between the network device and the terminal device based on the location information reported by the terminal device, and cache this information for subsequent use. Combined with its own ephemeris information, a Cartesian coordinate system with the terminal device as the origin is constructed, and the position coordinates of the terminal device are marked as Location coordinates of network devices The movement speed of the network device is recorded as If the priority of downlink reception is higher than the priority of uplink transmission, the network device may not perform the above operation; if the priority of uplink transmission is higher than the priority of downlink reception, the network device performs the above operation. Location information of network devices The speed of the network device The time interval T between two adjacent TA reports and other information can be used to estimate the correction value of the collision position. Specifically, the position information of the terminal device can be used to estimate the correction value of the collision position. and location information of network devices Calculate the initial distance between the two Then, according to the movement speed of the network device Calculate the new distance between the two after a TA report cycle: Finally, the difference between the initial distance between the network device and the terminal device and the new distance after one TA report cycle is calculated, and the difference is divided by the speed of light c to obtain the correction value of the collision position. Afterwards, the network device may determine the collision ambiguity period according to the correction value in combination with the direction of relative movement between the network device and the terminal device.

[0102] It can be understood that if the collision ambiguity period has been determined based on the collision position determined by the TA report and the maximum TA mismatch value, such as the aforementioned Figure 2If the collision ambiguity period shown in , the network device can modify (or reconfigure) the collision ambiguity period in the downlink receiving interval according to the correction value of the collision position, thereby optimizing the range of the collision ambiguity period to improve resource utilization. Of course, in some cases, the network device may not modify the collision ambiguity period.

[0103] For example, when the correction value of the collision position is less than the threshold, the network device may determine the collision ambiguity period based on the collision position before correction, that is, the collision position determined based on the TA report, such as the aforementioned Figure 2 After the network device determines the correction value, if the correction value is less than the threshold, the network device may not modify the collision ambiguity period using the correction value.

[0104] For another example, when the correction value of the collision position is greater than or equal to the threshold, the network device may determine the collision ambiguity period based on the collision position determined by the TA report and the correction value of the collision position, for example, different from the aforementioned Figure 2 After determining the correction value, if the correction value is greater than the threshold, the network device needs to use the correction value to correct the original collision ambiguity period, such as the aforementioned Figure 2 The collision blur period shown in is modified to optimize the range of the collision blur period.

[0105] In some implementations, when the network device and the terminal device move toward each other, the collision ambiguity period is [TA0, TA0+ΔTA]; when the network device and the terminal device move away from each other, the collision ambiguity period is [TA0-ΔTA, TA0], where TA0 is the collision position and ΔTA is the correction value of the collision position.

[0106] There are two cases of relative motion between the network device and the terminal device. One case is that the network device and the terminal device move toward each other. At this time, the distance between the network device and the terminal device gradually decreases, so the collision ambiguity period can be set to [TA0-△TA, TA0]; the other case is that the network device and the terminal device move away from each other. At this time, the distance between the network device and the terminal device gradually increases, so the collision ambiguity period can be set to [TA0, TA0+△TA]. Here, TA0 is the collision position estimated based on the TA report, or the collision position determined without considering the relative motion between the network device and the terminal device.

[0107] In some implementations, when the first angle is less than 90°, the network device and the terminal device move toward each other; when the first angle is greater than 90°, the network device and the terminal device move away from each other. The first angle is the angle between the direction of movement of the network device and the distance between the network device and the terminal device. For example, in a Cartesian coordinate system established with the position of the terminal device as the origin, the angle between the direction of movement of the network device and the line between the position of the network device and the position of the terminal device is the first angle. When the first angle is greater than 90°, it indicates that the network device and the terminal device are moving away from each other, that is, the distance between the network device and the terminal device is increasing rapidly; when the first angle is less than 90°, it indicates that the network device and the terminal device are moving toward each other, that is, the distance between the network device and the terminal device is decreasing rapidly.

[0108] In some implementations, the network device may further send configuration information to the terminal device. The configuration information includes priority information for uplink transmission and downlink reception and / or ephemeris information of the network device, and the ephemeris information includes, for example, information about the location of the network device and / or the movement speed of the network device. The configuration information may be used, for example, by the terminal device to determine a collision ambiguity period for uplink transmission, and the collision ambiguity period for uplink transmission may be configured to not perform uplink transmission.

[0109] As an example, Figure 5 FIG. 2 shows the process of determining the collision ambiguity period for uplink transmission and downlink reception by the terminal device and the network device respectively. Figure 5 As shown, it can be determined whether to modify the collision ambiguity period set in the uplink transmission interval or the downlink reception interval according to the priority information of the uplink transmission and the downlink reception.

[0110] In step 510, the terminal device reports the location information of the terminal device to the network device.

[0111] In step 520, the network device establishes a Cartesian coordinate system with the terminal device as the origin.

[0112] In step 530, the network device determines the priority order of uplink transmission and downlink reception.

[0113] In step 540, it is determined whether the priority of the uplink transmission is higher than the priority of the downlink reception.

[0114] Wherein, in step 540, if the priority of uplink transmission is higher than the priority of downlink reception, steps 551 to 553 are executed.

[0115] In step 551, the network device determines a correction value of the collision position according to the position of the terminal device and the ephemeris information of the network device.

[0116] In step 552, the network device determines whether the correction value is greater than a threshold value. Step 552 is optional.

[0117] If the correction value is greater than the threshold, step 553 is executed.

[0118] In step 553, the network device modifies the range of the collision ambiguity period set in the downlink receiving interval.

[0119] Wherein, in step 540, if the priority of downlink reception is higher than the priority of uplink transmission, steps 561 to 564 are executed.

[0120] In step 561, the terminal device receives the signaling sent by the network device, which carries the priority order of uplink transmission and downlink reception, and the ephemeris information of the network device.

[0121] In step 562, the terminal device determines a correction value of the collision position based on its position information and the ephemeris information of the network device.

[0122] In step 563, the terminal device determines whether the correction value is greater than a threshold value. Step 563 is optional.

[0123] If the correction value is greater than the threshold, step 564 is executed.

[0124] In step 564, the terminal device modifies the range of the collision ambiguity period set in the uplink transmission interval.

[0125] The following describes the embodiments of the present application in more detail with reference to specific examples. Figures 5 to 8 The examples are only intended to help those skilled in the art understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific values ​​or specific scenarios illustrated. Figures 6 to 13 It is obvious that various equivalent modifications or changes can be made, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0126] See also Figures 6 to 9 , assuming that the priority of downlink reception is higher than that of uplink transmission, the collision ambiguity period is set in the uplink transmission area. Figure 6 As shown, in step 610, the network device receives the location information of the terminal device reported by the terminal device.

[0127] In step 620, the network device acquires relative motion information and determines priority information for uplink transmission and downlink reception.

[0128] The network device can combine the location coordinates of the terminal device and its own ephemeris information to construct a Cartesian coordinate system with the terminal device as the origin, and determine the relative motion information based on the constructed coordinate system, such as the location coordinates of the terminal device. Location coordinates of network devices The movement speed of the network device is recorded as

[0129] Among them, if the first angle between the movement direction of the network device and the distance between the two is less than 90°, it indicates that the network device and the terminal device are approaching each other; if the first angle between the movement direction of the network device and the distance between the two is greater than 90°, it indicates that the network device and the terminal device are moving away from each other.

[0130] Since downlink reception has a higher priority, the terminal device needs to give priority to downlink reception and set a collision ambiguity interval in the uplink transmission interval, that is, when the uplink transmission and downlink reception may collide, the uplink transmission at the position where the collision may occur is canceled.

[0131] As an example, Figure 7 As shown, if the uplink transmission UL8 collides with the downlink reception DL4, the uplink transmission UL8 can be cancelled to avoid the collision with the downlink reception DL4. Hereinafter, the position of the uplink transmission UL8 is referred to as the collision position TA0, which can be determined based on the TA report, for example.

[0132] In step 630, the network device sends the location coordinates of the terminal device to Location coordinates of network devices The movement speed of network equipment Priority information for uplink transmission and downlink reception is sent to the terminal device.

[0133] In step 640, the terminal device determines the location of the terminal device based on the location coordinates of the terminal device. Location coordinates of network devices The speed of network equipment And the time interval T between two adjacent TA reports is used to determine the correction value △TA of the collision position.

[0134] Next, execute step 650; or execute step 660. That is, step 650 is optional.

[0135] In step 650, the terminal device compares the correction value ΔTA with a threshold value.

[0136] When the correction value is greater than the threshold, step 660 is executed.

[0137] In step 660, the terminal device sets a collision ambiguity period in the uplink transmission interval based on the correction value ΔTA, or modifies the collision ambiguity period in the uplink transmission interval.

[0138] There are two cases: if the network device and the terminal device move towards each other, the collision ambiguity period is [TA0-△TA, TA0]; if the network device and the terminal device move away from each other, the collision ambiguity period is [TA0, TA0+△TA].

[0139] For example, Figure 8 As shown, the collision position TA0 is the position of the uplink transmission UL8. Assuming that the △TA calculated in step 640 is 2ms (or 2 subframes), the network device and the terminal device move towards each other, then the collision ambiguity period includes uplink transmissions UL6, UL7 and UL8, that is, the terminal device will not send uplink data at the positions of uplink transmissions UL6, UL7 and UL8, thereby avoiding possible collision with downlink reception during this period.

[0140] For example, Fig. 9 As shown, the collision position TA0 is the position of the uplink transmission UL8. Assuming that the △TA calculated in step 640 is 2ms (or 2 subframes), the network device and the terminal device are moving apart, then the collision ambiguity period includes uplink transmissions UL8, UL9 and UL10, that is, the terminal device will not send uplink data at the positions of uplink transmissions UL8, UL9 and UL0, thereby avoiding possible collision with downlink reception during this period.

[0141] See also Figures 10 to 13 , assuming that the priority of uplink transmission is higher than that of downlink reception, the collision ambiguity period is set in the downlink reception area. Fig.10 As shown, in step 1010, the network device constructs a Cartesian coordinate system with the terminal device as the origin based on the location information of the terminal device reported by the terminal device and in combination with its own ephemeris information, and determines the relative motion information.

[0142] The relative motion information includes, for example, the position coordinates of the terminal device. Location coordinates of network devices The movement speed of the network device is recorded as

[0143] Among them, if the first angle between the movement direction of the network device and the distance between the two is less than 90°, it indicates that the network device and the terminal device are approaching each other; if the first angle between the movement direction of the network device and the distance between the two is greater than 90°, it indicates that the network device and the terminal device are moving away from each other.

[0144] In step 1020, the network device determines priority information for uplink transmission and downlink reception.

[0145] Since uplink transmission has a higher priority, the terminal device gives priority to uplink transmission, and the network device needs to set a collision ambiguity interval in the downlink reception interval, that is, when the uplink transmission and downlink reception may collide, the downlink reception at the position where the collision may occur is canceled.

[0146] As an example, Fig.11 As shown, if a collision occurs between uplink transmission UL8 and downlink reception DL4, downlink reception DL4 may be cancelled to avoid collision with uplink transmission UL8. Hereinafter, the position of downlink reception DL4 is referred to as collision position TA0, which may be determined based on a TA report, for example.

[0147] In step 1030, the network device uses the location coordinates of the terminal device to Location coordinates of network devices The speed of network equipment And the time interval T between two adjacent TA reports, calculate the correction value △TA of the collision position TA0.

[0148] Next, execute step 1040; or execute step 1050. That is, step 1040 is optional.

[0149] In step 1040 , the network device compares the correction value ΔTA with a threshold value, and if the correction value is greater than the threshold value, further performs step 1050 .

[0150] In step 1050, the network device sets a collision ambiguity period in the downlink receiving interval based on the correction value ΔTA, or modifies the collision ambiguity period in the downlink receiving interval.

[0151] There are two cases: if the network device and the terminal device move towards each other, the collision ambiguity period is [TA0, TA0+△TA]; if the network device and the terminal device move away from each other, the collision ambiguity period is [TA0-△TA, TA0].

[0152] For example, Fig.12 As shown, the collision position TA0 is the position of downlink reception DL4. Assuming △TA is 2ms (or 2 subframes), the network device and the terminal device move towards each other, then the collision ambiguity period includes downlink reception DL2, DL3 and DL4. That is to say, the network device will not send downlink data at the position of downlink reception DL2, DL3 and DL4, so as to avoid possible collision with uplink transmission during this period.

[0153] For example, Fig.13As shown, the collision position TA0 is the position of downlink reception DL4. Assuming △TA is 2ms (or 2 subframes), the network device and the terminal device move away from each other, then the collision ambiguity period includes downlink reception DL4, DL5 and DL6. That is to say, the network device will not send downlink data at the position of downlink reception DL4, DL5 and DL6, so as to avoid possible collision with uplink transmission during this period.

[0154] Combination of the above Figures 1 to 13 , describes the method embodiment of the present application in detail, and the following is combined with Figures 14 to 16 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0155] Fig.14 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application. Fig.14 The terminal device 1400 shown may include a processing unit 1410. The processing unit 1410 is configured to determine a collision ambiguity period for uplink transmission according to relative motion information between the network device and the terminal device, wherein the collision ambiguity period is configured to not perform uplink transmission.

[0156] In some implementations, the relative motion information includes one or more of the following: location information of the terminal device; location information of the network device; moving speed of the terminal device; and moving speed of the network device.

[0157] In some implementations, the processing unit 1410 is specifically used to: determine a correction value of a collision position based on the relative motion information, the collision position being a position where the uplink transmission collides with the downlink reception determined based on a time advance TA report; and determine the collision ambiguity period based on the correction value of the collision position.

[0158] In some implementations, the correction value of the collision position is a ratio between a change in the distance between the network device and the terminal device and a signal transmission speed within a predetermined period of time.

[0159] In some implementations, the correction value of the collision position is: Among them, △TA is the correction value of TA, is the position of the network device in the coordinate system, is the position of the terminal device in the coordinate system, and the coordinate system is a Cartesian coordinate system established with the position of the terminal device as the coordinate, is the moving speed of the network device, T is the predetermined time, and c is the speed of light.

[0160] In some implementations, the predetermined duration is equal to a period for the terminal device to report a TA report.

[0161] In some implementations, when the network device and the terminal device move toward each other, the collision ambiguity period is [TA0-△TA, TA0]; when the network device and the terminal device move away from each other, the collision ambiguity period is [TA0, TA0+△TA]; wherein TA0 is the collision position and △TA is the correction value of the collision position.

[0162] In some implementations, when the first angle is less than 90°, the network device and the terminal device move toward each other; when the first angle is greater than 90°, the network device and the terminal device move away from each other; wherein the first angle is the angle between the movement direction of the network device and the distance between the network device and the terminal device.

[0163] In some implementations, the processing unit 1410 is specifically used to: when the correction value of the collision position is less than a threshold value, determine the collision blur period based on the collision position before correction; when the correction value of the collision position is greater than or equal to the threshold value, determine the collision blur period based on the collision position before correction and the correction value of the collision position.

[0164] In some implementations, the priority of the downlink reception is higher than the priority of the uplink transmission.

[0165] In some implementations, the terminal device also includes a transceiver unit 1420, which is used to: receive configuration information sent by the network device, the configuration information including priority information of the uplink transmission and downlink reception and / or ephemeris information of the network device, the ephemeris information including information on the location of the network device and / or the movement speed of the network device.

[0166] In some implementations, the terminal device also includes a transceiver unit 1420, which is used to: send location information of the terminal device to the network device, and the location information of the terminal device is used by the network device to determine a collision ambiguity period for downlink reception, wherein the collision ambiguity period is configured to not perform downlink reception.

[0167] In some implementations, the transceiver unit 1420 is specifically configured to: when the location of the terminal device changes within a predetermined time interval, the terminal device sends the location information of the terminal device to the network device.

[0168] In some implementations, the terminal device is a lightweight terminal device in half-duplex frequency division duplex mode; and / or, the network device is a network device disposed on a non-ground platform in the NTN.

[0169] It can be understood that the processing unit 1410 can be, for example, the processor 1610. In addition, optionally, the terminal device 1400 also includes a transceiver 1630 and a memory 1620, for details, see Fig.16 .

[0170] Fig.15 A schematic diagram of the structure of a network device provided in an embodiment of the present application. Figure 7 The network device 1500 shown may include a processing unit 1510. The processing unit 1510 is configured to determine a collision ambiguity period for downlink reception according to relative motion information between the network device and the terminal device, wherein the collision ambiguity period is configured to not perform downlink reception.

[0171] In some implementations, the relative motion information includes one or more of the following: location information of the terminal device; location information of the network device; moving speed of the terminal device; and moving speed of the network device.

[0172] In some implementations, the processing unit 1510 is specifically used to: determine a correction value of a collision position based on the relative motion information, the collision position being a position where the downlink reception and uplink transmission collide based on a time advance TA report; and determine the collision ambiguity period based on the correction value of the collision position.

[0173] In some implementations, the correction value of the collision position is a ratio between a change in the distance between the network device and the terminal device and a signal transmission speed within a predetermined period of time.

[0174] In some implementations, the correction value of the collision position is: Among them, △TA is the correction value of TA, is the position of the network device in the coordinate system, is the position of the terminal device in the coordinate system, and the coordinate system is a Cartesian coordinate system established with the position of the terminal device as the coordinate, is the moving speed of the network device, T is the predetermined time, and c is the speed of light.

[0175] In some implementations, the predetermined duration is equal to a period for the terminal device to report a TA report.

[0176] In some implementations, when the network device and the terminal device move toward each other, the collision ambiguity period is [TA0, TA0+△TA]; when the network device and the terminal device move away from each other, the collision ambiguity period is [TA0-△TA, TA0]; wherein TA0 is the collision position and △TA is the correction value of the collision position.

[0177] In some implementations, when the first angle is less than 90°, the network device and the terminal device move toward each other; when the first angle is greater than 90°, the network device and the terminal device move away from each other; wherein the first angle is the angle between the movement direction of the network device and the distance between the network device and the terminal device.

[0178] In some implementations, the processing unit 1510 is specifically used to: when the correction value of the collision position is less than a threshold, determine the collision blur period based on the collision position before correction; when the correction value of the collision position is greater than or equal to the threshold, determine the collision blur period based on the collision position before correction and the correction value of the collision position.

[0179] In some implementations, the network device further includes a transceiver unit 1520, configured to receive location information of the terminal device reported by the terminal device.

[0180] In some implementations, the network device also includes a transceiver unit 1520, which is used to: send configuration information to the terminal device, the configuration information including priority information of the uplink transmission and downlink reception and / or ephemeris information of the network device, the ephemeris information including information about the location of the network device and / or the movement speed of the network device, the configuration information is used by the terminal device to determine a collision ambiguity period for uplink transmission, and the collision ambiguity period is configured to not perform uplink transmission.

[0181] In some implementations, the terminal device is a lightweight terminal device in half-duplex frequency division duplex mode; and / or, the network device is a network device disposed on a non-ground platform in the NTN.

[0182] It can be understood that the processing unit 1510 can be, for example, a processor 1610. In addition, optionally, the network device 1500 further includes a transceiver 1630 and a memory 1620, for details, see Fig.16 .

[0183] Fig.16 It is a schematic structural diagram of a device for communication according to an embodiment of the present application. Fig.16The dotted line shown in indicates that the unit or module is optional. The apparatus 1600 may be used to implement the method described in the above method embodiment. The apparatus 1600 may be, for example, a chip, a terminal device or a network device.

[0184] The device 1600 may include one or more processors 1610. The processor 1610 may support the device 1600 to implement the method described in the aforementioned method embodiment. The processor 1610 may be a general-purpose processor or a special-purpose processor. For example, the processor 1610 may be a central processing unit (CPU). Alternatively, the processor 1610 may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or may be any conventional processor, etc.

[0185] The apparatus 1600 may further include one or more memories 1620. The memory 1620 stores a program, which can be executed by the processor 1610, so that the processor 1610 executes the method described in the above method embodiment. The memory 1620 may be independent of the processor 1610, or may be integrated in the processor 1610.

[0186] The apparatus 1600 may further include a transceiver 1630. The processor 1610 may communicate with other devices or chips through the transceiver 1630. For example, the processor 1610 may transmit and receive data with other devices or chips through the transceiver 1630.

[0187] The embodiment of the present application also provides a communication system. The communication system includes the above-mentioned terminal device and network device. In some implementations, the system also includes other devices that interact with the terminal device and the network device.

[0188] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal device or a network device provided in the present application, and the program enables a computer to execute the method performed by the terminal device or the network device in each embodiment of the present application.

[0189] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal device or network device provided in the embodiment of the present application, and the program enables the computer to execute the method performed by the terminal device or network device in each embodiment of the present application.

[0190] The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal device or network device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the terminal device or network device in each embodiment of the present application.

[0191] It should be understood that the terms "system" and "network" in the embodiments of the present application can be used interchangeably. In addition, the terms used in the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of the present application and the accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions.

[0192] In the embodiments of the present application, the "indication" mentioned 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.

[0193] In the embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

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

[0195] In the embodiments of the present application, "pre-definition" or "pre-configuration" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0196] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0197] In the embodiments of the present application, the term "and / or" is only a description of the association relationship of the 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.

[0198] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0199] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

[0202] 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 described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may 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 may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (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 may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

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

Claims

1. A wireless communication method, characterized in that: include: The terminal device determines a collision ambiguity period for uplink transmission according to relative motion information between the network device and the terminal device, wherein the collision ambiguity period is configured to not perform uplink transmission.

2. The method according to claim 1, characterized in that The relative motion information includes one or more of the following: The location information of the terminal device; location information of the network device; The moving speed of the terminal device; The moving speed of the network device.

3. The method according to claim 1 or 2, characterized in that: The terminal device determines a collision ambiguity period for uplink transmission according to relative motion information between the network device and the terminal device, including: The terminal device determines, according to the relative motion information, a correction value of a collision position, where the collision position is a position where the uplink transmission and the downlink reception collide based on a timing advance TA report; The collision ambiguity period is determined based on the correction value of the collision position.

4. The method according to claim 3, characterized in that The correction value of the collision position is the ratio between the distance change between the network device and the terminal device and the signal transmission speed within a predetermined time period.

5. The method according to claim 4, characterized in that The correction value of the collision position is: The position in the coordinate system is a Cartesian coordinate system established with the position of the terminal device as the coordinate, is the moving speed of the network device, T is the predetermined time, and c is the speed of light.

6. The method according to claim 4 or 5, characterized in that: The predetermined duration is equal to the period for the terminal device to report the TA report.

7. The method according to any one of claims 3 to 6, characterized in that When the network device and the terminal device move toward each other, the collision ambiguity period is [TA0-△TA, TA0]; In the case where the network device and the terminal device move away from each other, the collision ambiguity period is [TA0, TA0+△TA]; Wherein, TA0 is the collision position, and ΔTA is the correction value of the collision position.

8. The method according to claim 7, characterized in that When the first angle is less than 90°, the network device and the terminal device move toward each other; When the first angle is greater than 90°, the network device and the terminal device move away from each other; The first angle is the angle between the movement direction of the network device and the distance between the network device and the terminal device.

9. The method according to any one of claims 3 to 8, characterized in that The determining the collision ambiguity period based on the correction value of the collision position comprises: determining the collision ambiguity period based on the collision position before correction when the correction value of the collision position is less than a threshold value; When the correction value of the collision position is greater than or equal to the threshold, the collision ambiguity period is determined based on the collision position before correction and the correction value of the collision position.

10. The method according to any one of claims 1 to 9, characterized in that The priority of the downlink reception is higher than the priority of the uplink transmission.

11. The method according to claim 10, characterized in that The method further comprises: The terminal device receives configuration information sent by the network device, the configuration information includes priority information of the uplink transmission and downlink reception and / or ephemeris information of the network device, the ephemeris information includes information on the location of the network device and / or the movement speed of the network device.

12. The method according to any one of claims 1 to 11, characterized in that The method further comprises: The terminal device sends location information of the terminal device to the network device, and the location information of the terminal device is used by the network device to determine a collision ambiguity period for downlink reception, wherein the collision ambiguity period is configured to not perform downlink reception.

13. The method according to claim 12, characterized in that The terminal device sending the location information of the terminal device to the network device includes: When the location of the terminal device changes within a predetermined time interval, the terminal device sends the location information of the terminal device to the network device.

14. The method according to any one of claims 1 to 13, characterized in that The terminal device is a lightweight terminal device in half-duplex frequency division duplex mode; and / or, the network device is a network device arranged on a non-terrestrial platform in a non-terrestrial network NTN.

15. A wireless communication method, characterized in that: include: The network device determines a collision ambiguity period for downlink reception according to relative motion information between the network device and the terminal device, wherein the collision ambiguity period is configured to not perform downlink reception.

16. The method according to claim 15, characterized in that The relative motion information includes one or more of the following: The location information of the terminal device; location information of the network device; The moving speed of the terminal device; The moving speed of the network device.

17. The method according to claim 15 or 16, characterized in that The network device determines, according to relative motion information between the network device and the terminal device, a collision ambiguity period for downlink reception, including: The network device determines, according to the relative motion information, a correction value of a collision position, where the collision position is a position where the downlink reception and the uplink transmission collide based on a timing advance TA report; The collision ambiguity period is determined based on the correction value of the collision position.

18. The method according to claim 17, characterized in that The correction value of the collision position is the ratio between the distance change between the network device and the terminal device and the signal transmission speed within a predetermined time period.

19. The method according to claim 18, characterized in that The correction value of the collision position is: The position in the coordinate system is a Cartesian coordinate system established with the position of the terminal device as the coordinate, is the moving speed of the network device, T is the predetermined time, and c is the speed of light.

20. The method according to claim 18 or 19, characterized in that The predetermined duration is equal to the period for the terminal device to report the TA report.

21. The method according to any one of claims 17 to 20, characterized in that When the network device and the terminal device move toward each other, the collision ambiguity period is [TA0, TA0+△TA]; In the case where the network device and the terminal device move away from each other, the collision ambiguity period is [TA0-△TA, TA0]; Wherein, TA0 is the collision position, and ΔTA is the correction value of the collision position.

22. The method according to claim 21, characterized in that When the first angle is less than 90°, the network device and the terminal device move toward each other; When the first angle is greater than 90°, the network device and the terminal device move away from each other; The first angle is the angle between the movement direction of the network device and the distance between the network device and the terminal device.

23. The method according to any one of claims 17 to 22, characterized in that The determining the collision ambiguity period based on the correction value of the collision position comprises: determining the collision ambiguity period based on the collision position before correction when the correction value of the collision position is less than a threshold value; When the correction value of the collision position is greater than or equal to the threshold, the collision ambiguity period is determined based on the collision position before correction and the correction value of the collision position.

24. The method according to any one of claims 15 to 23, characterized in that The method further comprises: The network device receives the location information of the terminal device reported by the terminal device.

25. The method according to any one of claims 15 to 24, characterized in that The method further comprises: The network device sends configuration information to the terminal device, the configuration information including priority information of the uplink transmission and downlink reception and / or ephemeris information of the network device, the ephemeris information including information of the position of the network device and / or the movement speed of the network device, the configuration information is used by the terminal device to determine a collision ambiguity period for uplink transmission, and the collision ambiguity period is configured to not perform uplink transmission.

26. The method according to any one of claims 15 to 25, characterized in that The terminal device is a lightweight terminal device in half-duplex frequency division duplex mode; and / or, the network device is a network device arranged on a non-terrestrial platform in a non-terrestrial network NTN.

27. A terminal device, characterized in that: include: A processing unit is used to determine a collision ambiguity period for uplink transmission according to relative motion information between the network device and the terminal device, wherein the collision ambiguity period is configured to not perform uplink transmission.

28. The terminal device according to claim 27, characterized in that: The relative motion information includes one or more of the following: The location information of the terminal device; location information of the network device; The moving speed of the terminal device; The moving speed of the network device.

29. The terminal device according to claim 27 or 28, characterized in that: The processing unit is specifically used for: Determine, according to the relative motion information, a correction value of a collision position, wherein the collision position is a position where the uplink transmission and the downlink reception collide based on a timing advance TA report; The collision ambiguity period is determined based on the correction value of the collision position.

30. The terminal device according to claim 29, characterized in that: The correction value of the collision position is the ratio between the distance change between the network device and the terminal device and the signal transmission speed within a predetermined time period.

31. The terminal device according to claim 30, characterized in that: The correction value of the collision position is: The position in the coordinate system is a Cartesian coordinate system established with the position of the terminal device as the coordinate, is the moving speed of the network device, T is the predetermined time, and c is the speed of light.

32. The terminal device according to claim 30 or 31, characterized in that: The predetermined duration is equal to the period for the terminal device to report the TA report.

33. The terminal device according to any one of claims 29 to 32, characterized in that: When the network device and the terminal device move toward each other, the collision ambiguity period is [TA0-△TA, TA0]; In the case where the network device and the terminal device move away from each other, the collision ambiguity period is [TA0, TA0+△TA]; Wherein, TA0 is the collision position, and ΔTA is the correction value of the collision position.

34. The terminal device according to claim 33, characterized in that: When the first angle is less than 90°, the network device and the terminal device move toward each other; When the first angle is greater than 90°, the network device and the terminal device move away from each other; The first angle is the angle between the movement direction of the network device and the distance between the network device and the terminal device.

35. The terminal device according to any one of claims 29 to 34, characterized in that: The processing unit is specifically used for: determining the collision ambiguity period based on the collision position before correction when the correction value of the collision position is less than a threshold value; When the correction value of the collision position is greater than or equal to the threshold, the collision ambiguity period is determined based on the collision position before correction and the correction value of the collision position.

36. The terminal device according to any one of claims 27 to 35, characterized in that: The priority of the downlink reception is higher than the priority of the uplink transmission.

37. The terminal device according to claim 36, characterized in that: The terminal device further includes: A transceiver unit is used to receive configuration information sent by the network device, the configuration information includes priority information of the uplink transmission and downlink reception and / or ephemeris information of the network device, the ephemeris information includes information on the location of the network device and / or the movement speed of the network device.

38. The terminal device according to any one of claims 27 to 37, characterized in that: The terminal device further includes: A transceiver unit is used to send the location information of the terminal device to the network device, and the location information of the terminal device is used by the network device to determine a collision ambiguity period for downlink reception, wherein the collision ambiguity period is configured to not perform downlink reception.

39. The terminal device according to claim 38, characterized in that: The transceiver unit is specifically used for: When the location of the terminal device changes within a predetermined time interval, the terminal device sends the location information of the terminal device to the network device.

40. The terminal device according to any one of claims 27 to 39, characterized in that: The terminal device is a lightweight terminal device in half-duplex frequency division duplex mode; and / or, the network device is a network device arranged on a non-terrestrial platform in a non-terrestrial network NTN.

41. A network device, characterized in that: include: A processing unit is used to determine a collision ambiguity period for downlink reception according to the relative motion information between the network device and the terminal device, wherein the collision ambiguity period is configured to not perform downlink reception.

42. The network device according to claim 41, characterized in that The relative motion information includes one or more of the following: The location information of the terminal device; location information of the network device; The moving speed of the terminal device; The moving speed of the network device.

43. The network device according to claim 41 or 42, characterized in that: The processing unit is specifically used for: Determine, according to the relative motion information, a correction value of a collision position, wherein the collision position is a position where the downlink reception and the uplink transmission collide based on a timing advance TA report; The collision ambiguity period is determined based on the correction value of the collision position.

44. The network device according to claim 43, characterized in that The correction value of the collision position is the ratio between the distance change between the network device and the terminal device and the signal transmission speed within a predetermined time period.

45. The network device according to claim 44, characterized in that The correction value of the collision position is: The position in the coordinate system is a Cartesian coordinate system established with the position of the terminal device as the coordinate, is the moving speed of the network device, T is the predetermined time, and c is the speed of light.

46. ​​The network device according to claim 44 or 45, characterized in that: The predetermined duration is equal to the period for the terminal device to report the TA report.

47. The network device according to any one of claims 43 to 46, characterized in that: When the network device and the terminal device move toward each other, the collision ambiguity period is [TA0, TA0+△TA]; In the case where the network device and the terminal device move away from each other, the collision ambiguity period is [TA0-△TA, TA0]; Wherein, TA0 is the collision position, and ΔTA is the correction value of the collision position.

48. The network device according to claim 47, characterized in that When the first angle is less than 90°, the network device and the terminal device move toward each other; When the first angle is greater than 90°, the network device and the terminal device move away from each other; The first angle is the angle between the movement direction of the network device and the distance between the network device and the terminal device.

49. The network device according to any one of claims 43 to 48, characterized in that: The processing unit is specifically used for: determining the collision ambiguity period based on the collision position before correction when the correction value of the collision position is less than a threshold value; When the correction value of the collision position is greater than or equal to the threshold, the collision ambiguity period is determined based on the collision position before correction and the correction value of the collision position.

50. The network device according to any one of claims 41 to 49, characterized in that: The network device further includes a transceiver unit, configured to: Receive location information of the terminal device reported by the terminal device.

51. The network device according to any one of claims 41 to 50, characterized in that: The network device further includes a transceiver unit, configured to: Configuration information is sent to the terminal device, the configuration information including priority information of the uplink transmission and downlink reception and / or ephemeris information of the network device, the ephemeris information including information of the position of the network device and / or the movement speed of the network device, the configuration information is used by the terminal device to determine a collision ambiguity period for uplink transmission, and the collision ambiguity period is configured to not perform uplink transmission.

52. The network device according to any one of claims 41 to 51, characterized in that: The terminal device is a lightweight terminal device in half-duplex frequency division duplex mode; and / or, the network device is a network device arranged on a non-terrestrial platform in a non-terrestrial network NTN.

53. A terminal device, characterized in that: It comprises a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the terminal device executes the method according to any one of claims 1 to 14.

54. A network device, characterized in that: It comprises a transceiver, a memory and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the network device executes the method according to any one of claims 15 to 26.

55. A device, characterized in that The device comprises a processor, configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 26.

56. A chip, characterized in that: The device comprises a processor, configured to call a program from a memory, so that a device equipped with the chip executes a method according to any one of claims 1 to 26.

57. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 26.

58. A computer program product, characterized in that A program is included, which causes a computer to execute the method according to any one of claims 1 to 26.

59. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 26.

Images