A method and apparatus for uplink and downlink time slot scheduling

Abstract

The present specification relates to the technical field of satellite communication, and particularly relates to an uplink and downlink time slot scheduling method and device, the method comprising: determining whether a sending time slot range occupied by uplink transmission data and a receiving time slot range occupied by downlink transmission data belong to the same time slot range, the time slot range comprising a first time slot range or a second time slot range; if not, sending first downlink control information DCI, the first downlink control information DCI corresponding to a third time slot range; wherein the third time slot range is greater than the first time slot range and the second time slot range. The present application effectively avoids problems such as too large user terminal access delay, small terminal throughput, reduced user perception ability, non-continuous connection interruption service and the like caused by frequent RRC retransmission.

Description

TECHNICAL FIELD

[0001] The present specification relates to the technical field of satellite communication, in particular to an uplink and downlink time slot scheduling method and device. BACKGROUND

[0002] According to the sending time slot occupied by the ground user terminal for sending uplink transmission data and the satellite-ground round-trip delay, the time slot number range occupied by the ground user terminal for receiving downlink data can be determined.

[0003] Since the ground user terminal can only receive and process the information in one field, it cannot receive and process the information in the above two fields at the same time. If the time slot number required to be sent by the sending time slot and the time slot number required to be sent by the receiving time slot are not in the same time slot number range, the RRC information needs to be reconfigured and retransmitted. However, frequent RRC retransmission causes problems such as too large user terminal access delay, small terminal throughput, reduced user perception ability, disconnected connection service, and the like. Therefore, the problem of RRC retransmission caused by the interval configuration of uplink and downlink time slot scheduling needs to be solved. SUMMARY

[0004] To solve the problems in the prior art, the present specification provides an uplink and downlink time slot scheduling method and device. The method comprises: determining whether the sending time slot range occupied by the uplink transmission data and the receiving time slot range occupied by the downlink transmission data belong to the same time slot range, the time slot range comprising a first time slot range or a second time slot range; if not, sending first downlink scheduling information DCI, the first DCI corresponding to a third time slot range, wherein the third time slot range is greater than the first time slot range and the second time slot range.

[0005] According to an aspect of an embodiment of the present specification, before sending the first downlink scheduling information DCI, the method comprises: merging the first time slot range and the second time slot range corresponding to the uplink transmission data and the downlink transmission data to generate a merged field; extracting the uplink time slot position and the downlink time slot position corresponding to the uplink transmission data and the downlink transmission data in the merged field, respectively; and generating the first downlink scheduling information DCI according to the uplink time slot position and the downlink time slot position.

[0006] According to an aspect of an embodiment of the present specification, merging the different time slot ranges corresponding to the uplink transmission data and the downlink transmission data to generate a merged field comprises: according to the first time slot number corresponding to the sending time slot range occupied by the uplink transmission data and the second time slot number corresponding to the receiving time slot range occupied by the downlink transmission data, configuring a third time slot range in the merged field, which is not less than the sum of the first time slot number and the second time slot number.

[0007] According to one aspect of the embodiments of this specification, extracting the uplink and downlink timeslot positions corresponding to the uplink and downlink transmission data in the merged field includes: extracting the starting transmission timeslot number from the transmission timeslot range and the starting reception timeslot number from the reception timeslot range; selecting a first preset number of transmission timeslot positions from the transmission timeslot range and a second preset number of reception timeslot positions from the reception timeslot range according to service requirements; the starting transmission timeslot number, the starting reception timeslot number, the first preset number of transmission timeslot positions, and the second preset number of reception timeslot positions constitute the uplink and downlink timeslot positions corresponding to the uplink and downlink transmission data in the merged field, respectively.

[0008] According to one aspect of the embodiments of this specification, generating first downlink scheduling information based on the uplink timeslot position and the downlink timeslot position includes: configuring the starting transmission timeslot number, the starting reception timeslot number, a first preset number of transmission timeslot positions, and a second preset number of reception timeslot positions into the pending transmission instruction of the merging field; and generating first downlink scheduling information based on the pending transmission instruction.

[0009] According to one aspect of an embodiment of this specification, before configuring the instruction to be sent to the merge field, the method further includes: selecting a third preset number of transmission time slot positions from a transmission time slot range, selecting a fourth preset number of reception time slot positions from a reception time slot range; and configuring the third preset number of transmission time slot positions and the fourth preset number of reception time slot positions in a timing layout diagram.

[0010] According to one aspect of the embodiments of this specification, when the transmission time slot range occupied by the uplink transmission data and the reception time slot range occupied by the downlink transmission data belong to two or more different time slot ranges, the method further includes: generating multiple merging fields according to the different time slot ranges corresponding to the uplink transmission data and the downlink transmission data; and configuring the multiple merging fields into an RRC command.

[0011] According to one aspect of the embodiments of this specification, determining whether the transmission time slot range occupied by the uplink transmission data and the reception time slot range occupied by the downlink transmission data belong to the same time slot range further includes: determining whether the transmission time slot range occupied by the uplink transmission data and the reception time slot range occupied by the downlink transmission data simultaneously belong to either the first time slot range of the first field of the preset link control information or the second time slot range of the second field of the preset link control information.

[0012] According to one aspect of the embodiments of this specification, before determining whether the transmission time slot range occupied by uplink transmission data and the reception time slot range occupied by downlink transmission data belong to the same time slot range, the method includes: determining the delay time slot corresponding to the satellite-to-ground round-trip delay based on the subcarrier interval and the subframe duration; and determining the reception time slot range occupied by downlink transmission data based on the transmission time slot range occupied by uplink transmission data and the delay time slot.

