Methods, systems, and apparatus for joint error correction coding for self-decodable payloads

Abstract

Joint error correction coding of a plurality of self-decodable payloads involves encoding a plurality of individual payloads using an error correction code to generate a codeword. The codeword includes a plurality of coded blocks respectively corresponding to the individual payloads. One or more of the individual payloads or coded blocks may be self-decoded independently of the other payloads or coded blocks, and may also be decoded in conjunction with one or more of the other payloads or coded blocks.

Description

Technical Field

[0001] The present application relates to error correction coding for wireless communications. Background Art

[0002] Resilience is a fundamental feature of the sixth generation (6G) of communications. According to some technical visions for future factories and industries, for example, ultra-reliable and low-latency wireless communications are key enablers for large-scale automated manufacturing.

[0003] In the recent development of 6G, two trends are also observed. From a technical perspective, millimeter-wavelength (mmWave) communication and massive multiple input multiple output (MIMO) may become more common because they can significantly expand current bandwidth resources. From a service perspective, a single communication device may need to support multiple services with different latency and reliability requirements.

[0004] A potential scenario arises when multiple services are aggregated into one physical radio link. The goal is to provide multiple quality of service (QoS) levels for multiple services in only one radio link. Given the high carrier frequencies and massive number of antennas in some communication systems, beamforming can be performed more aggressively to aggregate multiple services into one radio link. At the same time, these services may have very diverse key performance indicators (KPIs). For example, ultra-reliable low latency communication (URLLC), massive machine type communication (mMTC), enhanced mobile broadband (eMBB), and terabit per second (Tbps) communication can all be integrated into one link. This is challenging because different KPIs, such as signal to noise ratio (SNR), fading, etc., must be supported under the same radio channel. Summary of the invention

[0005] The present application includes embodiments that can be used to solve various technical defects of current coding methods. Under current technology, there is a balance between ultra-reliable communication and low-latency communication. In order to achieve high reliability, hybrid automatic repeat request (HARQ) has been used in current systems to reduce the block error rate (BLER) level by several orders of magnitude. However, the loop delay caused by negative acknowledgment (NACK) signaling, rescheduling and retransmission may not meet the low latency requirements of 6G. A simple solution is to reduce the code rate and modulation order, but this comes at the expense of spectral efficiency and is generally not encouraged in system design.

[0006] This trade-off may also occur in typical joint coding approaches, where different payloads are mapped and encoded into one long codeword according to their priorities. Although this can provide non-uniform error protection to support various reliability requirements and provide multiple QoS for multiple services within one wireless link, decoding cannot start before the entire long codeword is received, which may cause additional delays.

[0007] Providing good coding performance in hybrid service and low-latency communication applications remains a challenge. For example, HARQ-based methods may bring long loop delays and may not meet low latency requirements, and the above joint coding methods do not support separate decoding of different payloads before receiving all payloads in a long codeword.

[0008] In some embodiments of the present application, retransmission delays can be mitigated or avoided by supporting further decoding operations after a decoding failure of a delay-sensitive payload. Requesting a retransmission may not be feasible in some applications because the resulting loop delay may exceed the maximum tolerable delay, and further decoding operations after a decoding failure may avoid a retransmission request. For example, after a decoding failure, the receiver may perform a second decoding attempt without requesting a retransmission. In this example, the additional decoding delay incurred during the second decoding attempt may be much less than the additional delay of the loop delay for retransmission.

[0009] Joint coding according to some embodiments may help to enhance performance because in joint coding, multiple services may actually enhance each other.

[0010] Non-uniform error protection may be provided for different payloads (e.g., payloads associated with different services). For example, the encoding and decoding of joint codewords may support different error protection levels for different services. Consider an application involving URLLC and eMBB services, where the target BLER for the URLLC payload should be at least one order of magnitude lower than the target BLER for the eMBB payload. The embodiments disclosed herein may implement such non-uniform error protection.

[0011] For example, self-decodability may be provided for each individual service in addition or alternatively. In order to support different latency requirements for multiple services, each service may be self-decoded based on its own coded bit ratio, or in other words, based on its own corresponding portion of the long codeword. For example, a shorter URLLC payload may be decoded after receiving some (but not all) coded bits (such as log-likelihood ratios or LLRs). Thus, the payload may be self-decodable without having to wait for the entire (longer) joint codeword to be received.

[0012] According to one aspect of the present application, a method involves: a first communication device sends a codeword to a second communication device in a wireless communication network, the codeword comprising a plurality of coding blocks generated by encoding corresponding individual payloads using an error correction code. The plurality of coding blocks comprises a self-decodable coding block. The self-decodable coding block can be decoded independently of other coding blocks in the plurality of coding blocks, and can also be jointly decoded with one or more other coding blocks in the plurality of coding blocks of the codeword.

[0013] A related method may involve a second communication device in a wireless communication network receiving, from a first communication device, a codeword, the codeword comprising a plurality of coding blocks corresponding to respective error correction encoded individual payloads. As described above, the plurality of coding blocks comprises a self-decodable coding block, the self-decodable coding block being decodable independently of other coding blocks in the plurality of coding blocks and also being decodable jointly with one or more other coding blocks in the plurality of coding blocks of the codeword.

[0014] Another method involves acquiring and encoding a plurality of individual payloads to generate a codeword, and outputting the codeword. The encoding involves encoding each of the individual payloads using an error correction code to generate the codeword. The codeword includes a plurality of coding blocks corresponding to respective individual payloads of the plurality of individual payloads. The plurality of coding blocks includes a self-decodable coding block that can be decoded not only independently of other coding blocks of the plurality of coding blocks, but also jointly with one or more other coding blocks of the plurality of coding blocks of the codeword.

[0015] According to a related embodiment, a method involves: decoding the individual payload from a codeword, the codeword comprising a plurality of coding blocks corresponding to the respective error-correction-encoded individual payloads; and outputting the individual payload. Also, the plurality of coding blocks comprises a self-decodable coding block, the self-decodable coding block being decodable not only independently of other coding blocks in the plurality of coding blocks, but also jointly decodable with one or more other coding blocks in the plurality of coding blocks of the codeword.

[0016] In an apparatus embodiment, the apparatus may include a processor and a non-transitory computer-readable storage medium coupled to the processor. The non-transitory computer-readable storage medium stores a program executed by the processor.

[0017] The storage medium does not necessarily need to be or only needs to be implemented in such a device or in combination with such a device. A computer program product may be or include, for example, a non-transitory computer-readable medium storing a program for execution by a processor.

[0018] The program stored by the computer-readable storage medium may include instructions for or for causing a processor to execute, implement, support or enable any method disclosed herein.

[0019] For example, the program may include instructions for or for causing a processor to perform the following operations: a first communication device sends a codeword to a second communication device in a wireless communication network, the codeword including a plurality of coded blocks generated by encoding corresponding individual payloads using an error correction code.

[0020] The program may include instructions for or for causing the processor to perform the following operations: a second communication device in the wireless communication network receives a codeword from the first communication device, the codeword including a plurality of coded blocks corresponding to respective error correction encoded individual payloads.

[0021] In another embodiment, the program may include instructions for or for causing the processor to perform the following operations: obtain and encode each of a plurality of separate payloads to generate a codeword; and output the codeword. The separate payloads are each encoded using an error correction code to generate the codeword, so that the codeword includes a plurality of encoding blocks corresponding to the respective separate payloads in the plurality of separate payloads.

[0022] According to yet another embodiment, the program comprises instructions for or for causing a processor to: decode the individual payloads from a codeword comprising a plurality of coded blocks corresponding to respective error correction coded individual payloads; and output the individual payloads.

[0023] In the above-mentioned apparatus and computer program product embodiments, as in the method embodiments, the plurality of coding blocks include a self-decodable coding block, which can be decoded independently of other coding blocks in the plurality of coding blocks, and can also be jointly decoded with one or more other coding blocks in the plurality of coding blocks of the codeword.

[0024] According to yet another embodiment, a system includes a first communication device and a second communication device. The first communication device is used to send a codeword, the codeword including a plurality of coding blocks generated by encoding corresponding individual payloads using an error correction code. The plurality of coding blocks include self-decodable coding blocks. The second communication device is used to receive the codeword including the plurality of coding blocks from the first communication device. The second communication device is also used to decode the self-decodable coding blocks to obtain individual payloads from the codeword.

[0025] This application encompasses these and other methods or embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] For a more complete understanding of the present embodiment and its advantages, reference is now made, by way of example, to the following description taken in conjunction with the accompanying drawings.

[0027] Figure 1 It is a simplified diagram of the communication system.

[0028] Figure 2 yes Figure 1 A schematic block diagram of an exemplary communication system in FIG.

[0029] Figure 3 Examples of exemplary electronic devices and base stations are shown.

[0030] Figure 4 Shows units or modules in the device.

[0031] Figure 5 is a block diagram illustrating an exemplary multi-service scenario.

[0032] Figure 6 is a block diagram illustrating self-decoding and joint decoding in case of self-decoding failure.

[0033] Figure 7 is a block diagram showing a robotic arm including a video device and two joints and communicating with a base station.

[0034] Figure 8 is a block diagram illustrating exemplary code blocks and encoding symbols provided by one embodiment.

[0035] Fig. 9 is a block diagram showing exemplary code blocks and encoding symbols provided by another embodiment.

[0036] Fig.10 is a block diagram showing exemplary code blocks and encoding symbols provided by yet another embodiment.

[0037] Fig.11 is a block diagram showing the sequential coupling of bits between individual payloads.

[0038] Fig.12 is a block diagram illustrating the many-to-one coupling of bits between individual payloads.

[0039] Fig.13 is a flow chart illustrating an exemplary method provided by an embodiment. DETAILED DESCRIPTION

[0040] For illustrative purposes, specific exemplary embodiments will be explained in greater detail below with reference to the accompanying drawings.

[0041] The embodiments described herein represent information sufficient to practice the claimed subject matter and illustrate methods of practicing such subject matter. After reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the claimed subject matter and will recognize that the application of these concepts is not specifically mentioned herein. It should be understood that these concepts and applications are within the scope of the present application and the appended claims.

