Patent Description:
In a new radio (new radio, NR) system, a hybrid automatic repeat request (Hybrid Automatic Repeat Request, HARQ) is used in a data transmission process. The HARQ is widely applied because the HARQ enjoys high reliability of an automatic repeat request (Automatic Repeat Request, ARQ) manner and high efficiency of a forward error correction (Forward Error Correction, FEC) manner.

However, when a HARQ mechanism is enabled, a relatively large storage space in a receiving device is occupied. In addition, more enabled HARQ processes occupy larger storage space in the receiving device. Therefore, how to prevent the HARQ process from occupying excessively large buffer space in the receiving device becomes an urgent problem to be resolved.

In <NPL>, it is shown that a decision for disabling/enabling HARQ operation can be made based on the NTN UE memory class, or RTT, or network. That means that if gNB belongs to a Non-Terrestrial Network, it may totally disable HARQ process retransmission for all UEs associated with. In such a case, signaling for disabling HARQ is broadcaset to all UEs through system information in broadcast channel. Disabling HARQ operation is issued by gNB (or Network) by sending a signal or a collection of signals through either broadcast channel, or RCC configuration, or L <NUM> DCI signaling, or a combination of RRC configuration and L1 DCI signaling. Disabling HARQ is done explicitly or implicitly.

In <NPL>, it is shown that a new identifier HARQ C-RNTI is defined which identifies grants/assignments with deactivated HARQ. HARQ C-RNTI is a dedicated RNTI and is configured by RRC. gNB configures a UE with a HARQ C-RNTI as part of RRC configuration. The CRC parity bits obtained for the PDCCH payload are scrambled with the HARQ C-RNTI for HARQ deactivation.

In order to solve the above problems, the present invention provides hybrid automatic repeat request, HARQ, process disabling methods, an apparatus, a computer-readable storage medium, a computer program product, having the features of the respective independent claims. Dependent claims refer to embodiments. In the following, examples are described which are useful for understanding the invention.

This application provides a HARQ process disabling method, a receiving device, and a sending device, to reduce buffer space occupied by a HARQ process, improve a network throughput, and enhance system performance.

In the solutions in the embodiments of this application, the receiving device may obtain the indication data, and if the receiving device determines that the indication data indicates to disable the HARQ process, the receiving device disables the HARQ process. Therefore, in the embodiments of this application, the receiving device may directly determine, based on the indication data, to disable the HARQ process. This prevents the HARQ process from occupying excessively large buffer space. In addition, after the HARQ process is disabled, subsequent data related to the HARQ process may be reused. This improves transmitted data utilization, saves network resources, and enhances system performance.

The HARQ process disabling method in this application may be applied to a scenario including a plurality of network devices. One receiving device may be connected to one or more sending devices, and one sending device may be connected to one or more receiving devices. For example, the sending device in this application may be a base station, and the receiving device may be a terminal device. One terminal device may be connected to one or more base stations, and one base station may be connected to one or more terminal devices. For example, a specific scenario of the HARQ process disabling method in this embodiment of this application may be shown in <FIG>. As shown in <FIG>, one base station may be connected to one or more terminal devices (a terminal device <NUM> and a terminal device <NUM> in <FIG>). As shown in <FIG>, one terminal device may be connected to one or more base stations (a base station <NUM>, a base station <NUM>, and a base station <NUM> in <FIG>).

More specifically, the sending device in this embodiment of this application may be a macro base station, a micro base station (which is also referred to as a small cell), a relay station, an access point, or the like in various forms. In different communications systems, names of sending devices may be different. For example, the sending device may be a global system for mobile communications (Global System for Mobile Communications, GSM), a base transceiver station (Base Transceiver Station, BTS) in a code division multiple access (Code Division Multiple Access, CDMA) network, an NB (NodeB) in wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA), or a long term evolutional NodeB (Evolutional NodeB, eNB or eNodeB) in a long term evolution (Long Term Evolution, LTE) system. Alternatively, the sending device may be a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN) scenario. Alternatively, the sending device may be a base station device, for example, a <NUM> NodeB (<NUM>th generation NodeB, gNB) in a <NUM> network or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN). Alternatively, the sending device may be a wearable device or a vehicle-mounted device. Alternatively, the sending device may be a transmission reception point (Transmission Reception Point, TRP) or the like.

The receiving device in this embodiment of this application may be a terminal device. The terminal device may be a handheld device with a communication function, a wearable device, a computing device, another processing device connected to a wireless modem, or the like. For example, the terminal device may be a mobile station (Mobile Station, MS), a subscriber unit (subscriber unit), a cellular phone (cellular phone), a smartphone (smartphone), a wireless data card, a personal digital assistant (Personal Digital Assistant, PDA for short) computer, a tablet computer, a wireless modem (modem), a handheld device (handset device), a laptop computer (laptop computer), a machine type communication (Machine Type Communication, MTC) terminal, or the like.

For example, a structure of a receiving device in this embodiment of this application may be shown in <FIG>. A receiving device <NUM> includes a processor <NUM>, a memory <NUM>, and a transceiver <NUM>. The transceiver <NUM> may include a transmitter <NUM>, a receiver <NUM>, and an antenna <NUM>. The memory <NUM> may be configured to store data or instructions. The processor <NUM> may be configured to execute the instructions stored in the memory <NUM>, or perform steps of a HARQ process disabling method performed by the receiving device in this embodiment of this application. The receiver <NUM> may be configured to receive, by using the antenna <NUM>, data sent by a sending device, and the transmitter <NUM> may be configured to send data to the sending device by using the antenna <NUM>.

For example, a structure of a sending device in this embodiment of this application may be shown in <FIG>. A sending device <NUM> may include a processor <NUM>, a memory <NUM>, and a transceiver <NUM>. The transceiver <NUM> includes a transmitter <NUM>, a receiver <NUM>, and an antenna <NUM>. The memory <NUM> may be configured to store data or instructions. The processor <NUM> may be configured to execute the instructions stored in the memory <NUM>, or perform steps of a HARQ process disabling method performed by the receiving device in this embodiment of this application. The transmitter <NUM> may be configured to send data to a receiving device by using the antenna <NUM>, and the receiver <NUM> may be configured to receive, by using the antenna <NUM>, data sent by the receiving device.

In addition, when the receiving device is a terminal device, the terminal device may be a mobile phone, a tablet computer, a laptop computer, a television, a smart wear, another electronic device with a display, or the like. A specific form of the terminal is not limited in this embodiment of this application. A system that may be installed on the terminal may include iOS®, Android®, Microsoft®, Linux®, another operating system, or the like. This is not limited in this embodiment of this application.

For example, a terminal <NUM> installing the Android® operating system is used as an example. As shown in <FIG>, the terminal <NUM> may be logically divided into a hardware layer <NUM>, an operating system <NUM>, and an application layer <NUM>. The hardware layer <NUM> includes hardware resources such as an application processor <NUM>, a microcontroller unit <NUM>, a modem <NUM>, a Wi-Fi module <NUM>, a sensor <NUM>, a positioning module <NUM>, and a memory <NUM>. The application layer <NUM> includes one or more application programs, for example, an application program <NUM>. The application program <NUM> may be any type of application program, for example, a social application, an e-commerce application, or a browser. The operating system <NUM> is used as software middleware between the hardware layer <NUM> and the application layer <NUM>, and is a computer program for managing and controlling hardware and software resources.

In an embodiment, the operating system <NUM> includes a kernel <NUM>, a hardware abstraction layer (hardware abstraction layer, HAL) <NUM>, library and runtime (library and runtime) <NUM>, and a framework (framework) <NUM>. The kernel <NUM> is configured to provide an underlying system component and a service, for example, power management, memory management, thread management, or a hardware driver. The hardware driver includes a Wi-Fi driver, a sensor driver, a positioning module driver, and the like. The hardware abstraction layer <NUM> encapsulates a kernel driver, provides an interface for the framework <NUM>, and shields implementation details of a lower layer. The hardware abstraction layer <NUM> runs in user space, and the kernel driver runs in kernel space.