[0013] According to one aspect of the embodiments of this specification, the satellite-to-ground round-trip time delay is determined based on the distance between the satellite and the ground user terminal and the range of the communication angle between the satellite and the user terminal during the satellite's overhead transit.

[0014] According to one aspect of an embodiment of this specification, the method further includes: if so, sending a second DCI, the second DCI corresponding to a first time slot range or a second time slot range.

[0015] This specification provides an uplink / downlink time slot scheduling device, the device comprising: a judgment unit, for determining whether the transmission time slot range occupied by uplink transmission data and the reception time slot range occupied by downlink transmission data belong to the same time slot range, the time slot range including a first time slot range or a second time slot range; and a transmission unit, for transmitting first downlink scheduling information (DCI) if not, the first DCI corresponding to a third time slot range.

[0016] This specification also provides a network device, including: at least one processor; and at least one memory storing instructions thereon, which, when executed individually or jointly by the at least one processor, cause the network device to perform the uplink / downlink time slot scheduling method.

[0017] This specification also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the uplink / downlink time slot scheduling method.

[0018] This application overcomes the defect of RRC retransmission caused by cross-segment configuration of uplink and downlink time slot scheduling intervals in RRC by increasing the range of time slot numbers, and realizes that uplink and downlink time slot scheduling is configured in the same field. It effectively avoids problems such as excessive user terminal access latency, reduced terminal throughput, reduced user perception, connection interruption and service discontinuity caused by frequent RRC retransmissions. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 The diagram shown is a flowchart of an uplink / downlink time slot scheduling method according to an embodiment of this specification.

[0021] Figure 2 The diagram shown is a flowchart of a method for generating first downlink scheduling information (DCI) according to an embodiment of this specification.

[0022] Figure 3 The diagram shown is a flowchart of a method for extracting uplink and downlink time slot positions according to an embodiment of this specification.

[0023] Figure 4 The diagram shown is a flowchart of a method for generating first downlink scheduling information (DCI) according to an embodiment of this specification.

[0024] Figure 5 The diagram shown is a flowchart of another method for extracting the uplink and downlink timeslot positions according to an embodiment of this specification.

[0025] Figure 6 The diagram shown is a flowchart of another method for generating RRC commands according to an embodiment of this specification;

[0026] Figure 7 This is a flowchart illustrating a method for determining the range of receive time slots occupied by downlink transmitted data, as described in an embodiment of this specification.

[0027] Figure 8a The diagram shown is a schematic diagram of the configuration of multiple fields used to configure uplink and downlink time slot resources in an embodiment of this specification;

[0028] Figure 8b The diagram shown is a field configuration diagram of a merged field according to an embodiment of this specification;

[0029] Figure 9a The diagram shown is a schematic diagram of the extraction of the time slot to be transmitted from the preset link control information field in an embodiment of this specification;

[0030] Figure 9b The diagram shown is a schematic diagram of extracting the uplink and downlink timeslot positions from a merged field according to an embodiment of this specification.

[0031] Figure 9c This is a schematic diagram of an uplink / downlink time slot scheduling interval state according to an embodiment of this specification;

[0032] Figure 10 The diagram shown is a structural schematic of an uplink / downlink time slot scheduling device according to an embodiment of this specification.

[0033] Figure 11 The diagram shown is a schematic representation of a user terminal according to an embodiment of this specification.

[0034] Figure 12 The diagram shown is a schematic representation of the network device according to an embodiment of this specification.

[0035] Figure 13 The diagram shown is a schematic diagram of an uplink / downlink time slot scheduling system according to an embodiment of the present invention.

[0036] Explanation of symbols in the attached drawings:

[0037] 1001. Judgment Unit;

[0038] 1002. Transmitting Unit;

[0039] 1100, User Terminal;

[0040] 1110. Processor;

[0041] 1120. Memory;

[0042] 1130. Communication module;

[0043] 1140. Input Unit;

[0044] 1150. Monitor;

[0045] 1160. Power supply;

[0046] 1200. Network equipment;

[0047] 1210. Processor;

[0048] 1220. Memory;

[0049] 1230, Program;

[0050] 1240. Transceiver;

[0051] 1250, Antenna. Detailed Implementation

[0052] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.

[0053] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, apparatus, product, or device that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0054] This specification provides the operational steps of the methods described in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only possible execution order. In actual system or device products, the methods shown in the embodiments or drawings can be executed sequentially or in parallel.

[0055] It should be noted that the uplink and downlink time slot scheduling method and apparatus described in this specification can be used in the field of satellite communication technology, but this specification does not limit the application field of the uplink and downlink time slot scheduling method and apparatus.

[0056] This application uses terminology used in some communication specifications (e.g., the 3rd Generation Partnership Project, the European Telecommunications Standards Institute, ETSI, Extensible Radio Access Network, ERAN, and Open-Radio Access Network, O-RAN) to describe various embodiments, but this is merely illustrative. The various embodiments of this application can also be readily modified and applied in other communication systems.

[0057] In the embodiments of this application, communication between devices in the communication system can be carried out according to communication protocols at any stage, such as including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other currently known or future communication protocols.

[0058] For ease of understanding, the technical terms involved in the embodiments of this application will be explained below.

[0059] (1) Terminal: refers to a device that has wireless transceiver function and can cooperate with network-side equipment to provide communication services to users. For example, terminal devices can be mobile phones, tablets, laptops, wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless communication devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, Internet of Things (IoT) devices, narrowband Internet of Things (NB-IoT) devices, vehicle-to-everything (V2X) devices, devices in device-to-device communication (D2D), enhanced machine-type communication (eMTC) devices, and reduced-capacity devices. Capability (RedCap), cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), clients, handheld devices with wireless communication capabilities, vehicle-mounted devices, or shipboard devices, etc.