[0042] refer to Figure 1 , a simplified schematic diagram of a communication system is provided as an illustrative example but not limiting. The communication system 100 includes a radio access network 120. The radio access network 120 may be a next generation (e.g., sixth generation (6G) or higher) radio access network, or a conventional (e.g., 5G, 4G, 3G, or 2G) radio access network. One or more communication electric devices (ED) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (generally referred to as 110) may be interconnected with each other or connected to one or more network nodes (170a, 170b, generally referred to as 170) in the radio access network 120. The core network 130 may be part of the communication system and may be dependent on or independent of the radio access technology used in the communication system 100. In addition, the communication system 100 includes a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0043] Figure 2An exemplary communication system 100 is shown. Typically, the communication system 100 enables multiple wireless or wired elements to transmit data and other content. The purpose of the communication system 100 may be to provide content such as voice, data, video and / or text through broadcast, multicast and unicast, etc. The communication system 100 may operate by sharing resources (e.g., carrier spectrum bandwidth) between its constituent elements. The communication system 100 may include a terrestrial communication system and / or a non-terrestrial communication system. The communication system 100 may provide a wide range of communication services and applications (e.g., earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous distribution and mobility, etc.). The communication system 100 may provide a high degree of availability and robustness through the joint operation of a terrestrial communication system and a non-terrestrial communication system. For example, integrating a non-terrestrial communication system (or its components) into a terrestrial communication system may realize a heterogeneous network including multiple layers. Compared with traditional communication networks, heterogeneous networks may obtain better overall performance through efficient multi-link joint operation, more flexible function sharing, and faster physical layer link switching between terrestrial networks and non-terrestrial networks.

[0044] The terrestrial communication system and the non-terrestrial communication system can be regarded as subsystems of the communication system. Figure 2 In the example shown in FIG. 1 , the communication system 100 includes electronic devices (EDs) 110a, 110b, 110c, 110d (generally referred to as ED 110), radio access networks (RANs) 120a and 120b, non-terrestrial communication networks 120c, core networks 130, public switched telephone networks (PSTNs) 140, the Internet 150, and other networks 160. The RANs 120a and 120b include corresponding base stations (BSs) 170a and 170b, which may be generally referred to as terrestrial transmit and receive points (T-TRPs) 170a and 170b. The non-terrestrial communication network 120c includes an access node 172, which may be generally referred to as a non-terrestrial transmit and receive point (NT-TRP) 172.

[0045] Any ED 110 may alternatively or additionally be used to connect, access, or communicate with any T-TRP 170a and 170b, NT-TRP 172, Internet 150, core network 130, PSTN 140, other network 160, or any combination thereof. In some examples, ED 110a may perform uplink and / or downlink transmissions with T-TRP 170a via ground air interface 190a. In some examples, ED 110a, 110b, 110c, and 110d may also communicate directly with each other via one or more sidelink air interfaces 190b. In some examples, ED 110d may perform uplink and / or downlink transmissions with NT-TRP 172 via non-ground air interface 190c.

[0046] The air interfaces 190a and 190b may use similar communication technologies, such as any suitable wireless access technology. For example, the communication system 100 may implement one or more channel access methods in the air interfaces 190a and 190b, such as code division multiple access (CDMA), space division multiple access (SDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA) or single-carrier FDMA (SC-FDMA). The air interfaces 190a and 190b may utilize other high-dimensional signal spaces, which may involve a combination of orthogonal dimensions and / or non-orthogonal dimensions.

[0047] The non-terrestrial air interface 190c may enable communication between ED 110d and one or more NT-TRPs 172 via a wireless link or a simple link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs 110 and one or more NT-TRPs 175 for multicast transmission.

[0048] The RANs 120a and 120b communicate with the core network 130 to provide various services, such as voice, data, and other services, to the EDs 110a, 110b, and 110c. The RANs 120a and 120b and / or the core network 130 may communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by the core network 130 and may or may not use the same radio access technology as the RANs 120a and / or RANs 120b. The core network 130 may also serve as a gateway access between (i) the RANs 120a and 120b and / or the EDs 110a, 110b, 110c, and (ii) other networks (e.g., the PSTN 140, the Internet 150, and other networks 160). In addition, some or all of the EDs 110a, 110b, 110c may include functionality to communicate with different wireless networks over different radio links using different radio technologies and / or protocols. Instead of (or in addition to) wireless communication, EDs 110a, 110b, 110c may also communicate with a service provider or switch (not shown) and with the Internet 150 through a wired communication channel. PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). Internet 150 may include computer networks and / or subnets (intranets) and include protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), etc. EDs 110a, 110b, and 110c may be multi-mode devices capable of operating according to a variety of wireless access technologies and include a plurality of transceivers required to support these wireless access technologies.