The library and runtime <NUM> is also referred to as a runtime library, and provides a library file and an execution environment required by an executable program during running. The library and runtime <NUM> includes Android runtime (Android Runtime, ART) <NUM>, a library <NUM>, and the like. The ART <NUM> is a virtual machine or a virtual machine instance that can convert bytecode of an application program into machine code. The library <NUM> is a program library that provides support for the executable program during running, and includes a browser engine (for example, webkit), a script execution engine (for example, a JavaScript engine), a graphics processing engine, and the like.

The framework <NUM> is configured to provide various basic common components and services, such as window management and location management, for an application program at the application layer <NUM>. The framework <NUM> may include a phone manager <NUM>, a resource manager <NUM>, a location manager <NUM>, and the like.

All functions of components in the operating system <NUM> described above may be implemented by the application processor <NUM> by executing programs stored in the memory <NUM>.

A person skilled in the art may understand that the terminal <NUM> may include fewer or more components than those shown in <FIG>. The terminal shown in <FIG> includes only components more related to a plurality of implementations disclosed in this embodiment of this application.

The terminal usually supports installation of a plurality of application programs (Application program, APP), such as a word processing application program, a phone application program, an email application program, an instant messaging application program, a photo management application program, a network browsing application program, a digital music player application program, and/or a digital video player application program.

The foregoing describes structures of the receiving device and the sending device in this application. The following describes a HARQ process disabling method in the embodiments of this application based on the receiving device or the sending device in <FIG>.

First, <FIG> is a schematic flowchart of a HARQ process disabling method according to an embodiment of this application.

<NUM>: A receiving device obtains indication data.

First, the receiving device obtains the indication data, where the indication data is used to indicate whether to disable a HARQ process. The indication data may be sent by a sending device, or may be stored in the receiving device.

Specifically, the indication data may include at least one of a network identifier number, first downlink control information (Downlink Control Information, DCI), or a broadcast message. The network identifier may be a network identifier corresponding to the receiving device. For example, if the receiving device is a mobile phone, the network identifier may be a subscriber identity module (Subscriber Identity Module, SIM) card of the mobile phone, a public land mobile network (Public Land Mobile Network, PLMN) number corresponding to a SIM card, or may be a network identifier allocated to the receiving device. The first DCI may be generated and sent by the sending device. The broadcast message may be a message broadcast by the sending device to all receiving devices that access the sending device. In addition, in this application, the indication data may be a type of data, for example, a broadcast message or DCI, or may be at least two pieces of data combined to indicate the receiving device to disable the HARQ process. For example, the broadcast message and the first DCI may simultaneously indicate the receiving device to disable the HARQ process, and only after receiving the broadcast message and the first DCI, the receiving device determines to disable the HARQ process. This improves transmission reliability.

In addition, if the indication data is stored in the receiving device, the receiving device may directly read the indication data. If the indication data is sent by the sending device, before the receiving device receives the indication data, the sending device further needs to determine whether to disable the HARQ process. Specifically, after the receiving device accesses the sending device, the sending device may determine whether to disable the HARQ process. Usually, the sending device may obtain HARQ process information corresponding to the receiving device. The sending device may obtain data related to the receiving device from the sending device or from a server, and then obtain the HARQ process information of the receiving device from the data related to the receiving device. The HARQ process information may include a quantity of HARQ processes, a time domain resource or a frequency domain resource corresponding to each HARQ process, and the like. After obtaining the HARQ process information corresponding to the receiving device, the sending device determines whether the HARQ process information meets a second preset condition. If the HARQ process information meets the second preset condition, the sending device may determine to disable the HARQ process, that is, not to enable a HARQ mechanism, and send, to the receiving device, the indication data indicating to disable the HARQ process. After receiving the indication data, the receiving device may determine, based on the indication data, whether to disable the HARQ process, or not to enable the HARQ process if the HARQ process is not enabled. Therefore, when the indication data is stored in the receiving device, the receiving device may directly determine, based on the indication data stored in the receiving device, whether to disable the HARQ process. This prevents the HARQ process from occupying excessively large storage space. If the indication data is sent by the sending device, the sending device may determine, based on an actual situation of the receiving device, whether to disable the HARQ process. This may implement dynamic adjustment of a HARQ of the receiving device, and prevent the HARQ process from occupying excessively large storage space in the receiving device.

In a specific application scenario, in a HARQ with soft combination, a data packet that is incorrectly received is stored in a buffer memory, and is combined with a subsequently retransmitted data packet to obtain a combined data packet, and then a decoding operation by using error correction code is performed on the combined data packet. If the decoding operation fails, retransmission is requested. Decoding a combined packet is more reliable than decoding only retransmitted data. However, when the HARQ mechanism is used, buffer space is required to store a data packet that is incorrectly received, and perform subsequent soft combination and decoding. Generally, a size of the buffer space is related to the quantity of HARQ processes, and a larger quantity of HARQ processes indicates larger required buffer space. For example, in an NR system, a quantity of supported HARQ processes is <NUM>, and in a non-terrestrial network (Non-Terrestrial Network, NTN) system, a quantity of supported HARQ processes is larger. For another example, for the geostationary orbit (Geostationary orbit, GEO), to make data occupy an entire air interface, when an SCS is equal to <NUM>, a quantity of required HARQ processes is about <NUM>, which is <NUM> times that of the NR system, and required storage space is also <NUM> times that of the NR system. Therefore, this occupies larger storage space in the receiving device. Therefore, in this embodiment of this application, the receiving device may disable the HARQ process based on the indication data. This prevents the HARQ process from occupying excessively large storage space in the receiving device.

<NUM>: If the receiving device determines that the indication data indicates to disable the HARQ process, the receiving device disables the HARQ process.

After obtaining the indication data, the receiving device determines, according to a preset rule, whether the indication data indicates to disable the HARQ process. If the receiving device determines that the indication data indicates to disable the HARQ process, the receiving device disables the HARQ process.

Specifically, the receiving device may determine, based on a preset correspondence, whether the indication data indicates to disable the HARQ process. If the indication data indicates to disable the HARQ process, the receiving device may disable the HARQ process, and not enable the HARQ mechanism.

It should be noted that the receiving device in this embodiment or the following embodiments of this application disables the HARQ process, that is, does not enable the HARQ mechanism. For example, when accessing a network, the receiving device may determine to disable the HARQ process, and when performing data transmission, the receiving device may perform data transmission only once without performing retransmission.

In addition, in an optional implementation of this application, after receiving the indication data, the receiving device may determine to disable the HARQ process, and not need to read specific content of the indication data. For example, if the sending device and the receiving device have agreed on a rule, in any pre-agreed SIB or between a SIB <NUM> and a SIB <NUM>, provided that the receiving device receives the indication data, the receiving device may determine to disable the HARQ process without reading specific content of the indication data. This improves efficiency of disabling the HARQ process by the receiving device.

Optionally, in another implementation, the receiving device may further clearly determine, based on the indication data, whether to disable the HARQ process. The receiving device may disable the HARQ process based on the indication data. This prevents the HARQ process from occupying excessively large buffer space. In addition, optionally, after the HARQ process is disabled, subsequent data related to the HARQ process may be reused. This improves transmitted data utilization, saves network resources, and enhances system performance.

In this application, the indication data may be data in a plurality of scenarios, for example, data stored in the receiving device, or data sent by the sending device. The following describes the different scenarios.

First, when the indication data is a network identifier number, a specific schematic flowchart may be shown in <FIG>, and includes the following steps.

<NUM>: Read a network identifier number.

A receiving device reads the network identifier number, where the network identifier number may be an identifier number allocated to the receiving device, a PLMN number stored in a SIM card of the receiving device, a PLMN number received by the receiving device, or the like.

For example, before accessing a network, the receiving device first performs network searching, and may select, based on operator-related data stored in the SIM card, a network to access. Each operator may correspond to a different PLMN number or another network identifier number, and the receiving device may determine, based on a PLMN number of an accessible satellite or another network identifier number sent by a device of the operator, whether to disable a HARQ process.

<NUM>: Determine, based on a preset mapping relationship, whether the network identifier number indicates to disable the HARQ process, and if the network identifier number indicates to disable the HARQ process, perform step <NUM>, or if the network identifier number indicates not to disable the HARQ process, perform step <NUM>.