[0060] (2) Network equipment: refers to network-side equipment capable of communicating with terminal equipment. Network equipment can be located on satellites or the ground. Network equipment can also be called space base station, satellite-borne base station, satellite, satellite communication node, satellite network terminal equipment, satellite communication module, or base station, etc. This network-side equipment can also be called access network equipment or wireless access network equipment. Network-side equipment can be a base station (BTS) in a satellite-borne Global System for Mobile Communication (GSM) or Code Division Multiple Access (CDMA) communication system; a base station (NodeB, NB) in a satellite-borne Wideband Code Division Multiple Access (WCDMA) system; an evolved base station (eNB, eNodeB) in a satellite-borne LTE system; a base station in a terrestrial network or non-terrestrial network (NTN), such as a base station (gNB) in a satellite-borne 5G network; a base station in a future network (e.g., 6G network) after 5G, carried by satellite; a base station in a future evolved Public Land Mobile Network (PLMN) network, carried by satellite; a Transmission Reception Point (TRP), carried by satellite; or a Cloud Radio Access Network, carried by satellite. In the context of Networks (CRAN), wireless controllers can also be satellite-borne city base stations, micro base stations, pico base stations, or femtobase stations. Base stations can also be ground-based base stations capable of satellite communication, and can be referred to as Access Points (APs), 5G nodes (5th generation nodes), wireless points, or Transmission / Reception Points (TRPs), the latter having equivalent technical meanings. Network equipment can also refer to base station equipment carried by High Altitude Platform Stations (HAPS) with loiter capabilities, such as large balloons or airships, base station equipment in Roadside Units (RSUs), or base station equipment in vehicle-to-everything (V2X) networks.

[0061] Figure 1 The diagram shown is a flowchart of an uplink / downlink time slot scheduling method according to an embodiment of this specification, which specifically includes the following steps:

[0062] Step 101: Determine whether the transmission time slot range occupied by the uplink transmission data and the reception time slot range occupied by the downlink transmission data belong to the same time slot range, wherein the time slot range includes a first time slot range or a second time slot range.

[0063] In low-Earth orbit (LEO) satellite mobile communication systems, when a ground-based user terminal (user terminal) acts as the transmitter, it sends uplink data to the satellite and receives downlink data after the satellite generates downlink data based on the uplink data. Conversely, when the satellite acts as the transmitter, it sends downlink data to the ground-based user terminal and receives uplink data after the user terminal generates uplink data based on the downlink data.

[0064] Specifically, when the ground user terminal acts as the transmitter, the downlink control information (DCI) configuration for the ground user terminal's receive time slot number must consider the impact of uplink transmission delay to ensure that the satellite can receive uplink data in a timely manner. When the satellite acts as the transmitter, the DCI configuration for the satellite's receive time slot number must consider the impact of downlink transmission delay to ensure that downlink data is received in a timely manner. The DCI configuration of transmit and receive time slot numbers is used for dynamic resource scheduling, informing the terminal how to send and receive data. In the embodiments of this specification, the transmit and receive time slot ranges include a first time slot range or a second time slot range, which can be specifically represented by the transmit and receive time slot numbers.

[0065] Figure 8a The diagram shows several field configurations for configuring uplink and downlink time slot resources in embodiments of this specification. The field DL-DataToUL-ACK is applicable to DCI format 1_1. The field DL-DataToUL-ACK-DCI-1-2 is applicable to DCI format 1_2. DL-DataToUL-ACK-v1700 is applicable to NTN. The size (1.8) on the right side of the diagram represents the number of bits occupied by the field, and INTEGER represents the range of integer values.

[0066] Prior to this step, the RRC fields DL-DataToUL-Ack-DCI-1-2-r16 and DL-DataToUL-Ack-v1700 in the 3GPP 38.331 protocol are configured in advance according to the transmit and receive time slot number ranges, respectively. The fields DL-DataToUL-Ack-DCI-1-2-r16 and DL-DataToUL-Ack-v1700 indicate time slot number ranges of 0-15 and 16-31, respectively, corresponding to the first and second time slot ranges described in this step. In this step, it is determined whether the transmit time slot range occupied by uplink transmission data and the receive time slot range occupied by downlink transmission data belong to the same time slot range. Specifically, it is determined whether both the transmit and receive time slot ranges belong to 0-15 or both belong to 16-31.

[0067] In existing technology, after configuring the DL-DataToUL-Ack-DCI-1-2-r16 field, the ground user terminal will ignore the DL-DataToUL-Ack-v1700 field; similarly, after configuring the DL-DataToUL-Ack-v1700 field, the ground user terminal will also ignore the DL-DataToUL-Ack-DCI-1-2-r16 field. When configuring the uplink transmission slot number in DL-DataToUL-Ack-DCI-1-2-r16 and the downlink reception slot number in DL-DataToUL-Ack-v1700, the user terminal cannot simultaneously receive and process these two fields. Therefore, configuring these two fields simultaneously in the same RRC configuration is invalid. In this case, these two fields must be completed in two separate RRC configurations, resulting in problems such as excessive user terminal access latency, low terminal throughput, and reduced user perception.

[0068] Step 102: If not, send a first downlink scheduling information (DCI), the first DCI corresponding to a third time slot range; wherein the third time slot range is greater than the first time slot range and the second time slot range.