[0049] Figure 3Another example of ED 110 and base stations 170a, 170b and / or 170c is shown. ED 110 is used to connect people, objects, machines, etc. ED 110 can be widely used in various scenarios, such as cellular communication, device-to-device (D2D), vehicle to everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), machine-type communication (MTC), Internet of Things (IOT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable devices, smart transportation, smart city, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.

[0050] Each ED 110 represents any suitable end-user device for wireless operation, and may include devices such as (or may be referred to as) user equipment (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile user unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronic device, smart book, vehicle, car, truck, bus, train or IoT device, industrial equipment or devices in the above devices (such as communication modules, modems, or chips), etc. The next generation ED 110 may be referred to using other terms. Base stations 170a and 170b are each T-TRPs, hereinafter referred to as T-TRP 170. Similarly in Figure 3 , the NT-TRP is hereinafter referred to as NT-TRP 172. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 may be dynamically or semi-statically opened (i.e., established, activated, or enabled), closed (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connection availability and connection necessity.

[0051] ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown in the figure. One, part or all of the antennas 204 may also be panels. Transmitter 201 and receiver 203 may be integrated into, for example, a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver may also be used to demodulate data or other content received by at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received by wireless or wired means. Each antenna 204 includes any suitable structure for sending and / or receiving wireless signals or wired signals.

[0052] ED 110 includes at least one memory 208. The memory 208 stores instructions and data used, generated, or collected by ED 110. For example, the memory 208 may store software instructions or modules that are used to implement some or all of the functions and / or embodiments described herein and are executed by one or more processing units (e.g., processor 210). Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and one or more retrieval devices. Any suitable type of memory may be used, such as a random access memory (RAM), a read only memory (ROM), a hard disk, an optical disk, a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, a processor ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., connected to a processor). Figure 1 The input / output device can interact with users or other devices in the network. Each input / output device includes any suitable structure for providing information to a user or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display or touch screen, including network interface communication, for example, through operation.

[0053] ED 110 includes a processor 210 for performing operations, including operations related to preparing transmissions for uplink transmission to NT-TRP 172 and / or T-TRP 170, processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170, and processing sidelink transmissions with another ED 110. Processing operations related to preparing transmissions for uplink transmission may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding received symbols. According to an embodiment, the downlink transmission may be received by receiver 203, possibly using receive beamforming, and processor 210 may extract signaling from the downlink transmission (e.g., by detecting and / or decoding the signaling). An example of signaling may be a reference signal sent by NT-TRP 172 and / or T-TRP 170. In some embodiments, the processor 210 implements transmit beamforming and / or receive beamforming based on an indication of a beam direction, such as beam angle information (BAI), received from the T-TRP 170. In some embodiments, the processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting a synchronization sequence, decoding, and obtaining system information. In some embodiments, the processor 210 may perform channel estimation, for example, using a reference signal received from the NT-TRP 172 and / or the T-TRP 170.

[0054] Although not shown, the processor 210 may form part of the transmitter 201 and / or the receiver 203. Although not shown, the memory 208 may form part of the processor 210.

[0055] The processor 210 and the processing components of the transmitter 201 and the processing components of the receiver 203 may each be implemented by the same or different one or more processors, which are used to execute instructions stored in a memory (e.g., in the memory 208). Alternatively, the processor 210 and some or all of the processing components of the transmitter 201 and the processing components of the receiver 203 may each be implemented using a dedicated circuit, such as a programmed field-programmable gate array (FPGA), a graphical processing unit (GPU), or an application-specific integrated circuit (ASIC).

[0056] In some implementations, T-TRP 170 may use other names, such as base station, base transceiver station (BTS), wireless base station, network node, network device, network side device, sending / receiving node, Node B, evolved NodeB (eNodeB or eNB), home eNodeB, next generation NodeB (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, remote radio head, ground node, ground network device, ground base station, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), centralized unit (CU), distributed unit (DU), positioning node, etc. T-TRP 170 may be a macro BS, a micro BS, a relay node, a host node, etc., or a combination thereof. T-TRP 170 may refer to the above-mentioned device or refer to a means in the above-mentioned device (eg, a communication module, a modem, or a chip).

[0057] In some embodiments, various parts of the T-TRP 170 may be distributed. For example, some modules of the T-TRP 170 may be located away from the device housing the antenna 256 of the T-TRP 170, and may be coupled to the device housing the antenna 256 via a communication link (not shown) (sometimes referred to as a fronthaul, such as a common public radio interface (CPRI)). Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations such as ED110 location determination, resource allocation (scheduling), message generation, and encoding / decoding, which are not necessarily part of the device housing the antenna 256 of the T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, the T-TRP 170 may actually be multiple T-TRPs that operate together to serve the ED 110, for example, by using coordinated multi-point transmission.

[0058] The T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in this figure. One, some or all of the antennas 256 may also be panels. The transmitter 252 and the receiver 254 may be integrated into a transceiver. The T-TRP 170 also includes a processor 260 for performing operations, including operations related to preparing transmissions for downlink transmission to the ED 110, processing uplink transmissions received from the ED 110, preparing transmissions for backhaul transmission to the NT-TRP 172, and processing transmissions received from the NT-TRP 172 via the backhaul. Processing operations related to preparing for downlink transmission or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., multiple input multiple output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in uplink transmission or via backhaul transmission may include operations such as receive beamforming, demodulation, and decoding received symbols. The processor 260 may also perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating the content of a synchronization signal block (SSB), generating system information, etc. In some embodiments, the processor 260 also generates an indication of a beam direction (e.g., a BAI), which may be scheduled by the scheduler 253 for transmission. The processor 260 performs other network-side processing operations described herein, such as determining the location of the ED 110, determining the location of the deployed NT-TRP 172, etc. In some embodiments, the processor 260 may generate signaling, such as configuring one or more parameters of the ED 110 and / or one or more parameters of the NT-TRP 172. Any signaling generated by the processor 260 is sent by the transmitter 252. It should be noted that the "signaling" used herein may also be referred to as control signaling. Dynamic signaling may be transmitted in a control channel (eg, a physical downlink control channel (PDCCH)), and static or semi-static higher-layer signaling may be included in a packet transmitted in a data channel (eg, a physical downlink shared channel (PDSCH)).

[0059] The scheduler 253 may be coupled to the processor 260. The scheduler 253 may be included within the T-TRP 170 or operate separately from the T-TRP 170. The scheduler 253 may schedule uplink transmissions, downlink transmissions, and / or backhaul transmissions, including issuing scheduling grants and / or configuring scheduling-free (“configured grants”) resources. The T-TRP 170 also includes a memory 258 for storing information and data. The memory 258 stores instructions and data used, generated, or collected by the T-TRP 170. For example, the memory 258 may store software instructions or modules for implementing some or all of the functionality and / or embodiments described herein and executed by one or more processors 260.

[0060] Although not shown, the processor 260 may form a part of the transmitter 252 and / or the receiver 254. In addition, although not shown, the processor 260 may implement the scheduler 253. Although not shown, the memory 258 may form a part of the processor 260.

[0061] The processor 260, the scheduler 253, and the processing components of the transmitter 252 and the receiver 254 may each be implemented by the same or different one or more processors that execute instructions stored in a memory (e.g., the memory 258). Alternatively, some or all of the processor 260, the scheduler 253, and the processing components of the transmitter 252 and the processing components of the receiver 254 may be implemented using dedicated circuits (e.g., FPGA, GPU, or ASIC).

[0062] It should be noted that the NT-TRP 172 is shown as a drone only as an example, but the NT-TRP 172 can be implemented in any suitable non-ground form. In addition, in some implementations, the NT-TRP 172 may use other names, such as non-ground nodes, non-ground network devices, or non-ground base stations. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is shown. One, part, or all of the antennas may also be panels. The transmitter 272 and the receiver 274 may be integrated into a transceiver. The NT-TRP 172 also includes a processor 276 for performing operations; the operations include operations related to: preparing transmissions for downlink transmission to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmission to T-TRP 170, and processing transmissions received from T-TRP 170 via backhaul. Processing operations related to preparation for downlink transmission or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in uplink transmission or through backhaul transmission may include operations such as receive beamforming, demodulating received signals, and decoding received symbols. In some embodiments, processor 276 implements transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, such as configuring one or more parameters of ED110. In some embodiments, NT-TRP 172 implements physical layer processing, but does not implement high-level functions, such as functions of the medium access control (MAC) or radio link control (RLC) layer. Since this is only an example, more generally, NT-TRP 172 may implement higher-level functions in addition to physical layer processing.

[0063] The NT-TRP 172 also includes a memory 278 for storing information and data. Although not shown, the processor 276 may form part of the transmitter 272 and / or the receiver 274. Although not shown, the memory 278 may form part of the processor 276.

[0064] Processor 276 and the processing components of transmitter 272 and receiver 274 may each be implemented by the same or different one or more processors that execute instructions stored in memory (e.g., memory 278). Alternatively, processor 276 and some or all of the processing components of transmitter 272 and receiver 274 may be implemented using dedicated circuits (e.g., programmed FPGAs, GPUs, or ASICs). In some embodiments, NT-TRP 172 may actually be multiple NT-TRPs that operate together to serve ED 110, such as through coordinated multi-point transmission.

[0065] The T-TRP 170, NT-TRP 172, and / or ED 110 may include other components, but these components are omitted for clarity.

[0066] according to Figure 4 One or more steps of the methods of each embodiment provided herein may be performed by corresponding units or modules. Figure 4 Units or modules in a device are shown, such as in ED 110, in T-TRP 170, or in NT-TRP 172. For example, a signal can be sent by a sending unit or a sending module. A signal can be received by a receiving unit or a receiving module. A signal can be processed by a processing unit or a processing module. Other steps can be performed by an artificial intelligence (AI) or machine learning (ML) module. The corresponding units or modules can be implemented using hardware, one or more components or devices that execute software, or a combination thereof. For example, one or more of the units or modules can be integrated circuits, such as programmed FPGAs, GPUs, or ASICs. It should be understood that if the above modules are implemented using software for execution by a processor or the like, these modules can be retrieved by the processor in whole or in part as needed, retrieved individually or collectively for processing, retrieved in one or more instances as needed, and these modules themselves can include instructions for further deployment and instantiation.

[0067] Other details about ED 110, T-TRP 170 and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted here.

[0068] Having considered communications more generally above, attention is now turned to specific exemplary embodiments.

[0069] As described above, multiple services may be aggregated or integrated into one physical wireless link, and these services may have different key performance indicators (KPIs). Figure 5 is a block diagram illustrating an exemplary multi-service scenario, wherein services integrated into one link may include any one of URLLC, mMTC, eMBB, and Tbps services. Figure 5 , the communication devices include a network device 502, a vehicle-based device represented at 504, a home-based or other location-based device represented at 506, a user device represented at 508, and an industrial or machine-based device represented at 510, each having exemplary services as shown.

[0070] The present application is not limited to these or any other types of devices or services. Figure 5 It is intended to provide an exemplary scenario in which the embodiments disclosed herein may be particularly useful. More generally, the disclosed embodiments may be implemented in, for example, next-generation mobile and wireless network services, cloud and edge computing services, and perception services. Some embodiments may be particularly suitable for automated manufacturing systems in smart factories and / or other smart vertical scenarios, such as ports, distribution systems, and medical systems. These possible applications of the embodiments are also illustrative and non-limiting examples.

[0071] Multi-service scenarios, such as Figure 5 The scenario shown in the example can be considered as a form of multiple access (MA) within a user equipment (UE). MA within a UE refers to the simultaneous transmission of multiple services by the same terminal device.

[0072] One aspect of the present application relates to adding a new process between decoding failure and retransmission request. For example, this can be achieved by integrating various services into a single block or payload for encoding and understanding different service priorities. Service priority can refer to any of various characteristics or features, such as any of one or more of target BLER, delay and source. Some embodiments relate to a novel channel coding design to support the self-decodability of one or more individual payloads and the enhanced joint decodability of such individual payloads. Individual payloads may also be referred to as blocks, component payloads or short or shorter messages or payloads, and are part of larger payloads. Large payloads may also be referred to as longer payloads, combined payloads or code blocks. Payloads, messages and code blocks used here refer to bits before channel coding or after channel decoding.

[0073] In one possible self-decodable joint encoding design, each of the one or more individual payloads may correspond to, for example, a different service and may be self-decodable while supporting joint decoding to further enhance performance. Figure 6is a block diagram illustrating self-decoding 600 and joint decoding 610 in case of self-decoding failure.

[0074] For example, several smaller messages or shorter messages can be embedded or otherwise combined into a longer code block or payload, also referred to herein as a combined payload. These smaller messages are self-decodable, meaning that they can be decoded after collecting only a subset of the coded bits or symbols or LLRs associated with a longer codeword rather than the entire longer codeword. A subset of coded bits is also an independent short code or codeword that can be decoded by itself.

[0075] Two or more of such smaller messages are also jointly decodable. Subsets of the coded bits corresponding to the jointly decodable smaller messages are combined into a longer code. This can be achieved by what is referred to herein as "coupling" between bits from the multiple messages.

[0076] For example, some or all of the bits of the first message may be copied and combined with the bits of the second message. The combined message is then encoded as a joint codeword. In this example, the bits from the first message may be directly copied and appended to the bits of the second message or otherwise combined with the bits of the second message. Another possible option is to first convert the bits from the first message, such as by multiplying the bits from the first message with a binary matrix, and then append the converted bits to the bits of the second message, or otherwise combine the converted bits with the bits of the second message.

[0077] Although this example refers to information bit (message) coupling, coding bits may be used additionally or alternatively for coupling. For example, in the case of system coding, message bits are also part of the coding bits, so the two alternatives become roughly the same for information bit coupling or coding bit coupling.

[0078] Some embodiments support multiple decoding attempts before requesting a retransmission. For example, joint decoding can actually be inserted or attempted between a decoding failure and a retransmission request.

[0079] For example, consider an embodiment involving a three-decoding attempt transmission method. In a first decoding attempt 600, a receiver receives a codeword and decodes a self-decodable first payload of the codeword after receiving the corresponding minimum required coded bits. If the decoding of the first payload is successful, the correctly decoded bits can be used to enhance the decoding performance of the second payload of the codeword after receiving the corresponding minimum required number of coded bits for decoding the second payload.

[0080] If the first payload fails to decode, a second decoding attempt is made 610. Instead of immediately requesting a retransmission, the receiver continues to attempt to jointly decode the first payload with the second payload. After decoding the second payload, whether the second payload is decoded successfully or unsuccessfully, the joint decoding can increase the probability that the first payload is successfully decoded.

[0081] In this example, if the decoding of the first payload still fails after the second (joint) decoding attempt, the receiver requests a retransmission from the transmitter (not shown). This will cause some delay, but with the retransmission, the receiver can make at least a third decoding attempt. For the retransmitted codeword, multiple decoding attempts can be made to self-decode from the retransmitted codeword, to jointly decode from a portion of the retransmitted codeword, and / or to jointly decode using a previously received codeword and a retransmitted codeword.

[0082] Now consider an example where a device such as a robotic arm communicates with a network device such as a base station and supports URLLC, eMBB, and mMTC services. Assume that the video streaming data transmission of the device belongs to the eMBB service, the signaling to control one or more joints of the robotic arm belongs to the URLLC service, and the delay-insensitive perception or monitoring data reporting belongs to the mMTC service. Figure 7 is a block diagram illustrating this example, in which a robot arm 702 includes a video device and two joints, and communicates with a BS 704 .

[0083] Figure 8 FIG. 1 is a block diagram showing exemplary code blocks and encoding symbols provided by one embodiment. Figure 8 Similarly, in the following description Fig. 9 and Fig.10 In the figure, 800 represents a code block or a combined payload including individual payloads 802, 804, 806, 808, 810. The individual payloads 802, 804, 806, 808, 810 include payloads associated with different services in the example shown. The code block 800 is channel encoded to generate a codeword 820 for transmission. The codeword 820 is generated by encoding the individual payloads using an error correction code. Taking the eMBB individual payload as an example, a polarization code or a weaving code is shown. Other codes (including different codes for different individual payloads) are also possible. The codeword 820 is also shown as including N symbols, but the symbols are intended only as illustrative examples of portions of a codeword. The arrangement of the symbols shown at 820 is also intended to be an example of a possible decoding order. It should be interpreted accordingly. Figure 8 and similar Fig. 9 and Fig.10 .

[0084] A code block as shown in 800 may be referred to as a combined code block or a joint code block because it includes separate payloads, blocks or bits corresponding to the URLLC, eMBB and mMTC services in the example shown. URLLC, eMBB and mMTC coding symbols represent information about the transmission or reception of coded bits, which are part of a codeword. Coding symbols may be referred to by any of a variety of names or terms, such as a packet, block, code, sub-codeword, signal, LLR, resource element (RE), etc. For ease of reference, this application refers primarily to coding symbols or coding blocks when referring to parts of a codeword.

[0085] In codeword 820, URLLC, eMBB, and mMTC coded symbols are self-decodable. After receiving the coded bits of each coded symbol, the symbol can be decoded even if the entire codeword 820 has not been received in the case of URLLC and mMTC coded symbols in the illustrated example. For example, in a first decoding attempt, a self-decodable symbol can be decoded independently of other coded symbols and can also be jointly decoded with one or more other coded symbols, which can be (but do not necessarily have to be) self-decodable symbols, as disclosed herein.

[0086] Self-decodable and jointly decodable may be referenced in the context of data before or after channel coding. For example, a short code or block that is part of a longer codeword may be considered self-decodable because the block is self-decodable independently of the remainder of the longer codeword. The data encoded to generate the short code or block (e.g., also referred to herein as a separate payload) may be considered self-decodable because the separate payload can be self-decoded from the short code or block. For example, decodable is intended to mean the same thing, whether in the context of an uncoded payload or a coded symbol or packet, specifically, separate payloads and combined payloads can be decoded from a codeword, or equivalently, a codeword can be decoded to recover separate payloads and combined payloads. In other words, payload (information bits) and coded blocks or packets (coded bits) can be deterministically converted to each other. Payload / information bits or code packets / coded bits may be referred to as decodable, or encodable.

[0087] For example, in Figure 8 , URLLC individual payloads 802, 804 are placed at the beginning of the code block 800, so that these delay-sensitive payloads can be decoded first, followed by the eMBB individual payload 806, and then the mMTC individual payloads 808, 810.

[0088] At the receiver, the decoder first attempts to decode the URLLC-encoded symbol or short packet. Figure 8802 and 804 are labeled as symbol-1 and symbol-2 in . For illustrative purposes, the URLLC individual payload is shown as being encoded into corresponding self-decodable encoded symbols, but in other embodiments, the encoding is based on the service type, and 802, 804 are treated as a single payload and can be self-decoded together as a single payload. If the URLLC packet can be successfully decoded, the URLLC bits from the packet or the individual payload decoded from the packet can assist or enhance the decoding of one or more other packets, or more generally, the decoding of one or more other blocks or sub-codewords of the long codeword 820. For example, the encoded or decoded URLLC bits can be coupled in the eMBB individual payload 806, and / or in one or more eMBB encoded packets, including symbol-k, symbol-k=1,..., symbol-N–1, symbol-N in the example shown. The coupled bits can enhance the decoding of one or more eMBB packets. After URLLC decoding, the decoder can then decode one or more eMBB packets or decode one or more mMTC packets, including symbol-i and symbol-i+1 in the example shown. If the decoder attempts to decode one or more eMBB packets after URLLC decoding and the eMBB decoding is successful, one or more mMTC packets can be decoded with a lower error probability based on any coupled eMBB bits. Otherwise, if the decoder attempts to decode one or more mMTC packets after URLLC decoding and the decoding is successful, one or more eMBB packets can be decoded with an even lower probability based on any URLLC and / or mMTC bits coupled in the eMBB separate payload 806 or one or more eMBB packets. Figure 8 In the example shown, the arrangement of the encoded packets at 820 shows an embodiment that supports URLLC decoding, then mMTC decoding, then eMBB decoding, but this is not the only possible decoding order.

[0089] After successfully decoding the first packet (which may include one or more URLLC packets and / or one or more mMTC packets in the above example), enhanced decoding of the second packet (which may include one or more eMBB packets in the above example) is achieved by coupling information bits and / or coding bits between separate payloads and / or packets. For example, in the case of coupled information bits, the decoding-enhanced packet will be generated from fewer information bits of the separate payloads, but the packet length remains unchanged, which results in a lower code rate. In the case of coupled coded bits, the decoding-enhanced packet will effectively have shortened coded bits that are known in advance by the decoder, which actually also results in a lower code rate. In both cases, regardless of whether the information bits, coded bits, or both are coupled between packets, the reference bit can be reduced. Figure 8 The example described herein uses a code rate for enhancing decoding of one or more eMBB packets. This may provide improved decoding performance by increasing the probability of successful decoding.

[0090] It should be noted that one or more packets that provide or support decoding enhancements may also be self-decodable. Bit coupling between packets does not mean that enhanced decoding must rely on the previous successful decoding of the coupled bits. For example, whether the decoding of URLLC and / or mMTC packets is successful or not, refer to Figure 8 One or more eMBB packets in the described examples may be self-decodable.

[0091] Fig. 9 800 and coded symbol 820 are block diagrams showing exemplary code blocks and coded symbols provided by another embodiment. Figure 8 Same as shown, but Fig. 9 A different decoding at 900 is shown, which may be referred to as HARQ-free URLLC. If a self-decodable packet (eg, for URLLC) fails to decode, the receiver may proceed to decode another self-decodable packet (eg, for eMBB or mMTC, where mMTC is shown as Fig. 9 ), instead of requesting a retransmission. If the latter self-decodable packet is successfully decoded, the code rate of the previous packet can be reduced based on the coupled bits from the latter packet, thereby improving performance. Another option is that if the self-decodable packet (for example, for URLLC) fails to decode, the receiver can continue to jointly decode the entire joint codeword 820 to recover the entire code block 800, instead of requesting a retransmission. If the joint codeword 820 is successfully decoded, all bits at 800 can be correctly recovered. Fig. 9 In one example shown at 900, if both URLLC decoding and mMTC decoding fail, the joint decoding may still succeed.

[0092] There may be different modes of coupling between coding blocks such as URLLC symbols and eMBB symbols. For example, in a mode or method that may be referred to as tight coupling, the coupling is within a time slot or a combined or joint code block 800, such as Fig. 9 As shown. To achieve joint decoding, there is coupling between separate payloads or coding blocks within a code block 800 or code word 820. Another mode or method may be referred to as loose coupling, that is, coupling between two different time slots or joint code blocks, such as two consecutive time slots or code blocks. For example, tight coupling may be preferred because it supports joint decoding based on a single time slot or a single joint code word instead of multiple time slots or multiple code words.

[0093] Fig.10 800 and coded symbol 820 are block diagrams showing exemplary code blocks and coded symbols provided by yet another embodiment. Figure 8 and Fig. 9 Same as shown, but Fig.10 Different decodings are shown at 1000, which may be referred to as HARQ-free URLLC with incremental redundancy (IR) combining. In some embodiments, there may be multiple decoding attempts without requesting retransmissions, as described above. Figure 8 and Fig. 9 As shown, and if these decoding attempts fail, the receiver can request retransmissions using incremental redundancy HARQ. In the context of multiple decoding attempts before the receiver sends and the transmitter receives the first retransmission request, this type of approach can still be referred to as "HARQ-free", and as mentioned above, HARQ-free URLLC with IR adds the option of retransmission requests after multiple unsuccessful decoding attempts.

[0094] The retransmission preferably contains incremental redundant information, such as the first message ( Fig.10 IR decoding based on incremental coded bits is generally indicated by “IR Decoding” at 1000 for URLLC and mMTC in the illustrated example, because successful decoding of the first message will increase the chance of successful decoding of subsequent messages. Optionally, the retransmission may additionally or alternatively contain incremental redundant information, such as incremental coded bits of subsequent messages, to further enhance decoding performance. For URLLC and mMTC in the illustrated example, IR decoding based on incremental coded bits is generally indicated by “IR Decoding” at 1000.

[0095] After receiving the retransmitted coded bits, the receiver may perform a decoding attempt similar to that described above by way of example.

[0096] Regarding requests and retransmissions, consider the traditional HARQ method implemented by acknowledgment (ACK) and / or negative acknowledgement (NACK) signaling, and up to four redundancy versions (RV1, RV2, RV3, RV4) for retransmission options. NACK signaling can be considered as a form of retransmission request, in response to which a retransmission including a redundant version of the previously transmitted data is sent by the transmitter. In this type of method, a NACK will be sent by the receiver after the first decoding failure.

[0097] According to the embodiments disclosed herein, a second decoding attempt is made by NACK signaling or other means before requesting a retransmission (ie, "no HARQ"). This may involve behavior or features at one or both of the encoder / transmitting device and the decoder / receiving device.

[0098] For example, a new type of signaling can be provided to support multiple decoding attempts before retransmission. ACK signaling can be sent from a decoder or receiving device and received by an encoder or transmitting device in a multiple attempt embodiment to confirm that the decoding is successful. In addition to or possibly in place of traditional NACK signaling, new signaling indicating a decoding failure after a second (or subsequent) attempt can be provided. For ease of reference, this signaling is referred to as "NACK-2" signaling herein, but it can be called by different names. In the NACK-2 signaling indicating a decoding failure after multiple decoding attempts, the encoder or transmitting device can determine whether the negative acknowledgment is from the first decoding failure or the second (or subsequent) decoding failure. The encoder or transmitting device can then choose to prioritize one or more retransmissions of any decoder or receiving device that sends the NACK-2 signaling, and delay one or more retransmissions of other devices that send the NACK signaling.

[0099] In these NACK / NACK-2 examples, it is up to the decoder or receiving device to decide whether to use NACK or NACK-2 to request retransmission. The device may send both NACK and NACK-2 after multiple decoding failures, or completely skip NACK and not send NACK at all on the first decoding failure. How to use the difference between NACK and NACK-2 is up to the sending device. For example, in resource-constrained situations, retransmission of NACK-2 can be prioritized, or in resource-sufficient situations, NACK and NACK-2 can be treated equally.

[0100] The retransmission process may be different in addition or alternatively. For example, in addition to or in place of the redundancy versions RV1 to RV4 in the above-described conventional HARQ method, there may be one or more new redundancy versions or joint retransmission versions to indicate whether the retransmission is an independent RV (as in the above-described conventional example) or embedded in the incoming payload or packet by joint encoding (e.g., in an incoming eMBB packet, achieving joint decoding of a URLLC packet or payload). The latter type of embedded retransmission may be referred to as a joint retransmission version or J-RV, for example, to enable a decoder or receiving device to determine whether the retransmission is an independent RV or a J-RV.

[0101] Other attachments in this article Figure 1 Sample, Figures 8 to 10 Illustrative and non-limiting examples are provided. Variants are possible; for example, the individual payloads of different packages may be ordered according to any of a variety of criteria, such as their priority or urgency. It may be preferred that the individual payloads be decoded first for more urgent services such as URLLC, and accordingly, these individual payloads may be located at the beginning of the combined payload shown. The coded bits of these individual payloads will then be sent, received, and decoded before other payloads.

[0102] Other criteria may be considered in addition or alternatively. For example, individual payloads and / or corresponding packets may be sorted according to data or packet size. For example, packets with smaller messages (fewer information bits) or fewer coded bits may be placed, sent, and received / decoded first. This may allow for a smaller decoded LLR buffer, since the first received packet may be decoded quickly, and the corresponding LLRs may be flushed from the buffer subsequently.

[0103] There are several possible ways to provide or support self-decoding and joint decoding. For example, payloads or packets can be coupled according to a sequential or chained structure, or coupled in a star structure.

[0104] Fig.11 is a block diagram illustrating sequential coupling of bits between separate payloads according to a sequential or chained structure. This coding method that provides or supports self-decoding and joint decoding may additionally or alternatively be referred to as continuous embedding to express the concept that information bits from one separate payload are embedded in or otherwise combined with information bits of another separate payload.

[0105] exist Fig.11 In the example shown, K1 information bits (e.g., associated with a URLLC service) are encoded as N1 coded bits with a code rate of R1=K1 / N1. Of the K1 information bits, K'1 bits (K'1≤K1) are preset to K2 additional bits of different individual payloads (e.g., for eMBB). The embedded bits may be preset as shown, but in other embodiments, the embedded bits may be appended to information bits of different individual payloads or otherwise combined with information bits of different individual payloads. The combined K'2=K'1+K2 bits are encoded as N2 coded bits with a code rate of R2=K'2 / N2>R1. By presetting K3 additional bits from different individual payloads (e.g., for mMTC) in the example shown, K"2 bits from K'2 are embedded (K"2≤K'2), and the resulting K"3=K"2+K3 bits are encoded as N3 coded bits. The code rate is R3=K"3 / N3>R2. A joint codeword includes N1 coded bits, N2 coded bits, and N3 coded bits. This type of sequential or continuous embedding can be repeated for more individual payloads, or in some embodiments there may be less than three individual payloads.

[0106] Fig.12is a block diagram illustrating what may be referred to as a many-to-one coupling of bits between separate payloads according to a star structure. This encoding method that provides or supports self-decoding and joint decoding may additionally or alternatively be referred to as many-to-one embedding, where information bits from multiple different separate payloads are embedded in or otherwise combined with information bits of another separate payload.

[0107] exist Fig.12 In the example shown, K1 information bits (e.g., associated with a URLLC service) are encoded as N1 coded bits with a code rate of R1=K1 / N1, and K2 information bits (e.g., associated with an mMTC service) are encoded as N2 coded bits with a code rate of R2=K2 / N2. This operation can be repeated if there are more than two separate payloads to be coupled to another separate payload. K'1 bits of the K1 information bits (K'1≤K1), K'2 bits of the K2 information bits (K'2≤K2), and some or all of the information bits of any other separate payloads to be coupled are embedded in the K bits of different separate payloads. x Additional bits (e.g., for eMBB). The embedded bits may be preset as shown, but in other embodiments, the embedded bits may be appended to or otherwise combined with the information bits of different individual payloads. Combined K' x =K” x +K x bits are encoded as N x coded bits, with a code rate of R x =K' x / N x >R1,R x >R2, etc.

[0108] Fig.11 and Fig.12 An example of coupling is shown, where one or more common bits couple one or more self-decodable coding blocks with one or more other coding blocks. Fig.11 In the embodiment, common bits are embedded successively between corresponding individual payloads in the codeword that are encoded to generate a self-decodable coded block (e.g., a K1 bit block) and one or more other coded blocks according to the order of corresponding individual payloads in the combined payload corresponding to the codeword. Fig.12 In the example shown, common bits are embedded from respective separate payloads encoded to generate a self-decodable coded block (e.g., a K1 bit block) and another coded block (e.g., a K2 bit block) into a separate payload encoded to generate a coded block (e.g., in the example shown). Fig.12 at the bottom of the ).