After obtaining the network identifier number, the receiving device determines, based on the network identifier number and the preset mapping relationship, whether the network identifier number indicates to disable the HARQ process. If the receiving device determines that the network identifier number indicates to disable the HARQ process, the receiving device disables the HARQ process, that is, performs step <NUM>. If the network identifier number indicates not to disable the HARQ process, the receiving device performs another step, that is, performs step <NUM>. The preset mapping relationship may be set in advance. When the network identifier number is allocated to the receiving device, the SIM card, the operator, or the like, correspondingly it may be determined whether to disable the HARQ process, and the preset mapping relationship is stored in the receiving device, so that the receiving device may determine, based on the preset mapping relationship, whether the read network identifier number indicates to disable the HARQ process.

Usually, if the receiving device includes a SIM card, the network identifier number may be a PLMN number, and the PLMN number may correspond to an operator corresponding to the SIM card. For example, a PLMN number of China Mobile includes <NUM>, a PLMN number of China Unicom includes <NUM>, and PLMN numbers of an existing satellite system include <NUM>, <NUM>, and the like. A PLMN number may further be allocated to each satellite of an operator. For example, a PLMN number may be configured for each of a geostationary orbit (Geostationary orbit, GEO) satellite, a medium earth orbit (Medium Earth Orbit, MEO) satellite, or a low earth orbit (Low Earth Orbit, LEO) satellite. Specifically, for example, if the receiving device is a mobile phone, after the mobile phone is powered on and before the mobile phone accesses a network, the mobile phone performs network searching, and may read a PLMN number stored in a SIM card. Then, the mobile phone determines, based on a preset mapping relationship, whether the PLMN number corresponds to disabling the HARQ process. Alternatively, when accessing a network, the mobile phone receives a PLMN number sent by an operator device, and determines, based on the PLMN number and a preset mapping relationship, whether to disable the HARQ process.

It should be understood that the preset mapping relationship may be set by a sending device, or may be determined by an operator. Specifically, adjustment may be performed based on an actual application scenario. This is not limited in this application.

For example, the preset mapping relationship between the network identifier number and the HARQ process may be represented by using a mapping relationship table as shown in Table <NUM>.

After reading the PLMN number, the receiving device may search preset mapping relationships based on the PLMN number for a mapping relationship corresponding to the PLMN number. For example, if the receiving device reads that the PLMN number is <NUM>, the receiving device may determine, according to the mapping relationship table, that the PLMN number indicates to disable the HARQ process.

For example, in a specific application scenario, the receiving device is a terminal device, and a plurality of PLMN numbers are stored in a SIM card of the terminal device. When the terminal device is powered on and performs network searching, the terminal device receives a master information block (master information block, MIB) message. The MIB message may carry access information of a terrestrial network, or may carry access information of an NTN system, where the access information of the NTN system may include a PLMN number. When the MIB message carries the PLMN number, if the PLMN number is an accessible PLMN number stored in the terminal device, the terminal device may determine that the terminal device can access the NTN system. In this case, the terminal device may determine, based on the PLMN number and a preset mapping relationship, whether the PLMN number corresponds to disabling the HARQ process. If the PLMN number corresponds to disabling the HARQ process, the terminal device may directly determine to disable the HARQ process. In addition, if all networks that can be accessed by the terminal device are NTN systems, the terminal device may directly determine, based on a preset mapping relationship, whether to disable the HARQ process.

After determining that the network identifier number indicates to disable the HARQ process, the receiving device keeps the HARQ process in a disabled status, that is, does not enable a HARQ mechanism.

In addition, if the receiving device determines that the network identifier number does not indicate to disable the HARQ process, the receiving device may perform another step, for example, enabling the HARQ process, disabling the entire HARQ process or a part of the HARQ process, or enabling an ARQ mechanism after disabling the HARQ process. Specifically, adjustment may be performed based on an actual application scenario.

Therefore, in this embodiment of this application, the receiving device may read the network identifier number, and determine, based on the preset mapping relationship, whether the network identifier number indicates to disable the HARQ process, so that the receiving device may clearly determine, based on the network identifier number, whether to disable the HARQ process. This prevents the HARQ process from occupying excessively large buffer space. In addition, after the HARQ process is disabled, subsequent data related to the HARQ process may be reused. This improves transmitted data utilization, saves network resources, and enhances system performance.

Optionally, when the indication data is a network identifier number, a specific schematic flowchart may be shown in <FIG>, and may include the following steps.

<NUM>: A sending device obtains HARQ process information corresponding to a receiving device.

After the receiving device accesses the sending device, the sending device may determine whether to disable a HARQ process. Usually, the sending device may obtain HARQ process information corresponding to the receiving device.

Specifically, the sending device may obtain data related to the receiving device from the sending device or from a server, and then obtain the HARQ process information of the receiving device from the data related to the receiving device. The HARQ process information includes a quantity of HARQ processes, a time domain resource or a frequency domain resource corresponding to each HARQ process, and the like.

<NUM>: The sending device determines whether to disable the HARQ process.

After obtaining the HARQ process information corresponding to the receiving device, the sending device determines whether the HARQ process information meets a second preset condition. If the HARQ process information meets the second preset condition, the sending device may determine to disable the HARQ process.

Specifically, the second preset condition may be that the quantity of HARQ processes is greater than a threshold, or that buffer space in the receiving device is less than a threshold. The threshold may be a preset value, maximum storage space occupied by the HARQ process, or indication data that is included in the HARQ process information and that directly indicates to disable the HARQ process. Specifically, adjustment may be performed based on an actual application scenario. This is not limited in this application.

For example, in an actual application scenario such as an NR system, when a HARQ mechanism is enabled for communication between sending devices, specific buffer space is needed in the receiving device to stored received data for subsequent soft combination and decoding. A size of the buffer space is related to the quantity of HARQ processes, and the quantity of HARQ processes is <MAT>. RTT represents round trip time (Round Trip Time, RTT) between the sending device and the receiving device, Tsf represents a length of a subframe for transmitting data, Tue represents processing time of UE, Tack represents transmission time of an acknowledgment (Acknowledgment, ACK) or a negative acknowledgment (Negative Acknowledgment, NACK), Tnb represents processing time of a gNB, and Mrx = NHARQNtrMp represents storage space required by the receiving device, where Ntr represents a maximum quantity of transmission times including retransmission, and Mp is a size of one packet. Therefore, a size of storage space required by the receiving device may be determined based on the quantity of HARQ processes. Usually, in the NR system, a quantity of supported HARQ processes is <NUM>. Because the RTT in the NR system is relatively small, the quantity of HARQ processes mainly depends on the processing time of the UE and the processing time of the gNB. In an NTN system, large RTT leads to a spiraling quantity of HARQ processes. For example, RTT of a bentpipe satellite of the GEO is equal to <NUM>, and therefore a quantity of required HARQ processes is about <NUM> (in a case in which an SCS is equal to <NUM>). If a quantity of retransmission times in the NTN system is the same as that in the NR system, storage space required by a receive end in the NTN is <NUM>/<NUM> = <NUM> times that required in the existing NR system. Therefore, the HARQ process occupies very large storage space in the receiving device. Therefore, in this embodiment of this application, the sending device may determine to disable the HARQ process, or the receiving device determines, based on a network identifier number stored in the receiving device, to disable the HARQ process. This reduces storage space in the receiving device that is occupied by the HARQ process.

In addition, when an NDI indicates newly transmitted data, buffered data may be cleared, but a bit related to the HARQ process cannot be reused as other data. In comparison with using the NDI to indicate newly transmitted or retransmitted data, in this embodiment of this application, optionally, after it is determined that the HARQ process is disabled, a subsequent bit related to the HARQ process may be reused to transmit reused data. Therefore, in this embodiment of this application, the sending device may determine to disable the HARQ, or the receiving device determines, based on the network identifier number, to disable the HARQ process. This may reduce storage space occupied by the HARQ process, improve a data throughput, and improve network resource utilization.

<NUM>: The sending device generates a broadcast message, and sends the broadcast message to the receiving device.

After determining to disable the HARQ process corresponding to the receiving device, the sending device generates the broadcast message used to indicate to disable the HARQ process, where the broadcast message meets a preset condition. The preset condition may be that a value of a first preset bit of the broadcast message is a first preset value, a value lower than a first value or higher than a second value, or the like. Specifically, adjustment may be performed based on an actual application scenario.