[0069] In this step, when the transmission time slot range occupied by uplink data and the reception time slot range occupied by downlink data do not belong to the same time slot range, a first downlink scheduling information (DCI) corresponding to the third time slot range is sent. The first downlink scheduling information (DCI) is used for uplink and downlink time slot scheduling. For example, when the uplink transmission time slot range occupied by uplink data is within the first time slot range 0-15, and the downlink reception time slot range occupied by downlink data is within the second time slot range 13-31, the transmission time slot range occupied by uplink data and the reception time slot range occupied by downlink data belong to different time slot ranges, and a first downlink scheduling information (DCI) is sent, which corresponds to the third time slot range. In this specification, the third time slot range is larger than the first and second time slot ranges. Specifically, the third time slot range is larger than both the first and second time slot ranges.

[0070] Figure 2 The diagram shown is a flowchart of a method for generating first downlink scheduling information (DCI) according to an embodiment of this specification, specifically including steps 201 to 203:

[0071] Step 201: Merge the first time slot range and the second time slot range corresponding to the uplink transmission data and the downlink transmission data to generate a merged field.

[0072] To generate the first downlink scheduling information (DCI), it is necessary to combine the first time slot range and the second time slot range to generate a merged field. According to... Figure 1 In the embodiments described above, a merge field is generated based on the first time slot range and the second time slot range provided by DL-DataToUL-Ack-DCI-1-2-r16 and DL-DataToUL-Ack-v1700, and the downlink receive time slot number and the uplink transmit time slot number are configured in the merge field.

[0073] In some embodiments of this specification, based on the number of first time slot numbers corresponding to the transmission time slot range occupied by uplink transmission data and the number of second time slot numbers corresponding to the reception time slot range occupied by downlink transmission data, a time slot not less than the number of the first time slot numbers or the number of the second time slot numbers is configured in the merging field, that is, a third time slot range is configured in the merging field.

[0074] For example, the uplink data transmission occupies a transmission time slot range of 0-15, and the time slot number corresponding to this range is called the first time slot number, with a total of 16 first time slot numbers. The downlink data transmission occupies a reception time slot range of 16-31, and the time slot number corresponding to this range is called the second time slot number, with a total of 16 second time slot numbers. Therefore, if the number of time slots configured in the merge field is greater than or equal to the number of first time slot numbers, or greater than or equal to the number of second time slot numbers, then the merge field needs to be configured with at least 16 time slots. For example, configuring 18, 20, or 24 time slots corresponds to the third time slot range, which can, to some extent, solve the problem of configuring RRC commands across fields.

[0075] In some other embodiments of this specification, the number of time slots configured in the merging field is not less than the sum of the number of the first time slot numbers and the number of the second time slot numbers, which constitutes the third time slot range. Specifically, for example, the uplink transmission data occupies a transmission time slot range of 0-15, and the time slot numbers corresponding to this range are called the first time slot numbers, with a total of 16 first time slot numbers; the downlink transmission data occupies a reception time slot range of 16-31, and the time slot numbers corresponding to this range are called the second time slot numbers, with a total of 16 second time slot numbers. Therefore, the merging field needs to be configured with a number of time slots greater than or equal to the sum of the number of the first and second time slot numbers, meaning the merging field needs to be configured with at least 32 time slots, which constitutes the third time slot range. In one embodiment, the third time slot range can be 0-31.

[0076] In this specification, the merged field can be the field DL-DataToUL-Ack-DCI-1-2-r18, which is applicable to multiple standard systems. It overcomes the defect of cross-segment configuration of the transmission time slot range occupied by uplink transmission data and the reception time slot range occupied by downlink transmission data in RRC by appropriately increasing the time slot number range, and realizes the configuration of uplink and downlink time slot scheduling in the same field.

[0077] In one embodiment of this specification, when the transmission time slot range occupied by uplink transmission data and the reception time slot range occupied by downlink transmission data belong to the same time slot range, a second downlink scheduling information (DCI) is transmitted. The second downlink scheduling information (DCI) corresponds to either the first time slot range or the second time slot range. That is, when both the transmission time slot number range and the reception time slot number range are within the same time slot range, the uplink time slot position and the downlink time slot position are configured simultaneously within either the first time slot range of the first field of the preset link control information or the second time slot range of the preset link control information second field. Based on the uplink and downlink time slot positions, the downlink scheduling information (DCI) and RRC commands are generated. For example, when both the transmission time slot number range and the reception time slot number range are within 0-15 or 16-31, the uplink transmission time slot number and the downlink reception time slot number can be uniformly configured based on either DL-DataToUL-Ack-DCI-1-2-r16 or DL-DataToUL-Ack-v1700, thereby generating the second downlink scheduling information (DCI).

[0078] Step 202: Extract the uplink and downlink timeslot positions corresponding to the uplink and downlink transmission data from the merged field, respectively.

[0079] Before performing this step, the process also includes: determining the uplink and downlink timeslot positions corresponding to the uplink and downlink transmitted data, respectively. The uplink timeslot position for the uplink transmitted data is extracted from the transmission timeslot range of the uplink transmitted data, and the downlink timeslot position for the downlink transmitted data is extracted from the reception timeslot range of the downlink transmitted data, such as... Figure 8a As shown.

[0080] Step 203: Generate first downlink scheduling information (DCI) based on the uplink time slot position and the downlink time slot position.

[0081] This step generates the instruction to be sent in the merge field, namely the first downlink scheduling information (DCI), based on the uplink and downlink timeslot positions in the uplink and downlink transmission data.

