CN117676820A

CN117676820A - Method and device for determining resource unit

Info

Publication number: CN117676820A
Application number: CN202210978214.0A
Authority: CN
Inventors: 吴毅凌; 鲁振伟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-08-16
Filing date: 2022-08-16
Publication date: 2024-03-08
Also published as: WO2024037455A1

Abstract

The application provides a method and a device for determining a resource unit, wherein the method determines a resource unit RU, and the time domain length of the RU is related to any one or more of a line code length, the repetition number of bit repetition and a spreading factor. It can be seen that the method defines RU, and the defined RU can be applied to a network using line codes and/or bit repetition and/or spreading, for example, passive internet of things, so as to be beneficial to efficiently indicating time-frequency resources based on the defined RU.

Description

Method and device for determining resource unit

Technical Field

The present invention relates to the field of communications, and in particular, to a method and apparatus for determining a resource unit.

Background

Passive internet of things (Passive internet of things, passive IoT) is a cellular internet of things communication technology that supports battery-free terminals. Terminals in the Passive IoT have the advantage of low cost and low power consumption, but their radio frequency front end performance and baseband processing capability can be far inferior to terminals in conventional cellular networks. In order to achieve the link budget required for co-deployment with the cellular network, in the Passive IoT, the link budget can be increased by adopting the manners of bit repetition transmission, spreading and increasing the length of the line code in uplink transmission and downlink transmission, so as to further improve the network coverage capability.

The manner in which bits are retransmitted, spread, and the length of the line code are increased affects the allocation of time-frequency resources employed for transmission in the Passive IoT. Therefore, how to allocate the time-frequency resources used for uplink and downlink in the Passive IoT is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a method and a device for determining a resource unit, which are beneficial to efficiently configuring time-frequency resources adopted by uplink and downlink in a Passive IoT based on the determined resource unit.

In a first aspect, an embodiment of the present application provides a method for determining a resource unit, where the method includes: a Resource Unit (RU) is determined, wherein a time domain length of the RU is related to any one or more of a line code length, a number of repetitions of a bit repetition, and a spreading factor.

As can be seen, the method defines RUs that can be applied in a communication scenario using line codes and/or bit repetition and/or spreading factors, based on which time-frequency resources can be efficiently indicated. For example, the RU defined by the method may be applied to a Passive IoT in which receiver sensitivity may be improved by increasing line code length and/or bit repetition and/or spreading to increase link budget, and it is more efficient to configure time-frequency resources in the Passive IoT by the RU defined by the method.

In an alternative embodiment, the time domain length of the RU is proportional to the product of any one or more of the line code length, the number of repetitions, and the spreading factor.

In an alternative embodiment, RU is used for downlink; the time domain length of the RU is also related to the subcarrier spacing employed in the downlink. That is, in the case where RU is used for downlink, the influence of subcarrier spacing on RU is also considered in defining RU.

In an alternative embodiment, the subcarrier spacing is i times the first subcarrier spacing, i being a positive integer; the time domain length of RU is equal to the power of 2,And the product between the first time length. Wherein the power of 2 is determined based on any one or more of the line code length, the number of repetitions, and the spreading factor.

Optionally, the first subcarrier spacing is 15kHz and the first time period is 1 millisecond.

In an alternative embodiment, RU is used for upstream; the time domain length of RU is also related to the signal bandwidth employed for uplink; alternatively, the time domain length of the RU is also related to the carrier bandwidth and signal bandwidth employed by the uplink. That is, in the case where the RU is used for uplink, the influence of the signal bandwidth on the RU, or the influence of the signal bandwidth and the carrier bandwidth on the RU, is also considered in defining the RU.

In an alternative embodiment, the signal bandwidth is equal to the first threshold or the second threshold; the time domain length of RU is equal to the product between the power of 2 and the second time length. Wherein the power of 2 is determined based on any one or more of the line code length, the number of repetitions, and the spreading factor.

Alternatively, the first threshold and the second threshold are each one of 30kHz, 90kHz, 180kHz, 240 kHz. When the signal bandwidth is equal to 30kHz, the second time length is equal to 4 milliseconds or 2 milliseconds; when the signal bandwidth is equal to 90kHz, the second time length is equal to 2 milliseconds; when the signal bandwidth is equal to 180kHz, the second time length is equal to 1 millisecond; the second length of time is equal to 0.5 milliseconds when the signal bandwidth is equal to 240 kHz.

In an alternative embodiment, the time domain length of RU when the value of the signal bandwidth is greater than the first threshold and less than the second threshold is equal to the time domain length of RU when the value of the signal bandwidth is equal to the first threshold or the second threshold; the first threshold is less than the second threshold.

In an alternative embodiment, the carrier bandwidth is greater than or equal to 180kHz.

In an alternative embodiment, the signal bandwidth is an integer multiple of 30 kHz.

In an alternative embodiment, there is a signal bandwidth of different value between the signal bandwidths comprised by the first set and the signal bandwidths comprised by the second set; the number of signal bandwidths included in the first set is greater than or equal to the number of signal bandwidths included in the second set; the signal bandwidths included in the first set are uplink candidate signal bandwidths when the carrier bandwidth is the first carrier bandwidth; the signal bandwidths included in the second set are uplink candidate signal bandwidths when the carrier bandwidth is the second carrier bandwidth; the first carrier bandwidth is greater than the second carrier bandwidth.

In an alternative embodiment, the first set includes the same number of signal bandwidths as the second set; the first carrier bandwidth is k times of the second carrier bandwidth, and k is an integer greater than 1; the first set includes a signal bandwidth that is k times the signal bandwidth that the second set includes.

In an alternative embodiment, the first set includes a greater number of signal bandwidths than the second set; the second set is a proper subset of the first set.

In a second aspect, the present application also provides a communication device. The communication device has the function of implementing some or all of the embodiments described in the first aspect. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

In one possible design, the communication device may include a processing unit in a structure configured to support the communication device to perform the corresponding functions of the above-described method. The communication device may further comprise a communication unit, and the processing unit may be configured to control the communication unit to perform data/signaling transceiving. The communication unit is used for supporting communication between the communication device and other communication devices. The communication device may further comprise a memory unit for coupling with the processing unit and the communication unit, which holds the necessary program instructions and data of the communication device.

In one embodiment, a processing unit is configured to determine a resource unit RU; the time domain length of the RU is related to any one or more of a line code length, a number of repetitions of bit repetition, and a spreading factor.

In addition, in this aspect, other optional embodiments of the communication device may be referred to in the relevant content of the first aspect, which is not described in detail herein.

As an example, the communication unit may be a transceiver or a communication interface, the storage unit may be a memory, and the processing unit may be a processor. The processor may be configured to perform the method of the first aspect described above by logic circuitry or by running a computer program, the transceiver may be configured to transmit and receive signals, and the memory may be configured to store the computer program.

In one embodiment, a processor is configured to determine a resource unit RU; the time domain length of the RU is related to any one or more of a line code length, a number of repetitions of bit repetition, and a spreading factor.

In another embodiment, the communication device is a chip or a system-on-chip. The processing unit may also be embodied as a processing circuit or logic circuit; the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit, etc. on the chip or system of chips.

In an implementation, a processor may be used to perform, for example but not limited to, baseband related processing, and a transceiver may be used to perform, for example but not limited to, radio frequency transceiving. The above devices may be provided on separate chips, or may be provided at least partially or entirely on the same chip. For example, the processor may be further divided into an analog baseband processor and a digital baseband processor. Wherein the analog baseband processor may be integrated on the same chip as the transceiver and the digital baseband processor may be provided on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, the digital baseband processor may be integrated on the same chip as a variety of application processors (e.g., without limitation, graphics processors, multimedia processors, etc.). Such a Chip may be referred to as a System on a Chip (SoC). Whether the individual devices are independently disposed on different chips or integrally disposed on one or more chips is often dependent on the needs of the product design. The implementation form of the device is not limited in the embodiment of the application.