For example, the preset condition may be that the value of the first preset bit in the broadcast message is the first preset value, where the first preset value may be <NUM>, <NUM>, or the like as shown in Table <NUM>.

When the value of the first preset bit is <NUM>, the broadcast message indicates to disable the HARQ process. When the value of the first preset bit is <NUM>, the broadcast message indicates to enable the HARQ process. Alternatively, the first preset bit is shown in Table <NUM>.

When the value of the first preset bit is <NUM>, the broadcast message indicates to disable the HARQ process. When the value of the first preset bit is <NUM>, the broadcast message indicates to enable the HARQ process.

For example, if the receiving device is a terminal device, the sending device may be a base station. Usually, when the terminal device accesses the base station, the base station may send a broadcast message to the terminal device that accesses the base station. The broadcast message may be a system information block (System Information Block, SIB) message, and the SIB message may include a SIB <NUM>, a SIB <NUM>, a SIB <NUM>, and the like. Different SIB messages can carry different data. The broadcast message in this embodiment of this application may be the SIB <NUM>, the SIB <NUM>, the SIB <NUM>, or the like. For example, usually, a plurality of different SIBs are defined in the NR system, each SIB carries a different type of data, and specific content corresponding to each SIB is different from that in an LTE system. For example, in the NR, the SIB <NUM> provides initial access information of user equipment (User Equipment, UE), and in the LTE system, initial information is provided by the SIB <NUM>. In addition, in the NR, the SIB <NUM> is periodically broadcast at an interval of <NUM>, and other SIBs may be transmitted in a plurality of manners: (<NUM>) transmission is still performed periodically at a fixed interval in a manner same as that in the LTE; (<NUM>) after the UE accesses a network, transmission is performed based on a request of the UE, to reduce signaling overheads. However, because an MSG <NUM> (message <NUM>) in random access supports a HARQ function, when performing random access, the UE needs to determine to disable or enable the HARQ process. Therefore, the indication data may be a SIB message. For example, the indication data may be a SIB <NUM> message. Alternatively, it may be understood that the SIB <NUM> message carries data indicating to disable or enable the HARQ process. The indication data may be added to the SIB <NUM> message in a plurality of manners. For example, one-bit information may be added to a cellAccessRelatedInfo field of the SIB <NUM> message, and is used to indicate to enable or disable the HARQ process. Alternatively, a field is added to the SIB <NUM> message, for example, the SIB <NUM> message may be named HARQDisableIndicator, and a specific range of HARQDisableIndicator may be (<NUM>, <NUM>).

<NUM>: The receiving device parses the broadcast message.

After receiving the broadcast message, the receiving device parses the broadcast message, to obtain data carried in the broadcast message.

Usually, the broadcast message received by the receiving device is data modulated by the sending device. After receiving the broadcast message, the receiving device may first perform demodulation, decoding, checking, or the like on the broadcast message, and then read data carried in the broadcast message.

<NUM>: If the broadcast message indicates to disable the HARQ process, the receiving device disables the HARQ process.

After obtaining the data carried in the broadcast message, the receiving device may read the first preset bit in the broadcast message, and determine, based on the first preset bit, whether to indicate to disable the HARQ process.

Specifically, it may be determined that whether the value of the first preset bit in the broadcast message is the first preset value. If the value of the first preset bit is the first preset value, the receiving device determines that the value of the first preset bit indicates to disable the HARQ process, and the receiving device disables the HARQ process.

Therefore, in this embodiment of this application, after determining to disable the HARQ process, the sending device may notify, by using the broadcast message, the receiving device to disable the HARQ process, so that the receiving device disables the HARQ process. This prevents the HARQ process from occupying excessively large buffer space. In addition, after the HARQ process is disabled, subsequent data related to the HARQ process may be reused. This improves transmitted data utilization, saves network resources, and enhances system performance.

The indication data may be a broadcast message, or DCI. When the indication data is downlink control information, a specific schematic flowchart may be shown in <FIG>, and may include the following steps.

It should be noted that step <NUM> and step <NUM> in this embodiment of this application are similar to step <NUM> and step <NUM> in <FIG>.

<NUM>: The sending device generates first DCI.

After determining to disable the HARQ process of the receiving device, the sending device may notify the receiving device by using DCI, that is, the sending device may generate the first DCI.

The DCI may indicate to disable the HARQ process in a plurality of manners, including adding data of a preset length to the first DCI, adjusting a field length related to the HARQ in the DCI, and the like. For example, the following specifically describes the two manners.

A value of the second preset bit in the first DCI is set to the second preset value. The second preset bit is a bit corresponding to the HARQ process in the first DCI, or a newly added bit. When the second preset bit is a newly added bit in the first DCI, data of a preset length may be added to the first DCI, and the data of a preset length is used to indicate whether to disable the HARQ process. When the second preset bit is a bit corresponding to the HARQ process in the first DCI, the second preset bit may include a bit related to an NDI, a quantity of HARQ processes, or the like.

For example, one-bit information may be added to the first DCI to indicate to enable or disable the HARQ. DCI_0 is used as an example. A one-bit HARQ status indication may be added to DCI_0. Specifically, data included in DCI_0 after the one-bit information is added may be shown in Table <NUM>.

As shown in Table <NUM>, one bit may be added to a last bit of DCI_0, to indicate whether to disable the HARQ. It is clear that in addition to adding one bit to a last bit of the DCI, bit data of a preset length may be added to another location of the DCI. Specifically, adjustment may be performed based on an actual application scenario. More specifically, "<NUM>" may indicate to disable the HARQ process, and " <NUM>" indicates to enable the HARQ process, or "<NUM>" indicates to disable the HARQ process, and "<NUM>" indicates to enable the HARQ process.

Alternatively, one bit may not be added to DCI_0, and at least one bit in data occupied by the NDI, the RV, or the quantity of HARQ processes may be directly set to the second preset value. For example, seven bits occupied by the NDI, the RV, and the quantity of HARQ processes may be all set to <NUM>, that is, "<NUM>", or all set to <NUM>, that is, "<NUM>", or set to preset values according to a rule agreed with the receiving device. Specifically, adjustment may be performed based on an actual application scenario. This manner (<NUM>) does not fall within the scope of the claims.

A field length related to the HARQ in the DCI is adjusted. This manner (<NUM>) falls within the scope of the claims.

The DCI usually carries data related to the HARQ, for example, the NDI, the RV, and the quantity of HARQ processes in Table <NUM>. The field length of the data related to the HARQ may be adjusted to indicate to disable or enable the HARQ process.

For example, as shown in Table <NUM>, the field length of the data related to the HARQ is <NUM> bits. When the sending device determines to disable the HARQ process, the <NUM>-bit data may be reused as other data, and a field length of the reused data is k, where k may be greater than <NUM> or less than <NUM>. When detecting that the field length of the data related to the HARQ is <NUM>, the receiving device may determine to disable the HARQ process or not to enable the HARQ process.

<NUM>: The receiving device parses the first DCI.

After receiving the first DCI, the receiving device may parse the first DCI, to extract information carried in the first DCI.

Usually, the first DCI received by the receiving device is data modulated by the sending device. After receiving the first DCI, the receiving device may first perform demodulation, decoding, checking, or the like on the first DCI, and then extract data carried in the first DCI.

<NUM>: If the first DCI meets a first preset condition, the receiving device disables the HARQ process.

After obtaining the information carried in the first DCI, the receiving device processes the carried information. The first DCI may include data related to the HARQ process.

The receiving device determines whether the received first DCI meets the first preset condition. The first preset condition is that the field length that corresponds to the HARQ process and that is included in the first DCI is a preset length. After determining that the first DCI meets the first preset condition, the receiving device determines to disable the HARQ process.

After the receiving device disables the HARQ process, the data related to the HARQ in the DCI may be reused as other data. In addition, if the field length corresponding to the HARQ process in the DCI is used to indicate whether to disable the HARQ process, the field length corresponding to the HARQ process in the first DCI may be reused as other data if it is determined to disable the HARQ process. This improves network resource utilization. Alternatively, the field length may not be reused as other data to reduce signaling overheads.