[0082] In this specification, the fields DL-DataToUL-Ack-DCI-1-2-r16 and DL-DataToUL-Ack-v1700 are merged into DL-DataToUL-Ack-DCI-1-2-r18. Within this merged field, a first downlink scheduling information (DCI) is generated based on the uplink and downlink timeslot positions. Furthermore, an RRC (Radio Resource Control) instruction can be generated based on the first downlink scheduling information (DCI). The RRC instruction is a core control plane protocol in 5G / 4G radio access networks, managing connection configuration, resource allocation, and mobility control between the UE (User Equipment) and the base station (gNB / eNB). The uplink transmit timeslot number and downlink receive timeslot number can be uniformly configured using either field in DL-DataToUL-Ack-DCI-1-2-r16 or DL-DataToUL-Ack-v1700.

[0083] This application can avoid problems such as excessive user terminal access latency, reduced terminal throughput, and decreased user perception caused by frequent RRC retransmissions.

[0084] Figure 3 The diagram shown is a flowchart of a method for extracting uplink and downlink time slot positions according to an embodiment of this specification, specifically including steps 301 to 303:

[0085] Step 301: Extract the starting transmission time slot number from the transmission time slot range and the starting reception time slot number from the reception time slot range.

[0086] In this step, the starting transmission time slot number and the starting reception time slot number can be defined in the transmission time slot range and the reception time slot range, respectively. For example, in the field DL-DataToUL-Ack-DCI-1-2-r16, the uplink transmission starting time slot number is defined as 7, and at least one time slot number is selected from the time slot number range of this field for further transmission via DCI; in the field DL-DataToUL-Ack-v1700, the downlink reception starting time slot number is defined as 17, and at least one time slot number is selected from the time slot number range of this field for further transmission via DCI. It is worth noting that after defining the uplink transmission time slot number, the downlink reception starting time slot number can be determined based on the bidirectional signal propagation delay between the satellite and the ground user terminal.

[0087] In this step, the starting transmission time slot number and the starting reception time slot number are deployed to the pending transmission instruction in the merged field. In the embodiment of this specification, the merged field is designed as DL-DataToUL-Ack-DCI-1-2-r18, such as... Figure 8b As shown, Figure 8bThe diagram shown is a field configuration diagram of a merged field according to an embodiment of this specification. The long field within the solid line box in the diagram is the merged field according to an embodiment of this specification. The length of the instruction to be sent in the merged field is still 8, and the instruction to be sent includes the uplink transmission start time slot number 7 and the downlink reception start time slot number 17.

[0088] Step 302: Based on business requirements, select a first preset number of transmission time slot positions from the transmission time slot range, and select a second preset number of reception time slot positions from the reception time slot range.

[0089] Further in this step, it is necessary to select the corresponding transmission time slot positions from the transmission time slot range and the corresponding reception time slot positions from the reception time slot range. A first preset number of transmission time slot positions and a second preset number of reception time slot positions can be selected according to business requirements.

[0090] In the embodiments of this specification, the first preset quantity may be the total number of transmission time slot positions in the transmission time slot range excluding the starting transmission time slot number; the second preset quantity may be the total number of reception time slot positions in the reception time slot range excluding the starting reception time slot number; the first preset quantity may also be less than the total number of transmission time slot positions in the transmission time slot range excluding the starting transmission time slot number, and the second preset quantity may also be less than the total number of reception time slot positions in the reception time slot range excluding the starting reception time slot number. This application does not limit the specific quantity of the first preset quantity or the second preset quantity.

[0091] For example, the transmission time slot range has a total of 3 transmission time slot positions excluding the starting transmission time slot number, and the reception time slot range has a total of 3 reception time slot positions excluding the starting reception time slot number. The first preset quantity and the second preset quantity can both be 3, or they can be less than 3. As another example, if the transmission time slot range has a total of 8 transmission time slot positions, and the reception time slot range has a total of 8 reception time slot positions, then the first preset quantity and the second preset quantity are numbers greater than or equal to 1 and less than or equal to 7.

[0092] Figure 8a In this context, the fields DL-DataToUL-Ack-DCI-1-2-r16 and DL-DataToUL-Ack-v1700 represent two existing configured fields. Uplink and downlink transmission data are generated based on these two field configurations. In a communication system, DL-DataToUL represents the transmission delay from downlink to uplink data, typically used to determine the timing of uplink feedback information (such as HARQ-ACK).

[0093] Figure 9aThe diagram shown is a schematic diagram of the extraction of the time slot to be transmitted from the preset link control information field in an embodiment of this specification.

[0094] In the embodiments of this specification, the first field of the preset link control information can be the field DL-DataToUL-Ack-DCI-1-2-r16, and the second field of the preset link control information can be the field DL-DataToUL-Ack-v1700. The time slots {0,3,7,8,9,12,14,15} are selected from the time slot number range of 0-15 in the first field of the preset link control information and transmitted via DCI. The time slots {17,19,20,23,25,27,29,31} are selected from the second field of the preset link control information DL-DataToUL-Ack-v1700 and transmitted via DCI.

[0095] In this specification, a first preset number of transmit time slot locations are selected after the time slot number selected in the field DL-DataToUL-Ack-DCI-1-2-r16, and a second preset number of receive time slot locations are selected within the time slot number range selected in the field DL-DataToUL-Ack-v1700, and then further transmitted via DCI.

[0096] Step 303: The starting transmission time slot number, the starting reception time slot number, the first preset number of transmission time slot positions, and the second preset number of reception time slot positions constitute the uplink and downlink time slot positions corresponding to the uplink transmission data and downlink transmission data in the merged field, respectively.