[0109] These are merely examples, and other types of coupling between individual payloads and / or encoded packets are possible, including combinations of Fig.11 Sequential or continuous coupling with Fig.12 For example, in this hybrid coupling method, a first individual payload may be encoded according to a sequential coupling, and a second individual payload may be encoded according to a many-to-one coupling, or vice versa.

[0110] The coupling is not in any way limited to common bits between different individual payloads, and the common bits may additionally or alternatively be common to the coding blocks. Fig.11 In the example of the example in the codeword, but in the method applied to the coding bits, the common bits can be continuously embedded between the self-decodable coding block (e.g., N1 bit block) and one or more other coding blocks according to the order of the self-decodable coding block and the one or more other coding blocks in the codeword. Similarly, considering the many-to-one coupling of the coding blocks, the common bits can be embedded from the self-decodable block (e.g., N1 bit block) and one or more other coding blocks (e.g., N2 bit block) to a coding block (e.g., N2 bit block) that is encoded to generate a coding block. Fig.12 N at the bottom x bit block).

[0111] As another example, embedding may be applied only between some but not all individual payloads, and / or a combination of the two approaches may be applied.

[0112] Variations on the encoding of the information bits are also possible.

[0113] In coding Fig.11 and Fig.12 When encoding information bits in a packet, the same or similar type of code may be used to encode all information bits, or different codes may be used for different individual payloads. This may additionally or alternatively apply more generally to the encoding of individual payloads.