Therefore, in this embodiment of this application, the DCI may indicate whether to disable the HARQ process. After determining that the first DCI meets the first preset condition, the receiving device determines to disable the HARQ process. Therefore, the receiving device may accurately determine, based on the received DCI, whether to disable the HARQ process. This prevents the HARQ process from occupying excessively large buffer space. In addition, after the HARQ process is disabled, subsequent data related to the HARQ process may be reused. This improves transmitted data utilization, saves network resources, and enhances system performance.

When the indication data is CRC data, a specific schematic flowchart may be shown in <FIG>, and may include the following steps.

<NUM>: A sending device obtains a HARQ process corresponding to a receiving device.

<NUM>: The sending device scrambles CRC data.

After determining to disable the HARQ process, the sending device scrambles the CRC data by using a random access radio network temporary identifier (random access-radio network temporary identifier, RA-RNTI).

Specifically, the CRC data may be CRC of any data sent by the sending device to the receiving device, or may be CRC of preset data, or the like. Specifically, adjustment may be performed based on an actual application scenario. For example, in an NR system, because an MSG <NUM> in random access supports a HARQ function, when a terminal device randomly accesses abase station, and before the MSG <NUM> is sent, the terminal device needs to determine whether to disable or enable the HARQ process. Therefore, the CRC data may be CRC of any message before the MSG <NUM> is sent. For example, the CRC data may be a DCI message, or may be a SIB message.

In addition, the CRC data may be scrambled by using the RA-RNTI in a plurality of manners. For example, when determining to disable the HARQ process, the sending device may scramble data of a third preset bit in the CRC data by using the RA-RNTI. Alternatively, after processing the RA-RNTI to obtain offset data, the sending device scrambles the CRC data by using the offset data. More specifically, that the sending device processes the RA-RNTI may be as follows: The sending device may adjust a sequence of the RA-RNTI according to a preset rule, to obtain the offset data, and scrambles the CRC data based on the offset data. Alternatively, the sending device may add a preset offset value to the RA-RNTI, to obtain the offset data, and scrambles the CRC data based on the offset data. Alternatively, the sending device may directly perform shifting on the RNTI, or add data of a preset length to the RA-RNTI. Alternatively, the sending device may map the RA-RNTI according to a preset mapping rule, to obtain the offset data. Specifically, adjustment may be performed based on an actual application scenario.

When determining to disable the HARQ process, the sending device may scramble the data of the third preset bit in the CRC data by using the RA-RNTI. For example, usually, in the NR system, if a length of the CRC is <NUM> bits, and a length of the RA-RNTI is <NUM> bits, the RA-RNTI may be scrambled to last <NUM> bits of the CRC, that is, a <NUM>th bit to a <NUM>th bit. In this embodiment of this application, the RA-RNTI may be scrambled to different locations, to indicate different information. In this embodiment of this application, when determining not to disable the HARQ process, the sending device may scramble the RA-RNTI to last <NUM> bits of the CRC, as shown in <FIG>. When determining to disable the HARQ process, the sending device may scramble the RA-RNTI to locations different from the last <NUM> bits in the CRC. For example, as shown in <FIG>, the sending device may scramble the RA-RNTI to <NUM>th to <NUM>rd bits of the CRC or other locations, to indicate the receiving device to disable the HARQ process. Usually, to reduce decoding complexity of the receiving device, when determining to disable the HARQ process, the sending device may scramble the RA-RNTI to the <NUM>th to <NUM>rd bits of the CRC, that is, one bit forward compared to <NUM>th to <NUM>th bits in a case in which the sending device determines not to disable the HARQ process.

It is assumed that the sending device adjusts the sequence of the RA-RNTI according to the preset rule, to obtain an RA-RNTI whose sequence is adjusted, and scrambles the CRC data based on the RA-RNTI whose sequence is adjusted. For example, if the RA-RNTI has <NUM> bits in total, the <NUM> bits may be divided into first m bits and last n bits, where m + n = <NUM>, and both m and n are positive integers. For example, when m and n are both equal to <NUM>, if the sending device determines to disable the HARQ process, the sending device may exchange a sequence of the m bits with the n bits, that is, exchange m+n bits into n+m bits, as shown in <FIG>, and scramble the CRC data by using an RA-RNTI whose sequence is adjusted, to indicate the receiving device to disable the HARQ process. If the sending device determines not to disable the HARQ process, the sending device may continue to scramble the CRC data by using the RA-RNTI whose sequence is m+n, as shown in <FIG>, to indicate the receiving device not to disable the HARQ process. Alternatively, it is clear that the CRC may be scrambled by using the RA-RNTI whose sequence is m+n, to indicate to disable the HARQ process, and be scrambled by using the RA-RNTI whose sequence is n+m, to indicate not to disable the HARQ process.

When the sending device adds the preset offset value to the RA-RNTI, to obtain the offset data, and scrambles the CRC data based on the offset data, for example, in the NR system, a gNB calculates the RA-RNTI based on a time-frequency location of a received MSG <NUM> (message <NUM>) and scrambles the CRC data. An offset operation may be performed on the RA-RNTI to some extent, that is, the CRC data is scrambled by using an RA-RNTI to which k is added, where k is a positive integer greater than <NUM>. To be specific, k is the preset offset value, as shown in <FIG>. Then, when the sending device generates an MSG <NUM> (message <NUM>), if the sending device determines to disable the HARQ process, the sending device may scramble the CRC data by using the RA-RNTI to which k is added, to indicate the receiving device to disable the HARQ process. If the sending device determines not to disable the HARQ process, the sending device may scramble the CRC by using the RA-RNTI, to indicate the receiving device not to disable the HARQ process. Alternatively, it is clear that the CRC may be scrambled by using the RA-RNTI to which k is added, to indicate the receiving device not to disable the HARQ process. Alternatively, the CRC may be scrambled by using the RA-RNTI, to indicate the receiving device to disable the HARQ process.

In addition, the sending device may map the RA-RNTI according to the preset mapping rule, to obtain the offset data, where the offset data includes or implicitly includes the RA-RNTI. The preset mapping rule may be that the RA-RNTI is mapped to a value different from the RA-RNTI. For example, the preset mapping rule may be that two RA-RNTIs with similar values are mapped to two values that differ greatly, to reduce a false detection probability of received data.

Specifically, a process of scrambling the CRC data may be as follows: After determining data that is used for scrambling the CRC, for example, the data may be an RA-RNTI, an RA-RNTI whose sequence is n+m, an RA-RNTI to which k is added, or the like, a scrambling polynomial is determined. Then, an exclusive OR operation is performed on the scrambling polynomial and data that needs to be scrambled in the CRC data, to obtain scrambled CRC data. Correspondingly, when receiving the CRC data, the receiving device needs to descramble the CRC data, that is, perform data recovery on the CRC by using the scrambling polynomial.

Therefore, in this embodiment of this application, the CRC may be scrambled in the plurality of manners. The CRC indicates the receiving device to disable or not to disable the HARQ process, so that the receiving device may accurately determine, based on the scrambled CRC, whether to disable the HARQ process.

<NUM>: The receiving device descrambles the CRC data based on the RA-RNTI.

After receiving the CRC data in data sent by the sending device, the receiving device descrambles the CRC data by using the RA-RNTI. The receiving device may descramble the received CRC data in a manner corresponding to a scrambling manner used by the sending device.

Specifically, the data of the third preset bit of the CRC may be descrambled by using the RA-RNTI, or the CRC data may be descrambled by using the RA-RNTI whose sequence is adjusted, or the CRC data may be descrambled by using the RA-RNTI whose preset offset value is shifted, or the RA-RNTI may be mapped according to the preset mapping rule to obtain the offset data. Specifically, adjustment may be performed based on an actual application scenario.

<NUM>: If a descrambling result is that descrambling succeeds, the receiving device disables the HARQ process.

After obtaining the CRC data sent by the HARQ process, the receiving device descrambles the CRC data based on the RA-RNTI. If descrambling succeeds, it is determined that the CRC data indicates to disable the HARQ process, and the receiving device disables the HARQ process based on the indication of the CRC.