[0097] This step merges and combines the time slot positions extracted in steps 301 and 302, such as... Figure 9b As shown, the instruction to be sent in the merge field is an instruction with size=8, which includes the uplink timeslot position corresponding to the uplink transmission data and the downlink timeslot position corresponding to the downlink transmission data.

[0098] Figure 4 The diagram shown is a flowchart of a method for generating RRC commands according to an embodiment of this specification, specifically including steps 401 to 402:

[0099] Step 401: Configure the starting transmission time slot number, the starting reception time slot number, the first preset number of transmission time slot positions, and the second preset number of reception time slot positions into the pending transmission instruction of the merging field.

[0100] In this step, according to the order of uplink and downlink data transmission, the starting transmission time slot number, the starting reception time slot number, the first preset number of transmission time slot positions, and the second preset number of reception time slot positions are combined into the instruction to be sent.

[0101] like Figure 9b The diagram illustrates an embodiment of this specification for extracting uplink and downlink time slot positions by merging fields. In this specification, four transmit time slot positions are selected after the time slot number selected in the field DL-DataToUL-Ack-DCI-1-2-r16, and four receive time slot positions are selected within the time slot number range selected in the field DL-DataToUL-Ack-v1700. These are combined to obtain the transmission instruction {0, 7, 12, 15, 17, 20, 25, 29}, which includes the starting transmit time slot number 7 and the starting receive time slot number 17.

[0102] Step 402: Generate the first downlink scheduling information (DCI) based on the instruction to be sent.

[0103] In this step, the command to be sent is configured in the DL-DataToUL-ACK field to obtain the first downlink scheduling information (DCI). Further using the DL-DataToUL-ACK field, combined with other fields (such as radioBearerConfig, masterCellGroup, secondaryCellGroup, measConfig, and mobilityControlInfo), an RRC command can be generated. This avoids problems such as excessive user terminal access latency, reduced terminal throughput, and decreased user perception caused by frequent RRC retransmissions.

[0104] Figure 5 The diagram shows a flowchart of another method for extracting the uplink and downlink timeslot positions according to an embodiment of this specification. Specifically, it includes steps 501 to 502:

[0105] Step 501: Select a third preset number of transmission time slot positions from the transmission time slot range, and select a fourth preset number of reception time slot positions from the reception time slot range.

[0106] This step is in Figure 3 This is implemented based on the above. If the first preset number selected from the transmission time slot range in step 302 is less than the number of all transmission time slot positions in the transmission time slot range except for the starting transmission time slot number, or the second preset number selected from the reception time slot range is less than the number of all reception time slot positions in the reception time slot range except for the starting reception time slot number, then in this step, the remaining number of transmission time slot positions are further selected from the transmission time slot range, and the remaining number of reception time slot positions are selected from the reception time slot range. That is, the third preset number of transmission time slot positions and the fourth preset number of reception time slot positions, respectively.

[0107] Step 502: Configure a third preset number of transmission time slot positions and a fourth preset number of reception time slot positions in the timing layout diagram.

[0108] In this step, the timing diagram is used in wireless communication systems to visualize the scheduling relationships of time-domain resources. It displays the precise correspondence between the transmit / receive actions of each node (base station, terminal, satellite) and time slots / symbols via a time axis. The timing diagram configures a third preset number of transmit time slot positions and a fourth preset number of receive time slot positions to ensure that the data content in the subsequently generated RRC commands is consistent with the transmitted data content in the uplink and downlink transmissions.

[0109] When the transmission time slot range occupied by the uplink data and the reception time slot range occupied by the downlink data belong to two or more different time slot ranges, Figure 6 The diagram shows another method for generating RRC commands according to an embodiment of this specification, specifically including steps 601 to 602:

[0110] Step 601: Generate multiple merge fields based on the different time slot ranges corresponding to the uplink transmission data and the downlink transmission data.

[0111] In some embodiments of this specification, if the time slot range corresponding to the uplink transmission data exceeds 0-15 or 16-31, and the receiving time slot range corresponding to the downlink transmission data also exceeds 0-15 or 16-31, it indicates that the time slot ranges corresponding to the uplink and downlink transmission data exceed two. Therefore, according to the time slot range in the merging field described above, two or more merging fields are required. Thus, it is necessary to generate two or more merging fields according to the aforementioned steps for generating merging fields.

[0112] Step 602: Configure multiple merge fields in the RRC command. This step is similar to step 203, and will not be described in detail here.

[0113] Figure 7 The diagram shows a method for determining the range of receive time slots occupied by downlink transmission data according to an embodiment of this specification, specifically including steps 701 to 702:

[0114] Step 701: Determine the time delay slot corresponding to the satellite-to-ground round-trip time delay based on the subcarrier spacing and subframe duration.

[0115] In the embodiments of this specification, the frame length of the NR radio frame is 10ms, the duration of a subframe is 1ms, the subcarrier spacing is 15KHz, and there is only one time slot in each subframe, so the duration of each time slot is 1ms.

[0116] In the embodiments of this specification, the satellite-to-ground round-trip time (RTT) is determined based on the distance between the satellite and the ground user terminal, and the range of the communication angle between the satellite and the user terminal during the satellite's overhead transit. Assuming the satellite's orbital altitude is 500 kilometers and the communication angle of the ground user terminal during the satellite's overhead transit ranges from 30° to 90°, the distance between the satellite and the ground during the satellite's overhead transit ranges from 500 kilometers to 910 kilometers. Therefore, the calculated RTT range is 3.4 milliseconds to 6 milliseconds. Thus, the RTT range in this application corresponds to 4-6 time slots.