[0114] Common code types for all individual payloads may be more suitable for coupling between individual payloads or packets. Codes for soft-output iterative decoding include, for example, convolutional codes, turbo codes, low-density parity check (LDPC) codes, product codes, and weaving codes. Any of them can be jointly decoded. For example, after decoding two codewords independently, soft information about shared / coupled bits can be exchanged between the two codes (in inter-code iterations) before further decoding. Codes for hard-output continuous decoding include polar codes, polarization-adjusted convolutional (PAC) codes, Reed-Muller (RM) codes, Bose-Chaudhuri-Hocquenghem (BCH) codes, and Reed-Solomon (RS) codes. These codes can also be decoded using joint continuous cancellation. For example, after decoding one codeword, the shared / coupled bits of the codeword can be eliminated from another codeword, and then the other codeword can be decoded. Since codes belonging to any type have more compatible decoders, they can be more conveniently decoded together. Therefore, for individual payloads that are part of the same composite payload, preferably the same type of code (ie, soft or hard) is used. However, different types of codes may be used in other embodiments.

[0115] Various aspects of the present application have been described above and illustrated by way of example in the accompanying drawings. Fig.13 is a flow chart of a more general exemplary method provided by the embodiment. On the left side, Fig.13 1300 in the figure shows the operations or features that can be provided or supported at the encoder or the transmitting end device, and on the right side, 1350 shows the operations or features that can be provided or supported at the decoder or the receiving end device. Fig.13 In the description of , a device that can implement or support encoding and / or sending features is referred to as a first communication device, and a device that can implement or support decoding and / or receiving features is referred to as a second communication device. Embodiments may involve either or both of these devices.

[0116] Referring first to 1300, the sending at 1308 is intended to represent, from the perspective of the sending device, the sending of a codeword by a first communication device in a wireless communication network to a second communication device. The codeword is or includes a coded block generated by encoding a corresponding individual payload using an error correction code. The coded block includes a self-decodable coded block that can be decoded independently of other coded blocks and can also be jointly decoded with one or more other coded blocks in the other coded blocks.

[0117] Fig.13 Also shown are the operations that may be involved in generating a codeword. Fig.13 Retrieving individual payloads, which may be or include, for example, data from different devices and / or data associated with different services, is shown at 1302. For example, retrieving payloads at 1302 may involve collecting or otherwise receiving data output from one or more devices and / or services, or accessing payload data in memory.

[0118] 1304 is intended to illustrate encoding each individual payload using an error correction code to generate a codeword, as described elsewhere herein, which includes a coding block corresponding to the respective individual payload. The coding block includes a self-decodable coding block, and may include more than one self-decodable coding block.

[0119] As shown at 1306, the method may also involve outputting the generated codeword at 1306. The codeword may be output for storage to a memory and / or for transmission, for example, at 1308.

[0120] In some embodiments, the method may involve acquiring as shown at 1302, encoding as shown at 1304, and outputting as shown at 1306. Other embodiments may involve sending a codeword as shown at 1308. These embodiments are not mutually exclusive, and the method may involve acquiring and encoding a separate payload as shown at 1302, 1304, and also include sending a codeword as shown at 1306.

[0121] The joint decodability of the self-decodable coding block may provide or enable any of the various other features disclosed herein. For example, the fact that the self-decodable coding block may also be jointly decodable with one or more other coding blocks in the other coding blocks of the codeword may enable joint decoding of one or more other coding blocks based on the success of decoding the self-decodable coding block independently of the other coding blocks. This is at least in the above reference to Figure 8 By way of example this is referred to as enhanced decoding.

[0122] The self-decodable coded block may also be jointly decoded with one or more other coded blocks, which may additionally or alternatively enable the joint decoding of the self-decodable coded block after a failure to decode the self-decodable coded block independently of the other coded blocks. A second attempt, and possibly one or more subsequent attempts, may be made to jointly decode the self-decodable coded block after a decoding failure, rather than requesting a retransmission after a decoding failure. This is at least in reference to the above Fig. 9 By way of example it is referred to as a HARQ-free method.

[0123] From the perspective of an encoder or transmitter, the method referred to herein as HARQ-free with IR combination by way of example may be summarized as involving receiving a first retransmission request, which may be or include NACK-2 signaling, for example, and retransmitting IR information, which may be or include RV or J-RV, for example. In one embodiment, a method may involve, at 1310, a first communication device receiving a first retransmission request from a second communication device after failing to decode a self-decodable coding block independently of other coding blocks and jointly decode the self-decodable coding block. It should be noted that the received request is the first retransmission request after multiple decoding failures. As shown in 1312, the method may also involve the first communication device retransmitting the IR information of the self-decodable coding block to the second communication device in response to the first retransmission request. For example, other IR information may also be sent at 1312 for other coding blocks.

[0124] although Fig.13 Only the sending of IR information at 1312 is shown, but it should be noted that some embodiments may involve generating and outputting IR information of a self-decodable coded block in response to a first retransmission request received after a failure to decode the self-decodable coded block independently of other coded blocks and to jointly decode the self-decodable coded block. Fig.13 The generation and output are not shown separately to avoid further cluttering the drawing.

[0125] Joint decoding of self-decodable coded blocks may be achieved by coupling as disclosed herein.For example, common bits may couple a self-decodable coded block with each of one or more other coded blocks that may be used to jointly decode the self-decodable coded block.