Specifically, if the sending device scrambles the data of the third preset bit or data of another bit in the CRC data by using the RA-RNTI, after obtaining the CRC data, the receiving device descrambles the data of the third preset bit in the CRC data by using the RA-RNTI. If descrambling succeeds, it may be determined that the CRC data indicates to disable the HARQ process. For example, in the NR system, if a length of the CRC is <NUM> bits, a length of the RA-RNTI is <NUM> bits. Last <NUM> bits of the CRC, that is, an <NUM>th bit to a <NUM>th bit, may be descrambled by using the RA-RNTI. If descrambling succeeds, it is determined that the CRC indicates not to disable the HARQ process. Alternatively, if descrambling fails, <NUM>th to <NUM>rd bits may be descrambled, and if descrambling succeeds, it may be determined that the CRC indicates to disable the HARQ process. Alternatively, it is clear that last <NUM> bits of the CRC, that is, an <NUM>th bit to a <NUM>th bit, may be descrambled by using the RA-RNTI. If descrambling succeeds, it is determined that the CRC indicates to disable the HARQ process. Alternatively, if descrambling fails, <NUM>th to <NUM>rd bits may be descrambled, and if descrambling succeeds, it may be determined that the CRC indicates not to disable the HARQ process. Specifically, how to indicate to disable the HARQ process or a sequence of using different data to descramble may be adjusted based on an actual application scenario.

If the sending device adjusts the sequence of the RA-RNTI according to the preset rule, to obtain the RA-RNTI whose sequence is adjusted, namely, the offset data, and scrambles the CRC data based on the RA-RNTI whose sequence is adjusted, the receiving device may descramble the CRC data by using the RA-RNTI and the RA-RNTI whose sequence is adjusted. If descrambling the CRC data by using the RA-RNTI succeeds, it may be determined that the CRC data indicates not to disable the HARQ process. If descrambling the CRC data by using the RA-RNTI whose sequence is adjusted succeeds, it may be determined that the CRC data indicates to disable the HARQ process. Alternatively, it is clear that if descrambling the CRC data by using the RA-RNTI succeeds, it may be determined that the CRC data indicates to disable the HARQ process. If descrambling the CRC data by using the RA-RNTI whose sequence is adjusted succeeds, it may be determined that the CRC data indicates not to disable the HARQ process. For example, if the RA-RNTI has <NUM> bits, and the <NUM> bits may be divided into first m bits and last n bits, where m + n = <NUM>, and both m and n are positive integers, the CRC may be descrambled by using the RA-RNTI whose sequence is m+n. If descrambling succeeds, it may be determined that the CRC indicates not to disable the HARQ process. If descrambling fails, the CRC may be descrambled by using the RA-RNTI whose sequence is n+m; and if descrambling succeeds, it may be determined that the CRC indicates to disable the HARQ process. Alternatively, the CRC may be descrambled by using the RA-RNTI whose sequence is m+n. If descrambling succeeds, it may be determined that the CRC indicates to disable the HARQ process. If descrambling fails, the CRC may be descrambled by using the RA-RNTI whose sequence is n+m; and if descrambling succeeds, it may be determined that the CRC indicates not to disable the HARQ process. Specifically, how to indicate to disable the HARQ process or a sequence of using different data to descramble may be adjusted based on an actual application scenario.

If the sending device shifts the RA-RNTI by the preset offset value, to obtain the offset data, and scrambles the CRC data based on the offset data, after obtaining the CRC data, the receiving device may descramble the CRC data by using the RA-RNTI or the offset data. Specifically, the CRC data may be descrambled by using the RA-RNTI. If descrambling succeeds, it is determined that the CRC data indicates to disable the HARQ process. If descrambling fails, the CRC data is continued to be descrambled by using the offset data; and if descrambling succeeds, it may be determined that the CRC indicates not to disable the HARQ process. Alternatively, it is clear that the CRC data may be descrambled by using the RA-RNTI. If descrambling succeeds, it is determined that the CRC data indicates not to disable the HARQ process. If descrambling fails, the CRC data is continued to be descrambled by using the offset data; and if descrambling succeeds, it may be determined that the CRC indicates to disable the HARQ process. Specifically, how to indicate to disable the HARQ process or a sequence of using different data to descramble may be adjusted based on an actual application scenario.

Therefore, in this embodiment of this application, the CRC data may be scrambled by using RA-RNTIs in different forms, and whether the CRC data indicates to disable the HARQ process can be accurately determined. This may prevent the HARQ process from occupying excessively large buffer space. In addition, after the HARQ process is disabled, subsequent data related to the HARQ process may be reused. This improves transmitted data utilization, saves network resources, and enhances system performance.

The foregoing specifically describes a specific procedure in which the receiving device determines to disable the HARQ process in this embodiment of this application. After the receiving device disables the HARQ process, based on any implementation in <FIG>, data corresponding to the HARQ process in subsequent DCI may continue to be reused. Specifically, as shown in <FIG>, the method may include the following steps.

<NUM>: The sending device sends indication data.

After determining whether to disable the HARQ process, the sending device generates indication data used to indicate whether to disable the HARQ process. The indication data may be specifically a network identifier number, first DCI, a broadcast message, CRC data, or the like. For details, refer to steps in any one of the foregoing embodiments in <FIG>.

<NUM>: The receiving device disables the HARQ process.

After receiving the indication data used to indicate to disable the HARQ process, the receiving device may determine, based on the indication data, to disable the HARQ process. Disabling the HARQ process includes not enabling the HARQ process, disabling the entire running HARQ process or a part of the running HARQ process, or the like.

In addition, after determining to disable the HARQ, the receiving device may enable an ARQ mechanism to perform data transmission. In the ARQ mechanism, when data received by the receiving device fails to be decoded or a relatively large amount of data is lost, the receiving device may directly discard the data, and notify the sending device of retransmitting data, without occupying excessively large buffer space. This may improve a throughput between the receiving device and the sending device.

<NUM>: The sending device generates second DCI.

After determining to disable the HARQ process, and notifying the receiving device of disabling the HARQ process, the sending device may generate the second DCI, where a fourth preset bit corresponding to the HARQ process in the second DCI may be used to transmit reused data after the HARQ process is disabled. The fourth preset bit is a vacated bit after the HARQ process is disabled, that is, a bit related to the HARQ process when the HARQ process is not disabled. To be specific, data related to the HARQ process in the second DCI may be reused as other data. The second DCI is DCI data obtained after the sending device determines to disable the HARQ process and notifies the receiving device to disable the HARQ process.

For example, if the HARQ process is not disabled, DCI_0 may include an NDI, an RV, a quantity of HARQ processes, and the like that are related to the HARQ process. However, in this embodiment of this application, after the HARQ process is disabled, that is, after the sending device notifies the receiving device to disable the HARQ process, a HARQ mechanism is not enabled between the sending device and the receiving device. Therefore, when reading data related to the HARQ process in DCI_0, the receiving device does not use the data. However, in this embodiment of this application, data related to the HARQ in the DCI may be other reused data. The reused data may include one or more of over-the-top time of a satellite corresponding to the receiving device, a power adjustment step, an interleaving depth, and interruption duration of the satellite corresponding to the receiving device.

For example, the reused data may include the over-the-top time of the satellite corresponding to the receiving device. Usually, for a non-GEO satellite, different beams alternately reach the top to serve one UE. Therefore, a regular change occurs between the non-GEO satellite and the UE as the satellite moves. For example, <FIG> shows an over-the-top rule of one satellite. If the UE learns over-the-top information of the satellite, the UE may determine uplink transmission time, to improve transmission reliability and a throughput. For example, usually, to ensure that a series of uplink scheduling procedures, for example, the UE sends DCI, a scheduling request (Scheduling Request, SR), and a buffer status report (Buffer Status Report, BSR), or data is transmitted through a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH), occur at a moment when quality of the channel is relatively good, a gNB may notify the UE of next over-the-top time of the beam by using the second DCI after the HARQ process is disabled, so that the UE determines a moment of sending uplink data at next time. Therefore, in this embodiment of this application, in the second DCI, the data related to the HARQ process is replaced with the over-the-top information of the satellite corresponding to the UE, so that the UE can send the uplink data at a moment when quality of the channel is relatively good. This improves reliability of uplink data transmission and improves a network throughput.