In a third aspect, the present application also provides a processor for performing the above-described methods. In performing these methods, the process of transmitting the signal and receiving the signal in the above-described methods may be understood as a process of outputting the signal by a processor and a process of inputting the signal by a processor. When the signal is output, the processor outputs the signal to the transceiver for transmission by the transceiver. The signal, after being output by the processor, may also require additional processing before reaching the transceiver. Similarly, when the processor receives the input signal, the transceiver receives the signal and inputs it to the processor. Further, after the transceiver receives the signal, the signal may need to be processed and then input to the processor.

With respect to operations such as transmission and reception, etc., related to the processor, unless specifically stated otherwise, or if there is no conflict with the actual role or inherent logic of the operations in the related description, the operations such as output and reception, input, etc., of the processor may be understood more generally, rather than the operations such as transmission and reception, which are directly performed by the radio frequency circuit and the antenna.

In implementation, the processor may be a processor dedicated to performing the methods, or may be a processor that executes computer instructions in a memory to perform the methods, e.g., a general purpose processor. The Memory may be a non-transitory (non-transitory) Memory, such as a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately provided on different chips, and the type of the Memory and the manner of providing the Memory and the processor are not limited in this embodiment of the present application.

In a fourth aspect, the present application provides a computer readable storage medium storing instructions which, when executed by a computer, cause the method of the first aspect described above to be performed.

In a fifth aspect, the present application also provides a computer program product comprising instructions which, when run on a computer, cause the method of the first aspect described above to be performed.

In a sixth aspect, the present application provides a chip system comprising a processor and an interface for acquiring a program or instructions, the processor being adapted to invoke the program or instructions to implement the functionality of the first aspect. In one possible design, the system on a chip further includes a memory for holding program instructions and data necessary for the terminal. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

Drawings

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 2 is a flow chart of a method for determining a resource unit according to an embodiment of the present application;

fig. 3 is a schematic diagram of a transmit chain processing procedure provided in an embodiment of the present application;

fig. 4 is a schematic diagram of another transmission link processing procedure provided in an embodiment of the present application;

fig. 5 is a schematic diagram of another transmission link processing procedure provided in an embodiment of the present application;

fig. 6 is a schematic diagram of another transmit chain processing procedure provided in an embodiment of the present application;

fig. 7 is a schematic diagram of another transmission link processing procedure provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application are clearly and completely described below with reference to the drawings in the embodiments of the present application.

In order to better understand the method for determining the resource unit disclosed in the embodiments of the present application, a communication system to which the embodiments of the present application are applicable will be described.

The embodiments of the present application may be applied to a long term evolution (long term evolution, LTE) system, an LTE-Advanced (LTE-a) system, a New Radio (NR) system, or the like, and with the continuous development of a communication technology, the technical solutions of the embodiments of the present application may also be applied to a communication system that is subsequently evolved, such as a sixth Generation (6 th-Generation, 6G) mobile communication technology system, a seventh Generation (7 th-Generation, 7G) mobile communication technology system, or the like.

The communication system applicable to the embodiment of the application comprises a device capable of sending information and a device for receiving information. Referring to fig. 1, fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application. The communication system may include, but is not limited to, one network device and one terminal device, or at least two network devices, or at least two terminal devices. The number and configuration of the devices shown in fig. 1 are for example and not intended to limit the embodiments of the present application. The communication system shown in fig. 1 is illustrated by way of example with two network devices and 8 terminal devices. The network device in fig. 1 takes a base station as an example, and the terminal device includes a terminal device in each scene and a terminal device in each form.

In fig. 1, a base station #2, and a terminal device #1 and a terminal device #8 form a communication system, in which the base station #1 and the terminal device #1 can communicate with one or more terminal devices of the terminal device #6, and the base station #1 can also communicate with one or more terminal devices of the terminal device #7 and the terminal device #8 through the base station # 2. In addition, the terminal device #4, the terminal device #5, and the terminal device #6 may form a single communication system, and communication may be performed between the terminal device #4 and the terminal device #5, and between the terminal device # 6. The base station #2, the terminal device #7, and the terminal device #8 may also constitute one communication system, in which the base station #2 may communicate with the terminal device #7, the terminal device # 8.

In the embodiment of the present application, the network device is a device with a radio transceiving function, which may be an evolved Node B (eNB or eNodeB) in LTE, or a next generation base station (the next Generation Node B, gNB or gndeb) in NR, or a base station in a public land mobile network (public land mobile network, PLMN) that evolves in the future, a broadband network service gateway (broadband network gateway, BNG), a convergence switch, or a non-third generation partnership project (3rd generation partnership project,3GPP) access device, or the like. Alternatively, the network device in the embodiments of the present application may include various types of base stations, which may be base stations that support receiving data transmitted by transmitting communications, and may also be base stations that support sending wake-up signals. For example: a macro base station, a micro base station (also called a small station), a small base station, a pole station, a relay station, an access point, an access node in a 5G later evolution communication system, or the like, which implements a base station function, or may also be a transmission receiving point (transmitting and receiving point, TRP), a transmitting point (transmitting point, TP), a mobile switching center, and a network device in a device-to-device (D2D), a vehicle-to-device (V2X), a machine-to-machine (M2M) communication device, which performs a base station function, or the like, and may also include a Centralized Unit (CU) and a distributed unit (DU, non-terrestrial network, NTN) in a cloud access network (cloud radio access network, C-RAN) system, that is, a network device in a non-terrestrial communication network (non-terrestrial network, NTN) communication system, that is, that may be deployed on a high-altitude platform or a satellite.