[0126] As reference Fig.11 and Fig.12 As described by way of example, common bits from one separate payload or one coded block may be embedded in or otherwise combined with bits from another separate payload or coded block. Consider an example of consecutive embedding of coded bits, where common bits are consecutively embedded between a self-decodable coded block and one or more other coded blocks according to the order of the self-decodable coded block and the one or more other coded blocks in a codeword (or in other words, a method may involve embedding common bits). In the example Fig.11 In the continuous embedding of payload bits shown, common bits have been continuously embedded between corresponding individual payloads of a self-decodable coded block and one or more other coded blocks encoded to generate a codeword according to the order of the corresponding individual payloads in a combined payload that includes the individual payloads (or in other words, a method may involve embedding common bits).

[0127] Another coupling example disclosed at least above is called many-to-one embedding, which involves coupling a self-decodable coding block and at least one other coding block to the same other coding block so that the self-decodable coding block can also be jointly decoded with two or more other coding blocks.

[0128] For a coded bit embedding embodiment, common bits are embedded from a self-decodable coded block in which the common bits are embedded or are being embedded and each coded block except one of the two or more coded blocks into the one coded block of the two or more coded blocks that can be jointly decoded with the self-decodable coded block (or in other words, a method may involve embedding common bits).

[0129] For many-to-one embedding of individual payload bits, common bits are embedded (or in other words, a method may involve embedding common bits) into one of the corresponding individual payloads that are encoded to generate one of two or more coded blocks that can be jointly decodable with the self-decodable coded block. The common bits are from the corresponding individual payloads that are encoded to generate the self-decodable coded block and each coded block except one of the two or more coded blocks.

[0130] At 1350, Fig.13 Various decoding and / or receiving corresponding steps of the features shown at 1300 are shown. From the perspective of the receiving device, the receiving at 1352 is intended to represent the receiving of the codeword by a second communication device in the wireless communication network from the first communication device. As in other embodiments, the codeword is or includes a coded block generated by encoding the corresponding individual payload using an error correction code, and at least in this sense, the coded block corresponds to the corresponding error correction encoded individual payload. The coded block includes a self-decodable coded block that can be decoded independently of other coded blocks and can also be decoded jointly with one or more other coded blocks in the other coded blocks.

[0131] Fig.13 Also shown are the operations that may be involved in decoding a codeword. At 1354, Fig.13 Decoding of individual payloads from a codeword comprising an encoding block corresponding to a respective error correction encoded individual payload is shown.After successful decoding, the individual payloads are output as shown at 1358, for example, for storage to a memory and / or further processing.

[0132] The receiving and decoding at 1352, 1354 may involve different receiving device components or features, but need not be mutually exclusive. The method may involve receiving a codeword at 1352 and decoding a separate payload from the codeword at 1354.

[0133] The decoding at 1354 may involve, for example, decoding the self-decodable coded block independently of other coded blocks, and jointly decoding one or more other coded blocks in the other coded blocks based on the success of decoding the self-decodable coded block independently of other coded blocks in the plurality of coded blocks. This is at least in the above reference to Figure 8 By way of example this is referred to as enhanced decoding. If the decoding is successful, a separate payload is output at 1358 .

[0134] Decoding may additionally or alternatively involve jointly decoding a self-decodable coded block after a failure to decode the self-decodable coded block independently of other coded blocks in the plurality of coded blocks. The "No (First Attempt)" label and the return arrow from 1356 to 1354 are intended to indicate a second attempt and possibly one or more subsequent attempts to jointly decode the self-decodable coded block after a decoding failure, rather than requesting a retransmission after a decoding failure. This is at least in reference to the above Fig. 9 This is referred to as a HARQ-free method by way of example. If decoding is successful after one or more subsequent attempts, a separate payload is output at 1358 .

[0135] A method also referred to herein by way of example as HARQ-free with IR combining may be summarized as involving a retransmission request, as shown at 1360. A method may involve sending a first retransmission request from a second communications device to a first communications device after a failure to decode a self-decodable coded block independently of other coded blocks and to jointly decode the self-decodable coded block, at 1360. This may be performed at Fig.13 , represented by the "No (final attempt)" label and the arrow from 1356. The request sent is the first retransmission request after multiple decoding failures, and may be, for example, or include NACK-2 signaling. IR information may be sent in response to the first request, as shown at 1312, and from the perspective of a receiving device, a method may involve, in response to the first retransmission request sent at 1360, a second communication device receiving IR information for a self-decodable coded block from the first communication device. For example, the IR information may be or include an RV or J-RV redundancy version. Other IR information, such as for other coded blocks, may also be received in response to the request.

[0136] Fig.13The dashed arrows from 1312 to 1352 in are intended to represent the sending and receiving of IR information, and the processing returns to 1352 to illustrate the performance of incremental redundancy decoding based on the IR information obtained for the self-decodable coded block in response to a first retransmission request after a failure to decode the self-decodable coded block independently of other coded blocks and to jointly decode the self-decodable coded block. 1352 involves receiving a codeword, but in the case of a retransmission, the same codeword may or may not be received again. The decoding after the retransmission may also be different, involving, for example, joint decoding using previously received codewords in combination with newly received IR information.

[0137] Coupling examples provided elsewhere herein may be provided in methods involving receiving and / or decoding codewords. Common bits from one separate payload or one coding block may be embedded in or otherwise combined with bits from another separate payload or coding block.

[0138] From the perspective of a receiver or decoder, an embodiment using continuous embedding of coded bits may involve embedding common bits continuously between a self-decodable coded block and one or more other coded blocks, depending on the order of the self-decodable coded block and the one or more other coded blocks in a codeword. Fig.11 In the consecutive embedding of payload bits shown, common bits have been consecutively embedded between corresponding individual payloads corresponding to a self-decodable coded block and one or more other coded blocks in a codeword according to the order of the corresponding individual payloads in a combined payload including the individual payloads.

[0139] In many-to-one embedding, the common bits may have been embedded into one of the two or more coding blocks that can be jointly decoded with the self-decodable coding block from the self-decodable coding block in which the common bits are embedded or are being embedded and each coding block except one of the two or more coding blocks. For many-to-one embedding of individual payload bits, the common bits may have been embedded into one of the corresponding individual payloads, the individual payload corresponding to one of the two or more coding blocks that can be jointly decoded with the self-decodable coding block. The common bits come from the corresponding individual payloads corresponding to the self-decodable coding block and each coding block except one of the two or more coding blocks.

[0140] In these coupled or embedded examples, the common bits may be decoded at a receiver or decoder, and accordingly, a method may involve decoding these bits for joint decoding.

[0141] The present application includes various embodiments, including not only method embodiments, but also other embodiments, such as device embodiments and embodiments related to non-transitory computer-readable storage media. The embodiments may combine the features disclosed herein alone or in combination.

[0142] The apparatus may include a processor and a non-transitory computer-readable storage medium coupled to the processor for storing a program for execution by the processor. Figure 3 In the embodiment of the present invention, for example, processors 210, 260, 276 may be or include one or more processors, and each memory 208, 258, 278 is an example of a non-transitory computer-readable storage medium in ED 110 and TRP 170, 172. For example, a non-transitory computer-readable storage medium need not be provided only in conjunction with a processor, but may be provided separately in a computer program product.

[0143] As an illustrative example, a program stored in or on a non-transitory computer-readable storage medium may include instructions for or for causing a processor to perform the following operations: a first communication device sends a codeword to a second communication device in a wireless communication network, the codeword including a coded block generated by encoding a corresponding individual payload using an error correction code. The program may additionally or alternatively include instructions for or for causing a processor to perform the following operations: obtaining individual payloads; encoding each of the individual payloads using an error correction code to generate a codeword; and outputting the codeword.

[0144] The coding blocks include self-decodable coding blocks that can be decoded independently of other coding blocks and can also be decoded jointly with one or more other coding blocks in other coding blocks.

[0145] For example, embodiments relating to an apparatus or non-transitory computer-readable storage medium may include any one or more of the following features, which are also discussed elsewhere herein:

[0146] The self-decodable coding block may also be jointly decoded with one or more other coding blocks in other coding blocks, which may enable joint decoding of one or more other coding blocks in other coding blocks based on successful decoding of the self-decodable coding block independently of other coding blocks;

[0147] The self-decodable coded block may also be jointly decoded with one or more other coded blocks in other coded blocks, which may enable the self-decodable coded block to be jointly decoded after a failure to decode the self-decodable coded block independently of other coded blocks;

[0148] The program also includes instructions for or for causing the processor to perform the following operations: after decoding the self-decodable coded block independently of other coded blocks and jointly decoding the self-decodable coded block fails, the first communication device receives a first retransmission request, such as NACK-2 signaling, from the second communication device;

[0149] The program further includes instructions for or for causing the processor to perform the following operations: the first communication device retransmits incremental redundancy information of the self-decodable coded block, such as RV or J-RV, to the second communication device in response to the first retransmission request;

[0150] The program also includes instructions for or for causing the processor to: generate and output incremental redundancy information for a self-decodable coded block in response to a first retransmission request received after a failure to decode the self-decodable coded block independently of other coded blocks and to jointly decode the self-decodable coded block;

[0151] The common bits couple the self-decodable coded block with each of one or more of the other coded blocks;

[0152] Common bits have been embedded successively between the self-decodable coded block and one or more of the other coded blocks according to the order of the self-decodable coded block and one or more of the other coded blocks in the codeword;

[0153] The program also includes instructions for or for causing the processor to: embed common bits successively between the self-decodable coding block and one or more other coding blocks of the other coding blocks according to the order of the self-decodable coding block and one or more other coding blocks of the other coding blocks in the codeword;

[0154] having embedded common bits successively between respective individual payloads of the self-decodable coded block and one or more other coded blocks in the coded block encoded to generate the codeword according to an order of the respective individual payloads in the combined payload including the individual payloads;

[0155] The program further includes instructions for or for causing the processor to: embed common bits successively between respective individual payloads of the self-decodable coded block and one or more other coded blocks in the coded block encoded to generate the codeword according to an order of respective individual payloads in a combined payload including the individual payloads;

[0156] One or more coding blocks in the other coding blocks include two or more coding blocks;

[0157] Common bits have been embedded from the self-decodable coded block and each coded block except one coded block from the two or more coded blocks into the one coded block from the two or more coded blocks;

[0158] The program also includes instructions for or for causing the processor to: embed common bits from the self-decodable coded block and each coded block except one of the two or more coded blocks into the one coded block of the two or more coded blocks;

