Communication method and communication device
The segment parser allocates bit streams into multiple frequency domain sub-blocks, including non-aggregated channels with additional subcarriers, to improve transmission performance in high-frequency WLAN systems by distributing bits more evenly, addressing inefficiencies in existing technologies.
Patent Information
- Application Number
- JP2025528687
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-11-17
- Filing Date
- 2023-06-29
- Publication Date
- 2025-12-03
AI Technical Summary
Existing communication technologies face challenges in efficiently utilizing high-frequency channels, particularly in WLAN systems, due to the limitations of segment parsers in handling non-aggregated channels with additional subcarriers, leading to suboptimal transmission performance.
A communication method and device that employs a segment parser to allocate bit streams into multiple frequency domain sub-blocks, including non-aggregated channels with additional subcarriers, using a cyclic polling mechanism to distribute bits more evenly across these sub-blocks, thereby improving transmission performance.
Enhances transmission performance by evenly distributing bits across frequency domain sub-blocks, particularly in high-frequency scenarios, addressing the inefficiencies of existing segment parsers in handling non-aggregated channels with additional subcarriers.
Smart Images

Figure 2025539121000001_ABST
Abstract
Description
[Technical Field]
[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese Patent Application No. 202211441914.2, entitled "COMMUNICATION METHOD AND COMMUNICATION APPARATUS," filed with the State Intellectual Property Office of China on November 17, 2022, which is incorporated herein by reference in its entirety.
[0002] [Technical field] This application relates to the field of communication technologies, and more particularly to communication methods and devices. [Background technology]
[0003] The development of wireless local area networks (WLANs) has gone through many generations, including sub-7 GHz standards such as 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, and the currently discussed 802.11be, as well as high-frequency standards such as the 802.11ad and 802.11ay standards that operate at approximately 60 GHz. Regarding the channel configurations of high-frequency standards, 802.11ad supports 2.16 GHz channels, while 802.11ay also supports 4.32 GHz, 6.48 GHz, 8.64 GHz, 2.16+2.16 GHz, and 4.32+4.32 GHz channels in addition to the 2.16 GHz channels. How to use a segment parser to perform segment analysis in high-frequency channels is a problem worth considering. Summary of the Invention
[0004] This application provides a communication method and device in which a bit stream can be split into multiple outputs in a high frequency channel.
[0005] According to a first aspect, a communication method is provided. The method may be performed by a communication device, or may be performed by a component (e.g., a chip, a circuit, or a module) within the communication device. This is not limited in this application. Optionally, the component within the communication device is a segment parser. For the purposes of explanation, the following uses an example in which the method is performed by a segment parser.
[0006] The method includes: a segment parser receives an output bitstream from a stream parser; the segment parser allocates the output bitstream to L frequency domain sub-blocks; the L frequency domain sub-blocks are located at high frequencies, and the frequency values of the high frequencies are equal to or greater than 45 GHz, where L is an integer greater than 1.
[0007] Based on the above technical solution, in a high frequency scenario, for example, when the frequency value is 45 GHz or higher, one frequency domain sub-block corresponds to one output branch, and the segment parser allocates the bit stream obtained from the stream parser to the L frequency domain sub-blocks through the L output branches. In this way, by using the segment parser in the high frequency channel for output, the bit stream can be divided into multiple blocks (also called multiple slices or multiple channels).
[0008] Referring to the first aspect, in some implementations of the first aspect, the L frequency domain subblocks include a first frequency domain subblock, the first frequency domain subblock includes a first subcarrier, and the first subcarrier is an additional subcarrier in the non-aggregated channel compared to the aggregated channel.
[0009] Based on the above technical solution, the first frequency domain subblock includes additional subcarriers in the non-aggregated channel compared to the aggregated channel. In this way, the additional subcarriers in the non-aggregated channel compared to the aggregated channel may also correspond to output branches of the segment parser. That is, the segment parser allocates the output bit stream to each frequency domain subblock through an output branch corresponding to each frequency domain subblock.
[0010] Referring to the first aspect, in some implementations of the first aspect, the L frequency domain subblocks further include a second frequency domain subblock, the second frequency domain subblock includes a second subcarrier, and the second subcarrier is not the first subcarrier.
[0011] Referring to the first aspect, in some implementations of the first aspect, the first frequency domain sub-block includes a first subcarrier.
[0012] Based on the above technical solution, the first frequency domain sub-block includes a first subcarrier. In this way, the first subcarrier may independently correspond to one output branch of the segment parser. That is, the segment parser assigns the output bit stream to the first subcarrier through the output branch corresponding to the first subcarrier.
[0013] Referring to the first aspect, in some implementations of the first aspect, the first subcarriers are not contiguous in the frequency domain.
[0014] For example, assume that there are multiple first subcarriers, and that the first subcarriers that are consecutive in the frequency domain are referred to as a first subcarrier group. In this case, the fact that the first subcarriers are not consecutive in the frequency domain may be replaced by the fact that at least two first subcarrier groups are not consecutive in the frequency domain.
[0015] Based on the above technical solution, the first subcarriers included in the first frequency domain subblock are not consecutive in the frequency domain, which is equivalent to the first subcarriers not consecutive in the frequency domain corresponding to one output branch of the segment parser.
[0016] Referring to the first aspect, in some implementations of the first aspect, in addition to the first subcarrier, the first frequency domain subblock further includes a second subcarrier, and the second subcarrier is not the first subcarrier.
[0017] For example, the second subcarrier is a subcarrier in an aggregate channel.
[0018] Based on the above technical solution, the subcarriers corresponding to the first frequency domain subblock may include the subcarriers in the aggregated channel and the first subcarriers, which is equivalent to the subcarriers in the aggregated channel and the first subcarriers corresponding to one output branch of the segment parser.
[0019] Referring to the first aspect, in some implementations of the first aspect, the number of output bits allocated to the L frequency domain sub-blocks by the segment parser may be determined according to the following relationship: S i =N i ·s Meet the following.
[0020] S i is the number of output bits allocated to the ith frequency domain sub-block in one round, and N i is a positive integer obtained by rounding the quotient of the number of subcarriers included in the i-th frequency domain subblock and the preset number of subcarriers;
number
[0021] Referring to the first aspect, in some implementations of the first aspect, the L frequency domain subblocks include one first frequency domain subblock and two second frequency domain subblocks, where the first frequency domain subblock includes z first subcarriers, one second frequency domain subblock includes x1 second subcarriers, and the other second frequency domain subblock includes x2 second subcarriers.
[0022] The numbers of output bits allocated by the segment parser to the first frequency domain sub-block and the two second frequency domain sub-blocks in at least one round are s, N1s, and N2s, respectively.
number
number
[0023] Referring to the first aspect, in some implementations of the first aspect, the segment parser allocates the output bitstream to the L frequency domain sub-blocks in a cyclic polling manner.
[0024] With reference to the first aspect, in some implementations of the first aspect, in at least one round of the segment parser allocating the output bit stream to the L frequency domain sub-blocks in a cyclic polling manner, the bits allocated by the segment parser to at least one of the L frequency domain sub-blocks are the result of being allocated at least twice.
[0025] Based on the above technical solution, the number of bits allocated to the frequency domain sub-blocks by the segment parser in one round is N iIf s, the number of bits allocated to the frequency domain subblock in the round may be obtained by a segment parser that outputs through the output branch corresponding to the frequency domain subblock at least twice. In this way, the bits on each frequency domain subblock may be more distributed, thereby improving transmission performance.
[0026] Referring to the first aspect, in some implementations of the first aspect, each of the L frequency domain sub-blocks corresponds to one interleaver, and the interleaver is configured to interleave bits allocated to the corresponding frequency domain sub-block.
[0027] According to a second aspect, there is provided a communications device configured to perform the method according to the first aspect, and in particular, the device may include units and / or modules configured to perform the method in the first aspect, such as an allocating unit and / or an obtaining unit.
[0028] According to a third aspect, there is provided a computer-readable storage medium storing program code for execution by a device, the program code being used to perform the method according to any one of the implementations of the first aspect.
[0029] According to a fourth aspect, there is provided a computer program product comprising instructions which, when executed on a computer, enable the computer to carry out a method according to any one of the implementations of the first aspect. [Brief explanation of the drawings]
[0030] [Figure 1] 1 is a diagram of a wireless communication system 100 applicable to embodiments of the present application. [Figure 2] 1 is a diagram of a channel configuration in a high frequency standard. [Figure 3]2.16+2.16 GHz (aggregated) channel and 4.32 GHz (non-aggregated) channel. [Figure 4] 1 is a diagram showing the configuration of an existing high-frequency transmission module. [Figure 5] FIG. 10 is a diagram of the output of a segment parser. [Figure 6] FIG. 10 is another diagram of the output of the segment parser. [Figure 7] FIG. 10 is another diagram of the output of the segment parser. [Figure 8] 1 is a diagram of the subcarrier usage method in 802.11be. [Figure 9] 1 is a diagram of 2.16 GHz, 2.16+2.16 GHz, and 4.32 GHz channels in 802.11ay. [Figure 10] 1 is a diagram of 4.32 GHz, 4.32+4.32 GHz, and 8.64 GHz channels in 802.11ay. [Figure 11] 11 is a diagram of a communication method 1100 according to an embodiment of the present application. [Figure 12] This is a diagram of subcarrier group #A. [Figure 13] FIG. 10 is another diagram of subcarrier group #A. [Figure 14] FIG. 1 is a diagram of disaggregation between two high frequency channel elements. [Figure 15] 1 is a diagram of disaggregation between three high frequency channel elements. [Figure 16] FIG. 10 is another illustration of disaggregation between three high frequency channel elements. [Figure 17] FIG. 10 is another illustration of disaggregation between two high frequency channel elements. [Figure 18] FIG. 10 is another illustration of disaggregation between two high frequency channel elements. [Figure 19] 19 is a diagram of a communication device 1900 according to an embodiment of the present application. [Figure 20] FIG. 20 is a diagram of another communication device 2000 according to an embodiment of the present application. [Figure 21]FIG. 21 is a diagram of a chip system 2100 according to an embodiment of the present application. [Figure 22] 22 is a diagram of a communication system 2200 according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION
[0031] The technical solutions of this application are described below with reference to the accompanying drawings.
[0032] The technical solution provided in this application is applicable to a wireless local area network (WLAN) system, and may support IEEE 802.11 related standards, such as the 802.11a / b / g standard, the 802.11n standard, the 802.11ac standard, the 802.11ax standard, the 802.11be standard (also called the Wi-Fi 7 standard) or the Wi-Fi 8 standard, or may be applied to an IEEE high frequency standard, such as the 802.11ad standard or the 802.11ay standard, or may be applied to the 802.15 standard, or may be applied to the 802.11bf standard for sensing. The 802.11n standard is called high throughput (HT), the 802.11ac standard is called very high throughput (VHT), the 802.11ax standard is called high efficient (HE), 802.11be is called extreme high throughput (EHT), the 802.11ad standard is called directional multi-gigabit (DMG), and the 802.11ay standard is called enhanced directional multi-gigabit (EDMG).
[0033] Although the embodiments of this application are mainly described by using an example in which a WLAN network, particularly a network to which the IEEE 802.11 system standard is applied, those skilled in the art will readily understand that various aspects of the embodiments of this application may be extended to other networks using various standards or protocols, such as a high performance radio local area network (HIPERLAN), a wireless wide area network (WWAN), a wireless personal area network (WPAN), or other networks now known or developed in the future. Therefore, regardless of the coverage area and wireless access protocol used, various aspects provided in the embodiments of this application are applicable to any suitable wireless network.
[0034] The technical solutions provided in this application may be applied to various communication systems, such as WLAN communication systems, wireless fidelity (Wi-Fi) systems, 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application may also be applied to future communication systems, such as 6th generation mobile communication systems. The technical solutions provided in this application may also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type communication (MTC), internet of things (IoT) communication systems, or other communication systems.
[0035] For example, FIG. 1 is a diagram of a WLAN communication system 100 applicable to an embodiment of this application. As shown in FIG. 1, the wireless communication system 100 may include at least one access point (AP), for example, AP1 and AP2 shown in FIG. 1. The wireless communication system 100 may further include at least one station (STA), for example, STA1, STA2, and STA3 shown in FIG. 1. The technical solution provided in this application may be applied to communication between access points, for example, communication between AP1 and AP2. The technical solution provided in this application may also be applied to communication between stations, for example, communication between STA2 and STA3. The technical solution provided in this application may also be applied to communication between an access point and a station, for example, communication between AP1 and STA1 and communication between AP1 and STA2.
[0036] An access point may be an access point used by a terminal to access a wired (or wireless) network, and is mainly deployed in homes, buildings, and campuses. A typical coverage radius is from tens of meters to hundreds of meters. Obviously, an access point may alternatively be deployed outdoors. An access point corresponds to a bridge connecting a wired network and a wireless network. The main function of an access point is to connect various wireless network clients together and then connect the wireless network to an Ethernet.
[0037] For example, the access point may be a terminal or a network device having a Wi-Fi chip. The network device may be a server, a router, a switch, a bridge, a computer, a mobile phone, a relay station, an in-vehicle device, a wearable device, a network device in a 5G network, a network device in a future 6G network, a network device in a public land mobile network (PLMN), etc. This is not limited to the embodiments of this application. The access point may also be a device that supports the Wi-Fi standard. For example, the access point may also support one or more standards of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family, such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11ad, and 802.11ay.
[0038] The station may be a wireless communication chip, a wireless sensor, a wireless communication terminal, etc., and may also be referred to as a user, user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile console, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. The station may be a mobile phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, an Internet of Things device, a wearable device, a terminal device in a 5G network, a terminal device in a future 6G network, a terminal device in a PLMN, etc. This is not limited in this embodiment of the application. The station may be a device supporting the WLAN standard. For example, a station may support one or more standards of the IEEE 802.11 family, such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11ad, and 802.11ay.
[0039] For example, the station may be a mobile phone, a tablet computer, a set-top box, a smart television, a smart wearable device, an in-vehicle communication device, a computer, a node or sensor in the internet of things (IoT), a smart camera, a smart remote control, or a smart water or electricity meter in a smart home, a sensor in a smart city, etc.
[0040] The access points and stations may be deployed on land, including indoors or outdoors, handheld, in vehicles, on water, or in airborne aircraft, balloons, and satellites. The scenarios in which the access points and stations are located are not limited by this application.
[0041] The access point or station may include a processor. Optionally, the access point or station may further include a transmitter, a receiver, a memory, etc.
[0042] Communication may be performed between devices (e.g., between APs, between APs and STAs, or between STAs) by using orthogonal frequency division multiplexing (OFDM) technology. In OFDM technology, a frequency domain resource is divided into several sub-resources, and each sub-resource in the frequency domain is called a subcarrier. A subcarrier may also be understood as the smallest granularity of a frequency domain resource, and the frequency difference between adjacent subcarriers is called a subcarrier spacing. The solution of this application may be applied to a system using OFDM technology.
[0043] Description of the Art Related to This Application
[0044] 1. Disaggregated and Aggregated Channels
[0045] The development of WLAN has gone through many generations of standards, including sub-7 GHz standards such as 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, and the currently discussed 802.11be, as well as higher frequency standards such as the 802.11ad and 802.11ay standards, which operate at approximately 60 GHz.
[0046] Regarding the channel configuration of the low-frequency standard, 802.11ax currently supports the following channel configurations: 20 megahertz (MHz), 40 MHz, 80 MHz, 160 MHz, and 80+80 MHz channels. The difference between the 160 MHz channel and the 80+80 MHz channel is that the former is a contiguous frequency band, while the latter two 80 MHz channels may be separated. 802.11be only supports contiguous channels such as 20 MHz, 40 MHz, 80 MHz, 160 MHz, and 320 MHz channels.
[0047] Regarding the channel configuration of the high frequency standards, 802.11ad supports 2.16 gigahertz (GHz) channels, while 802.11ay supports more 2.16 GHz channels, and also supports 4.32 GHz, 6.48 GHz, 8.64 GHz, 2.16+2.16 GHz, and 4.32+4.32 GHz channels.
[0048] For example, Figure 2 is a diagram of a channel configuration in a high-frequency standard. As shown in Figure 2, channel numbers supported by 802.11ad are #1, #2, #3, and #4. Channel numbers supported by 802.11ay are #1 to #29, and channel numbers #1 to #29 may also be referred to as channel identifiers 1 to 29. In Figure 2, channel indexes represent different frequency values, and the frequency values represented by channel indexes 0 to 16 are 57.24 GHz, 58.32 GHz, 59.4 GHz, 60.48 GHz, 61.56 GHz, 62.64 GHz, 63.72 GHz, 64.8 GHz, 65.88 GHz, 66.96 GHz, 68.04 GHz, 69.12 GHz, 70.2 GHz, 71.28 GHz, 72.36 GHz, 73.44 GHz, and 74.52 GHz, respectively. The difference between two adjacent frequency positions is 1.08 GHz.
[0049] Furthermore, in Figure 2, #1, #2, ..., and #29 represent channel numbers and are used to identify channels. Channels #1 to #8 are 2.16 GHz channels, channels #9 to #15 are 4.32 GHz channels, channels #17 to #22 are 6.48 GHz channels, and channels #25 to #29 are 8.64 GHz channels. Currently, the channel numbers supported by the 802.11ad standard are #1, #2, #3, and #4, and the channel numbers supported by the 802.11ay standard are #1 to #29. The channel width of each channel is the frequency difference between the start frequency and the end frequency of the channel.
[0050] Based on the above channels, there may also be an aggregate channel including two or more channels #1 to #29, such as a 2.16+2.16 GHz channel or a 4.32+4.32 GHz channel.
[0051] All of the above channels except the 2.16 GHz channel may be derived from the 2.16 GHz channel. For example, channels #1 to #8 are represented as 8 bits from low frequency to high frequency, with a bit set to 1 to indicate the corresponding channel is occupied.
[0052] A 4.32 GHz channel may be represented as 11000000, 01100000, 00110000, 00011000, 00001100, 00000110, or 00000011.
[0053] The 6.48 GHz channel may be represented as 11100000, 01110000, 00111000, 00011100, 00001110, or 00000111.
[0054] The 8.64 GHz channel may be represented as 11110000, 01111000, 00111100, 00011110, or 00001111.
[0055] The 2.16+2.16 GHz channels may be represented as 11000000, 10100000, 10010000, 01100000, 00101000, ...
[0056] The 4.32+4.32 GHz channels may be, for example, 11110000, 11011000, 11001100, 01101100, 01111000, ...
[0057] The 4.32 GHz channel and the 2.16+2.16 GHz channel are used as examples. It can be seen from the above that both occupy two 2.16 GHz channels but are different from each other. That is, the 2.16+2.16 GHz channel may be understood as two independent (or aggregated) 2.16 GHz channels, while the 4.32 GHz channel is a larger contiguous channel formed by aggregating two 2.16 GHz channels, which is referred to in the standard as a non-aggregated or bonded channel. Because the 2.16+2.16 GHz channel is a channel formed by two independent 2.16 GHz channels, there is no need for a "contiguous" constraint between the channels. "Contiguous" means that there are two consecutive bits set to 1 in the above 8 bits. For the 4.32 GHz channel, the above "contiguous" constraint must be observed to form a larger bonded channel. The principle of the relationship between the 8.64 GHz channel and the 4.32+4.32 GHz channel is similar to that described above. The 8.64 GHz channel is called an unaggregated channel, while the 4.32+4.32 GHz channel is called an aggregated channel and is formed by aggregating two independent 4.32 GHz channels.
[0058] The following describes the differences between aggregated and non-aggregated channels used in 802.11ay.
[0059] In 802.11ay, the supported non-aggregated channels are shown in Table 1. [Table 1] TIFF2025539121000006.tif254170TIFF2025539121000007.tif40170
[0060] For 802.11ay, the supported 2.16+2.16 GHz aggregate channels are shown in Table 2. [Table 2] TIFF2025539121000009.tif254170
[0061] In 802.11ay, the supported 4.32+4.32 GHz aggregate channels are shown in Table 3. [Table 3] TIFF2025539121000011.tif254170
[0062] In the following, a 2.16+2.16 GHz channel (aggregated channel) and a 4.32 GHz channel (non-aggregated channel) are used as examples to specifically explain the difference in subcarrier distribution when the channel width is the same.
[0063] For example, Figure 3 is a diagram of a 2.16+2.16 GHz channel (aggregated channel) and a 4.32 GHz channel (non-aggregated channel). Figure 3(a) is a diagram of the 2.16+2.16 GHz channel, and Figure 3(b) is a diagram of the 4.32 GHz channel. In Figure 3, the shaded area may be considered as the range in which the data subcarriers, pilot subcarriers, and DC subcarriers are located. As shown in Figure 3, the 2.16+2.16 GHz channel includes two independent 2.16 GHz channels. In the 4.32 GHz channel, two consecutive 2.16 GHz channels are considered as a whole for subcarrier distribution.
[0064] In the standard, N is used to describe the size of a contiguous channel. CB The representation where N is equal to 1, 2, 3 or 4 is used. CB N denotes the number of contiguous channel bandwidths. CB is 1, which indicates a 2.16 GHz channel or a 2.16+2.16 GHz channel, and N CB is 2, which means 4.32GHz channel or 4.32+4.32GHz channel, and N CB is 3, which represents the 6.48GHz channel, and N CB A value of 4 represents an 8.64 GHz channel. Table 4 shows the N CB indicates the channel configuration for which is 1, 2, 3 or 4. [Table 4] TIFF2025539121000013.tif40170
[0065] From Table 4, it can be seen that the number of subcarriers in the 2.16 GHz channel is 355. In other words, the number of subcarriers in the aggregate 2.16+2.16 GHz channel (number of DC subcarriers + number of data subcarriers + number of pilot subcarriers) is 710, and the number of subcarriers in the 4.32 GHz channel (number of DC subcarriers + number of data subcarriers + number of pilot subcarriers) is 773. In the 4.32 GHz channel, two consecutive 2.16 GHz channels are considered as a whole for subcarrier distribution, so the 4.32 GHz channel has more subcarriers than the 2.16+2.16 GHz channel. Referring to FIG. 3, as shown in FIG. 3, the shaded area in FIG. 3(b) is larger than the shaded area in FIG. 3(a). Looking only at data subcarriers, the number of data subcarriers corresponding to the 2.16 GHz channel is 336, and the number of data subcarriers corresponding to the 4.32 GHz channel is 734. In other words, when occupying two adjacent channel bandwidths, the non-aggregated 4.32 GHz channel has more data subcarriers than the aggregated 2.16+2.16 GHz channel. Similarly, the numbers of data subcarriers corresponding to the non-aggregated 6.48 GHz channel and the non-aggregated 8.64 GHz channel are 1134 and 1532, respectively, which are also greater than 3*336 and 4*336, respectively. Similarly, the number of data subcarriers corresponding to the non-aggregated 8.64 GHz channel is greater than the number of data subcarriers corresponding to the aggregated 4.32+4.32 GHz channel.
[0066] According to the definition of aggregated and non-aggregated channels, it can be understood that the low frequency channel may be understood as an aggregated channel, or the use of the low frequency channel may be understood as being in an aggregated state.
[0067] 2. Brief description of the transmission procedure in high-frequency OFDM mode
[0068] Figure 4 is a diagram of an existing high-frequency transmission module by taking physical layer protocol data unit (PPDU) transmission as an example. The function of the module in Figure 4 is briefly described as follows:
[0069] (1) Scrambler: performs a scrambling operation on data bits, which can reduce the probability of consecutive 0s and consecutive 1s in a data string.
[0070] (2) Low-density parity check code encoder (LDPC encoder): Encodes data. It can be understood that the LDPC encoding here is merely an example for explanation purposes and that the specific encoding scheme is not limited.
[0071] (3) Stream parser: Splits the bits output by the low-density parity-check code encoder into multiple streams of bit sequences.
[0072] (4) Constellation mapper: Maps bit strings to constellation points.
[0073] (5) Interleaver: Performs subcarrier interleaving within an OFDM symbol.
[0074] (6) Space-time block code (STBC): Spreads spatial streams into space-time streams.
[0075] (7) Preamble builder: Constructs preamble-related symbols in the frequency domain.
[0076] (8) Spatial mapper: Maps the space-time streams to transmission chains. This operation can be performed on a subcarrier-by-subcarrier basis.
[0077] (9) Training builder (TRN builder): Builds symbols related to the training field.
[0078] (10) Inverse discrete Fourier transformation (IDFT): Apply the inverse discrete Fourier transform to the subcarrier block.
[0079] (11) Guard interval (GI) and window insertion: A guard interval and a window are inserted.
[0080] (12) Digital to Analog Converter (DAC) and Radio Frequency (RF): Performs digital-to-analog conversion and maps signals to a specified frequency and bandwidth for transmission.
[0081] It should be noted that the above description of the modules is a simple example for ease of understanding, and does not limit the scope of protection of this application.
[0082] 3. Low Frequency Segment Parser
[0083] In a low-frequency scenario, a segment parser may perform segment parsing on the bit stream. Specifically, the segment parser may divide the bit stream into multiple parallel outputs (alternatively referred to as multiple data segments), with each output corresponding to one frequency domain subblock. In other words, the bit stream may be assigned to multiple frequency domain subblocks by the segment parser, or the segment parser may divide the bit stream into multiple outputs carried on subcarriers corresponding to multiple frequency domain subblocks. The segment parser in 802.11ax and 802.11be is described below.
[0084] 1. Segment Parser in 802.11ax
[0085] Case 1: The resource unit (RU) size is less than or equal to 996.
[0086] An RU may represent a resource unit allocated to a user. For example, an AP communicates with a STA, and data may be transmitted between the AP and the STA by using the allocated RU. An RU may include multiple subcarriers. An RU may be a 26-tone RU, a 52-tone RU, a 106-tone RU, a 242-tone RU, a 484-tone RU, a 996-tone RU, etc. A tone represents a subcarrier. For example, a 996-tone RU represents an RU containing 996 subcarriers. In Case 1, if the size of an RU is 996 or less, this indicates that the number of subcarriers included in the RU is 996 or less.
[0087] In this case, the bandwidth corresponding to the frequency domain subblock is 80 MHz, and the number of subcarriers is 996. Therefore, if the size of the RU is 996 or less, the bit stream corresponds to one output after passing through the segment parser, which is equivalent to bypassing the segment parser. For example, after the bit stream is input to the segment parser, the output bits of the segment parser are y k,l =x k is.
[0088] x k is the kth bit in the coded bits of one OFDM symbol corresponding to the bit stream, where 0≦k≦N CBPSS -1 and N CBPSS is the number of coded bits in one OFDM symbol. l is the index number of the frequency domain subblock. y k,l is the k-th bit of frequency-domain sub-block l.
[0089] For example, Figure 5 is a diagram of the output of a segment parser. As shown in Figure 5, if the size of the RU is 996 or less, after the bitstream (0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20...) is input to the segment parser, the output of the segment parser is 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20.... This is equivalent to bypassing the segment parser.
[0090] Case 2: The size of the RU is greater than 996.
[0091] In case 2, if the size of the RU is greater than 996, this indicates that the number of subcarriers included in the RU is greater than 996.
[0092] In this case, the bandwidth corresponding to the frequency domain subblock is 80 MHz, and the number of subcarriers corresponding to the frequency domain subblock with a bandwidth of 80 MHz is 996. Therefore, if the size of the RU is larger than 996, the bit stream corresponds to multiple outputs after passing through the segment parser. That is, the bit stream is assigned to multiple frequency domain subblocks. For example, after the bit stream is input to the segment parser, the output bits of the segment parser are y k,l =x m is.
[0093] x m is the mth bit in the coded bits of one OFDM symbol corresponding to the bit stream, where 0≦m≦N CBPSS -1. N CBPSS is the number of coded bits in one OFDM symbol.
[0094]
number
number
[0095] l is the index number of the frequency domain sub-block, and the index number of the frequency domain sub-block may start from 0. k,l is the k-th bit of frequency domain subblock l. N BPSCS is the number of coded bits per single carrier per spatial stream.
[0096] For example, Figure 6 is another diagram of the output of the segment parser. As shown in Figure 6, when the RU size is greater than 996, assume that s=2 corresponds to 16-quadrature amplitude modulation (QAM). After the bit stream (0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21...) is input to the segment parser, the segment parser will produce two outputs, namely (0 1)(4 5)(8 9)(12 13)(16 17)(20 21)... and (2 3)(6 7)(10 11)(14 15)(18 19)..., respectively.
[0097] From the above, we can see that when performing segment parsing, the segment parser in 802.11ax allocates the bit stream to one or two frequency domain subblocks with a granularity of 80 MHz. One frequency domain subblock corresponds to 996 subcarriers, and there are 980 data subcarriers in the 996 subcarriers. Two frequency domain subblocks correspond to 2 x 996 subcarriers (2 x 996 subcarriers, there are 2 x 980 data subcarriers).
[0098] 2. Segment Parser in 802.11
[0099] Compared with the segment parser in 802.11ax, the segment parser in 802.11be is mainly modified in the following two aspects:
[0100] (1) The bandwidth varies from 160 MHz to 320 MHz. In this case, the segment parser can support allocating the bitstream to up to four frequency domain sub-blocks with a granularity of 80 MHz. That is, there may be up to four parallel outputs.
[0101] (2) Multiple resource units (multi-RU, MRU) are introduced, i.e., one user can be assigned multiple RUs simultaneously.
[0102] The segment parser parameters in 802.11be are shown in Table 5. [Table 5]
[0103] From Table 5, we can see that the power ratio of the segment parser in 802.11ax is s:s, while the power ratio of the segment parser in 802.11be is 2x996 s:s, as well as other power ratios, i.e., 3x996 s:s:s and 4x996 s:s:s:s. For example, a 484+996-tone MRU includes two output branches, each with a power ratio of s:2s. An output branch corresponds to a frequency domain subblock. In low-frequency scenarios, the output branch, frequency domain subblock, and 80 MHz may be equivalent. Specifically, the segment parser may allocate a bitstream to each frequency domain subblock through an output branch corresponding to each frequency domain subblock.
[0104] In this embodiment of the application, the output ratio is mentioned multiple times. This is described here and will not be described in detail below. The output ratio indicates the ratio of the number of bits corresponding to each output branch in one round. Two output branches are used as an example. In one round, if the number of bits corresponding to the first output branch is s and the number of bits corresponding to the second output branch is 2s, the output ratio of the first output branch to the second output branch is s:2s. In other words, if the output ratio of the first output branch to the second output branch in one round is s:2s, in the output round, the number of bits corresponding to the first output branch is s and the number of bits corresponding to the second output branch is 2s. Below, an example for explanation is provided with reference to FIG. 7.
[0105] For example, Figure 7 is another diagram of the output of a segment parser. As shown in Figure 7, assume that s = 2. The segment parser corresponds to two output branches, the output ratio of the two output branches is s:2s, and the bit stream input to the segment parser is 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20... In this case, in the first round of output, the bits output by the first output branch are (0 1), and the bits output by the second output branch are (2 3 4 5); in the second round of output, the bits output by the first output branch are (6 7), and the bits output by the second output branch are (8 9 10 11), and so on.
[0106] Table 5 further refers to leftover bits. The following uses the 484+996-tone MRU as an example to explain the concept of leftover bits. The 484-tone RU corresponds to 468 data subcarriers, and the 996-tone RU corresponds to 980 data subcarriers, which are output in a ratio of s:2s. After the 484-tone RU completes output, the 996-tone RU correspondingly outputs 980-468*2=44 subcarriers. Therefore, the 996-tone RU correspondingly outputs 44*N subcarriers that are not output. BPSCS u The reason for the value 22 in the case of dual carrier modulation (DCM) is also explained above: in DCM mode, each two subcarriers corresponds to one bit, so 44 subcarriers correspond to 22 bits.
[0107] 4. Solution of this application
[0108] The segment parsers in 802.11ax and 802.11be are described separately above. However, the above segment parsers do not take into account the possibility of newly added subcarriers in high frequency scenarios. The following provides a specific analysis with reference to two figures.
[0109] For example, Figure 8 is a diagram of a subcarrier usage scheme in 802.11be. As shown in Figure 8, assuming that the bandwidth corresponding to a frequency domain subblock in 802.11 is 80 MHz, the number of subcarriers corresponding to the frequency domain subblock is 996. The channels corresponding to the frequency domain subblocks are relatively independent. In other words, when n frequency domain subblocks are used, the number of corresponding subcarriers is n x 996. Figure 8 is used as an example. When two frequency domain subblocks are used, the number of corresponding subcarriers is 2 x 996.
[0110] For example, Figure 9 is a diagram of the 2.16 GHz channel, the 2.16+2.16 GHz channel, and the 4.32 GHz channel in 802.11ay. Referring to Table 4, it can be seen that the 4.32 GHz channel has 773-2*355=63 additional subcarriers (DC subcarriers+data subcarriers+pilot subcarriers) compared to the 2.16+2.16 GHz channel. Regarding data subcarriers, the 4.32 GHz channel has 734-336*2=734-672=62 additional data subcarriers compared to the 2.16+2.16 GHz channel. These additional subcarriers may be referred to as newly added subcarriers. It should be noted that the newly added subcarriers are added to the center, and one subcarrier is removed from the edge in a non-aggregated state.
[0111] For example, Figure 10 is a diagram of the 4.32 GHz channel, the 4.32+4.32 GHz channel, and the 8.64 GHz channel in 802.11ay. Referring to Table 4, it can be seen that the 8.64 GHz channel has 1611-2*773=65 additional subcarriers (DC subcarriers+data subcarriers+pilot subcarriers) compared to the 4.32+4.32 GHz channel. Regarding data subcarriers, the 8.64 GHz channel has 1532-734*2=64 additional data subcarriers compared to the 4.32+4.32 GHz channel. These additional subcarriers may be referred to as newly added subcarriers. It should be noted that the newly added subcarriers are added to the center, and one subcarrier is removed from the edge in a non-aggregated state.
[0112] The above provides two examples with reference to Figures 9 and 10, which are not limited here. Channel division in 802.11ay is used as an example. When the channel element is a 2.16 GHz channel, newly added subcarriers exist in the following channels: (1) 4.32 GHz, (2) 6.48 GHz, (3) 8.64 GHz, and (4) 4.32 + 4.32 GHz. For example, when the channel element is a 4.32 GHz channel, newly added subcarriers exist in the following channels: (1) 6.48 GHz and (2) 8.64 GHz. Furthermore, when the channel element is a 2.16 + 2.16 GHz channel, newly added subcarriers may also be designed between two channel elements. This is not limited. It can be understood that newly added subcarriers are additional subcarriers resulting from aggregation or non-aggregation between two channel elements. Regarding aggregation between channel elements, it is not limited whether the channel elements are in an aggregated state or a non-aggregated state.
[0113] In the case of aggregation between channel elements, the total number of subcarriers and the number of data subcarriers in a channel element may change slightly. In the following, two channel elements #1 are used as an example for illustration.
[0114] For example, the total number of subcarriers of channel element #1 in the aggregated state may be slightly increased or decreased compared to the total number of subcarriers of channel element #1 in the non-aggregated state.
[0115] In another example, the most newly added subcarrier or data subcarrier is located between two aggregated channel elements #1. However, due to changes or adjustments of pilot subcarriers, DC subcarriers, etc., some data subcarriers (referred to as subcarriers #B for distinction) may be further added within the frequency domain range of non-aggregated channel element #1 compared to aggregated channel element #1. Subcarriers #B appearing in the frequency domain range of channel element #1 may belong to a first frequency domain subblock (i.e., the first frequency domain subblock described in the following embodiment) including the newly added subcarriers and be output through an output branch corresponding to the first frequency domain subblock, or may belong to a second frequency domain subblock (i.e., the first frequency domain subblock described in the following embodiment) and be output through an output branch corresponding to the second frequency domain subblock, or may have other designs. This is not limited.
[0116] In another example, in an aggregation scenario between channel elements #1, the data subcarriers within channel element #1 may also be reduced.
[0117] When the segment parser is used in a high frequency scenario, the presence of newly added subcarriers needs to be taken into account.
[0118] This application provides a solution in which output bits of a stream parser are allocated to L frequency domain sub-blocks, the L frequency domain sub-blocks include a first frequency domain sub-block, and the first frequency domain sub-block includes newly added sub-carriers, thereby solving the problem of allocating bits to the newly added sub-carriers.
[0119] For example, Figure 11 is a diagram of a communication method 1100 according to an embodiment of the present application. The method 1100 may include the following steps.
[0120] 1110: Get the output bitstream of the stream parser.
[0121] For example, the coded bits are input to a stream parser, which outputs at least one bitstream, and at least one bitstream is input to a segment parser. For ease of distinction and description, the bitstream output by the stream parser, i.e., the bitstream input to the segment parser, is referred to as the output bitstream.
[0122] 1120: Allocate the output bitstream to L frequency domain sub-blocks, where the L frequency domain sub-blocks are located at high frequencies, the frequency value of the high frequencies is equal to or greater than 45 GHz, and L is an integer greater than 1.
[0123] The method 1100 may be performed by a communication device or by a component (e.g., a chip, circuit, or module) within the communication device, for example, by a segment parser within the communication device. The solution will be described below using an example in which a segment parser performs the method. The following segment parser may be replaced by the communication device.
[0124] The fact that the L frequency domain sub-blocks are located at high frequency may alternatively be replaced by the segment parser being applied to a scenario where the frequency value is 45 GHz or higher, or alternatively by the segment parser being applied to a high frequency scenario, which may alternatively be replaced by a high frequency standard.
[0125] Those skilled in the art should understand the meaning of "high frequency." High frequency may refer to, for example, a frequency band having a frequency value greater than 45 GHz, or in another example, a frequency band having a frequency value greater than 56.16 GHz, such as the frequency values represented by channel indexes 0 to 16 shown in FIG. 2, i.e., 57.24 GHz, 58.32 GHz, 59.4 GHz, 60.48 GHz, 61.56 GHz, 62.64 GHz, 63.72 GHz, 64.8 GHz, 65.88 GHz, 66.96 GHz, 68.04 GHz, 69.12 GHz, 70.2 GHz, 71.28 GHz, 72.36 GHz, 73.44 GHz, 74.52 GHz, etc.
[0126] One frequency-domain subblock may correspond to one output branch of the segment parser, and L frequency-domain subblocks may correspond to L output branches of the segment parser. For example, the bandwidth corresponding to some of the L frequency-domain subblocks may be 80 MHz, or the bandwidth corresponding to some of the L frequency-domain subblocks may be 320 MHz, or the bandwidth corresponding to some of the L frequency-domain subblocks may be 2.16 GHz. It can be understood that the above is an illustrative example and is not limiting. For example, the bandwidth corresponding to some of the L frequency-domain subblocks may be extended based on a multiple of 20 MHz channel granularity, such as 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, 640 MHz, or 1280 MHz, or the bandwidth corresponding to some of the L frequency-domain subblocks may be extended based on a multiple of 2.16 GHz channel granularity, or the bandwidth corresponding to some of the L frequency-domain subblocks may be extended based on other channel granularities.
[0127] It can be understood that at low frequencies, an output branch corresponding to a frequency-domain subblock corresponds to a specific frequency band (e.g., 80 MHz). At high frequencies, the above correspondence relationship may not be established due to the presence of the first subcarrier (i.e., a newly added subcarrier). In this application, for ease of explanation, an example in which one frequency-domain subblock corresponds to one output branch (or one output branch corresponds to one frequency-domain subblock) is mainly used for explanation. These specific correspondence relationships do not limit the scope of protection of this application. For example, a frequency-domain subblock may also correspond to a frequency band. In other examples, a frequency-domain subblock may not have a one-to-one relationship with an output branch. For example, one frequency-domain subblock may correspond to multiple output branches.
[0128] The segment parser's allocation of the output bit stream to the L frequency domain subblocks may alternatively be replaced by the segment parser's allocation of the output bit stream to some or all of the subcarriers corresponding to the L frequency domain subblocks. For simplicity, the following mainly uses subcarriers corresponding to frequency domain subblocks as an example for explanation. It may be understood that the segment parser's allocation of the output bit stream to the subcarriers corresponding to the L frequency domain subblocks may also mean that the segment parser allocates the output bit stream to some of the subcarriers corresponding to the L frequency domain subblocks, or that the segment parser allocates the output bit stream to all of the subcarriers corresponding to the L frequency domain subblocks.
[0129] If possible, after the coded bits are input to the stream parser, at least one output bitstream is output, and one output bitstream (referred to as output bitstream #1 for distinction) in the at least one output bitstream may be input to one segment parser corresponding to output bitstream #1 for segment analysis. Specifically, the segment parser allocates output bitstream #1 to L frequency domain sub-blocks. Each of the at least one output bitstream may be input to a corresponding segment parser for segment analysis.
[0130] In other possible cases, the coded bits are input to a stream parser, and then at least one output bitstream is output, and the at least one output bitstream is input to one segment parser for segment parsing. Specifically, the segment parser allocates the at least one output bitstream to L frequency domain sub-blocks.
[0131] Optionally, the L frequency domain subblocks include a first frequency domain subblock, the first frequency domain subblock including a first subcarrier, the first subcarrier being an additional subcarrier in the non-aggregated channel compared to the aggregated channel, or a subcarrier position (number) corresponding to the first subcarrier being an available subcarrier position in the non-aggregated channel but an unavailable subcarrier position in the aggregated channel. The first frequency domain subblock including the first subcarrier may alternatively be replaced with the first frequency domain subblock corresponding to the first subcarrier.
[0132] Further optionally, the L frequency domain subblocks include a second frequency domain subblock, the second frequency domain subblock including a second subcarrier, the second subcarrier not being the first subcarrier, or the subcarrier position corresponding to the second subcarrier is an available subcarrier position in both the non-aggregated channel and the aggregated channel. For example, the second subcarrier is a subcarrier in the aggregated channel, e.g., some or all of the subcarriers in the aggregated channel. The second frequency domain subblock including the second subcarrier may alternatively be replaced with the second frequency domain subblock corresponding to the second subcarrier.
[0133] In this embodiment of the present application, for the sake of distinction, a frequency domain subblock including a first subcarrier is referred to as a first frequency domain subblock, and a frequency domain subblock not including a first subcarrier is referred to as a second frequency domain subblock. Furthermore, the first frequency domain subblock and the second frequency domain subblock are named for the sake of distinction, and the names of the first frequency domain subblock and the second frequency domain subblock do not limit the scope of protection of the embodiment of the present application.
[0134] The first subcarrier is an additional subcarrier in the non-aggregated channel compared to the aggregated channel, and the first subcarrier is the newly added subcarrier described above, for example, the newly added subcarrier shown in Figure 9 or Figure 10.
[0135] In one example, the additional subcarrier in the non-aggregated channel compared to the aggregated channel may be an additional data subcarrier in the non-aggregated channel compared to the aggregated channel. Figure 9 is used as an example. The non-aggregated channel is a 4.32 GHz channel, the aggregated channel is a 2.16+2.16 GHz channel, and the first subcarrier is an additional data subcarrier in the 4.32 GHz channel compared to the 2.16+2.16 GHz channel. Figure 10 is used as another example. The non-aggregated channel is an 8.64 GHz channel, the aggregated channel is a 4.32+4.32 GHz channel, and the first subcarrier is an additional data subcarrier in the 8.64 GHz channel compared to the 4.32+4.32 GHz channel.
[0136] In another example, the additional subcarriers in the non-aggregated channel compared to the aggregated channel may be the total subcarriers in the non-aggregated channel compared to the aggregated channel. Figure 9 is used as an example. The non-aggregated channel is a 4.32 GHz channel, the aggregated channel is a 2.16 + 2.16 GHz channel, and the first subcarrier is the additional total subcarriers in the 4.32 GHz channel compared to the 2.16 + 2.16 GHz channel, i.e., the DC subcarrier + the data subcarrier + the pilot subcarrier. Figure 10 is used as another example. The non-aggregated channel is an 8.64 GHz channel, the aggregated channel is a 4.32 + 4.32 GHz channel, and the first subcarrier is the additional total subcarriers in the 8.64 GHz channel compared to the 4.32 + 4.32 GHz channel, i.e., the DC subcarrier + the data subcarrier + the pilot subcarrier.
[0137] The first subcarrier being an additional subcarrier in a non-aggregated channel compared to an aggregated channel may be, for example, replaced with the first subcarrier being an additional subcarrier for non-aggregation between high-frequency channel elements compared to aggregation between high-frequency channel elements. The high-frequency channel elements may be, for example, 2.16 GHz channels (or channels extended based on a multiple of 2.16 GHz channel granularity), 4.32 GHz channels (or channels extended based on a multiple of 4.32 GHz channel granularity), 6.48 GHz channels (or channels extended based on a multiple of 6.48 GHz channel granularity), 8.64 GHz channels (or channels extended based on a multiple of 8.64 GHz channel granularity), etc. In one example, the first subcarrier being an additional subcarrier for non-aggregation between high-frequency channel elements compared to aggregation between high-frequency channel elements may be, for example, an additional subcarrier within a frequency domain range for non-aggregation between high-frequency channel elements compared to aggregation between high-frequency channel elements, e.g., located in the center. In another example, the first subcarrier being an additional subcarrier for non-aggregation between high-frequency channel elements compared to aggregation between high-frequency channel elements may be an additional subcarrier within any frequency domain range for non-aggregation between high-frequency channel elements compared to aggregation between high-frequency channel elements, for example, an additional subcarrier within a frequency domain range for non-aggregation between high-frequency channel elements compared to aggregation between high-frequency channel elements, and a newly added subcarrier that is not within the frequency domain range (e.g., subcarrier #B above). In the case of non-aggregation between high-frequency channel elements, it is not limited whether the high-frequency channel elements are in an aggregated state or a non-aggregated state.
[0138] For ease of understanding, the following mainly uses an example in which the additional subcarrier for non-aggregation between high-frequency channel elements is the first subcarrier compared to aggregation between high-frequency channel elements. In the following, it can be understood that non-aggregation between high-frequency channel elements may be replaced with a non-aggregated channel, and aggregation between high-frequency channel elements may be replaced with an aggregated channel.
[0139] For ease of distinction and description, a first subcarrier is hereinafter referred to as subcarrier #A, and multiple subcarriers #A are hereinafter referred to as a group of subcarriers, e.g., subcarrier group #A. The meaning of subcarrier group #A may be as follows: additional subcarriers for non-aggregation between adjacent high-frequency channel elements compared to aggregation between adjacent high-frequency channel elements may correspond to one subcarrier group #A, or subcarriers at a channel boundary corresponding to adjacent high-frequency channel elements may correspond to one subcarrier group #A, or consecutive first subcarriers in the frequency domain may correspond to one subcarrier group #A. Furthermore, for example, a first frequency-domain subblock may include at least one subcarrier group #A.
[0140] For example, FIG. 12 is a diagram of subcarrier group #A. As shown in FIG. 12(a), assume there are two high-frequency channel elements, which are referred to as high-frequency channel element #1 and high-frequency channel element #2, respectively. In the case of aggregation between high-frequency channel element #1 and high-frequency channel element #2, the number of data subcarriers corresponding to high-frequency channel element #1 (i.e., the shaded area) is x1, and the number of data subcarriers corresponding to high-frequency channel element #2 (i.e., the shaded area) is x2. As shown in FIG. 12(b), the number of corresponding subcarriers for aggregation between high-frequency channel element #1 and high-frequency channel element #2 is x1+x2. As shown in FIG. 12(c), the number of corresponding subcarriers for non-aggregation between high-frequency channel element #1 and high-frequency channel element #2 is (x1+x2)+z. From a comparison between (b) and (c) of Figure 12, it can be seen that the non-aggregated channel (i.e., in the case of non-aggregation between high-frequency channel elements) has z additional subcarriers compared to the aggregated channel (i.e., in the case of aggregation between high-frequency channel elements), and the z subcarriers are z subcarriers #A, and the z subcarriers #A may be referred to as one subcarrier group #A.
[0141] 12(c) is used as an example. There is one first frequency domain subblock, i.e., a frequency domain subblock including z subcarriers #A (i.e., subcarrier group #A), and there are two second frequency domain subblocks, i.e., frequency domain subblock #1 corresponding to high-frequency channel element #1 (or a frequency domain subblock including x1 subcarriers) and frequency domain subblock #2 corresponding to high-frequency channel element #2 (or a frequency domain subblock including x2 subcarriers). In the example shown in FIG. 12(c), L=3, L1=1, and L2=2, and it can be seen that the L frequency domain subblocks are frequency domain subblock #1, frequency domain subblock #2, and the first frequency domain subblock including z subcarriers #A, respectively.
[0142] It can be understood that the values of x1 and x2 may or may not be equal, this is not a limitation.
[0143] For example, Figure 13 is another diagram of subcarrier group #A. As shown in Figure 13(a), assume that there are three high-frequency channel elements, which are denoted as high-frequency channel element #1, high-frequency channel element #2, and high-frequency channel element #3, respectively. In the case of aggregation between high-frequency channel element #1, high-frequency channel element #2, and high-frequency channel element #3, the number of data subcarriers corresponding to high-frequency channel element #1 (i.e., the shaded area) is x1, the number of data subcarriers corresponding to high-frequency channel element #2 (i.e., the shaded area) is x2, and the number of data subcarriers corresponding to high-frequency channel element #3 (i.e., the shaded area) is x3. As shown in Figure 13(b), the number of subcarriers corresponding to the aggregated channel for aggregation between high-frequency channel element #1, high-frequency channel element #2, and high-frequency channel element #3 is x1 + x2 + x3. As shown in (c) of FIG. 13, the number of subcarriers corresponding to the non-aggregated channel for non-aggregation between high-frequency channel element #1, high-frequency channel element #2, and high-frequency channel element #3 is (x1 + x2 + x3) + z1 + z2. A comparison between (b) and (c) of FIG. 13 reveals that the non-aggregated channel (i.e., the case of non-aggregation between high-frequency channel elements) has (z1 + z2) additional subcarriers compared to the aggregated channel (i.e., the case of aggregation between high-frequency channel elements). The z1 subcarriers are z1 subcarriers #A, and the z1 subcarriers #A may be referred to as one subcarrier group #A. The z2 subcarriers are z2 subcarriers #A, and the z2 subcarriers #A may be referred to as one subcarrier group #A. In other words, the example shown in (c) of FIG. 13 includes two subcarrier groups #A: a subcarrier group #A corresponding to z1 subcarriers #A and a subcarrier group #A corresponding to z2 subcarriers #A.
[0144] 13(c) is used as an example. There are two first frequency domain subblocks, i.e., a frequency domain subblock including z1 subcarriers #A (i.e., one subcarrier group #A) and a frequency domain subblock including z2 subcarriers #A (i.e., the other subcarrier group #A), and there are three second frequency domain subblocks, i.e., a frequency domain subblock #1 corresponding to high-frequency channel element #1 (or a frequency domain subblock including x1 subcarriers), a frequency domain subblock #2 corresponding to high-frequency channel element #2 (or a frequency domain subblock including x2 subcarriers), and a frequency domain subblock #3 corresponding to high-frequency channel element #3 (or a frequency domain subblock including x3 subcarriers). In the example shown in (c) of Figure 12, L = 5, L1 = 2, and L2 = 3, and it can be seen that the L frequency domain subblocks are frequency domain subblock #1, frequency domain subblock #2, frequency domain subblock #3, one first frequency domain subblock including z1 subcarriers #A, and the other first frequency domain subblock including z2 subcarriers #A, respectively.
[0145] It can be understood that the values of x1, x2, and x3 may all be equal, or may be partially equal, or may be completely different. This is not a limitation. The values of z1 and z2 may be equal or unequal. This is not a limitation.
[0146] It may be further understood that in the examples shown in (c) of Figure 12 or (c) of Figure 13, one subcarrier group #A corresponds to one first frequency domain subblock, or one first frequency domain subblock may be replaced with one subcarrier group #A.
[0147] The first frequency domain sub-block may include the following two solution designs:
[0148] Solution 1: The first frequency domain sub-block includes subcarrier #A.
[0149] Optionally, in this solution, the L frequency domain sub-blocks may include at least one first frequency domain sub-block and at least one second frequency domain sub-block. In step 1120, the segment parser allocates the output bitstream to the at least one first frequency domain sub-block and the at least one second frequency domain sub-block.
[0150] Below, we will explain two implementation methods that can be applied to Solution 1.
[0151] In a first possible implementation, one subcarrier group #A is one first frequency domain subblock, and one first frequency domain subblock corresponds to one output branch of the segment parser. Based on this implementation, each subcarrier group #A corresponds to one output branch of the segment parser.
[0152] Based on this implementation scheme, assuming there are Z subcarrier groups #A, the Z subcarrier groups #A correspond to Z first frequency-domain sub-blocks, the Z first frequency-domain sub-blocks correspond to Z output branches of the segment parser, and each of the Z first frequency-domain sub-blocks corresponds to one output branch of the segment parser.
[0153] For ease of understanding, the first possible implementation scheme will be described below with reference to two examples.
[0154] Example 1: Assume that there are two second frequency-domain subblocks, as shown in (c) of FIG. 12. In this example, the two second frequency-domain subblocks correspond to one subcarrier group #A. Since one subcarrier group #A corresponds to one first frequency-domain subblock, L=3. The L frequency-domain subblocks include two second frequency-domain subblocks and one first frequency-domain subblock. The two second frequency-domain subblocks correspond to two output branches, and the first frequency-domain subblock (or subcarrier group #A) corresponds to one output branch.
[0155] For example, FIG. 14 is a diagram of non-aggregation between two high-frequency channel elements. In the case of non-aggregation between two high-frequency channel elements, there may be two second frequency-domain subblocks and one first frequency-domain subblock. For distinction, the two second frequency-domain subblocks are referred to as frequency-domain subblock #1 and frequency-domain subblock #2, respectively. The number of data subcarriers corresponding to frequency-domain subblock #1 is x1, and the number of data subcarriers corresponding to frequency-domain subblock #2 is x2. As shown in FIG. 14, for a non-aggregation channel (i.e., in the case of non-aggregation between two high-frequency channel elements), due to the existence of subcarrier group #A (i.e., one subcarrier group #A including z subcarriers #A), the two second frequency-domain subblocks and subcarrier group #A (i.e., one first frequency-domain subblock) correspond to three output branches. For the sake of distinction, the output branch corresponding to frequency domain subblock #1 is referred to as the first output branch, the output branch corresponding to subcarrier group #A is referred to as the second output branch, and the output branch corresponding to frequency domain subblock #2 is referred to as the third output branch.
[0156] For example, as shown in FIG. 14, after a bit stream (0 1 2 3 4 5 6 7...) is input to the segment parser, the segment parser assigns the bit stream to frequency domain subblock #1, frequency domain subblock #2, and subcarrier group #A (i.e., one first frequency domain subblock). Specifically, the segment parser outputs bits to subcarriers corresponding to frequency domain subblock #1 (i.e., x1 subcarriers) through the first output branch, outputs bits to subcarrier group #A (i.e., z subcarriers) through the second output branch, and outputs bits to subcarriers corresponding to frequency domain subblock #2 (i.e., x2 subcarriers) through the third output branch. If each subcarrier corresponds to one bit, the final ratio of the number of bits corresponding to the three output branches is x1:z:x2. The specific bits output by each output branch will be described in detail below.
[0157] In the case of aggregation between high frequency channel elements, due to the absence of subcarrier group #A, there are two frequency domain subblocks (i.e., two second frequency domain subblocks), and it can be understood that the two frequency domain subblocks correspond to two output branches, i.e., the first output branch corresponding to frequency domain subblock #1 and the third output branch corresponding to frequency domain subblock #2.
[0158] 14, it can be further understood that the values of x1 and x2 may or may not be equal. This is not a limitation.
[0159] Example 2: Assume that there are three high-frequency channel elements, as shown in (c) of FIG. 13. In this example, the three high-frequency channel elements correspond to two subcarrier groups #A. Since one subcarrier group #A corresponds to one first frequency-domain subblock, L=5. The L frequency-domain subblocks include three second frequency-domain subblocks and two first frequency-domain subblocks. The three second frequency-domain subblocks correspond to three output branches, and the two first frequency-domain subblocks (or two subcarrier groups #A) correspond to two output branches.
[0160] For example, FIG. 15 is a diagram of non-aggregation between three high-frequency channel elements. In the case of non-aggregation between three high-frequency channel elements, three second frequency-domain subblocks and two first frequency-domain subblocks may exist. For distinction, the three second frequency-domain subblocks are referred to as frequency-domain subblock #1, frequency-domain subblock #2, and frequency-domain subblock #3, respectively. The number of data subcarriers corresponding to frequency-domain subblock #1 is x1, the number of data subcarriers corresponding to frequency-domain subblock #2 is x2, and the number of data subcarriers corresponding to frequency-domain subblock #3 is x3. As shown in FIG. 15, for the non-aggregation channel (i.e., in the case of non-aggregation between three high-frequency channel elements), due to the presence of subcarrier groups #A (i.e., one subcarrier group #A including z1 subcarriers #A and one subcarrier group #A including z2 subcarriers #A), the three second frequency-domain subblocks and two subcarrier groups #A (i.e., two first frequency-domain subblocks) correspond to five output branches. For the purpose of distinction, the output branch corresponding to frequency domain subblock #1 is referred to as the first output branch, the output branch corresponding to subcarrier group #A containing z1 subcarriers #A is referred to as the second output branch, the output branch corresponding to frequency domain subblock #2 is referred to as the third output branch, the output branch corresponding to subcarrier group #A containing z2 subcarriers #A is referred to as the fourth output branch, and the output branch corresponding to frequency domain subblock #3 is referred to as the fifth output branch.
[0161] For example, as shown in FIG. 15, after a bit stream (0 1 2 3 4 5 6 7...) is input to the segment parser, the segment parser allocates the bit stream to frequency domain subblock #1, frequency domain subblock #2, frequency domain subblock #3, and subcarrier group #A (i.e., two first frequency domain subblocks). Specifically, the segment parser outputs bits to subcarriers corresponding to frequency domain subblock #1 (i.e., x1 subcarriers) through a first output branch, outputs bits to subcarrier group #A including z1 subcarriers #A through a second output branch, outputs bits to subcarriers corresponding to frequency domain subblock #2 (i.e., x2 subcarriers) through a third output branch, outputs bits to subcarrier group #A including z2 subcarriers #A through a fourth output branch, and outputs bits to subcarriers corresponding to frequency domain subblock #3 (i.e., x3 subcarriers) through a fifth output branch. If each subcarrier corresponds to one bit, the final ratio of the number of bits corresponding to the five output branches is x1:z1:x2:z2:x3.
[0162] In the case of aggregation between high-frequency channel elements, due to the absence of subcarrier group #A, there are three frequency-domain subblocks (i.e., three second frequency-domain subblocks), and it can be seen that the three frequency-domain subblocks correspond to three output branches, namely, the first output branch corresponding to frequency-domain subblock #1, the third output branch corresponding to frequency-domain subblock #2, and the fifth output branch corresponding to frequency-domain subblock #3.
[0163] It can be further understood that the values of x1, x2, and x3 may all be equal, or may be partially equal, or may be completely different. This is not a limitation. The values of z1 and z2 may be equal or unequal. This is not a limitation.
[0164] The above describes the cases of two high-frequency channel elements and three high-frequency channel elements separately with reference to Example 1 and Example 2. It can be understood that the above is an illustrative example and the number of high-frequency channel elements is not limited. For example, in the case of non-aggregation between four high-frequency channel elements, there may be four second frequency domain subblocks and three subcarrier groups #A (i.e., three first frequency domain subblocks). Therefore, the four second frequency domain subblocks and three subcarrier groups #A correspond to a total of seven output branches.
[0165] In a second possible implementation, the plurality of subcarrier groups #A are one first frequency domain subblock, and one first frequency domain subblock corresponds to one output branch of the segment parser. Based on this implementation, the plurality of subcarrier groups #A correspond to one output branch of the segment parser.
[0166] Optionally, based on this implementation, the subcarriers #A are not contiguous in the frequency domain. In other words, the subcarriers #A forming the first frequency domain subblock are not contiguous in the frequency domain. The fact that the subcarriers #A are not contiguous in the frequency domain may indicate that at least two of the multiple subcarriers #A are not contiguous in the frequency domain. Details will not be described below. For example, the first frequency domain subblock may include subcarriers #A that are not contiguous in the frequency domain. In other words, the first frequency domain subblock may include at least two subcarrier groups #A, where the subcarriers in each subcarrier group #A are contiguous in the frequency domain, and the two subcarrier groups #A are not contiguous in the frequency domain.
[0167] For ease of understanding, the second possible implementation will be described below with reference to an example.
[0168] Assume that there are three high-frequency channel elements, as shown in (c) of Figure 13. In this example, the three high-frequency channel elements correspond to two subcarrier groups #A. Since multiple subcarrier groups #A correspond to one first frequency-domain subblock, L=4, L1=1, and L2=3. That is, the L frequency-domain subblocks include three second frequency-domain subblocks corresponding to the three high-frequency channel elements and one first frequency-domain subblock. The three second frequency-domain subblocks correspond to three output branches, and the first frequency-domain subblock (or two subcarrier groups #A) corresponds to one output branch.
[0169] For example, FIG. 16 is another diagram of non-aggregation among three high-frequency channel elements. In the case of non-aggregation among three high-frequency channel elements, three second frequency-domain subblocks and one first frequency-domain subblock may exist. For distinction, the three second frequency-domain subblocks are referred to as frequency-domain subblock #1, frequency-domain subblock #2, and frequency-domain subblock #3, respectively. The number of data subcarriers corresponding to frequency-domain subblock #1 is x1, the number of data subcarriers corresponding to frequency-domain subblock #2 is x2, and the number of data subcarriers corresponding to frequency-domain subblock #3 is x3. As shown in FIG. 16, for the non-aggregation channel (i.e., in the case of non-aggregation among three high-frequency channel elements), due to the presence of subcarrier groups #A (i.e., one subcarrier group #A including z1 subcarriers #A and one subcarrier group #A including z2 subcarriers #A), three second frequency-domain subblocks and two subcarrier groups #A (i.e., one first frequency-domain subblock) correspond to four output branches. The subcarriers corresponding to the first frequency-domain subblock include z1 subcarriers #A and z2 subcarriers #A, and the z1 subcarriers #A and z2 subcarriers #A are not consecutive in the frequency domain. For the sake of distinction, the output branch corresponding to frequency-domain subblock #1 is called the first output branch, the output branch corresponding to the first frequency-domain subblock including z1 subcarriers #A and z2 subcarriers #A is called the second output branch, the output branch corresponding to frequency-domain subblock #2 is called the third output branch, and the output branch corresponding to frequency-domain subblock #3 is called the fourth output branch.
[0170] For example, as shown in FIG. 16, after a bit stream (0 1 2 3 4 5 6 7...) is input to the segment parser, the segment parser assigns the bit stream to frequency domain subblock #1, frequency domain subblock #2, frequency domain subblock #3, and a first frequency domain subblock including z1 subcarriers #A and z2 subcarriers #A. Specifically, the segment parser outputs bits to subcarriers corresponding to frequency domain subblock #1 (i.e., x1 subcarriers) through a first output branch, outputs bits to the first frequency domain subblock including z1 subcarriers #A and z2 subcarriers #A through a second output branch, outputs bits to subcarriers corresponding to frequency domain subblock #2 (i.e., x2 subcarriers) through a third output branch, and outputs bits to subcarriers corresponding to frequency domain subblock #3 (i.e., x3 subcarriers) through a fourth output branch. If each subcarrier corresponds to one bit, the final ratio of the number of bits corresponding to the four output branches is x1:(z1+z2):x2:x3.
[0171] In the case of aggregation between high-frequency channel elements, due to the absence of subcarrier group #A, there are three frequency-domain subblocks (i.e., three second frequency-domain subblocks), and it can be seen that the three frequency-domain subblocks correspond to three output branches, i.e., the first output branch corresponding to frequency-domain subblock #1, the third output branch corresponding to frequency-domain subblock #2, and the fourth output branch corresponding to frequency-domain subblock #3.
[0172] It can be further understood that the values of x1, x2, and x3 may all be equal, or may be partially equal, or may be completely different. This is not a limitation. The values of z1 and z2 may be equal or unequal. This is not a limitation.
[0173] It can be further understood that the above description is given by using an example in which the output branch corresponding to the first frequency-domain sub-block including z1 subcarriers #A and z2 subcarriers #A is the second output branch. This is not limited here. For example, the output branch corresponding to the first frequency-domain sub-block may alternatively be the first output branch, the third output branch, or the fourth output branch.
[0174] The above describes the case of three high-frequency channel elements. It can be understood that the above is an illustrative example and the number of high-frequency channel elements is not limited. For example, in the case of disaggregation between four high-frequency channel elements, there are four second frequency-domain subblocks and three subcarrier groups #A, and the three subcarrier groups #A correspond to one first frequency-domain subblock. Therefore, the four second frequency-domain subblocks and three subcarrier groups #A correspond to a total of five output branches.
[0175] Solution 2: In addition to the first subcarrier, the first frequency domain subblock further includes a second subcarrier, for which see the above description.
[0176] Specifically, the first frequency domain subblock includes subcarrier #A and a second subcarrier (eg, a subcarrier in an aggregated channel).
[0177] Based on this solution, the maximum number of data subcarriers corresponding to a frequency domain subblock may be adjusted based on the number of subcarriers #A, so that no further output branches of the segment parser need to be added for subcarriers #A.
[0178] Optionally, in this solution, the L frequency domain sub-blocks may include at least one first frequency domain sub-block and at least one second frequency domain sub-block. In step 1120, the segment parser allocates the output bit stream to the at least one first frequency domain sub-block and the at least one second frequency domain sub-block. Alternatively, optionally, in this solution, the L frequency domain sub-blocks may include the L first frequency domain sub-blocks. In step 1120, the segment parser allocates the output bit stream to the L first frequency domain sub-blocks.
[0179] A specific example of Solution 2 will be described below with reference to FIG.
[0180] For example, FIG. 17 is another diagram of disaggregation between two high-frequency channel elements. In the case of disaggregation between two high-frequency channel elements, two second frequency-domain subblocks may exist. For distinction, the two second frequency-domain subblocks are referred to as frequency-domain subblock #1 and frequency-domain subblock #2, respectively. In the case of disaggregation between two high-frequency channel elements, the number of data subcarriers corresponding to frequency-domain subblock #1 is x1, and the number of data subcarriers corresponding to frequency-domain subblock #2 is x2. In the case of disaggregation between two high-frequency channel elements, it is assumed that there is one subcarrier group #A, and that subcarrier group #A includes z subcarriers #A. For distinction, the output branch corresponding to frequency-domain subblock #1 is referred to as the first output branch, and the output branch corresponding to frequency-domain subblock #2 is referred to as the second output branch.
[0181] For example, as shown in FIG. 17, in the case of non-aggregation between two high-frequency channel elements, z subcarriers #A may be assigned to existing output branches. For example, z1 subcarriers #A in subcarrier group #A are assigned to the first output branch corresponding to frequency-domain subblock #1, and z2 subcarriers #A in subcarrier group #A are assigned to the second output branch corresponding to frequency-domain subblock #2. In this case, two first frequency-domain subblocks are included, and the subcarriers corresponding to one first frequency-domain subblock include z1 subcarriers #A and x1 subcarriers, while the subcarriers corresponding to the other first frequency-domain subblock include z2 subcarriers #A and x2 subcarriers. After the bit stream (0 1 2 3 4 5 6 7...) is input to the segment parser, the segment parser assigns the bit stream to the two first frequency-domain subblocks. Specifically, the segment parser outputs bits to one first frequency-domain sub-block including x1 subcarriers and z1 subcarriers #A through a first output branch, and the segment parser outputs bits to another first frequency-domain sub-block including x2 subcarriers and z2 subcarriers #A through a second output branch, where z1 is equal to or approximately equal to z2 in a possible implementation.
[0182] In the example shown in Figure 17, L = 2, and it can be understood that the L frequency domain subblocks are a first frequency domain subblock including x1 subcarriers and z1 subcarriers #A, and a first frequency domain subblock including x2 subcarriers and z2 subcarriers #A, respectively.
[0183] Due to the addition of the first subcarrier (i.e., the newly added subcarrier), the number of subcarriers (e.g., data subcarriers, or total subcarriers (i.e., DC subcarriers + data subcarriers + pilot subcarriers)) corresponding to the frequency domain subblock may change. In the following, using data subcarriers as an example, three methods of the maximum number of data subcarriers corresponding to the frequency domain subblock will be described.
[0184] Scheme 1: For aggregated channels (ie, aggregation among high-frequency channel elements) and non-aggregated channels (ie, non-aggregation among high-frequency channel elements), the maximum number of data subcarriers supported by a frequency-domain subblock is different.
[0185] For example, the maximum number of data subcarriers supported by a frequency domain subblock in the case of aggregation between high frequency channel elements is a, and the maximum number of data subcarriers supported by a frequency domain subblock in the case of non-aggregation between high frequency channel elements is a+t, where t is an integer greater than or equal to 1.
[0186] The specific value of t is not limited. For example, in the example shown in FIG.
number
number
number
[0187] It can be understood that the above example is described by using an example in which the maximum number of supported data subcarriers is different in the cases of aggregation and non-aggregation between high-frequency channel elements, which is not limited here. For example, the maximum number of supported data subcarriers may alternatively be different in the cases of aggregation and non-aggregation between some high-frequency channel elements.
[0188] Scheme 2: The maximum number of data subcarriers supported by a frequency domain subblock is a+t.
[0189] Based on Scheme 2, regardless of aggregation or non-aggregation among high-frequency channel elements, the maximum number of data subcarriers supported by a frequency-domain subblock is x+t.
[0190] Scheme 3: The maximum number of data subcarriers supported by a frequency domain subblock is related to the channel bandwidth and / or subcarrier spacing corresponding to the frequency domain subblock.
[0191] For example, the channel corresponding to frequency domain subblock #1 is channel #1, and the maximum number of data subcarriers supported by frequency domain subblock #1 is equal to the total number of data subcarriers, pilot subcarriers, and DC subcarriers on channel #1.
[0192] For example, when the channel bandwidth corresponding to a frequency domain subblock is 20 MHz and the subcarrier spacing is 78.125 kHz, the maximum number of data subcarriers supported by the frequency domain subblock is 256.
[0193] In another example, when the channel bandwidth corresponding to a frequency domain subblock is 20 MHz and the subcarrier spacing is 321.5 kHz, the maximum number of data subcarriers supported by the frequency domain subblock is 264.
[0194] A specific implementation of the segment parser will be described below. The following implementation may be used in combination with Solution 1 and Solution 2, or may be used independently.
[0195] Optionally, the segment parser allocates the output bit stream to the L frequency domain sub-blocks in a circular polling manner, and the number of output bits in each round is determined by the following Equation 1: S i =N i ·s expression 1 Meet the following.
[0196] S i is the number of output bits allocated to the ith frequency domain sub-block in one round, and N i is a positive integer obtained by rounding the quotient of the number of subcarriers included in the i-th frequency domain subblock and the preset number of subcarriers, and s is an integer greater than 0. The preset number of subcarriers may be a predefined number of subcarriers. Table 5 is used as an example. For example, when the MRU is "994 + 484", the preset number of subcarriers may be 484. In another example, when the MRU is "996 + 484 + 242", the preset number of subcarriers may be 242. The specific rounding method is not limited. For example, a truncation method or a rounding method may be used.
[0197] for example,
number
[0198] Figure 7 will be used as an example. The bit stream input to the segment parser is 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20.... In this case, in the first round of output, the bits output by the first output branch are (0 1) and the bits output by the second output branch are (2 3 4 5), in the second round of output, the bits output by the first output branch are (6 7) and the bits output by the second output branch are (8 9 10 11), and so on.
[0199] Below we describe two possible implementations of the segment parser, which may be used in combination with the circular polling method described above.
[0200] Based on the above cyclic polling method, in one possible implementation, each output branch performs output once in each output round. In another possible implementation, each output branch performs output at least twice in each output round. The following describes the two methods in detail.
[0201] In a first possible implementation, each output branch executes its output once in each round of outputs.
[0202] The first possible implementation of Solution 1 is used as an example (the example shown in FIG. 14). For example, the number of subcarriers #A included in the first frequency domain subblock is z, and the corresponding numbers of subcarriers (i.e., data of the second subcarriers) for aggregation between two second frequency domain subblocks are x1 and x2, respectively. The numbers of bits of the output bitstream allocated by the segment parser to the first frequency domain subblock and the two second frequency domain subblocks in at least one round are s, N1s, and N2s, respectively.
number
number
[0203] The second possible implementation of Solution 1 is used as an example (the example shown in FIG. 16). For example, the number of subcarriers #A included in the first frequency domain subblock is (z1+z2), and the corresponding numbers of subcarriers (i.e., data of the second subcarriers) for aggregation between two second frequency domain subblocks are x1 and x2, respectively. The numbers of bits of the output bitstream allocated by the segment parser to the first frequency domain subblock and the two second frequency domain subblocks in at least one round are s, N1s, and N2s, respectively.
number
number
[0204] For example, after the bitstream is input to the segment parser, the output bits of the segment parser are y k,j =x m is.
[0205] k is the bit number (excluding the remaining bits) corresponding to frequency domain subblock l, usually starting from 0. l is the number for frequency domain subblocks, usually starting from 0 and ending at L-1, i.e., l=[0,L-1]. m is the bit number of the stream, usually starting from 0.
[0206] Based on the first possible implementation scheme, for example, m satisfies Equation 2.
number
[0207] m i and m l denotes the number of bits corresponding to frequency domain sub-blocks i and l in each round of output (or the number of bits output by each output branch of a frequency domain sub-block in each round of output).
[0208] It should be noted that Equation 2 is a possible example, and variations of Equation 2 are also applicable to the embodiments of this application.
[0209] For example, FIG. 18 is another diagram of non-aggregation between two high-frequency channel elements. In the case of non-aggregation between two high-frequency channel elements, there may be two second frequency-domain subblocks and one first frequency-domain subblock. For distinction, the two second frequency-domain subblocks are referred to as frequency-domain subblock #1 and frequency-domain subblock #2, respectively. The number of data subcarriers corresponding to frequency-domain subblock #1 is x, and the number of data subcarriers corresponding to frequency-domain subblock #2 is x. As shown in FIG. 18, for the non-aggregation channel (i.e., in the case of non-aggregation between two second frequency-domain subblocks), there is one subcarrier group #A (i.e., one first frequency-domain subblock), and the number of subcarriers included in subcarrier group #A is z. Assume that frequency-domain subblock #1, frequency-domain subblock #2, and subcarrier group #A correspond to three output branches. For the sake of distinction, the output branch corresponding to frequency domain subblock #1 is referred to as the first output branch, the output branch corresponding to subcarrier group #A is referred to as the second output branch, and the output branch corresponding to frequency domain subblock #2 is referred to as the third output branch.
[0210] Assume that w = number of subcarriers corresponding to the second frequency-domain subblock / number of subcarriers corresponding to the first frequency-domain subblock ≈ 5 (e.g., 5 is obtained by rounding down the quotient of the number of subcarriers corresponding to the second frequency-domain subblock and the number of subcarriers corresponding to the first frequency-domain subblock). Therefore, the power ratio corresponding to the output branches may be 5s:1s:5s. That is, each output branch may be output according to 5s:1s:5s. s = 1 is used as an example. For example, in the first output round, bits (0 1 2 3 4) are output to subcarriers corresponding to frequency-domain subblock #1 through the first output branch, bit (5) is output to subcarrier group #A through the second output branch, and bit (6 7 8 9 10) is output to subcarriers corresponding to frequency-domain subblock #2 through the third output branch. In the second output round, bits (11 12 13 14 15) are output to the subcarriers corresponding to frequency domain subblock #1 through the first output branch, bit (16) is output to subcarrier group #A through the second output branch, bits (17 18 19 20 21) are output to the subcarriers corresponding to frequency domain subblock #2 through the third output branch, and so on, until the remaining bits are finally output.
[0211] In a second possible implementation, when each output branch performs output in each output round, at least one output branch performs output at least twice. Based on this, in at least one round in which the segment parser allocates the output bit stream to the L frequency domain subblocks in a cyclic polling manner, the bits allocated to one frequency domain subblock (or at least one frequency domain subblock) among the L frequency domain subblocks by the segment parser are allocated at least twice. In other words, the bits allocated to one frequency domain subblock by the segment parser in one round are not obtained in a single output, but rather in a batch or distributed output. In this way, the bits output to the frequency domain subblocks may be more distributed. Details will be described below with reference to the example shown in FIG. 19.
[0212] The first possible implementation of Solution 1 is used as an example (the example shown in FIG. 14). For example, the number of subcarriers #A included in the first frequency domain subblock is z, and the corresponding numbers of subcarriers (i.e., data of the second subcarriers) for aggregation between two second frequency domain subblocks are x1 and x2, respectively. The numbers of bits of the output bitstream allocated by the segment parser to the first frequency domain subblock and the two second frequency domain subblocks in at least one round are s, N1s, and N2s, respectively.
number
number
[0213] The second possible implementation of Solution 1 is used as an example (the example shown in FIG. 16). For example, the number of subcarriers #A included in the first frequency domain subblock is (z1+z2), and the corresponding numbers of subcarriers (i.e., data of the second subcarriers) for aggregation between two second frequency domain subblocks are x1 and x2, respectively. The numbers of bits of the output bitstream allocated by the segment parser to the first frequency domain subblock and the two second frequency domain subblocks in at least one round are s, N1s, and N2s, respectively.
number
number
[0214] For example, after the bitstream is input to the segment parser, the output bits of the segment parser are y k,j =x m For the meaning of the parameters, see the explanation above.
[0215] Based on the second possible realization scheme, i.e., in each round, w l The output is completed, for example, m satisfies Equation 3.
number
[0216] It should be noted that Equation 3 is a possible example, and variations of Equation 3 are also applicable to the embodiments of this application.
[0217] In one example, FIG. 18 is used as an example. In each output round, both the first output branch and the third output branch perform five output operations (i.e., w1 = w2 = w), and the second output branch performs one output operation. In other words, every time the second output branch performs one output operation, both the first output branch and the third output branch perform five output operations. s=1 is used as an example. For example, in the first output of the first round, bit (0) is output to the subcarrier corresponding to frequency domain subblock #1 through the first output branch, and bit (1) is output to the subcarrier corresponding to frequency domain subblock #2 through the third output branch. In the second output of the first round, bit (2) is output to the subcarrier corresponding to frequency domain subblock #1 through the first output branch, and bit (3) is output to the subcarrier corresponding to frequency domain subblock #2 through the third output branch. In the third output of the first round, bit (4) is output via the first output branch to the subcarriers corresponding to frequency domain subblock #1, and bit (5) is output via the third output branch to the subcarriers corresponding to frequency domain subblock #2. In the fourth output of the first round, bit (6) is output via the first output branch to the subcarriers corresponding to frequency domain subblock #1, and bit (7) is output via the third output branch to the subcarriers corresponding to frequency domain subblock #2. In the fifth output of the first round, bit (8) is output via the first output branch to the subcarriers corresponding to frequency domain subblock #1, bit (9) is output via the third output branch to the subcarriers corresponding to frequency domain subblock #2, and bit (10) is output via the second output branch to subcarrier group #A, and so on, until the remaining bits are finally output.
[0218] In another example, FIG. 18 is used as an example. In each output round, both the first and third output branches perform output twice (i.e., w1 = w2 = 2), and the second output branch performs output once. In other words, every time the second output branch performs output once, both the first and third output branches perform output twice. s = 1 is used as an example. For example, in the first output of the first round, bits (0 1) are output to subcarriers corresponding to frequency domain subblock #1 through the first output branch, and bits (2 3) are output to subcarriers corresponding to frequency domain subblock #2 through the third output branch. In the second output of the first round, bits (4 5 6) are output to subcarriers corresponding to frequency domain subblock #1 through the first output branch, bits (7 8 9) are output to subcarriers corresponding to frequency domain subblock #2 through the third output branch, and bits (10) are output to subcarrier group #A through the second output branch. In the first output of the second round, bits (11 12) are output via the first output branch onto the subcarriers corresponding to frequency domain subblock #1, and bits (13 14) are output via the third output branch onto the subcarriers corresponding to frequency domain subblock #2. In the second output of the second round, bits (15 16 17) are output via the first output branch onto the subcarriers corresponding to frequency domain subblock #1, bits (18 19 20) are output via the third output branch onto the subcarriers corresponding to frequency domain subblock #2, and bit (21) is output via the second output branch onto subcarrier group #A, and so on, until the remaining bits are finally output.
[0219] It can be understood that the above mainly uses an example in which the bits on subcarrier group #A are in the last output of each round of output for the purpose of explanation. This is not limited here. For example, the bits on subcarrier group #A may be in the first output of each round, or the second output of each round, or the third output of each round, or the fourth output of each round.
[0220] It can be further understood that in the above two examples, w1=w2 is mainly used as an example for explanation, which is not limited here. For example, w1 may alternatively not be equal to w2.
[0221] It can be further understood that in the second possible implementation manner, the explanation is mainly provided by using an example in which the number of bits output each time through each output branch in each output round is not directly output according to the output ratio. This is not limited here. For example, the number of bits output each time through each output branch in at least one round may not be directly output according to the output ratio. In another example, the number of bits output each time through at least one output branch is not directly output according to the output ratio.
[0222] It can be further understood that the second possible implementation method mainly describes that the number of bits output each time through each output branch does not need to be directly output according to the output ratio. Any variation of the above method can be applied to the embodiments of this application.
[0223] It can be further understood that the above second possible implementation manner can alternatively be used independently. The example shown in Figure 7 is used as an example. When there are two output branches and the output ratio of the two output branches is s:2s, in each output round, the second output branch may perform output twice, and the first output branch performs output once.
[0224] It can be further understood that in the output process according to the above two implementation methods, if there are remaining bits, the processing of the remaining bits can be referred to existing methods, which is not limited.
[0225] Optionally, each of the L frequency domain sub-blocks corresponds to an interleaver, and the interleaver is configured to interleave the bits allocated to the corresponding frequency domain sub-block. Some implementations are listed below.
[0226] In a first possible implementation, one subcarrier group #A may be considered as one first frequency domain subblock, and each first frequency domain subblock corresponds to one interleaver, and the interleaver is configured to permute bits carried in the corresponding first frequency domain subblock. Based on this implementation, each subcarrier group #A corresponds to one interleaver, and the interleaver is configured to permute bits on the corresponding subcarrier group #A.
[0227] For example, assume there are two subcarrier groups #A, denoted as subcarrier group #A1 and subcarrier group #A2, respectively. The interleaver corresponding to subcarrier group #A1 is called interleaver #1, and the interleaver corresponding to subcarrier group #A2 is called interleaver #2. Interleaver #1 is configured to permute the bits carried in subcarrier group #A1, and interleaver #2 is configured to permute the bits carried in subcarrier group #A2.
[0228] Furthermore, in this implementation, each second frequency domain sub-block corresponds to one interleaver, and the interleaver is configured to permute bits on the corresponding frequency domain sub-block. Details will not be described again here.
[0229] In a second possible implementation, multiple subcarrier groups #A may be considered as one first frequency domain subblock, and each first frequency domain subblock corresponds to one interleaver, where the interleaver is configured to permute bits carried in the corresponding first frequency domain subblock. Based on this implementation, multiple subcarrier groups #A correspond to one interleaver, where the interleaver is configured to permute bits on multiple corresponding subcarrier groups #A.
[0230] For example, suppose there are two subcarrier groups #A, denoted as subcarrier group #A1 and subcarrier group #A2, respectively. The interleaver corresponding to subcarrier group #A1 and subcarrier group #A2 is called interleaver #1, and interleaver #1 is configured to permute bits on subcarrier group #A1 and subcarrier group #A2, while interleaver #2 is configured to permute bits carried on subcarrier group #A2.
[0231] Furthermore, in this implementation, each second frequency domain sub-block corresponds to one interleaver, and the interleaver is configured to permute bits on the corresponding frequency domain sub-block. Details will not be described again here.
[0232] In a third possible implementation, in addition to the first subcarriers, the first frequency domain subblock further includes subcarriers in the aggregate channel, and each first frequency domain subblock corresponds to one interleaver, and the interleaver is configured to permute bits carried in the corresponding first frequency domain subblock.
[0233] For example, Figure 17 is used as an example. z1 subcarriers in subcarrier group #A are assigned to a first output branch corresponding to frequency domain subblock #1, and z2 subcarriers in subcarrier group #A are assigned to a second output branch corresponding to frequency domain subblock #2. The subcarriers corresponding to frequency domain subblock #1 and the z1 subcarriers correspond to one interleaver (e.g., called interleaver #1), where interleaver #1 is configured to permute the bits carried by the subcarriers corresponding to frequency domain subblock #1 and the z1 subcarriers. The subcarriers corresponding to frequency domain subblock #2 and the z2 subcarriers correspond to one interleaver (e.g., called interleaver #2), where interleaver #2 is configured to permute the bits carried by the subcarriers corresponding to frequency domain subblock #2 and the z2 subcarriers.
[0234] The above three possible implementation methods are examples for explanation, which are not limiting here. For example, as long as the range of the interleaver is bound to the range of the output branches, that is, as long as the interleaver rearranges the data bits corresponding to each output branch, any possible implementation method can be applied to the embodiment of this application.
[0235] It may be further understood that some optional features in the embodiments of this application may be independent of other features in some scenarios, or may be combined with other features in some scenarios, without limitation.
[0236] It may be further understood that "at least one" in this application indicates one or more, and "plurality" means two or more. The term "and / or" describes an association relationship between related objects and indicates that three relationships may exist. For example, A and / or B may indicate the following three cases: only A is present, both A and B are present, and only B is present. The character " / " generally indicates an "or" relationship between related objects. Furthermore, although terms such as first, second, etc. may be used in this application to describe objects, it should be understood that these objects are not limited by these terms. These terms are used merely to distinguish objects from one another.
[0237] It can be further understood that in the above embodiment, the segment parser is mainly used as an example for explanation, and its name does not limit the protection scope of the embodiment of this application.
[0238] It can be further understood that in the embodiment of this application, the sequence numbers of the output branches are merely names for distinction and do not limit the scope of protection of the embodiment of this application. Furthermore, the output sequence corresponding to each output branch is not limited in the embodiment of this application.
[0239] It may be further understood that in the embodiments of this application, the specific descriptions of the subcarriers are not limiting. For example, in some of the above embodiments, the specific descriptions of the listed subcarriers are merely examples, and the specific values of the subcarriers do not limit the scope of protection of the embodiments of this application.
[0240] In the embodiment of this application, it may be further understood that in the case of non-aggregation and aggregation between high-frequency channel elements, the subcarriers corresponding to the high-frequency channel elements may change. For example, in the case of non-aggregation between high-frequency channel elements, the subcarriers corresponding to the high-frequency channel elements may change due to the presence of subcarrier #A. For example, some subcarriers (e.g., one subcarrier) may be reduced at the edge.
[0241] In the embodiments of this application, aggregation between high-frequency channel elements and non-aggregation between high-frequency channel elements are mentioned multiple times, and it can be further understood that a person skilled in the art should understand the meaning of aggregation and non-aggregation. Aggregation between high-frequency channel elements may alternatively be replaced with an aggregated channel, and non-aggregation between high-frequency channel elements may alternatively be replaced with a non-aggregated channel.
[0242] It can be further understood that the solutions in the embodiments of this application may be combined appropriately for use, and the explanations or descriptions of terms in the embodiments may be mutually referenced or explained in the embodiments. This is not limited.
[0243] It may be further understood that in the above method embodiments, the methods and operations implemented by the communication device may alternatively be implemented by components (such as chips or circuits) of the communication device, without this being limiting.
[0244] Above, the method provided in the embodiment of this application is described in detail with reference to Figures 11 to 18. Hereinafter, the device provided in the embodiment of this application will be described with reference to Figures 19 and 22. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for contents not described in detail, reference will be made to the method embodiment. For the sake of brevity, the details will not be described again here.
[0245] For example, Figure 19 is a diagram of a communication device 1900 according to an embodiment of the present application. The device 1900 includes an acquiring unit 1910 and an allocating unit 1920. The acquiring unit 1910 is configured to acquire an output bitstream of a stream parser. The allocating unit 1920 is configured to allocate the output bitstream to L frequency domain sub-blocks. The L frequency domain sub-blocks are located in high frequencies, where the frequency value of the high frequencies is equal to or greater than 45 GHz, and L is an integer greater than 1.
[0246] It should be understood that the specific processes by which the units perform the above corresponding steps have been described in detail in the above method embodiments, and for the sake of brevity, the details will not be described again here.
[0247] Optionally, the device 1900 may be, for example, a segment parser.
[0248] Optionally, the apparatus 1900 is a communication device including a segment parser. The communication device may be, for example, a terminal device or a network device.
[0249] It should be understood that the apparatus 1900 herein is embodied in the form of a functional unit. The term "unit" herein may refer to an application-specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor) configured to execute one or more software or firmware programs, a memory, a coupled logic circuit, and / or other suitable components supporting the described functionality. In an optional example, those skilled in the art may understand that the apparatus 1900 may specifically be the segment parser in the above embodiment or may be configured to perform procedures and / or steps corresponding to the segment parser in the above method embodiment. To avoid repetition, the details will not be described again here.
[0250] The device 1900 in the above solution has functions for implementing corresponding steps performed in the above method. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the acquisition unit may be replaced with a transmitter, and other units such as the allocation unit may be replaced with a processor, which respectively perform the transmitting and receiving operations and the processing-related operations in the method embodiments.
[0251] 20 is a diagram of another communication device 2000 according to an embodiment of the present application. The device 2000 includes a processor 2010.
[0252] Optionally, the apparatus 2000 further includes a memory 2020 and a transceiver 2030. The processor 2010 is coupled to the memory 2020. The memory 2020 is configured to store computer programs or instructions and / or data. The processor 2010 is configured to execute the computer programs or instructions stored in the memory 2020 or read the data stored in the memory 2020 to perform the method in the above method embodiments. The transceiver 2030 is configured to receive and / or transmit signals. For example, the processor 2010 is configured to control the transceiver 2030 to receive and / or transmit signals.
[0253] Optionally, there are one or more processors 2010 .
[0254] Optionally, there is one or more memories 2020 .
[0255] Optionally, memory 2020 and processor 2010 are integrated together or located separately.
[0256] Optionally, the device 2000 may be, for example, a segment parser.
[0257] Optionally, the apparatus 2000 is a communication device including a segment parser. The communication device may be, for example, a terminal device or a network device.
[0258] For example, the processor 2010 may have the functionality of the allocation unit 1920 shown in FIG. 19, the memory 2020 may have the functionality of the storage unit, and the transceiver 2030 may have the functionality of the acquisition unit 1910 shown in FIG.
[0259] In the solution, the apparatus 2000 is configured to implement the operations performed in the above method.
[0260] For example, the processor 2010 is configured to execute computer programs or instructions stored in the memory 2020 to implement the relevant operations of the segment parser in the above method embodiments.
[0261] It should be understood that the processor referred to in the embodiments of this application may be a central processing unit (CPU), or alternatively, may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.
[0262] It should be further understood that the memory referred to in the embodiments of this application may be volatile and / or non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM). For example, RAM may be used as an external cache. By way of example and not limitation, RAM may include the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DR RAM).
[0263] It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (storage module) may be integrated into the processor.
[0264] It should be further noted that memory, as referred to herein, is intended to include, without being limited to, these and any other suitable types of memory.
[0265] 21 is a diagram of a chip system 2100 according to an embodiment of the present application. The chip system 2100 (which may alternatively be referred to as a processing system) includes a logic circuit 2110 and an input / output interface 2120.
[0266] The logic circuit 2110 may be a processing circuit in the chip system 2100. The logic circuit 2110 calls instructions in the storage unit, so that the chip system 2100 can implement the methods and functions in the embodiments of this application. The input / output interface 2120 may be an input / output circuit in the chip system 2100, which outputs information processed by the logic circuit 2110 or inputs data or signaling information to be processed into the logic circuit 2110 for processing.
[0267] Specifically, the input / output interface 2120 is configured to receive the output bitstream of the stream parser. The logic circuit 2110 is configured to allocate the output bitstream to L frequency domain sub-blocks. The L frequency domain sub-blocks are located at high frequencies, and the frequency values of the high frequencies are equal to or greater than 45 GHz, where L is an integer greater than 1.
[0268] It should be understood that the details of performing the above method by the input / output interface 2120 and the logic circuit 2110 have been described in detail in the above method embodiments, and for the sake of brevity, the details will not be described again here.
[0269] As described above, the communication device provided in the embodiment of this application may be a segment parser. Accordingly, reference is made to Fig. 22. For example, the embodiment of this application provides a communication system 2200. The communication system 2200 includes a segment parser. Optionally, the communication system 2200 further includes a stream parser, for example, a stream parser 2220. Optionally, the communication system 2200 further includes an interleaver, for example, an interleaver 2231 and an interleaver 2232.
[0270] Optionally, there is one or more segment parsers, for example, two segment parsers are shown in FIG.
[0271] Optionally, there is one or more interleavers 2230. For example, two interleavers are shown in FIG.
[0272] Optionally, the communication system 2200 may be a terminal device or a component (e.g., a chip, circuit, or module) used in a terminal device, or may be a network device or a component (e.g., a chip, circuit, or module) used in a network device.
[0273] For example, the output bitstream output from the stream parser may be input to a segment parser, which performs segment parsing on the output bitstream. For example, the segment parser may allocate the output bitstream to L frequency domain subblocks, and the bits on each frequency domain subblock may be input to a corresponding interleaver for interleaving or reordering. Figure 22 is used as an example. The output bitstream #1 output from the stream parser may be input to a segment parser 2211, which performs segment parsing on the output bitstream #1. For example, the segment parser 2211 allocates the output bitstream #1 to at least two frequency domain subblocks, and the bits on each frequency domain subblock may be input to a corresponding interleaver for interleaving or reordering (e.g., the interleaver 2231 includes multiple interleavers, each corresponding to one frequency domain subblock). In another example, output bitstream #2 output from the stream parser may be input to segment parser 2212, which performs segment parsing on output bitstream #2. For example, segment parser 2212 may allocate output bitstream #2 to at least two frequency domain subblocks, and the bits on each frequency domain subblock may be input to a corresponding interleaver for interleaving or reordering (e.g., interleaver 2232 may include multiple interleavers, each corresponding to one frequency domain subblock).
[0274] The functions of the segment parser, stream parser and interleaver are described above and will not be described in detail here.
[0275] An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions for implementing a method to be performed by a communication device in the above method embodiment.
[0276] For example, when the computer program is executed by a computer, the computer is enabled to implement the method performed by the communication device in the method embodiments described above.
[0277] An embodiment of the present application further provides a computer program product including instructions, which, when executed by a computer, realize the method performed by the communication device in the above method embodiment.
[0278] For the description of the relevant contents and beneficial effects of any one of the devices provided above, please refer to the corresponding method embodiments provided above, and the details will not be described again here.
[0279] In some embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the described apparatus embodiments are merely examples. For example, the division into units is merely a logical division of function, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into other systems, or some features may be ignored or not implemented. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be indirect couplings or communication connections through some interfaces, devices, or units, and may be electrical, mechanical, or other types.
[0280] All or part of the above embodiments may be realized by using software, hardware, firmware, or any combination thereof. When software is used to realize the embodiments, the above embodiments may be fully or partially realized in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded into a computer and executed, the procedures or functions according to the embodiments of this application are fully or partially generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer may be a personal computer, a server, a network device, etc. The computer instructions may be stored in a computer-readable storage medium or 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 via a wired (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave) method. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device integrating one or more available media, such as a server or a data center. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a DVD), a semiconductor medium (e.g., a solid-state drive (SSD)), etc. For example, the available medium may include, but is not limited to, any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
[0281] The above description is merely a specific implementation of this application and is not intended to limit the scope of protection of this application. Any variations or replacements that can be easily conceived by those skilled in the art within the technical scope disclosed in this application shall fall within the scope of protection of this application. Therefore, the scope of protection of this application shall be subject to the scope of protection of the claims.
Claims
1. 1. A communication method comprising: obtaining an output bitstream of the stream parser; A method comprising: allocating the output bitstream to L frequency domain sub-blocks, the L frequency domain sub-blocks being located at high frequencies, a frequency value of the high frequencies being equal to or greater than 45 GHz, and L being an integer greater than 1.
2. 2. The method of claim 1, wherein the L frequency domain subblocks include a first frequency domain subblock, the first frequency domain subblock including a first subcarrier, the first subcarrier being an additional subcarrier in a non-aggregated channel compared to an aggregated channel.
3. The method of claim 2 , wherein the first frequency domain subblock includes the first subcarrier.
4. The method of claim 3 , wherein the first subcarriers are not contiguous in the frequency domain.
5. 3. The method of claim 2, wherein in addition to the first subcarrier, the first frequency domain subblock further includes a second subcarrier, the second subcarrier not being the first subcarrier.
6. 3. The method of claim 1, wherein the L frequency domain subblocks further include a second frequency domain subblock, the second frequency domain subblock including a second subcarrier, and the second subcarrier is not the first subcarrier.
7. The method of claim 5 or 6, wherein the second subcarrier is a subcarrier in the aggregate channel.
8. The number of output bits allocated to the L frequency domain sub-blocks is determined by the following relationship: S i =N i ・s Fulfilling S i is the number of output bits allocated to the ith frequency domain sub-block in one round, and N i is a positive integer obtained by rounding the quotient of the number of subcarriers included in the i-th frequency domain subblock and the preset number of subcarriers; [Equation 1] and N BPSCS 8. The method according to claim 3, wherein ∑ is the number of output bits corresponding to one subcarrier in one stream.
9. the L frequency domain subblocks include one first frequency domain subblock and two second frequency domain subblocks, the first frequency domain subblock includes z first subcarriers, one second frequency domain subblock includes x1 second subcarriers, and the other second frequency domain subblock includes x2 second subcarriers; The number of output bits allocated to the first frequency domain sub-block and the two second frequency domain sub-blocks in at least one round is denoted by s and N, respectively. 1 s and N 2 It is s. [Equation 2] and [Equation 3] The method of claim 8, wherein
10. The step of allocating the output bitstream to L frequency domain sub-blocks comprises: The method of claim 1 , comprising the step of allocating the output bitstream to the L frequency domain sub-blocks in a circular polling manner.
11. 11. The method of claim 10, wherein in at least one round of allocating the output bit stream to the L frequency domain sub-blocks in the cyclic polling manner, bits allocated to at least one of the L frequency domain sub-blocks are the result of being allocated at least twice.
12. 12. The method of claim 1, wherein each of the L frequency domain sub-blocks corresponds to an interleaver, and the interleaver is configured to interleave bits allocated to a corresponding frequency domain sub-block.
13. A communication device including an obtaining unit and an allocating unit, The acquisition unit is configured to acquire an output bitstream of a stream parser; the allocation unit is configured to allocate the output bitstream to L frequency domain sub-blocks, the L frequency domain sub-blocks being located at a high frequency, a frequency value of the high frequency being equal to or greater than 45 GHz, and L being an integer greater than 1.
14. 14. The communication device of claim 13, wherein the L frequency domain subblocks include a first frequency domain subblock, the first frequency domain subblock including a first subcarrier, the first subcarrier being an additional subcarrier in a non-aggregated channel compared to an aggregated channel.
15. The communications device of claim 14 , wherein the first frequency domain sub-block includes the first sub-carrier.
16. The communication device of claim 15 , wherein the first subcarriers are not contiguous in the frequency domain.
17. 15. The communications device of claim 14, wherein in addition to the first subcarrier, the first frequency domain subblock further includes a second subcarrier, the second subcarrier being different from the first subcarrier.
18. 15. The communication device of claim 13, wherein the L frequency domain subblocks further include a second frequency domain subblock, the second frequency domain subblock includes a second subcarrier, and the second subcarrier is not the first subcarrier.
19. 19. The communication device according to claim 17 or 18, wherein the second subcarrier is a subcarrier in the aggregate channel.
20. The number of output bits allocated to the L frequency domain sub-blocks by the allocation unit is determined by the following relationship: S i =N i ・s Fulfilling S i is the number of output bits allocated to the ith frequency domain sub-block in one round, and N i is a positive integer obtained by rounding the quotient of the number of subcarriers included in the i-th frequency domain subblock and the preset number of subcarriers; [Equation 4] and N BPSCS 20. The communication device according to claim 15, wherein ∑ is the number of output bits corresponding to one subcarrier in one stream.
21. the L frequency domain subblocks include one first frequency domain subblock and two second frequency domain subblocks, the first frequency domain subblock includes z first subcarriers, one second frequency domain subblock includes x1 second subcarriers, and the other second frequency domain subblock includes x2 second subcarriers; The number of output bits allocated by the allocation unit to the first frequency domain sub-block and the two second frequency domain sub-blocks in at least one round is s, N 1 s and N 2 It is s. [Equation 5] and [Equation 6] 21. The communication device according to claim 20, wherein:
22. The communication device of claim 13 , wherein the allocation unit allocates the output bitstream to the L frequency domain sub-blocks in a cyclic polling manner.
23. 23. The communication device of claim 22, wherein in at least one round of the allocation unit allocating the output bit stream to the L frequency domain sub-blocks in the cyclic polling manner, the bits allocated to at least one of the L frequency domain sub-blocks by the allocation unit are the result of being allocated at least twice.
24. 23. The communication device of claim 13, wherein each of the L frequency domain sub-blocks corresponds to an interleaver, and the interleaver is configured to interleave bits allocated to a corresponding frequency domain sub-block.
25. 1. A communication device including a processor, A communications device, wherein the processor is configured to execute computer programs or instructions stored in a memory to enable the device to perform the method of any one of claims 1 to 12.
26. 1. A computer-readable storage medium, comprising:
13. The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform a method according to any one of claims 1 to 12.
27. A computer program product comprising a computer program or instructions used to carry out the method of any one of claims 1 to 12.
Citation Information
Patent Citations
Multiple channel transmission in MMW WLAN systems.
JP2019526990A
Method and apparatus for transmitting coded bits
JP2021529492A
Parser and interleaving parameter design for resource unit aggregation
US20210160889A1
Distributed tone mapping for power spectral density (PSD) limits
US20210288768A1
Methods and arrangements for large resource unit allocation
US20210329637A1