The terminal device may include various handheld devices, vehicle mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. The terminal device may be a user device for machine type communication. The terminal device may be a terminal device in NR, or may be a terminal device supporting a wake-up receiver, or may be a terminal device not supporting a wake-up receiver. The terminal device may be a terminal device supporting reflective communication, such as a tag. The terminal device may also refer to a User Equipment (UE), an access terminal, a customer-terminal device (customer-premises equipment, CPE), a subscriber unit (subscriber unit), a user agent, a cellular phone (smart phone), a smart phone (smart phone), a wireless data card, a personal digital assistant (personal digital assistant, PDA) computer, a tablet, a wireless modem, a handheld device (handset), a laptop (laptop computer), a machine type communication (machine type communication, MTC) terminal, a communication device onboard an aerial plane, a wearable device, an unmanned plane, a robot, a point of sale (POS) terminal in D2D, a terminal in V2X, a Virtual Reality (VR) terminal device, a wireless terminal in an augmented reality (augmented reality, AR) terminal device, a wireless terminal in an industrial control (industrial control), a wireless terminal in a self-driving (self-driving) terminal, a wireless terminal in a remote medical network (smart) terminal in a smart network (smart terminal in a smart network, a wireless terminal in a smart mobile device (smart network of a smart device of a home, a mobile device in a smart device, or the like).

In order to facilitate an understanding of the embodiments disclosed herein, the following two descriptions are provided.

(1) In the embodiments disclosed in the present application, the scenario is described by taking the scenario of an NR network in a wireless communication network as an example, and it should be noted that the schemes in the embodiments disclosed in the present application may also be applied to other wireless communication networks, and the corresponding names may also be replaced by names of corresponding functions in other wireless communication networks.

(2) Embodiments of the present disclosure will present various aspects, embodiments, or features of the present disclosure around a system comprising a plurality of devices, components, modules, etc. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. Furthermore, combinations of these schemes may also be used.

The internet of things is a hot topic in the field of wireless communication, and various objects can be connected with a network through information sensing equipment according to an agreed protocol in the internet of things so that the objects can be interconnected and intercommunicated. In the 3GPP cellular communication system, multi-layer internet of things formed by NR mobile bandwidth (MBB), reduced capability (reduced capability, redcap) and LTE Category4 (Category 4, cat.4), enhanced Machine-type communication (eMTC) and LTE Category1 (Category 1, cat.1), and narrowband internet of things (narrow band internet of things, NB-IoT) are gradually formed, so that the multi-layer internet of things formed by multi-type terminals such as communication capability, terminal cost and power consumption of different application scenarios can be adapted. The explosive development of the internet of things is an important power for continuously improving the production and life of human beings.

In some of the internet of things, for example NB-IoT, a battery may be used to power terminal devices in the internet of things (which may be simply referred to as internet of things terminals). However, the life cycle of an internet of things terminal is typically in units of years, even up to ten years; the large number of the internet of things terminals are wide in distribution range and are installed at the position with high construction difficulty, so that maintenance cost generated by replacing batteries for the internet of things terminals is high regularly. And moreover, the high-performance battery with long service life and meeting the rated voltage and power requirements of the terminal module is higher in cost and even comparable with the terminal module, so that the network cost is obviously increased. In addition, the adoption of batteries to supply power to a large number of internet of things terminals consumes a large amount of materials and causes serious environmental protection pressure. While Passive internet of things (Passive internet of things, passive IoT) is a cellular internet of things communication technology supporting battery-free terminals, it is oriented towards the next-level internet of things market with lower cost and power consumption than NB-IoT pair terminals.

In NB-IoT, the uplink may employ two different subcarrier spacings (subcarrier spacing) of 15 kiloHertz (kHz) and 3.75 kHz. In addition, with a subcarrier spacing of 15kHz, there are several alternatives available for scheduling to support frequency domain scheduling of different numbers of subcarriers, i.e., signal bandwidth employed in the uplink in NB-IoT. For different signal bandwidths, there is a significant difference in the number of Resource Elements (REs) corresponding to the same time domain length, which is not beneficial to the description of the transport block size (transport block size, TBS) and the design of the corresponding fields of the downlink control information (downlink control information, DCI). Thus, resource Units (RUs) for uplink scheduling are defined in NB-IoT, as shown in table 1 below. Table 1 shows the correspondence between the number of subcarriers (subcarrier number), the number of slots (slots number), the number of REs, the number of single-carrier frequency division multiple access (SC-carrier frequency-division multiple access, SC-FDMA) symbols (SC-FDMA symbols number), and the time domain length of RU (RU duration) for NB-IoT subcarriers at 3.75kHz and 15kHz, respectively. In addition, the time domain length of RU in table 1 is in units of milliseconds (ms).

TABLE 1

It can be seen that, in uplink transmission of NB-IoT, the number of REs included in RU is equal when the two sub-carrier transmission is performed at a sub-carrier interval of 15kHz and 3.75kHz, and the number of REs included in RU corresponding to each multi-sub-carrier transmission is equal when the sub-carrier interval is 15 kHz.

Since the NB-IoT uplink employs bit block retransmission. In the repeated transmission of the bit block, the whole bit block is transmitted repeatedly each time, that is, the number of data bits transmitted repeatedly each time is the same, the influence of the repeated number of repeated transmission of the bit block on the number of the loadable data bits in the RU is basically not considered, so that the change of the time domain length of the RU along with the repeated number is not considered in the NB-IoT. However, since the baseband processing buffer of the terminal device in the Passive IoT is extremely limited, it is not suitable to repeat transmission using bit blocks that require a large buffer space, but mainly uses bit repeat transmission. In the bit repetition transmission, another bit is repeated after 1 bit is repeated, so RU defined in NB-IoT is not applicable to Passive IoT.

The embodiment of the application provides a method for determining a resource unit, which can determine that the time domain length of an RU is related to any one or more of the length of a line code, the repetition number of bit repetition and a spreading factor. The RU defined by the method may be applicable to the Passive IoT, thereby facilitating efficient configuration of uplink and downlink time-frequency resources in the Passive IoT based on the determined RU.

The method for determining the resource unit provided in the embodiments of the present application is described below with reference to the accompanying drawings.

Referring to fig. 2, fig. 2 is a flowchart of a method for determining a resource unit according to an embodiment of the present application, where the method for determining a resource unit may be performed by a network device or a terminal device, or may be performed by a terminal device or a component of a network device (for example, a processor, a chip, or a system on a chip). For convenience of explanation, the method for determining a resource unit provided in the embodiment of the present application is explained below with a communication device as an execution body, where the communication device may be a network device or a terminal device. The method for determining the resource unit comprises the following steps:

s101, the communication equipment determines a resource unit RU, wherein the time domain length of the RU is related to any one or more of a line code length, the repetition number of bit repetition and a spreading factor.

It can be seen that in the embodiment that the time domain length of the RU is related to any one of the line code length, the repetition number of bit repetition, and the spreading factor, the influence of any one of the line code length, the repetition number, and the spreading factor on the time domain length of the RU is considered, and the influence of the other two terms on the time domain length of the RU may not be considered. In the embodiment that the time domain length of the RU is related to any two of the line code length, the repetition number and the spreading factor, the influence of any two of the line code length, the repetition number and the spreading factor on the time domain length of the RU is considered, and the influence of the other one on the time domain length of the RU may not be considered. In an embodiment in which the time domain length of the RU is related to three of the line code length, the repetition number, and the spreading factor, the influence of the three of the line code length, the repetition number, and the spreading factor on the time domain length of the RU is considered.

Optionally, the method may further include: the communication device indicates the time-frequency resource using the determined RU. The time-frequency resource may be a time-frequency resource used in uplink transmission or a time-frequency resource used in downlink transmission. The method may make indicating time-frequency resources in a communication scenario using line codes and/or bit repetition and/or spreading factors more efficient. For example, receiver sensitivity may be improved in a Passive IoT by increasing line code length and/or bit repetition and/or spreading to increase link budget, and time-frequency resources in the Passive IoT may be efficiently indicated based on the determined RU.

In addition, link budget may be raised in a Passive IoT by bit repetition, increasing line code length, or spreading, and it can be seen that the 3 implementations of defining RUs described above may be applied in IoT, enabling efficient configuration/indication of time-frequency resources based on defined RUs.

In an alternative embodiment, the time domain length of the RU is proportional to the product of any one or more of the line code length, the number of repetitions, and the spreading factor. Specifically, the time domain length of RU is proportional to any one of the line code length, the number of repetitions, and the spreading factor. Alternatively, the time domain length of RU is proportional to the product of any two of the line code length, the number of repetitions, and the spreading factor. Alternatively, the time domain length of RU is proportional to the product of the three terms of line code length, repetition number and spreading factor.

Optionally, any one or more of the line code length, the number of repetitions of the bit repetition, the spreading factor may be determined based on the link budget or the coverage level. For example, in a scenario where the required link budget or coverage level is high, the value of any one or more of the line code length, the number of repetition of the bit repetition, and the spreading factor may be set to be large.

Alternatively, each of the line code length, the number of repetitions of the bit repetition, and the spreading factor may be individually scheduled or configured. For example, different independent fields are employed in the DCI or configuration message to indicate the line code length, the number of repetitions of the bit repetition, and the spreading factor, respectively. Or any of the line code length, the number of repeated bit and the spreading factor may be jointly configured, for example, the same field is used in the DCI or the configuration message to indicate any of the line code length, the number of repeated bit and the spreading factor, and the value of any of the line code length, the number of repeated bit and the spreading factor may be determined from a predefined table based on the information carried by the field. The predefined table may be used to characterize a correspondence between information carried by the field and any of a line code length, a repetition number of bit repetition, and a spreading factor.

In an alternative embodiment, the RU is used for the downlink, and the time domain length of the RU is also related to the subcarrier spacing employed for the downlink. That is, the time domain length of the RU is also affected by the subcarrier spacing employed for the downlink. In addition, when the RU is used in downlink, the frequency domain width of the RU is equal to the signal bandwidth or carrier bandwidth adopted in downlink, and the signal bandwidth adopted in downlink is equal to the carrier bandwidth or less than but close to the carrier bandwidth.

Optionally, the subcarrier spacing is i times the first subcarrier spacing, i is a positive integer, and the time domain length of RU is equal to a power of 2,And the product between the first time length. Wherein the power of 2 is determined based on any one or more of the line code length, the number of repetitions, and the spreading factor. Alternatively, the first subcarrier spacing may be 15kHz, in which case the first time period may be 1 millisecond.

In the following, taking an example that the first subcarrier spacing is 15kHz and the first time length is 1 ms, the time domain length of the RU when the RU is used for downlink is described as one, two, or three of the line code length, the repetition number of bit repetition, and the spreading factor are related to each other, respectively, as described in embodiments 1.1 to 1.3. In these 3 embodiments, the line code length is equal to 2 ⁿ The number of repetitions is equal to 2 ^m A spreading factor equal to 2 ^l The method comprises the steps of carrying out a first treatment on the surface of the n is a positive integer, m and l are integers greater than or equal to 0.

In embodiment 1.1, the time domain length of ru is related to any one of the line code length, the number of repetition of bit repetition, and the spreading factor. This embodiment mode 1.1 includes the following cases 1.1.1 to 1.1.3.

Case 1.1.1: the time domain length of RU is related to the line code length, the time domain length of RU is equal to

For example, in case i is equal to 1, i.e., the subcarrier spacing is 15kHz, if the line code length is 2, i.e., n is 1, the time domain length of ru is 1ms; if the line code length is 4, i.e., n is 2, the time domain length of ru is 2ms; if the line code length is 8, i.e., n is 3, the time domain length of ru is 4ms.

For another example, in case i is equal to 2, i.e., the subcarrier spacing is 30kHz, if the line code length is 2, i.e., n is 1, the time domain length of ru is 0.5ms; if the line code length is 4, i.e., n is 2, the time domain length of RU is 1ms; if the line code length is 8, i.e., n is 3, the time domain length of ru is 2ms.

Case 1.1.2: the time domain length of RU is related to the number of repetitions of the bit repetition, the time domain length of RU is equal to

For example, in case i is equal to 1, i.e., the subcarrier spacing is 15kHz, if the repetition number is 1, i.e., m is 0, the time domain length of ru is 1ms; if the repetition number is 2, i.e. m is 1, the time domain length of RU is 2ms; if the repetition number is 4, i.e., m is 2, the time domain length of ru is 4ms.

For another example, in case i is equal to 2, i.e., the subcarrier spacing is 30kHz, if the repetition number is 1, i.e., m is 0, the time domain length of ru is 0.5ms; if the repetition number is 2, i.e. m is 1, the time domain length of RU is 1ms; if the repetition number is 4, i.e., m is 2, the time domain length of ru is 2ms.

Case 1.1.3: the time domain length of RU is related to the spreading factor, the time domain length of RU is equal to

For example, in case i is equal to 1, i.e., the subcarrier spacing is 15kHz, if the spreading factor is 1, i.e., l is 0, the time domain length of ru is 1ms; if the spreading factor is 2, i.e. l is 1, the time domain length of RU is 2ms; if the spreading factor is 4, i.e. l is 2, the time domain length of ru is 4ms.

For another example, in case i is equal to 2, i.e., the subcarrier spacing is 30kHz, if the spreading factor is 1, i.e., l is 0, the time domain length of ru is 0.5ms; if the spreading factor is 2, i.e. l is 1, the time domain length of RU is 1ms; if the spreading factor is 4, i.e. l is 2, the time domain length of ru is 2ms.

In embodiment 1.2, the time domain length of ru is related to any two of the line code length, the number of repetition of bit repetition, and the spreading factor. This embodiment mode 1.2 includes the following cases 1.2.1 to 1.2.3.

Case 1.2.1: the time domain length of RU is related to the line code length, the number of repetitions of the bit repetition, the time domain length of RU is equal to

For example, in case i is equal to 1, i.e., the subcarrier spacing is 15kHz, if n+m=1 (i.e., n=1, m=0), the time domain length of RU is 1ms; if n+m=2 (where n=2 and m=0, or n=1 and m=1), the time domain length of RU is 2ms; if n+m=3 (where n=3 and m=0, or n=2 and m=1, or n=1 and m=2), the time domain length of RU is 4ms.

For another example, in case i is equal to 2, i.e., the subcarrier spacing is 30kHz, if n+m=1 (i.e., n=1, m=0), the time domain length of RU is 0.5ms; if n+m=2 (where n=2 and m=0, or n=1 and m=1), the time domain length of RU is 1ms; if n+m=3 (where n=3 and m=0, or n=2 and m=1, or n=1 and m=2), the time domain length of RU is 2ms.

Case 1.2.2: the time domain length of RU is related to the length of line code and the spreading factor, and is equal to

For example, in case i is equal to 1, i.e., the subcarrier spacing is 15kHz, if n+l=1 (i.e., n=1, l=0), the time domain length of RU is 1ms; if n+l=2 (where n=2 and l=0, or n=1 and l=1), the time domain length of RU is 2ms; if n+l=3 (where n=3 and l=0, or n=2 and l=1, or n=1 and l=2), the time domain length of RU is 4ms.

For another example, if n+l=1 (i.e., n=1, l=0) in the case where i is equal to 2, i.e., the subcarrier spacing is 30kHz, the time domain length of RU is 0.5ms; if n+l=2 (where n=2 and l=0, or n=1 and l=1), the time domain length of RU is 1ms; if n+l=3 (where n=3 and l=0, or n=2 and l=1, or n=1 and l=2), the time domain length of RU is 2ms.

Case 1.2.3: the time domain length of RU is related to the length of line code and the spreading factor, and is equal to

For example, in case i is equal to 1, i.e., the subcarrier spacing is 15kHz, if m+l=1 (where m=1 and l=0, or m=0 and l=1), the time domain length of RU is 2ms; if m+l=2 (where m=2 and l=0, or m=1 and l=1, or m=0 and l=2), the time domain length of RU is 4ms.

For another example, if m+l=1 (where m=1 and l=0, or m=0 and l=1) in the case where i is equal to 2, i.e. the subcarrier spacing is 30kHz, the time domain length of RU is 1ms; if m+l=2 (where m=2 and l=0, or m=1 and l=1, or m=0 and l=2), the time domain length of RU is 2ms.

In embodiment 1.3, the time domain length of ru is related to three terms of line code length, number of repetition of bit repetition, and spreading factor. In this case, the time domain length of RU is equal to This embodiment mode 1.3 includes the following cases 1.3.1 to 1.2.6.

Case 1.3.1: the communication device increases the link budget by increasing the line code length without bit repetition and spreading, i.e. with a repetition number of 1 (i.e. m=0) and a spreading factor of 1 (i.e. l=0). In this case, the time domain length of RU is equal to

In this case, the transmission link processing flow of the communication device is shown in fig. 3, and the communication device performs cyclic redundancy check (cyclic redundancy check, CRC) and forward error correction (forward error correction, FEC) on the signal to be transmitted, then adjusts the line code length, and performs amplitude-shift keying (ASK), discrete fourier transform (discrete fourier transform, DFT) spread orthogonal frequency division multiplexing (orthogonal frequency division multiplexing, OFDM) (i.e., DFT-s-OFDM), and Low-pass filtering (Low-pass filtering). Among them, for example, polar (Polar) codes may be used in FEC, and for example, manchester (Manchester) codes may be used in line codes. The DFT-s-OFDM performed by the communication device includes: DFT, frequency domain pulse shaping (frequency domain pulse shaping), mapping to subcarriers (mapping to subcarrier), inverse fast fourier transform (inverse fast fourier transform, IFFT), cyclic Prefix (CP) Insertion (i.e., CP Insertion).

Case 1.3.2: the communication device increases the link budget by bit repetition without spreading and increasing the line code length, i.e. the spreading factor is 1 (i.e. l=0) and the line code length is 2 (i.e. n=1), in which case the time domain length of RU is equal to

Case 1.3.3: the communication device increases the link budget by spreading without bit repetition and increasing the line code length, i.e. the number of repetitions is 1 (i.e. m=0) and the line code length is 2 (i.e. n=1), in which case the time domain length of RU is equal to

In both cases 1.3.2 and 1.3.3, the transmission link processing flow of the communication device is as shown in fig. 4, and after the communication device performs CRC, FEC and setting the line code length to 2 on the signal to be transmitted, the bit Repetition (Repetition) or the spreading (Spectrum spreading) is configured, followed by ASK, DFT-s-OFDM and low-pass filtering.

Case 1.3.4: communication apparatusThe link budget is increased by increasing the line code length and bit repetition without spreading, i.e. with a spreading factor of 1 (i.e. l=0), in which case the time domain length of RU is equal to

Case 1.3.5: the communication device increases the link budget by increasing the line code length and spreading without bit repetition, i.e. with a repetition number of 1 (i.e. m=0), in which case the time domain length of RU is equal to

In both cases 1.3.4 and 1.3.5, the transmission link processing flow of the communication device is similar to that shown in fig. 4, except that in cases 1.3.4 and 1.3.5, the communication device can adjust the line code length according to the link budget or coverage level, instead of setting the direct line code length to 2.

Case 1.3.6: the communication device increases the link budget by bit repetition and spreading without increasing the line code length, i.e. the line code length is 2 (i.e. n=1), in which case the time domain length of RU is equal to

In an alternative embodiment, in case the RU is used for downlink, the carrier bandwidth may be 180kHz, and may be greater than or equal to 360kHz, such as 540kHz, 720kHz, etc. When the carrier bandwidth is 180kHz, the subcarrier interval adopted by orthogonalization of the downlink signal subcarriers is 15kHz; when the bandwidth of the carrier is greater than or equal to 360kHz, the subcarrier spacing used for orthogonalization of the downlink signal subcarriers may be a positive integer multiple of 15 kHz. In addition, in the downlink, the signal bandwidth is equal to the carrier bandwidth, or the signal bandwidth is smaller than but close to the carrier bandwidth.

In an alternative embodiment, RU is used for upstream. In the uplink of the Passive IoT, the communication device may further increase the signal-to-noise ratio of the received signal by narrowing the signal bandwidth, so as to further increase the link budget, and then the time domain length of the RU is further related to the signal bandwidth employed in the uplink; alternatively, the time domain length of the RU is also related to the carrier bandwidth and signal bandwidth employed by the uplink. That is, the influence of the signal bandwidth on the RU may be considered when defining the RU, or the influence of the signal bandwidth and the carrier bandwidth on the RU may be considered. In addition, the frequency domain width of RU is equal to the signal bandwidth.

In an alternative embodiment, in case the RU is used for upstream, the signal bandwidth is equal to the first threshold or the second threshold. The time domain length of RU is equal to the product between the power of 2 and the second time length. Wherein the power of 2 is determined based on any one or more of the line code length, the number of repetitions, and the spreading factor.

Alternatively, the first threshold and the second threshold may be one of 30kHz, 90kHz, 180kHz, 240kHz, respectively. The second length of time is equal to 4 milliseconds or 2 milliseconds when the signal bandwidth is equal to 30 kHz. The second length of time is equal to 2 milliseconds when the signal bandwidth is equal to 90 kHz. The second length of time is equal to 1 millisecond when the signal bandwidth is equal to 180 kHz. The second length of time is equal to 0.5 milliseconds when the signal bandwidth is equal to 240 kHz. In addition, the first threshold value and the second threshold value may take other values, such as 60kHz, 360kHz, 420kHz, 540kHz, 720kHz, etc., based on the characteristics of the communication scene, in addition to the aforementioned 30kHz, 90kHz, 180kHz, 240 kHz. When the first threshold or the second threshold is equal to 60kHz, the second length of time may be equal to 2 milliseconds; the second length of time may be equal to 0.5 milliseconds when the first threshold or the second threshold is greater than 240 kHz.

Optionally, the time domain length of the RU when the value of the signal bandwidth is greater than the first threshold and less than the second threshold is equal to the time domain length of the RU when the value of the signal bandwidth is equal to the first threshold or the second threshold; the first threshold is less than the second threshold. For example, the first threshold is 30kHz and the second threshold is 90kHz, and for signal bandwidths greater than 30kHz and less than 90kHz, the time-domain length of the RU is equal to the time-domain length of the RU for signal bandwidths of 90 kHz. For another example, the first threshold is 90kHz and the second threshold is 180kHz, and for signal bandwidths greater than 90kHz and less than 180kHz, the time domain length of the RU is equal to the time domain length of the RU for signal bandwidths of 180kHz.

Optionally, the time domain length of RU when the value of the signal bandwidth is greater than the first threshold is equal to the time domain length of RU when the value of the signal bandwidth is equal to the first threshold. For example, the first threshold is 240kHz, and the time domain length of the RU when the channel bandwidth is greater than 240kHz is equal to the time domain length of the RU when the signal bandwidth is 240 kHz.

In an alternative embodiment, the carrier bandwidth in the upstream is greater than or equal to 180kHz.

In an alternative embodiment, the signal bandwidth in the upstream is an integer multiple of 30 kHz. Optionally, in the case that the time domain length of the RU is also related to the carrier bandwidth and the signal bandwidth used for uplink, the signal bandwidth is less than or equal to the carrier bandwidth. For example, when the carrier bandwidth in the uplink is 180kHz, the signal bandwidth may be 30kHz, 60kHz or 180kHz.

The time domain length of RU at different values of the signal bandwidth is exemplarily described below for the case where RU is used for uplink, as described in embodiments 2.1 to 2.3. In these 3 embodiments, the line code length is equal to 2 ⁿ The number of repetitions is equal to 2 ^m A spreading factor equal to 2 ^l The method comprises the steps of carrying out a first treatment on the surface of the n is a positive integer, m and l are integers greater than or equal to 0.

In embodiment 2.1, the time domain length of ru is related to any one of the line code length, the number of repetition of bit repetition, and the spreading factor. This embodiment mode 2.1 includes the following cases 2.1.1 to 2.1.4.

Case 2.1.1: the signal bandwidth is 30kHz.

When the time domain length of RU is related to the length of the line code, the time domain length of RU is 2 ^n-1 X 4 milliseconds. For example, if the line code length is 2 (i.e., n=1), the time domain length of RU is 4ms; if the line code length is 4 (i.e., n=2), the time domain length of RU is 8ms.

When the time domain length of RU is related to the repetition number, the time domain length of RU is 2 ^m X 4 milliseconds. For example, if the number of repetitions is 1 (i.e., m=0), the time domain length of RU is 4ms; if the repetition number is 2 (i.e., m=1), the time domain length of RU is 8ms。

When the time domain length of RU is related to the spreading factor, the time domain length of RU is 2 ^l X 4 milliseconds. For example, if the spreading factor is 1 (i.e., l=0), the time domain length of RU is 4ms; if the spreading factor is 2 (i.e. l=1), the time domain length of RU is 8ms.

Alternatively, when the time domain length of the RU is related to the line code length, the time domain length of the RU is 2 ^n-1 X 2 milliseconds; when the time domain length of RU is related to the repetition number, the time domain length of RU is 2 ^m X 2 milliseconds; when the time domain length of RU is related to the spreading factor, the time domain length of RU is 2 ^l X 2 milliseconds.

Case 2.1.2: the signal bandwidth is greater than 30kHz and less than or equal to 90kHz.

When the time domain length of RU is related to the length of the line code, the time domain length of RU is 2 ^n-1 X 2 milliseconds. For example, if the line code length is 2 (i.e., n=1), the time domain length of RU is 2ms; if the line code length is 4 (i.e., n=2), the time domain length of RU is 4ms.

When the time domain length of RU is related to the repetition number, the time domain length of RU is 2 ^m X 2 milliseconds. For example, if the number of repetitions is 1 (i.e., m=0), the time domain length of RU is 2ms; if the repetition number is 2 (i.e., m=1), the time domain length of RU is 4ms.

When the time domain length of RU is related to the spreading factor, the time domain length of RU is 2 ^l X 2 milliseconds. For example, if the spreading factor is 1 (i.e., l=0), the time domain length of RU is 2ms; if the spreading factor is 2 (i.e. l=1), the time domain length of RU is 4ms.

Case 2.1.3: the signal bandwidth is greater than 90kHz and less than or equal to 180kHz.

When the time domain length of RU is related to the length of the line code, the time domain length of RU is 2 ^n-1 X 1 millisecond. For example, if the line code length is 2 (i.e., n=1), the time domain length of RU is 1ms; if the line code length is 4 (i.e., n=2), the time domain length of RU is 2ms.

When the time domain length of RU is related to the repetition number, the time domain length of RU is 2 ^m X 1 millisecond. For example, if the number of repetitions is 1 (i.e., m=0), the time domain length of RU is 1ms; RU if the repetition number is 2 (i.e., m=1)Is 2ms.

When the time domain length of RU is related to the spreading factor, the time domain length of RU is 2 ^l X 1 millisecond. For example, if the spreading factor is 1 (i.e., l=0), the time domain length of RU is 1ms; if the spreading factor is 2 (i.e. l=1), the time domain length of RU is 2ms.

Case 2.1.4: the signal bandwidth is greater than or equal to 240kHz.

When the time domain length of RU is related to the length of the line code, the time domain length of RU is 2 ^n-1 X 0.5 milliseconds. For example, if the line code length is 2 (i.e., n=1), the time domain length of RU is 0.5ms; if the line code length is 4 (i.e., n=2), the time domain length of RU is 1ms.

When the time domain length of RU is related to the repetition number, the time domain length of RU is 2 ^m X 0.5 milliseconds. For example, if the number of repetitions is 1 (i.e., m=0), the time domain length of RU is 0.5ms; if the repetition number is 2 (i.e., m=1), the time domain length of RU is 1ms.

When the time domain length of RU is related to the spreading factor, the time domain length of RU is 2 ^l X 0.5 milliseconds. For example, if the spreading factor is 1 (i.e., l=0), the time domain length of RU is 0.5ms; if the spreading factor is 2 (i.e. l=1), the time domain length of RU is 1ms.

In embodiment 2.2, the time domain length of ru is related to any two of the line code length, the number of repetition of bit repetition, and the spreading factor. This embodiment mode 2.2 includes the following cases 2.2.1 to 2.2.4.

Case 2.2.1: the signal bandwidth is equal to 30kHz.

When the time domain length of RU is related to the length of line code and the repetition number, the time domain length of RU is 2 ^n+m-1 X 4 milliseconds. For example, if n+m=1 (i.e., n=1, m=0), the time domain length of RU is 4ms; if n+m=2 (where n=2 and m=0, or n=1 and m=1), the time domain length of RU is 8ms.

When the time domain length of RU is related to the length of line code and the spreading factor, the time domain length of RU is 2 ^n+l-1 X 4 milliseconds. For example, if n+l=1 (i.e., n=1, l=0), the time domain length of RU is 4ms; if n+l=2 (where n=2 and l=0, or n=1 and l=1), the time domain length of RU The degree is 8ms.

When the time domain length of RU is related to the repetition number and the spreading factor, the time domain length of RU is 2 ^m+l X 4 milliseconds. For example, if m+l=1 (where m=1 and l=0, or m=0 and l=1), the time domain length of RU is 8ms; if m+l=2 (where m=2 and l=0, or m=1 and l=1, or m=0 and l=2), the time domain length of RU is 16ms.

Alternatively, when the time domain length of the RU is related to the line code length and the repetition number, the time domain length of the RU is 2 ^n+m-1 X 2 milliseconds; when the time domain length of RU is related to the length of line code and the spreading factor, the time domain length of RU is 2 ^n+l-1 X 2 milliseconds; when the time domain length of RU is related to the repetition number and the spreading factor, the time domain length of RU is 2 ^m+l X 2 milliseconds.

Case 2.2.2: the signal bandwidth is greater than 30kHz and less than or equal to 90kHz.

When the time domain length of RU is related to the length of line code and the repetition number, the time domain length of RU is 2 ^n+m-1 X 2 milliseconds. For example, if n+m=1 (i.e., n=1, m=0), the time domain length of RU is 2ms; if n+m=2 (where n=2 and m=0, or n=1 and m=1), the time domain length of RU is 4ms.

When the time domain length of RU is related to the length of line code and the spreading factor, the time domain length of RU is 2 ^n+l-1 X 2 milliseconds. For example, if n+l=1 (i.e., n=1, l=0), the time domain length of RU is 2ms; if n+l=2 (where n=2 and l=0, or n=1 and l=1), the time domain length of RU is 4ms.

When the time domain length of RU is related to the repetition number and the spreading factor, the time domain length of RU is 2 ^m+l X 2 milliseconds. For example, if m+l=1 (where m=1 and l=0, or m=0 and l=1), the time domain length of RU is 4ms; if m+l=2 (where m=2 and l=0, or m=1 and l=1, or m=0 and l=2), the time domain length of RU is 8ms.

Case 2.2.3: the signal bandwidth is greater than 90kHz and less than or equal to 180kHz.

When the time domain length of RU is related to the length of line code and the repetition number, the time domain length of RU is 2 ^n+m-1 X 1 millisecond. For example, if n+m=1 (i.e., n=1, m=0), the time domain length of RU is 1ms; if n+m=2 (where n=2 and m=0, or n=1 and m=1), the time domain length of RU is 2ms.

When the time domain length of RU is related to the length of line code and the spreading factor, the time domain length of RU is 2 ^n+l-1 X 1 millisecond. For example, if n+l=1 (i.e., n=1, l=0), the time domain length of RU is 1ms; if n+l=2 (where n=2 and l=0, or n=1 and l=1), the time domain length of RU is 2ms.

When the time domain length of RU is related to the repetition number and the spreading factor, the time domain length of RU is 2 ^m+l X 1 millisecond. For example, if m+l=1 (where m=1 and l=0, or m=0 and l=1), the time domain length of RU is 2ms; if m+l=2 (where m=2 and l=0, or m=1 and l=1, or m=0 and l=2), the time domain length of RU is 4ms.

Case 2.2.4: the signal bandwidth is greater than or equal to 240kHz.

When the time domain length of RU is related to the length of line code and the repetition number, the time domain length of RU is 2 ^n+m-1 X 0.5 milliseconds. For example, if n+m=1 (i.e., n=1, m=0), the time domain length of RU is 0.5ms; if n+m=2 (where n=2 and m=0, or n=1 and m=1), the time domain length of RU is 1ms.

When the time domain length of RU is related to the length of line code and the spreading factor, the time domain length of RU is 2 ^n+l-1 X 0.5 milliseconds. For example, if n+l=1 (i.e., n=1, l=0), the time domain length of RU is 0.5ms; if n+l=2 (where n=2 and l=0, or n=1 and l=1), the time domain length of RU is 1ms.

When the time domain length of RU is related to the repetition number and the spreading factor, the time domain length of RU is 2 ^m+l X 0.5 milliseconds. For example, if m+l=1 (where m=1 and l=0, or m=0 and l=1), the time domain length of RU is 1ms; if m+l=2 (where m=2 and l=0, or m=1 and l=1, or m=0 and l=2), the time domain length of RU is 2ms.

In embodiment 2.3, the time domain length of ru is related to three of the line code length, the repetition number, and the spreading factor.

In this case, ifThe signal bandwidth is equal to 30kHz, and the RU time domain length is 2 ^n+m+l-1 X 4 milliseconds, or 2 ⁿ ^+m+l-1 X 2 milliseconds. If the signal bandwidth is greater than 30kHz and less than or equal to 90kHz, the RU time domain length is 2 ^n+m+l-1 X 2 milliseconds. If the signal bandwidth is greater than 90kHz and less than or equal to 180kHz, the RU time domain length is 2 ^n+m+l-1 X 1 millisecond. If the signal bandwidth is greater than or equal to 240kHz, the RU time domain length is 2 ^n+m+l-1 X 0.5 milliseconds.

This embodiment mode 2.3 includes the following cases 2.3.1 to 2.3.6.

Case 2.3.1: the communication device increases the link budget by increasing the line code length without bit repetition and spreading, i.e. with a repetition number of 1 and a spreading factor of 1, then m= 0,l =0.

In case 2.3.1, the transmission link processing flow of the communication device is as shown in fig. 5, and the communication device performs CRC and FEC on the signal to be transmitted, then adjusts the line code length, and performs ASK, binary phase shift keying (binary phase shift keying, BPSK), and low-pass filtering. The FEC may use a convolutional (conv) code or a Polar code, and the line code may use a manchester code.

Case 2.3.2: the communication device increases the link budget by bit repetition without spreading and increasing the line code length, i.e. the spreading factor is 1 and the line code length is 2, then n=1, l=0.

Case 2.3.3: the communication device increases the link budget by spreading without bit repetition and increasing the line code length, i.e. the number of repetitions is 1 and the line code length is 2, then n=1, m=0.

In both cases 2.3.2 and 2.3.3, the transmission link processing flow of the communication device is as shown in fig. 6, and after the communication device performs CRC, FEC and setting the line code length to 2 on the signal to be transmitted, the communication device configures bit Repetition (Repetition) or configures spreading (Spectrum spreading), and then performs ASK, BPSK, and low-pass filtering.

Case 2.3.4: the communication device increases the link budget by increasing the line code length and bit repetition without spreading, i.e. with a spreading factor of 1, then l=0.

Case 2.3.5: the communication device increases the link budget by increasing the line code length and spreading without performing bit repetition, i.e. the number of repetitions is 1, then m=0.

In both cases 2.3.4 and 2.3.5, the transmission link processing flow of the communication device is similar to that shown in fig. 6, except that in cases 2.3.4 and 2.3.5, the communication device can adjust the line code length according to the link budget or coverage level, instead of setting the direct line code length to 2.

Case 2.3.6: the communication device increases the link budget by bit repetition and spreading without increasing the line code length, i.e. the line code length is 2, then n=1.

In addition, in the above embodiments 2.1 to 2.3, when the signal bandwidth is different from the carrier bandwidth, in the transmission link processing flow of the communication device, the communication device may further perform sample rate conversion (sampling rate conversion) after performing BPSK to implement signal bandwidth adjustment (bandwidth adjustment), as shown in fig. 7.

In an alternative embodiment, there is a signal bandwidth of different value between the signal bandwidths comprised by the first set and the signal bandwidths comprised by the second set; the number of signal bandwidths included in the first set is greater than or equal to the number of signal bandwidths included in the second set. The signal bandwidths included in the first set are uplink candidate signal bandwidths when the carrier bandwidth is the first carrier bandwidth; the signal bandwidths included in the second set are uplink candidate signal bandwidths when the carrier bandwidth is the second carrier bandwidth; the first carrier bandwidth is greater than the second carrier bandwidth.

For example, the first carrier bandwidth is 360kHz and the second carrier bandwidth is 180kHz; the signal bandwidth of the uplink candidate is different from the signal bandwidth of the uplink candidate when the carrier bandwidth is 360kHz, and the number of the signal bandwidths of the uplink candidate when the carrier bandwidth is 360kHz is larger than or equal to the number of the signal bandwidths of the uplink candidate when the carrier bandwidth is 180 kHz.

Optionally, the number of signal bandwidths included in the first set is the same as the number of signal bandwidths included in the second set; the first carrier bandwidth is k times of the second carrier bandwidth, and k is an integer greater than 1; the first set includes a signal bandwidth that is k times the signal bandwidth that the second set includes. For example, the first carrier bandwidth is 360kHz and the second carrier bandwidth is 180kHz; it can be seen that the first carrier bandwidth is 2 times the second carrier bandwidth. If the number of signal bandwidths included in the first set is the same as the number of signal bandwidths included in the second set, and the signal bandwidths included in the second set are: 30kHz, 60kHz, 180kHz, then the first set includes signal bandwidths of: 60kHz, 120kHz, 360kHz.

Optionally, the number of signal bandwidths included in the first set is greater than the number of signal bandwidths included in the second set; the second set is a proper subset of the first set. For example, the first carrier bandwidth is 360kHz and the second carrier bandwidth is 180kHz. If the number of signal bandwidths included in the first set is 4, the number of signal bandwidths is greater than the number of signal bandwidths included in the second set by 3, and the signal bandwidths included in the second set are: 30kHz, 60kHz, 180kHz, then the first set includes 3 of the 4 signal bandwidths of 30kHz, 60kHz, 180kHz, respectively.

In summary, in the method for determining a resource unit, the communication device may determine an RU, where a time domain length of the RU is related to any one or more of a line code length, a repetition number of bit repetition, and a spreading factor. As can be seen, the method defines the RU, and the time-frequency resources can be indicated efficiently based on the defined RU, for example, when uplink transmission or downlink transmission is scheduled or configured, the time-domain starting position or scheduling delay of the time-frequency resources can be indicated efficiently based on the defined RU, and the number of the time-frequency resources (including time-domain length and frequency-domain width) and the like.

In order to implement the functions in the methods provided in the embodiments of the present application, the network device or the terminal device may include a hardware structure and/or a software module, and implement the functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Some of the functions described above are performed in a hardware configuration, a software module, or a combination of hardware and software modules, depending on the specific application of the solution and design constraints.

As shown in fig. 8, an embodiment of the present application provides a communication device 800. The communication device 800 may be a component of a network device (e.g., an integrated circuit, a chip, etc.) or a component of a terminal device (e.g., an integrated circuit, a chip, etc.). The communication device 800 may also be other communication units for implementing the method in the method embodiments of the present application. The communication device 800 may comprise a processing unit 801. Optionally, the communication device 800 may further include a communication unit 802, where the processing unit 801 is configured to control the communication unit 802 to perform data/signaling. Optionally, the communication device 800 may further comprise a storage unit 803.

In one possible design, processing unit 801 is configured to determine a resource unit RU, where a time domain length of the RU is related to any one or more of a line code length, a number of repetitions of a bit repetition, and a spreading factor.

In an alternative embodiment, RU is used for downlink; the time domain length of the RU is also related to the subcarrier spacing employed in the downlink.

In an alternative embodiment, RU is used for upstream; the time domain length of RU is also related to the signal bandwidth employed for uplink; alternatively, the time domain length of the RU is also related to the carrier bandwidth and signal bandwidth employed by the uplink.

The embodiment of the present application and the method for determining the resource unit shown in the foregoing embodiments are based on the same concept, and the technical effects brought by the same concept are also the same, and the specific principle is referred to the description of the foregoing embodiments and is not repeated.

The embodiment of the application also provides a communication device 900, as shown in fig. 9. The communication device 900 may be a network device or a terminal device, a chip system, a processor, or the like that supports the network device to implement the above method, or a chip, a chip system, a processor, or the like that supports the terminal device to implement the above method. The device can be used for realizing the method described in the method embodiment, and can be particularly referred to the description in the method embodiment.

The communication device 900 may include one or more processors 901. The processor 901 may be configured to implement some or all of the functions of the network device or the terminal device described above through logic circuits or running a computer program. The processor 901 may be a general purpose processor or a special purpose processor, etc. For example, it may be a baseband processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or a central processing unit (Central Processing Unit, CPU). The baseband processor may be used to process communication protocols and communication data, and the central processor may be used to control communication devices (e.g., base stations, baseband chips, terminals, terminal chips, DUs or CUs, etc.), execute software programs, and process data of the software programs.

Optionally, the communication device 900 may include one or more memories 902, on which instructions 904 may be stored, which may be executed on the processor 901, to cause the communication device 900 to perform the methods described in the method embodiments above. Optionally, the memory 902 may also have data stored therein. The processor 901 and the memory 902 may be provided separately or may be integrated.

The memory 902 may include, but is not limited to, nonvolatile memory such as Hard Disk Drive (HDD) or Solid State Drive (SSD), random access memory (random access memory, RAM), erasable programmable read-only memory (erasable programmable ROM, EPROM), ROM or portable read-only memory (compact disc read-only memory), and the like.

Optionally, the communication device 900 may further include a transceiver 905, an antenna 906. The transceiver 905 may be referred to as a transceiver unit, a transceiver circuit, or the like, for implementing a transceiver function. The transceiver 905 may include a receiver, which may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function, and a transmitter; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

In one manner, the processor 901 is configured to determine a resource unit RU, where a time domain length of the RU is related to any one or more of a line code length, a number of repetitions of a bit repetition, and a spreading factor.

In another possible design, a transceiver for implementing receive and transmit functions may be included in processor 901. For example, the transceiver may be a transceiver circuit, or an interface circuit. The transceiver circuitry, interface or interface circuitry for implementing the receive and transmit functions may be separate or may be integrated. The transceiver circuit, interface or interface circuit may be used for reading and writing codes/data, or the transceiver circuit, interface or interface circuit may be used for transmitting or transferring signals.

In yet another possible design, the processor 901 may optionally have instructions 903 stored therein, where the instructions 903 run on the processor 901 may cause the communications apparatus 900 to perform the method described in the method embodiments above. Instructions 903 may be solidified in processor 901, in which case processor 901 may be implemented in hardware.

In yet another possible design, communication device 900 may include circuitry that may perform the functions of transmitting or receiving or communicating in the foregoing method embodiments. The processors and transceivers described in embodiments of the present application may be implemented on integrated circuits (integrated circuit, ICs), analog ICs, radio frequency integrated circuits (radio frequency integrated circuit, RFIC), mixed signal ICs, application specific integrated circuits (application specific integrated circuit, ASIC), printed circuit boards (printed circuit board, PCB), electronics, and the like. The processor and transceiver may also be fabricated using a variety of IC process technologies such as complementary metal oxide semiconductor (complementary metal oxide semiconductor, CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The communication apparatus described in the above embodiment may be a network device or a terminal device, but the scope of the communication apparatus described in the embodiment of the present application is not limited thereto, and the structure of the communication apparatus may not be limited by fig. 9. The communication means may be a stand-alone device or may be part of a larger device. For example, the communication device may be:

(1) A stand-alone integrated circuit IC, or chip, or a system-on-a-chip or subsystem;

(2) A set of one or more ICs, optionally including storage means for storing data, instructions;

(3) An ASIC, such as a modem;

(4) Modules that may be embedded within other devices;

(5) Receivers, terminals, smart terminals, cellular telephones, wireless devices, handsets, mobile units, vehicle devices, network devices, cloud devices, artificial intelligence devices, etc.;

(6) Others, and so on.

For the case where the communication device may be a chip or a chip system, reference may be made to the schematic structural diagram of the chip shown in fig. 10. The chip 1000 shown in fig. 10 includes a processor 1001 and an interface 1002. Wherein the number of processors 1001 may be one or more, and the number of interfaces 1002 may be a plurality. The processor 1001 may be a logic circuit, and the interface 1002 may be an input-output interface, an input interface, or an output interface. The chip 1000 may also include a memory 1003.

In one manner, the processor 1001 is configured to determine a resource unit RU, where a time domain length of the RU is related to any one or more of a line code length, a number of repetitions of a bit repetition, and a spreading factor.

The communication device 900 and the chip 1000 in the embodiments of the present application may also perform the implementation manner described in the communication device 800. Those of skill would further appreciate that the various illustrative logical blocks (illustrative logical block) and steps (steps) described in connection with the embodiments herein may be implemented as electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present application.

The embodiment of the present application and the method for determining a resource unit are based on the same concept, and the technical effects brought by the same concept are the same, and the specific principle is referred to the description in the method for determining a resource unit and is not repeated.

Those of skill would further appreciate that the various illustrative logical blocks (illustrative logical block) and steps (steps) described in connection with the embodiments herein may be implemented as electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present application.

The present application also provides a computer readable storage medium storing computer software instructions which, when executed by a communications device, implement the functions of any of the method embodiments described above.

The present application also provides a computer program product for storing computer software instructions which, when executed by a communications device, implement the functions of any of the method embodiments described above.

The present application also provides a computer program which, when run on a computer, implements the functions of any of the method embodiments described above.

In the above embodiments, the implementation may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., SSD), etc.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for determining a resource unit, the method comprising:

determining a resource unit RU;

the time domain length of the RU is related to any one or more of a line code length, a number of repetitions of bit repetition, and a spreading factor.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the time domain length of the RU is proportional to the product of any one or more of the line code length, the number of repetitions, and the spreading factor.

3. The method according to claim 1 or 2, wherein the RU is used for downlink;

the time domain length of the RU is also related to the subcarrier spacing employed for the downlink.

4. A method according to claim 3, wherein the subcarrier spacing is i times the first subcarrier spacing, the i being a positive integer;

The time domain length of the RU is equal to the power of 2,And a product between the first time length;

the power of 2 is determined based on any one or more of the line code length, the number of repetitions, and the spreading factor.

5. The method according to claim 1 or 2, characterized in that the RU is used for uplink;

the time domain length of the RU is also related to the signal bandwidth adopted by the uplink; or,

the time domain length of the RU is also related to the carrier bandwidth and the signal bandwidth employed by the uplink.

6. The method of claim 5, wherein the signal bandwidth is equal to a first threshold or a second threshold;

the time domain length of the RU is equal to a product between a power of 2 and a second time length;

7. The method of claim 6, wherein the step of providing the first layer comprises,

the time domain length of the RU when the value of the signal bandwidth is larger than the first threshold and smaller than the second threshold is equal to the time domain length of the RU when the value of the signal bandwidth is equal to the first threshold or the second threshold;

The first threshold is less than the second threshold.

8. The method according to any of claims 5 to 7, wherein the carrier bandwidth is greater than or equal to 180kHz.

9. The method according to any of claims 5 to 8, wherein the signal bandwidth is an integer multiple of 30 kHz.

10. The method according to any one of claims 5 to 9, wherein,

the signal bandwidths with different values exist between the signal bandwidths included in the first set and the signal bandwidths included in the second set;

the number of signal bandwidths included in the first set is greater than or equal to the number of signal bandwidths included in the second set;

the signal bandwidths included in the first set are the signal bandwidths of the uplink candidates when the carrier bandwidth is the first carrier bandwidth; the signal bandwidths included in the second set are the signal bandwidths of the uplink candidates when the carrier bandwidth is the second carrier bandwidth; the first carrier bandwidth is greater than the second carrier bandwidth.

11. The method of claim 10, wherein the first set comprises the same number of signal bandwidths as the second set;

the first carrier bandwidth is k times of the second carrier bandwidth, and k is an integer greater than 1;

The first set includes signal bandwidths that are k times greater than the signal bandwidths included in the second set.

12. The method according to claim 10 or 11, wherein the first set comprises a greater number of signal bandwidths than the second set;

the second set is a proper subset of the first set.

13. A communication device, the device comprising:

a processing unit for determining a resource unit RU;

14. The apparatus of claim 13, wherein the device comprises a plurality of sensors,

15. The apparatus of claim 13 or 14, wherein the RU is for downlink;

16. The apparatus of claim 15, wherein the subcarrier spacing is i times the first subcarrier spacing, the i being a positive integer;

17. The apparatus of claim 13 or 14, wherein the RU is for upstream;

18. The apparatus of claim 17, wherein the signal bandwidth is equal to a first threshold or a second threshold;

19. The apparatus of claim 18, wherein the device comprises a plurality of sensors,

The first threshold is less than the second threshold.

20. The apparatus of any of claims 17 to 19, wherein the carrier bandwidth is greater than or equal to 180kHz.

21. The apparatus of any of claims 17 to 20, wherein the signal bandwidth is an integer multiple of 30 kHz.

22. The device according to any one of claims 17 to 21, wherein,

23. The apparatus of claim 22, wherein the first set comprises the same number of signal bandwidths as the second set;

24. The apparatus of claim 22 or 23, wherein the first set comprises a greater number of signal bandwidths than the second set;

the second set is a proper subset of the first set.

25. A communication device comprising a memory and a processor;

the memory is used for storing instructions or computer programs;

the processor being configured to execute a computer program or instructions stored in the memory to cause the communication device to perform the method of any one of claims 1 to 12.

26. A computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 12.

27. A computer program product comprising computer instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 12.