[0159] The common bits have been embedded from each but one of the two or more coded blocks encoded to generate the self-decodable coded block and into a separate payload of a corresponding separate payload of one of the coded blocks encoded to generate the two or more coded blocks;

[0160] The program also includes instructions for or for causing the processor to perform the following operations: embedding common bits from each coded block except one of the two or more coded blocks encoded to generate the self-decodable coded block into a separate payload of the corresponding separate payloads of one of the coded blocks encoded to generate the two or more coded blocks.

[0161] The program stored in or on a non-transitory computer-readable storage medium may additionally or alternatively include instructions for or for causing a processor to perform the following operations: a second communication device in a wireless communication network receives a codeword from a first communication device, the codeword including a coding block corresponding to a corresponding error-correction-encoded individual payload. The program may additionally or alternatively include instructions for or for causing a processor to perform the following operations: decoding an individual payload from a codeword including a coding block corresponding to a corresponding error-correction-encoded individual payload; outputting an individual payload.

[0162] The coding blocks include self-decodable coding blocks that can be decoded independently of other coding blocks and can also be decoded jointly with one or more other coding blocks in other coding blocks.

[0163] For example, embodiments relating to an apparatus or non-transitory computer-readable storage medium may include any one or more of the following features, which are also discussed elsewhere herein:

[0164] The program includes instructions for or for causing a processor to perform the following operations: decoding a separate payload by: decoding a self-decodable coded block independently of other coded blocks in a plurality of coded blocks, and based on successful decoding of the self-decodable coded block independently of the other coded blocks, jointly decoding one or more other coded blocks in the other coded blocks;

[0165] The program includes instructions for or for causing a processor to: decode the individual payload by: jointly decoding a self-decodable coded block after a failure to decode the self-decodable coded block independently of other coded blocks in a plurality of coded blocks;

[0166] The program also includes instructions for or for causing the processor to perform the following operations: after failing to decode the self-decodable coded block independently of other coded blocks and jointly decode the self-decodable coded block, the second communication device sends a first retransmission request, such as NACK-2 signaling, to the first communication device;

[0167] The program includes instructions for or for causing a processor to perform the following operations: in response to the first retransmission request, the second communication device receives incremental redundancy information of a self-decodable coded block, such as RV or J-RV, from the first communication device;

[0168] The program includes instructions for or for causing a processor to: in response to a first retransmission request received after a failure to decode the self-decodable coded block independently of other coded blocks and to jointly decode the self-decodable coded block, perform incremental redundancy decoding based on incremental redundancy information obtained for the self-decodable coded block;

[0169] The common bits couple the self-decodable coded block with each of one or more of the other coded blocks;

[0170] Common bits have been embedded successively between the self-decodable coded block and one or more of the other coded blocks according to the order of the self-decodable coded block and one or more of the other coded blocks in the codeword;

[0171] The program also includes instructions for or for causing the processor to: embed common bits successively between the self-decodable coding block and one or more other coding blocks of the other coding blocks according to the order of the self-decodable coding block and one or more other coding blocks of the other coding blocks in the codeword;

[0172] Common bits have been embedded successively between respective individual payloads corresponding to the self-decodable coded block in the codeword and one or more other coded blocks in accordance with an order of respective individual payloads in a combined payload comprising the individual payloads;

[0173] The program further includes instructions for or for causing the processor to: embed common bits successively between respective individual payloads corresponding to the self-decodable coded block in the codeword and one or more other coded blocks in the other coded blocks according to an order of respective individual payloads in a combined payload including the individual payloads;

[0174] One or more coding blocks in the other coding blocks include two or more coding blocks;

[0175] Common bits have been embedded from the self-decodable coded block and each coded block except one coded block from the two or more coded blocks into the one coded block from the two or more coded blocks;

[0176] The program also includes instructions for or for causing the processor to: embed common bits from the self-decodable coded block and each coded block except one of the two or more coded blocks into the one coded block of the two or more coded blocks;

[0177] The common bits have been embedded from the corresponding separate payloads corresponding to the self-decodable coded block and each coded block except one of the two or more coded blocks into one of the respective separate payloads corresponding to one of the two or more coded blocks;

[0178] The program also includes instructions for or for causing the processor to perform the following operations: embed common bits from each coding block except one of the two or more coding blocks and corresponding to the self-decodable coding block into a separate payload in the corresponding separate payloads corresponding to one of the two or more coding blocks.

[0179] Embodiments disclosed herein cover various aspects of what may be referred to as intra-UE MA coding.

[0180] The multiple payloads are encoded into a joint codeword that includes one or more self-decodable shorter codewords.

[0181] According to the enhanced decoding method, after successfully decoding a self-decodable codeword, the code rate of at least one other self-decodable codeword may be reduced, thereby improving performance by increasing the possibility of correctly decoding another self-decodable codeword.

[0182] If the decoding of a self-decodable codeword fails, the receiver can continue to decode another self-decodable codeword instead of immediately requesting retransmission. If the latter self-decodable codeword is successfully decoded, the code rate of the previous (decoding failed) codeword can be reduced, thereby improving performance.

[0183] In some embodiments, only if the above second (and possibly further subsequent) decoding attempts fail again, the receiver requests a retransmission, for example using incremental redundancy HARQ.

[0184] Multiple payloads are encoded as long codewords, where (in various embodiments):

[0185] One payload, several payloads or all payloads are self-decodable after receiving only a subset of the joint codewords containing all the encoded information of said payloads;

[0186] All or some of the bits of a payload to be encoded as a shorter code may be embedded in or otherwise combined with bits of another payload to be encoded as a longer code;

[0187] The code rate of the (embedded) shorter code is less than the code rate of the (embedded) longer code;

[0188] The embedding can be performed step by step, or, as mentioned in this article, continuously, such as Code1→Code2→Code3→…;

[0189] The embedding may additionally or alternatively be many-to-one, e.g. Code1 → CodeX, Code2 → CodeX, Code3 → CodeX, ...

[0190] Potential advantages may include, for example, any one or more of the following:

[0191] Recovery capability, which has the ability to quickly recover from multiple decoding failures compared to retransmission-based methods;

[0192] Providing multiple services with different KPI requirements, for example, code rate design can help ensure additional reliability of URLLC over eMBB;

[0193] Lower latency relative to IR-HARQ, as the disclosed HARQ-free technique can potentially avoid the higher latency associated with IR-HARQ;

[0194] Better performance, as URLLC performance can be significantly enhanced after the second (or subsequent) decoding attempt, but eMBB performance is almost the same as e.g. Figures 8 to 10 The independent decoding is the same as in the illustrated embodiment, in which URLLC decoding and mMTC decoding are attempted first;

[0195] Flexibility, because, for example, any of a variety of embedding methods can be supported to meet different QoS requirements.

[0196] Embodiments may be applicable to a wide range of communication networks, such as 5G+, 6G, WiFi, non-terrestrial networks (NTN), and distributed networks or ad hoc networks.

[0197] Although the present application has been described with reference to illustrative embodiments, this specification is not to be interpreted in a limiting sense. Various modifications and combinations of the illustrative embodiments and other embodiments of the present application will be apparent to those skilled in the art with reference to this specification. Therefore, the appended claims are intended to cover any such modifications or embodiments.

[0198] For example, features disclosed herein in the context of method embodiments may additionally or alternatively be implemented in apparatus or computer program product embodiments. Furthermore, although embodiments are primarily described in the context of methods and apparatus, other implementations are also contemplated, such as instructions stored in one or more non-transitory computer-readable media. These media may store programs or instructions to perform any of a variety of methods consistent with the present application.

[0199] Although various aspects of the present application have been described with reference to the specific features and embodiments of the present application, various modifications and combinations of the present application can be formulated without departing from the present application. The specification and the drawings are therefore only regarded as the description of some embodiments of the present application defined by the attached claims, and any and all modifications, variants, combinations or equivalents within the scope of the present application are considered to be covered. Therefore, although the embodiments and possible advantages have been described in detail, various changes, substitutions and modifications can be made here without departing from the present application defined by the attached claims. In addition, the scope of the present application is not limited to the specific embodiments of the processes, machines, products, material compositions, modules, methods and steps described in the specification. It will be easily understood by those of ordinary skill in the art from the disclosure of the present application that the processes, machines, manufactured products, material compositions, modules, methods or steps (including currently existing or later developed) that perform or realize the functions or results substantially the same as the corresponding embodiments described herein can be used according to the present application. Accordingly, the scope of the attached claims includes these processes, machines, products, material compositions, components, methods or steps.

[0200] In addition, any module, component, or device that executes instructions as illustrated herein may include or otherwise access one or more non-transitory computer-readable or processor-readable storage media to store information, such as computer-readable or processor-readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer-readable or processor-readable storage media includes magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, compact disc read-only memory (CD-ROM), digital video discs or digital versatile discs (DVD), Blu-ray discs, or other optical discs. TMOptical disks, or other optical storage, volatile and non-volatile, removable and non-removable media implemented in any method or technology, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other storage technology. Any such non-transitory computer-readable or processor-readable storage medium can be part of a device or can be accessed or connected to a device. Any application or module described herein can be implemented using computer-readable and executable instructions, or the processor can be stored or otherwise held by such non-transitory computer-readable or processor-readable storage medium.

Claims

1. A method, characterized in that include: A first communication device transmits a codeword to a second communication device in a wireless communication network, the codeword comprising a plurality of coded blocks generated by encoding respective individual payloads using an error correction code, the plurality of coded blocks comprising a self-decodable coded block, The self-decodable coding block can be decoded independently of other coding blocks in the plurality of coding blocks, The self-decodable coded block may also be jointly decodable with one or more other coded blocks of the other coded blocks of the plurality of coded blocks of the codeword.

2. A method, characterized in that include: Get multiple individual payloads; encoding each of the individual payloads using an error correction code to generate a codeword, the codeword comprising a plurality of coded blocks corresponding to respective individual payloads of the plurality of individual payloads, the plurality of coded blocks comprising a self-decodable coded block; output the codeword, The self-decodable coding block can be decoded independently of other coding blocks in the plurality of coding blocks, The self-decodable coded block may also be jointly decodable with one or more other coded blocks of the other coded blocks of the plurality of coded blocks of the codeword.

3. The method according to claim 1, characterized in that Also includes: obtaining the plurality of individual payloads; Each of the individual payloads is encoded to generate the codeword, the codeword including the plurality of encoding blocks respectively corresponding to the individual payloads.

4. The method according to any one of claims 1 to 3, characterized in that The self-decodable coding block can also be jointly decoded with one or more other coding blocks in the other coding blocks, which can make it possible to jointly decode the one or more other coding blocks in the other coding blocks based on the successful decoding of the self-decodable coding block independently of the other coding blocks in the multiple coding blocks.