For example, the reused data may further include the power adjustment step. Usually, a non-GEO satellite system differs significantly from a terrestrial system in NR. Only UE moves in the terrestrial system, but a satellite and UE move simultaneously in the non-GEO satellite system. For example, as shown in <FIG>, at a moment t0, the satellite is relatively close to the UE. At a moment t1, because the satellite moves quickly, a distance between the satellite and the UE changes greatly. However, when the distance between the satellite and the UE changes greatly, power for performing data transmission between the UE and the satellite also changes, and a change range is relatively large. In a scenario in which the change range of the power is relatively large, a larger power adjustment step is required to more rapidly adjust the transmission power between the UE and the satellite. Usually, in the existing NR system, the power control data occupies two-bit information, and only indicates four steps (-<NUM> dB, <NUM> dB, +<NUM> dB, and +<NUM> dB). However, in this embodiment of this application, because the data related to the HARQ process in the DCI may be reused, a length of the power control data may be increased, and more steps may be transmitted. For example, if two bits are added to the DCI, that is, four bits are used to transmit power control data, eight steps (-<NUM> dB, -<NUM> dB, - <NUM> dB, -<NUM> dB, <NUM> dB, +<NUM> dB, +<NUM> dB, and +<NUM> dB) may be indicated, so that a range of the power adjustment step is larger, and a power adjustment speed is faster. This improves data transmission efficiency between the UE and the satellite.

For example, the reused data may further include the interleaving depth. Usually, a delay of a GEO satellite is relatively large. When scheduling is performed, for an uplink direction, a channel quality indicator (Channel Quality Indicator, CQI) fed back by UE expires, or a determined modulation and coding scheme (Modulation and Coding Scheme, MCS) expires. For a downlink direction, an MCS expires. The foregoing expiration phenomena cause a mismatch between adaptive modulation and coding (Adaptive Modulation and Coding, AMC) and a channel, and an increase of a block error rate (Block Error Rate, BLER) of a communications system. However, in a power control method, only a change of a large granularity is tracked, and a change of a small granularity in the channel cannot be tracked effectively. Therefore, to overcome impact caused by the small granularity, symbol interleaving or subframe interleaving may be introduced, to average impact on the channel. For example, the symbol interleaving may be shown in <FIG>, and an arrangement sequence of symbols may be adjusted according to a preset rule. Alternatively, the subframe interleaving is shown in <FIG>, and a structure of subframes may be changed. The interleaving depth, as an adjustable parameter, may be adaptively changed based on a delay requirement or a channel condition. Interleaving is used to process data before transmission. This may overcome fading, reduce a data loss rate, and make it easier for the receiving device to recover data. Specifically, some or all of the data related to the HARQ process in the second DCI may be reused, to notify the UE of the interleaving depth. For example, two-bit data is reused as an interleaving depth, and a mapping relationship between bits and an interleaving depth may be shown in Table <NUM>.

<NUM> may indicate an interleaving depth of <NUM>, <NUM> indicates an interleaving depth of <NUM>, <NUM> indicates an interleaving depth of <NUM>, and <NUM> indicates an interleaving depth of <NUM>. Therefore, in this embodiment of this application, the data related to the HARQ process in the second DCI may be reused as the interleaving depth, so that the receiving device may determine an interleaving depth based on reused data included in the second DCI, and further perform de-interleaving on received interleaved data. This reduces impact of fading, reduces a probability of data loss, and improves data transmission reliability.

For example, the reused data may further include the interruption duration of the satellite corresponding to the receiving device. Usually, in an actual application, when UE searches for a satellite at an instant moment t, a link may be interrupted when the UE is not at a location of an elevation angle greater than a required one. For example, link interruption duration of different satellite systems is shown in Table <NUM>.

For the Iridium system, the mean interruption time is <NUM>, the minimum interruption time is <NUM>, the maximum interruption time is <NUM>, and the standard interruption time is <NUM>. For the Globalstar system and the Odyssey system, as shown in Table <NUM>, the rest may be deduced by analogy. When the link is interrupted, the satellite cannot receive uplink data sent by the UE. Alternatively, even if the satellite receives data, the satellite cannot decode the data correctly. Therefore, in the second DCI, the UE may be notified, by using some or all of the data related to the HARQ process, of duration T of next interruption time with the satellite. Therefore, the UE may sleep within the duration T. This may reduce power consumption and reduce interference in a network. Therefore, in this embodiment of this application, after the HARQ process is disabled, the data related to the HARQ process in the second DCI may be reused as the interruption duration of the satellite corresponding to the receiving device, so that the receiving device may learn of the link interruption duration with the satellite in advance, and make adequate preparation, for example, sleeping, or communicating in another manner. This may reduce power consumption of the receiving device, and reduce network interference to the receiving device.

It should be understood that the data related to the HARQ process in the second DCI may be simultaneously reused as one or more of the over-the-top time of the satellite corresponding to the receiving device, the power adjustment step, the interleaving depth, and the interruption duration of the satellite corresponding to the receiving device. In addition, the data related to the HARQ process in the second DCI may be reused as other data other than the over-the-top time of the satellite corresponding to the receiving device, the power adjustment step, the interleaving depth, and the interruption duration of the satellite corresponding to the receiving device. It is clear that the data related to the HARQ process in the second DCI may alternatively not be reused, to reduce signaling overheads and improve system performance. Specifically, adjustment may be performed based on an actual application scenario. This is not limited in this application.

<NUM>: The receiving device parses the second DCI.

Correspondingly, after receiving the second DCI, the receiving device may parse the second DCI, to determine the data included in the second DCI. If the sending device replaces the data related to the HARQ process in the second DCI with the reused data, after receiving the second DCI, the receiving device may obtain the reused data in the second DCI, for example, one or more of the over-the-top time of the satellite corresponding to the receiving device, the power adjustment step, the interleaving depth, and the interruption duration of the satellite corresponding to the receiving device.

It should be understood that step <NUM> and step <NUM> in this embodiment of this application are optional steps.

Therefore, in this embodiment of this application, after determining to disable the HARQ process, the sending device may reuse the data related to the HARQ process as other data, to implement data reusing. This improves network resource utilization between the sending device and the receiving device. In addition, the sending device may notify the receiving device of other data, for example, the power adjustment step or the interleaving depth, so that communication of the receiving device is more stable. This improves transmission reliability of the receiving device, and improves network resource utilization. In addition, this may prevent the HARQ process from occupying excessively large buffer space. In addition, after the HARQ process is disabled, subsequent data related to the HARQ process may be reused. This improves transmitted data utilization, saves network resources, and enhances system performance.

In addition, in a possible implementation, if the receiving device does not support a HARQ function, after the sending device determines, in a pre-agreed manner or by using capability negotiation data sent by the receiving device, that the receiving device does not support the HARQ function, when communicating with the receiving device, the sending device disable the HARQ process, that is, does not enable the HARQ mechanism. For example, if a terminal device does not support the HARQ function, when the terminal device accesses a base station, the base station may obtain a feature of the terminal device, including that the terminal device does not support the HARQ function. The base station may determine that the HARQ mechanism is not used for communication with the terminal device. When performing data transmission, data may be transmitted only once, or data may be transmitted through an ARQ. Therefore, in this embodiment of this application, if the receiving device does not support the HARQ function, the sending device may directly determine to disable the HARQ process, and not enable the HARQ mechanism. This can reduce storage space in the receiving device occupied by the HARQ process, and reduce energy consumption of the receiving device.

The foregoing describes in detail the method provided in this application. In addition to the receiving device and the sending device provided in <FIG>, this application further provides another sending device or receiving device. <FIG> is a schematic structural diagram of another receiving device according to this application. The receiving device may include:.

The receiving device may perform the steps performed by the receiving device in the embodiments corresponding to <FIG>.

Optionally, in some possible implementations, the indication data includes a network identifier number.

The processing unit <NUM> is specifically configured to determine, based on a preset mapping relationship, that the network identifier number indicates to disable the HARQ process, and the receiving device disables the HARQ process.

Optionally, in some possible implementations, the indication data includes a broadcast message.