[0117] Step 702: Determine the range of receiving time slots occupied by the uplink transmission data based on the range of transmission time slots occupied by the uplink transmission data and the delay time slots.

[0118] In this step, after determining the time slots corresponding to the round-trip delay, the range of receiving time slots occupied by the downlink transmission data is determined based on the range of transmission time slots occupied by the uplink transmission data. For example... Figure 9c As shown, Figure 9c This is a schematic diagram illustrating one uplink / downlink time slot scheduling interval state according to an embodiment of this specification. The user terminal starts sending Msg information with a time slot length of 4 starting from the 7th time slot. After a 6ms round-trip time delay between the satellite and ground, the user terminal receives the Msg information fed back by the satellite. The user terminal then starts receiving Msg information with a time slot length of 4 starting from the 14th time slot, thus determining that the downlink transmission data occupies the receiving time slot range from the 14th to the 17th time slot. Both the sending and receiving time slot ranges fall within the time slot range specified in the field DL-DataToUL-Ack-DCI-1-2-r1. Data transmission between the user terminal and the satellite can be completed with only one RRC command generated, avoiding frequent RRC retransmissions.

[0119] Figure 10 The diagram shown is a structural schematic of an uplink / downlink time slot scheduling device according to an embodiment of this specification. The basic structure of the uplink / downlink time slot scheduling device is illustrated in this figure. The functional units and modules can be implemented in software, or uplink / downlink time slot scheduling can be implemented using general-purpose chips or specific chips. The device specifically includes:

[0120] The judgment unit 1001 determines whether the transmission time slot range occupied by the uplink transmission data and the reception time slot range occupied by the downlink transmission data belong to the same time slot range, wherein the time slot range includes a first time slot range or a second time slot range.

[0121] The transmitting unit 1002 is configured to transmit, if not, first downlink scheduling information (DCI), the first downlink scheduling information (DCI) corresponding to a third time slot range, wherein the third time slot range is greater than the first time slot range and the second time slot range;

[0122] like Figure 11The diagram shown is a schematic representation of a user terminal according to an embodiment of this specification. Figure 11 As shown, the user terminal 1100 may include a processor 1110 and a memory 1120; the memory 1120 stores data and programs and is coupled to the processor 1110. It is worth noting that this figure is exemplary, and other types of structures may be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0123] For example, processor 1110 can be configured to execute a program to implement the uplink / downlink time slot method as described in the previous embodiment. For example, processor 1110 can be configured to perform control such as generating uplink transmission data and sending it to the network device.

[0124] like Figure 11 As shown, the user terminal 1100 may further include: a communication module 1130, an input unit 1140, a display 1150, and a power supply 1160. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the user terminal 1100 is not necessarily required to include these components. Figure 11 Of all the components shown, the aforementioned components are not essential; furthermore, the user terminal 1100 may also include Figure 11 For components not shown, please refer to existing technologies.

[0125] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices. Figure 12 The diagram shown is a schematic representation of the network device according to an embodiment of this specification. Figure 12 As shown, the network device 1200 may include a processor 1210 (e.g., a central processing unit CPU) and a memory 1220; the memory 1220 is coupled to the processor 1210. The memory 1220 can store various data; in addition, it also stores an information processing program 1230, and executes the program 1230 under the control of the processor 1210.

[0126] For example, processor 1210 can be configured to execute a program to implement the uplink / downlink time slot scheduling method as described in the previous embodiment. For example, processor 1210 can be configured to perform the following control: generate downlink transmission data and send it to the user terminal; determine whether the transmission time slot range occupied by the uplink transmission data and the reception time slot range occupied by the downlink transmission data belong to the same time slot range.

[0127] In addition, such as Figure 12 As shown, network device 1200 may also include: transceiver 1240 and antenna 1250, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 1200 is not necessarily required to include... Figure 12All components shown; in addition, network device 1200 may also include Figure 12 For components not shown, please refer to existing technologies.

[0128] like Figure 13 The diagram illustrates an uplink / downlink time slot scheduling system according to an embodiment of the present invention. The system may include a user terminal 1100 and a network device 1200. The user terminal 1100 and the network device 1200 communicate via an intermediate channel. The user terminal 1100 sends an uplink transmission signal, which arrives at the network device 1200 via the intermediate channel, enabling the network device 1200 to generate downlink transmission data and send it to the user terminal 1100. After determining that the transmission time slot range occupied by the uplink transmission data and the reception time slot range occupied by the downlink transmission data belong to different time slot ranges, the user terminal 1100 sends a first downlink scheduling information (DCI), which corresponds to a third time slot range.

[0129] The network equipment 1200 includes, but is not limited to, satellite and smart terminal equipment, and the user terminal 1100 includes, but is not limited to, smart terminal equipment, which are not limited herein.

[0130] In addition, it should be noted that, Figure 13 The example shown is merely one application environment provided in this disclosure. In practical applications, multiple user terminals may be included, and this specification does not impose any restrictions.

[0131] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), computer-readable storage media, and computer program products according to some embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processor to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processor, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0132] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processor to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0133] These computer program instructions may also be loaded onto a computer or other programmable data processor, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0134] It should be understood that in the various embodiments of this specification, the sequence number of each process does not imply 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 this specification.

[0135] It should also be understood that, in the embodiments of this specification, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this specification generally indicates that the preceding and following related objects have an "or" relationship.

[0136] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this specification can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this specification.

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

[0138] In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, devices, or units, or they may be electrical, mechanical, or other forms of connection.