5. The method according to any one of claims 1 to 4, characterized in that The self-decodable coded block may also be jointly decoded with one or more other coded blocks among the other coded blocks, which may enable the self-decodable coded block to be jointly decoded after failure to decode the self-decodable coded block independently of the other coded blocks among the multiple coded blocks.

6. The method according to claim 1, characterized in that Also includes: The first communication device receives a first retransmission request from the second communication device; The first communication device retransmits the incremental redundancy information of the self-decodable coded block to the second communication device in response to the first retransmission request.

7. The method according to claim 2 or 3, characterized in that: Also includes: In response to the first retransmission request, incremental redundancy information of the self-decodable coded block is generated and output.

8. The method according to any one of claims 1 to 7, characterized in that Common bits couple the self-decodable coded block with each of the one or more other coded blocks of the other coded blocks.

9. The method according to claim 8, characterized in that The common bits are a subset of bits of the self-decodable coded block, the subset of bits of the self-decodable coded block being encoded to generate the one or more other of the other coded blocks.

10. The method according to claim 8, characterized in that The common bits are a subset of bits of a separate payload of the corresponding separate payload, the separate payload being encoded to generate the self-decodable coded block, the subset of bits of the separate payload being encoded to generate the one or more other coded blocks of the other coded blocks.

11. A method, characterized in that include: a second communication device in a wireless communication network receiving a codeword from a first communication device, the codeword comprising a plurality of coded blocks corresponding to respective error correction encoded individual payloads, the plurality of coded blocks comprising a self-decodable coded block, The self-decodable coding block can be decoded independently of other coding blocks in the plurality of coding blocks, The self-decodable coded block may also be jointly decodable with one or more other coded blocks of the other coded blocks of the plurality of coded blocks of the codeword.

12. The method according to claim 11, characterized in that Also includes: The self-decodable coded blocks are decoded to obtain individual payloads from the codewords.

13. The method according to claim 11 or 12, characterized in that: Also includes: decoding the self-decodable coded block independently of the other coded blocks in the plurality of coded blocks; Based on successfully decoding the self-decodable coded block independently of the other coded blocks in the plurality of coded blocks, jointly decoding the one or more other coded blocks in the other coded blocks.

14. The method according to any one of claims 11 to 13, characterized in that Also includes: The self-decodable coded block is jointly decoded after failing to decode the self-decodable coded block independently of the other coded blocks in the plurality of coded blocks.

15. The method according to any one of claims 11 to 14, characterized in that Also includes: The second communication device sends a first retransmission request to the first communication device; The second communication device receives incremental redundancy information of the self-decodable coded block from the first communication device in response to the first retransmission request.

16. The method according to claim 15, characterized in that Also includes: In response to the first retransmission request, incremental redundancy decoding is performed based on incremental redundancy information obtained for the self-decodable coded block.

17. The method according to any one of claims 11 to 16, characterized in that Common bits couple the self-decodable coded block with each of the one or more other coded blocks of the other coded blocks.

18. The method according to claim 17, characterized in that The common bits are a subset of bits of the self-decodable coded block, the subset of bits of the self-decodable coded block being encoded to generate the one or more other of the other coded blocks.

19. The method according to claim 17, characterized in that The common bits are a subset of bits of a separate payload of the corresponding separate payload, the separate payload being encoded to generate the self-decodable coded block, the subset of bits of the separate payload being encoded to generate the one or more other coded blocks of the other coded blocks.

20. A device, characterized in that: include: processor; A non-transitory computer-readable storage medium coupled to the processor and storing a program executed by the processor, the program including instructions for: A first communication device transmits a codeword to a second communication device in a wireless communication network, the codeword comprising a plurality of coded blocks generated by encoding respective individual payloads using an error correction code, the plurality of coded blocks comprising a self-decodable coded block, The self-decodable coding block can be decoded independently of other coding blocks in the plurality of coding blocks, The self-decodable coded block may also be jointly decodable with one or more other coded blocks of the other coded blocks of the plurality of coded blocks of the codeword.

21. A device, characterized in that: include: processor; A non-transitory computer-readable storage medium coupled to the processor and storing a program executed by the processor, the program including instructions for: Get multiple individual payloads; encoding each of the individual payloads using an error correction code to generate a codeword, the codeword comprising a plurality of coded blocks corresponding to respective individual payloads of the plurality of individual payloads, the plurality of coded blocks comprising a self-decodable coded block; output the codeword, The self-decodable coding block can be decoded independently of other coding blocks in the plurality of coding blocks, The self-decodable coded block may also be jointly decodable with one or more other coded blocks of the other coded blocks of the plurality of coded blocks of the codeword.

22. The device according to claim 20, characterized in that The program also includes instructions for: obtaining the plurality of individual payloads; Each of the individual payloads is encoded to generate the codeword, the codeword including the plurality of encoding blocks respectively corresponding to the individual payloads.

23. The device according to any one of claims 20 to 22, characterized in that The self-decodable coding block can also be jointly decoded with one or more other coding blocks in the other coding blocks, which can make it possible to jointly decode the one or more other coding blocks in the other coding blocks based on the successful decoding of the self-decodable coding block independently of the other coding blocks in the multiple coding blocks.

24. The device according to any one of claims 20 to 23, characterized in that The self-decodable coded block may also be jointly decoded with one or more other coded blocks among the other coded blocks, which may enable the self-decodable coded block to be jointly decoded after failure to decode the self-decodable coded block independently of the other coded blocks among the multiple coded blocks.

25. The device according to claim 20, characterized in that The program also includes instructions for: The first communication device receives a first retransmission request from the second communication device; The first communication device retransmits the incremental redundancy information of the self-decodable coded block to the second communication device in response to the first retransmission request.

26. The device according to claim 21 or 22, characterized in that The program also includes instructions for: In response to the first retransmission request, incremental redundancy information of the self-decodable coded block is generated and output.

27. The device according to any one of claims 20 to 26, characterized in that Common bits couple the self-decodable coded block with each of the one or more other coded blocks of the other coded blocks.

28. The device according to claim 27, characterized in that The common bits are a subset of bits of the self-decodable coded block, the subset of bits of the self-decodable coded block being encoded to generate the one or more other of the other coded blocks.

29. The device according to claim 27, characterized in that The common bits are a subset of bits of a separate payload of the corresponding separate payload, the separate payload being encoded to generate the self-decodable coded block, the subset of bits of the separate payload being encoded to generate the one or more other coded blocks of the other coded blocks.

30. A device, characterized in that: include: processor; A non-transitory computer-readable storage medium coupled to the processor and storing a program executed by the processor, the program including instructions for: a second communication device in a wireless communication network receiving a codeword from a first communication device, the codeword comprising a plurality of coded blocks corresponding to respective error correction encoded individual payloads, the plurality of coded blocks comprising a self-decodable coded block, The self-decodable coding block can be decoded independently of other coding blocks in the plurality of coding blocks, The self-decodable coded block may also be jointly decodable with one or more other coded blocks of the other coded blocks of the plurality of coded blocks of the codeword.

31. The device according to claim 30, characterized in that The program also includes instructions for: The decodable coded blocks are decoded to obtain individual payloads from the codewords.

32. The device according to claim 30 or 31, characterized in that The program also includes instructions for: decoding the self-decodable coded block independently of the other coded blocks in the plurality of coded blocks; Based on successfully decoding the self-decodable coded block independently of the other coded blocks in the plurality of coded blocks, jointly decoding the one or more other coded blocks in the other coded blocks.

33. The device according to any one of claims 30 to 32, characterized in that The program also includes instructions for: The self-decodable coded block is jointly decoded after failing to decode the self-decodable coded block independently of the other coded blocks in the plurality of coded blocks.

34. The device according to any one of claims 30 to 33, characterized in that The program also includes instructions for: The second communication device sends a first retransmission request to the first communication device; The second communication device receives incremental redundancy information of the self-decodable coded block from the first communication device in response to the first retransmission request.

35. The device according to claim 34, characterized in that The program also includes instructions for: In response to the first retransmission request, incremental redundancy decoding is performed based on incremental redundancy information obtained for the self-decodable coded block.

36. The device according to any one of claims 30 to 35, characterized in that Common bits couple the self-decodable coded block with each of the one or more other coded blocks of the other coded blocks.

37. The device according to claim 36, characterized in that The common bits are a subset of bits of the self-decodable coded block, the subset of bits of the self-decodable coded block being encoded to generate the one or more other of the other coded blocks.

38. The device according to claim 36, characterized in that The common bits are a subset of bits of a separate payload of the corresponding separate payload, the separate payload being encoded to generate the self-decodable coded block, the subset of bits of the separate payload being encoded to generate the one or more other coded blocks of the other coded blocks.

39. A computer program product, characterized in that A non-transitory computer-readable medium is included, wherein the non-transitory computer-readable medium stores a program for execution by a processor, the program including instructions for performing the following operations: A first communication device transmits a codeword to a second communication device in a wireless communication network, the codeword comprising a plurality of coded blocks generated by encoding respective individual payloads using an error correction code, the plurality of coded blocks comprising a self-decodable coded block, The self-decodable coding block can be decoded independently of other coding blocks in the plurality of coding blocks, The self-decodable coded block may also be jointly decodable with one or more other coded blocks of the other coded blocks of the plurality of coded blocks of the codeword.

40. A computer program product, characterized in that A non-transitory computer-readable medium is included, wherein the non-transitory computer-readable medium stores a program for execution by a processor, the program including instructions for performing the following operations: Get multiple individual payloads; encoding each of the individual payloads using an error correction code to generate a codeword, the codeword comprising a plurality of coded blocks corresponding to respective individual payloads of the plurality of individual payloads, the plurality of coded blocks comprising a self-decodable coded block; output the codeword, The self-decodable coding block can be decoded independently of other coding blocks in the plurality of coding blocks, The self-decodable coded block may also be jointly decodable with one or more other coded blocks of the other coded blocks of the plurality of coded blocks of the codeword.

41. A computer program product, characterized in that The invention comprises a non-transitory computer-readable medium storing a program for execution by a processor, wherein the program comprises instructions for executing the method according to any one of claims 1 to 19.

42. A system, characterized in that: include: a first communication device for transmitting a codeword, the codeword comprising a plurality of coded blocks generated by encoding respective individual payloads using an error correction code, the plurality of coded blocks comprising a self-decodable coded block; A second communication device is configured to receive the codeword including the plurality of coding blocks from the first communication device, and decode the self-decodable coding blocks to obtain individual payloads from the codeword.

Images