The processing unit <NUM> is specifically configured to: if a value of a first preset bit in the broadcast message is a first preset value, disable the HARQ process.

Optionally, in some possible implementations, the indication data includes first downlink control information DCI.

The processing unit <NUM> is specifically configured to:.

Optionally, in some possible implementations, the processing unit <NUM> is specifically configured to:.

Optionally, in some possible implementations, the indication data includes cyclic redundancy check CRC data.

Optionally, in some possible implementations, the processing unit <NUM> is specifically configured to:
descramble data of a third preset bit in the CRC data by using the RA-RNTI, to obtain the descrambling result.

Optionally, in some possible implementations, after the processing unit <NUM> disables the HARQ process, the transceiver unit <NUM> is further configured to receive second DCI, where a fourth preset bit related to the HARQ process in the second DCI is used to transmit reused data after the HARQ process is disabled, and the fourth preset bit is a vacated bit after the HARQ process is disabled.

Optionally, in some possible implementations, the reused data includes at least one of over-the-top time of a satellite corresponding to the receiving device, a power adjustment step, an interleaving depth, and interruption duration of the satellite corresponding to the receiving device.

Optionally, in some possible implementations, after the processing unit <NUM> disables the HARQ process, the transceiver unit <NUM> is further configured to perform data transmission by using an automatic repeat request ARQ.

<FIG> is a schematic structural diagram of another sending device according to this application. The sending device may include:.

The sending device may be configured to perform the steps performed by the sending device in any one of the embodiments corresponding to <FIG>.

Optionally, in some possible implementations, the processing unit <NUM> is further configured to determine that the HARQ process information meets the second preset condition, if the sending device determines that a quantity of HARQ processes is greater than a threshold; and the transceiver unit <NUM> is specifically configured to send the indication data to the receiving device.

Optionally, in some possible implementations, the indication data is a broadcast message, and the transceiver unit <NUM> is specifically configured to send the broadcast message to the receiving device, where a value of a first preset bit in the broadcast message is a first preset value, and the first preset value is used to indicate the receiving device to disable the HARQ process.

Optionally, in some possible implementations, the indication data is first DCI.

Optionally, in some possible implementations, the transceiver unit <NUM> is specifically configured to send the first DCI to the receiving device, where a value of a second preset bit in the first DCI is a second preset value, and the second preset value is used to indicate the receiving device to disable the HARQ process.

Optionally, in some possible implementations, the transceiver unit <NUM> is specifically configured to send the first DCI to the receiving device, where a field length corresponding to the HARQ process in the first DCI is a preset length, and the preset length is used to indicate the receiving device to disable the HARQ process.

Optionally, in some possible implementations, the processing unit <NUM> is further configured to scramble CRC data by using an RA-RNTI, to obtain scrambled CRC data; and the transceiver unit <NUM> is specifically configured to send the scrambled CRC data to the receiving device.

Optionally, in some possible implementations, the processing unit <NUM> is specifically configured to scramble data of a third preset bit in the CRC data by using the RA-RNTI, to obtain the scrambled CRC data.

Optionally, in some possible implementations, the processing unit <NUM> is further configured to generate second DCI based on reused data after the transceiver unit <NUM> sends the indication data to the receiving device, where a fourth preset bit in the second DCI is reused data, and the fourth preset bit is a vacated bit after the HARQ process is disabled; and the transceiver unit <NUM> is further configured to send the second DCI to the receiving device.

Optionally, in some possible implementations, the reused data may include at least one of over-the-top time of a satellite corresponding to the receiving device, a power adjustment step, an interleaving depth, and interruption duration of the satellite corresponding to the receiving device.

This application provides a chip system. The chip system includes a processor, configured to support a network device to implement functions in the foregoing aspects, for example, sending or processing data and/or information in the foregoing method. In a possible design, the chip system further includes a memory. The memory is configured to store necessary program instructions and data. The chip system may include a chip, or may include a chip and another discrete component.

In another possible design, when the chip system is a chip in a sending vice or a receiving device, the chip includes a processing unit and a communications unit. The processing unit may be, for example, a processor, and the communications unit may be, for example, an input/output interface, a pin, or a circuit. The processing unit may execute computer executable instructions stored in a storage unit, so that the chip in the sending device or the receiving device performs the steps of the method performed by the sending device or the receiving device in any one of the embodiments in <FIG>. Optionally, the storage unit is a storage unit in the chip, for example, a register or a buffer. Alternatively, the storage unit may be a storage unit in a terminal but outside the chip, for example, a read-only memory (read-only memory, ROM), another type of static storage device that can store static information and instructions, or a random access memory (random access memory, RAM).

An embodiment of this application further provides a chip, including a processing module and a communications interface. The processing module can perform the method procedure related to the sending device or the receiving device in any one of the foregoing method embodiments. Further, the chip may further include a storage module (for example, a memory). The storage module is configured to store instructions, and the processing module is configured to execute the instructions stored in the storage module, so that the processing module performs the method procedure related to the sending device or the receiving device in any one of the foregoing method embodiments.

An embodiment of this application further provides a communications system. The communications system may include at least one sending device and at least one receiving device. The sending device may be the sending device mentioned in any one of the embodiments in <FIG>, and the receiving device may be the receiving device mentioned in any one of the embodiments in <FIG>.

An embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the program is executed by a computer, the method procedure related to the sending device or the receiving device in any one of the foregoing method embodiments is implemented. Correspondingly, the computer may be the sending device or the receiving device.

An embodiment of this application further provides a computer program or a computer program product including a computer program. When the computer program is executed by a computer, the computer is enabled to implement the method procedure related to the sending device or the receiving device in any one of the foregoing method embodiments. Correspondingly, the computer may be the sending device or the receiving device.

All or some of the foregoing embodiments in <FIG> may be implemented by using software, hardware, firmware, or a combination thereof. When software is used to implement the embodiments, all or some of the embodiments may be implemented in a 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 the computer, the procedure or functions according to the embodiments of this application are all or partially generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by the computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid-state disk (Solid-State Disk, SSD)), or the like.

It should be understood that, the processor mentioned in the embodiments of this application may be a central processing unit (Central Processing Unit, CPU), another general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or another programmable logic device, discrete gate or transistor logic device, discrete hardware component, or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

It should be further understood that there may be one or more processors in this application. Specifically, adjustment may be performed based on an actual application scenario. This is merely an example for description, and is not limited herein. There may be one or more memories in this embodiment of this application. Specifically, adjustment may be performed based on an actual application scenario. This is merely an example for description, and is not limited.

It should be further noted that when the sending device or the receiving device both include a processor (or a processing module) and a memory, the processor in this application may be integrated with the memory, or the processor may be connected to the memory by using an interface. Specifically, adjustment may be performed based on an actual application scenario. This is not limited.

It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for detailed working processes of the foregoing system, apparatus, and unit, refer to corresponding processes in the foregoing method embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in another manner. For example, the apparatus embodiments described in the foregoing are only examples. For example, division of the units is only a type of division of logical functions, and may be another manner of division during actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or may not be performed. The indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.

When the integrated unit is implemented in the form of the software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the conventional technology, or all or some of the technical solutions may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, or another network device) to perform all or some of the steps of the methods described in the embodiments in <FIG> of this application. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc.

It may be understood that the memory in this embodiment of this application may be a volatile memory or a nonvolatile memory, or may include both a volatile memory and a nonvolatile memory. The nonvolatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), used as an external cache. Through example but not limitative descriptions, many forms of RAMs may be used, for example, a static random access memory (Static RAM, SRAM), a dynamic random access memory (Dynamic RAM, DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (Synchlink DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DR RAM).

Claim 1:
A hybrid automatic repeat request, HARQ, process disabling method, comprising:
obtaining (<NUM>), by a receiving device, indication data, wherein the indication data is used to indicate to disable a HARQ process; and
disabling (<NUM>), by the receiving device, the HARQ process, characterized in that,
the indication data comprises a network identifier number; and
the disabling, by the receiving device, the HARQ process comprises:
determining (<NUM>), by the receiving device based on a preset mapping relationship, that the network identifier number indicates to disable the HARQ process, and disabling (<NUM>), by the receiving device, the HARQ process.