[0139] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments described in this specification, depending on actual needs.

[0140] Furthermore, the functional units in the various embodiments of this specification can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0141] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this specification, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this specification. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0142] This specification uses specific embodiments to illustrate the principles and implementation methods of this specification. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this specification. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this specification. Therefore, the content of this specification should not be construed as a limitation of this specification.

Claims

1. A method for scheduling uplink and downlink time slots, characterized in that, The method includes: The time slot corresponding to the satellite-to-ground round-trip delay is determined based on the subcarrier spacing and subframe duration. The range of receiving time slots occupied by the uplink transmission data is determined based on the range of transmission time slots occupied by the uplink transmission data and the delay time slots. Determine whether the transmission time slot range occupied by the uplink transmission data and the reception time slot range occupied by the downlink transmission data belong to the same time slot range, wherein the time slot range includes a first time slot range or a second time slot range; If not, merge the first and second time slot ranges corresponding to the uplink and downlink transmission data to generate a merged field; extract the uplink and downlink time slot positions corresponding to the uplink and downlink transmission data respectively from the merged field; generate a first downlink scheduling information (DCI) based on the uplink and downlink time slot positions; send the first downlink scheduling information (DCI), which corresponds to a third time slot range; wherein the third time slot range is greater than the first and second time slot ranges.

2. The method according to claim 1, characterized in that, By merging the different time slot ranges corresponding to the uplink and downlink transmission data, the generated merged field includes: Based on the number of first time slot numbers corresponding to the transmission time slot range occupied by uplink transmission data and the number of second time slot numbers corresponding to the reception time slot range occupied by downlink transmission data, a third time slot range not less than the sum of the number of first time slot numbers and the number of second time slot numbers is configured in the merging field.

3. The method according to claim 2, characterized in that, Extracting the uplink and downlink timeslot positions corresponding to the uplink and downlink transmission data from the merged field includes: Extract the starting transmission time slot number from the transmission time slot range and the starting reception time slot number from the reception time slot range; According to business requirements, a first preset number of transmission time slot positions are selected from the transmission time slot range, and a second preset number of reception time slot positions are selected from the reception time slot range; The starting transmission time slot number, the starting reception time slot number, the first preset number of transmission time slot positions, and the second preset number of reception time slot positions constitute the uplink and downlink time slot positions corresponding to the uplink transmission data and downlink transmission data in the merged field, respectively.

4. The method according to claim 3, characterized in that, The generation of the first downlink scheduling information (DCI) based on the uplink and downlink timeslot positions includes: Configure the starting transmission time slot number, the starting reception time slot number, the first preset number of transmission time slot positions, and the second preset number of reception time slot positions into the pending transmission instruction of the merging field; The first downlink scheduling information (DCI) is generated based on the instruction to be sent.

5. The method according to claim 4, characterized in that, Before configuring the instruction to be sent to the merge field, the method further includes: Select a third preset number of transmission time slot positions from the transmission time slot range, and select a fourth preset number of reception time slot positions from the reception time slot range; Configure a third preset number of transmit time slot positions and a fourth preset number of receive time slot positions in the timing layout diagram.

6. The method according to claim 1, characterized in that, When the transmission time slot range occupied by the uplink data and the reception time slot range occupied by the downlink data belong to two or more different time slot ranges, The method further includes: Based on the different time slot ranges corresponding to the uplink and downlink transmission data, multiple merge fields are generated; Configure multiple merge fields into a single RRC command.

7. The method according to claim 1, characterized in that, Determining whether the transmission time slot range occupied by uplink transmission data and the reception time slot range occupied by downlink transmission data belong to the same time slot range further includes: Determine whether the range of transmission time slots occupied by uplink transmission data and the range of reception time slots occupied by downlink transmission data both belong to either the first time slot range of the first field of the preset link control information or the second time slot range of the second field of the preset link control information.

8. The method according to claim 7, characterized in that, The satellite-to-ground round-trip time delay is determined based on the distance between the satellite and the ground user terminal and the range of the communication angle between the satellite and the user terminal during the satellite's overhead transit.

9. The method according to claim 1, characterized in that, The method further includes: If so, send a second DCI, which corresponds to either the first time slot range or the second time slot range.

10. An uplink / downlink time slot scheduling device, characterized in that, The device includes: The delay slot determination unit is used to determine the delay slot corresponding to the satellite-to-ground round-trip delay based on the subcarrier spacing and subframe duration. The receiving time slot range determination unit is used to determine the receiving time slot range occupied by the downlink transmission data based on the transmission time slot range occupied by the uplink transmission data and the delay time slot. The judgment unit determines whether the transmission time slot range occupied by the uplink transmission data and the reception time slot range occupied by the downlink transmission data belong to the same time slot range, wherein the time slot range includes a first time slot range or a second time slot range; The transmitting unit is configured to, if not, merge the first time slot range and the second time slot range corresponding to the uplink transmission data and the downlink transmission data to generate a merged field; extract the uplink time slot position and the downlink time slot position corresponding to the uplink transmission data and the downlink transmission data respectively from the merged field; generate a first downlink scheduling information (DCI) based on the uplink time slot position and the downlink time slot position; and transmit the first downlink scheduling information (DCI), wherein the first downlink scheduling information (DCI) corresponds to a third time slot range; wherein the third time slot range is greater than the first time slot range and the second time slot range.

11. A network device, characterized in that, include: At least one processor; as well as At least one memory storing instructions that, when executed individually or jointly by the at least one processor, cause the network device to perform the method of any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1 to 9.

Images