Data transmission method, device and equipment

Abstract

The invention discloses a data transmission method, device and equipment, and belongs to the technical field of communication, and the data transmission method comprises the steps that a first protocol layer of first equipment generates a first data stream and a second data stream corresponding to each piece of target equipment in at least one piece of target equipment based on a service data unit (SDU) of the first protocol layer, the receiving object of the first data stream is the at least one target device, and the receiving object of the second data stream is the corresponding target device; and the first protocol layer of the first device submits the first data stream and a second data stream corresponding to the at least one target device to a second protocol layer.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a data transmission method, apparatus, and device. Background Technology

[0002] Rate Splitting Multiple Access (RSMA) is a novel multiple access technology primarily used for downlink transmission. It improves transmission efficiency by superimposing two types of data streams (a common stream and a private stream). The common stream is the data stream that all receiving devices need to demodulate and decode, while the private stream is the data stream transmitted for a specific receiving device. RSMA requires operations such as generating these two types of data streams; however, existing mobile communication systems do not support these functionalities. Summary of the Invention

[0003] This application provides a data transmission method, apparatus, and device that can solve the problem that existing mobile communication systems do not support functions related to generating two types of data streams.

[0004] Firstly, a data transmission method is provided, the method comprising:

[0005] The first protocol layer of the first device generates a first data stream and a second data stream corresponding to each of the at least one target devices based on the Service Data Unit (SDU) of the first protocol layer. The first data stream is received by the at least one target device, and the second data stream is received by the corresponding target device.

[0006] The first protocol layer of the first device delivers the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer.

[0007] Secondly, a data transmission method is provided, the method comprising:

[0008] The first protocol layer of the second device generates the SDU of the first protocol layer based on the first data stream. The first data stream is received by at least one target device, and the at least one target device includes the second device.

[0009] The first protocol layer of the second device submits the SDU of the first protocol layer to the third protocol layer.

[0010] Thirdly, a data transmission device is provided, comprising:

[0011] The processing module is configured to generate a first data stream and a second data stream corresponding to each of the at least one target devices through the first protocol layer based on the service data unit (SDU) of the first protocol layer. The first data stream is received by the at least one target device, and the second data stream is received by the corresponding target device.

[0012] The processing module is configured to deliver the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer through the first protocol layer.

[0013] Fourthly, a data transmission device is provided, comprising:

[0014] The processing module is configured to generate an SDU of the first protocol layer based on the first data stream through the first protocol layer, wherein the receiving object of the first data stream is at least one target device, and the at least one target device includes the second device;

[0015] The processing module is also used to submit the SDU of the first protocol layer to the third protocol layer through the first protocol layer.

[0016] Fifthly, a data transmission apparatus is provided, the apparatus being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0017] In a sixth aspect, a first device is provided, the first device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0018] In a seventh aspect, a first device is provided, including a processor and a communication interface, wherein,

[0019] The processor is configured to generate a first data stream and a second data stream corresponding to each of the at least one target devices via a first protocol layer based on the service data unit (SDU) of the first protocol layer, wherein the first data stream is received by the at least one target device and the second data stream is received by the corresponding target device.

[0020] The processor is also configured to deliver the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer via the first protocol layer.

[0021] In an eighth aspect, a second device is provided, the second device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0022] Ninthly, a second device is provided, including a processor and a communication interface, wherein,

[0023] A processor is configured to generate an SDU of the first protocol layer based on a first data stream, wherein the first data stream is received by at least one target device, and the at least one target device includes the second device;

[0024] The processor is also used to deliver the SDU of the first protocol layer to the third protocol layer via the first protocol layer.

[0025] In a tenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0026] Eleventhly, a wireless communication system is provided, comprising: a first device and a second device, wherein the first device is configured to perform the steps of the method as described in the first aspect, and the second device is configured to perform the steps of the method as described in the second aspect.

[0027] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0028] In a thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0029] In this embodiment, the first protocol layer of the first device generates a first data stream and a second data stream corresponding to each of the at least one target device based on the service data unit of the first protocol layer. The first data stream is received by the at least one target device, and the second data stream is received by the corresponding target device. The first protocol layer of the first device submits the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer. In this way, by generating two types of data streams through the first protocol layer, the related processing of the first and second data streams can be supported. Furthermore, the first protocol layer has functions such as data splitting. Utilizing the first protocol layer to generate two types of data streams avoids functional redundancy, improves data processing efficiency, and enhances the flexibility of data transmission. Attached Figure Description

[0030] Figure 1This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0031] Figure 2a This is one of the downlink NOMA diagrams in related technologies;

[0032] Figure 2b This is the second schematic diagram of a downlink NOMA in related technologies;

[0033] Figure 2c This is the third schematic diagram of a downlink NOMA in related technologies;

[0034] Figure 3 This is a schematic diagram of a user plane protocol stack in related technologies;

[0035] Figure 4 This is one of the flowcharts of a data transmission method provided in the embodiments of this application;

[0036] Figure 5a This is a schematic diagram of data transmission provided in an embodiment of this application;

[0037] Figure 5b This is another data transmission diagram provided in an embodiment of this application;

[0038] Figure 6a This is another data transmission diagram provided in an embodiment of this application;

[0039] Figure 6b This is another data transmission diagram provided in an embodiment of this application;

[0040] Figure 6c This is another data transmission diagram provided in an embodiment of this application;

[0041] Figure 7a This is another data transmission diagram provided in an embodiment of this application;

[0042] Figure 7b This is another data transmission diagram provided in an embodiment of this application;

[0043] Figure 7c This is another data transmission diagram provided in an embodiment of this application;

[0044] Figure 8 This is a second flowchart of a data transmission method provided in an embodiment of this application;

[0045] Figure 9 This is one of the structural schematic diagrams of a data transmission device provided in the embodiments of this application;

[0046] Figure 10 This is a second schematic diagram of the structure of a data transmission device provided in an embodiment of this application;

[0047] Figure 11 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0048] Figure 12 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0049] Figure 13 This is one of the structural schematic diagrams of a network-side device provided in the embodiments of this application;

[0050] Figure 14 This is a second schematic diagram of the structure of a network-side device provided in an embodiment of this application. Detailed Implementation

[0051] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0052] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0053] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0054] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0055] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0056] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support Function. Support Functions (BSF), Application Functions (AF), Location Management Functions (LMF), Gateway Mobile Location Centres (GMLC), and Network Data Analytics Functions (NWDAF), etc. It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0057] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0058] For ease of understanding, the following explains some aspects of the embodiments of this application:

[0059] 2. Rate Splitting Multiple Access (RSMA)

[0060] The basic idea of ​​rate splitting is to split the messages sent to different receivers at the transmitter into two parts, called the dedicated part (dedicated data stream) and the common part (common data stream). Then, all the common parts are merged into a single unit and multiplexed using downlink non-orthogonal multiple access technology, namely Multiuser Superposition Transmission (MUST). This is achieved by designing a composite constellation and allocating constellation points and bits to different users. Next, similar to the multi-stream transmission of traditional Multi-User MIMO (MU-MIMO), the common data stream and multiple dedicated data streams are transmitted using different precoding and DMRS resources within the same time-frequency resources. At the receiver, each user, in addition to decoding its own dedicated data stream, also needs to decode the common data stream, and then merge its two parts into a complete data stream. It should be noted that the receiver may need to decode information sent to other users and perform interference removal when decoding the common data stream.

[0061] Data multiplexing is equivalent to the MUST technique when all data is transmitted using a public data stream. When all data uses a private data stream, data multiplexing is equivalent to the MU-MIMO method. Therefore, to a certain extent, RSMA is a combination of the MUST and MU-MIMO methods.

[0062] 3. Downlink Non-Orthogonal Multiple Access Technology

[0063] The main idea of ​​downlink non-orthogonal multiple access (NOMA) is to use superposition coding and successive interference cancellation (SIC) to carry information of multiple users on the same resource element (RE).

[0064] The following lists three overlay encoding methods: Cat 1, Cat 2, and Cat 3. Cat 1 and Cat 2 combine multiple sub-constellations into a composite constellation, while Cat 3 directly allocates different bits to different users based on a composite constellation.

[0065] Cat1: Different sub-constellations are superimposed with adaptive power ratios, and the mapping between points and bits in the composite constellation does not conform to the Gray mapping criterion. Figure 2a For example, this is a composite constellation formed by superimposing two sub-constellations of size 4. The constellation point of the first sub-constellation is actually the center point of the clusters distributed across the four quadrants of the composite constellation. For instance, the four points located in the first quadrant, although with different specific values, all represent bit "00". The constellation point of the second sub-constellation is the constellation point of each cluster in the composite constellation. For instance, the last two bits of the first constellation point in each quadrant represent bit "10".

[0066] Cat2: Different sub-constellations are superimposed with adaptive power ratios, and the mapping between points and bits in the composite constellation conforms to the Gray mapping criterion. Figure 2b For example, this is a composite constellation formed by superimposing two sub-constellations of size 4 using the composite Gray mapping criterion. And Figure 2a Similar, only the bit mapping rules are slightly different.

[0067] For Cat1 and Cat2, the composite constellation they transmit is derived from the superposition of sub-constellations, and the variable controlling how the sub-constellations are superimposed is the power ratio. For the two-user case, the transmission steps at the transmitting end are as follows: The transmitting end first determines the constellation point to be transmitted based on the information bits of the first user, and then multiplies that constellation point by the power ratio. in α It is the power ratio of the second user; then, the transmitter determines the constellation point to be transmitted based on the information bits of the second user, and then multiplies that constellation point by the power ratio. Finally, the two constellation points are vector-summed to obtain the final composite constellation point for transmission. At the receiving end, the first user only needs to determine which quadrant the constellation point is located in to obtain the required bits, while the second user needs to determine not only which quadrant the constellation point is in, but also its specific position within the quadrant. In other words, the first user only needs to demodulate 2 bits; while the second user actually needs to demodulate 4 bits and then take the last 2 bits.

[0068] Cat3: Directly partitions a constellation point that conforms to the Gray mapping rule into bits. For example... Figure 2cThe entire constellation diagram conforms to the Gray mapping rule, and it is agreed that the first 2 bits are the bits of the first user and the last 2 bits are the bits of the second user.

[0069] As can be seen, the sub-constellations of Cat1 and Cat2 can be different, and the composite constellation formed by superposition may be irregular. Cat3 first defines a regular composite constellation and then divides the bits.

[0070] For downlink NOMA, fully utilizing the channel conditions of different users is key to improving overall spectral efficiency. For example, for users with poor channel conditions, such as those far from the transmitter, the resolution of constellation points is poor. They can only distinguish constellation points with large Euclidean distances, such as those in different quadrants, but cannot accurately determine constellation points within the same quadrant. On the other hand, for users with good channel conditions, such as those close to the transmitter, the resolution of constellation points is good, and they can make accurate decisions even for constellation points with small Euclidean distances. In this case, it is equivalent to being able to decode all the bits transmitted by the transmitter and then extract the bits of interest. In practical applications, directly determining composite constellation points to obtain all bits and then extracting a portion of the bits is a computationally complex method. A less complex method is SIC: first determine the sub-constellation points with large Euclidean distances (i.e., the constellation points transmitted to distant users), then remove these sub-constellation points from the received signal (vector difference), and then determine the sub-constellation points with smaller Euclidean distances.

[0071] 4. Protocol Stack Architecture

[0072] like Figure 3 As shown, the User Plane protocol stack includes:

[0073] Physical Layer (PHY);

[0074] Medium Access Control (MAC) layer;

[0075] Radio Link Control (RLC);

[0076] Packet Data Convergence Protocol (PDCP);

[0077] Service Data Adaptation Protocol (SDAP).

[0078] The data transmission method, apparatus, and related equipment provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0079] See Figure 4 , Figure 4 This is a flowchart of a data transmission method provided in an embodiment of this application, such as... Figure 4 As shown, the data transmission method includes the following steps:

[0080] Step 101: The first protocol layer of the first device generates a first data stream and a second data stream corresponding to each of the at least one target devices based on the Service Data Unit (SDU) of the first protocol layer. The first data stream is received by the at least one target device, and the second data stream is received by the corresponding target device.

[0081] Step 102: The first protocol layer of the first device delivers the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer.

[0082] The first device can be the sending end.

[0083] The first protocol layer can be any protocol layer other than the lowest protocol layer (such as the physical layer) (or described as a protocol function layer). The first protocol layer can be the layer above the second protocol layer. The second protocol layer can be a functional layer responsible for modulation / demodulation and generating wireless signals.

[0084] In one implementation, the first protocol layer can be the second protocol layer, that is, the layer above the bottommost protocol layer. For example, the first protocol layer can be the Medium Access Control (MAC) layer. The second protocol layer can be the bottommost protocol layer (i.e., the first protocol layer). For example, the second protocol layer can be the physical layer or Layer 1 (L1).

[0085] The first device can be the data sender, and can be a UE, base station, relay, TRP, or other devices. There can be one or more first devices. In the case of multiple devices, it includes, but is not limited to, scenarios such as Single Frequency Network (SFN), Coherent Joint Transmission (CJT), Non-Coherent Joint Transmission (NCJT), and Cell Free.

[0086] The target device can be a data receiver, and can be a UE, base station, relay, TRP or other devices. There can be one or more target devices, but usually there are more.

[0087] In addition, the transmission time-frequency resources of the first data stream and the second data stream overlap at least partially, wherein the target receiving device of the first data stream includes at least one target device, while the target receiving device of the second data stream is a single target device.

[0088] The second data stream corresponding to the target device can refer to the second data stream whose receiving object is the target device.

[0089] In one embodiment, the first protocol layer of the first device merges and / or splits the SDUs in multiple channels of the first protocol layer to obtain a first data stream and a second data stream corresponding to each of the at least one target device. This enables the splitting of the data stream by the first protocol layer.

[0090] In one implementation, the first protocol layer of the first device obtains a first data stream based on the SDU of a first channel among multiple channels of the first protocol layer, and obtains a second data stream corresponding to each target device in at least one target device based on the SDU of a second channel among multiple channels of the first protocol layer. The first channel carries the first data stream, and the second channel carries the second data stream. This enables the data stream to be split by a higher layer of the first protocol layer.

[0091] The first data stream can be a public stream in RSMA (or expressed as a public data stream), and the second data stream can be a private stream in RSMA (or expressed as a private data stream).

[0092] It should be noted that RSMA is a novel multiple access technology primarily used for downlink transmission. It improves transmission efficiency by superimposing two types of data streams (a common stream and a private stream), achieving better transmission performance than simply using MUST and MU-MIMO. Specifically, the common stream is the data stream that all receiving devices need to demodulate and decode, while the private stream is the data stream transmitted for a specific receiving device. After decoding the common stream, the receiver performs interference removal and demodulates the private stream. By flexibly utilizing both data streams, the common stream can compensate for the performance loss of MU-MIMO when the transmitter's Channel State Information (CSI) is imperfect or the receiving device's channel isolation is poor.

[0093] In related technologies, the design involves splitting RSMA data streams at the lowest layer of the protocol layer (such as the physical layer). However, the physical layer of existing mobile communication systems does not have the function of splitting data streams, which makes it impossible for existing mobile communication systems to support the splitting of RSMA data streams, resulting in poor flexibility in data transmission.

[0094] Currently, RSMA-related design schemes only utilize the lowest layer of the protocol layer (such as the physical layer) to perform functions such as splitting, splicing, and superimposing data streams. However, the lowest layer of the protocol layer in existing mobile communication systems does not have functions such as packet splitting and merging. Related designs need to make significant modifications to it, and its functions overlap significantly with those of higher layers (such as the MAC layer), increasing unnecessary costs and complexity of the system.

[0095] This application proposes a novel data transmission architecture. On the one hand, it fully utilizes the functions of higher layers (such as the MAC layer) to perform operations in RSMA such as splitting and merging data streams, which are more suitable for higher-layer processing. On the other hand, it defines the corresponding cooperation operations at the lowest level of the protocol layer and the interfaces between layers, which can minimize the addition of redundant functions and reduce costs and complexity while ensuring RSMA gains.

[0096] The relevant technologies require special processing such as merging and splitting the two types of data streams, but existing mobile communication systems do not consider related functions and lack a unified design, which may lead to functional redundancy and reduced data transmission efficiency.

[0097] In this embodiment, the first protocol layer of the first device generates a first data stream and a second data stream corresponding to each of the at least one target device based on the service data unit of the first protocol layer. The first data stream is received by the at least one target device, and the second data stream is received by the corresponding target device. The first protocol layer of the first device submits the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer. In this way, by generating two types of data streams through the first protocol layer, the related processing of the first and second data streams can be supported. Furthermore, the first protocol layer has functions such as data splitting. Utilizing the first protocol layer to generate two types of data streams avoids functional redundancy, improves data processing efficiency, and enhances the flexibility of data transmission.

[0098] Optionally, the first protocol layer of the first device delivers the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer, including:

[0099] The first protocol layer of the first device submits the transport block (TB) of the first data stream to the second protocol layer through a Hybrid Automatic Repeat Request (HARQ) process; or, the first protocol layer of the first device submits the TB of the first data stream to the second protocol layer through multiple first HARQ processes, wherein the first data stream includes multiple sub-data streams, and the multiple sub-data streams correspond one-to-one with the multiple first HARQ processes;

[0100] The first protocol layer of the first device submits the TB of the second data stream corresponding to the at least one target device to the second protocol layer through at least one second HARQ process, and the at least one second HARQ process corresponds one-to-one with the at least one target device.

[0101] In one implementation, the first protocol layer of the first device submits the first data stream's TB to the second protocol layer through a HARQ process. The first protocol layer of the first device also submits the TB of the second data stream corresponding to the at least one target device to the second protocol layer through at least one second HARQ process. In this way, the first protocol layer (MAC layer) splits a common stream and a private stream based on at least one logical channel, and provides independent HARQ processes for the common stream (without distinguishing sub-streams) and each private stream. This data stream splitting is achieved through a non-bottom layer (e.g., a non-physical layer), improving the flexibility of data transmission.

[0102] For example, the first protocol layer (MAC layer) merges and splits multiple logical channels into a common part and multiple private parts, generating independent TBs respectively. The splitting method can be based on rules; or it can be split dynamically. The first device (sender) indicates the correlation between TBs to the second device (receiver), guiding the receiver to merge TBs. The first protocol layer submits the common TB and private TB to their respective independent HARQ processes, which are independently responsible for transmission and retransmission.

[0103] In one implementation, the first protocol layer of the first device submits the TB of the first data stream to the second protocol layer through multiple first HARQ processes. The first protocol layer of the first device also submits the TB of the second data stream corresponding to the at least one target device to the second protocol layer through at least one second HARQ process. In this way, the first protocol layer (MAC layer) splits a public stream and a private stream based on at least one logical channel. The first protocol layer provides independent HARQ processes for each sub-stream of the public stream and each private stream. By implementing data stream splitting through a non-bottom layer (such as a non-physical layer) of the protocol layer, the flexibility of data transmission can be improved.

[0104] For example, the first protocol layer (MAC layer) merges and splits multiple logical channels into multiple sub-streams of a common stream and multiple private parts, generating independent TBs respectively. The splitting method can be based on rules; or it can be dynamically split. The first device (sender) indicates the correlation between TBs to the second device (receiver), guiding the receiver to merge TBs. Each common sub-stream TB and private stream TB is processed by its own independent HARQ process, which is independently responsible for transmission and retransmission.

[0105] Optionally, the method further includes:

[0106] The second protocol layer of the first device generates the codeword of the first data stream based on the TB corresponding to the one HARQ process, or generates the codeword of the first data stream based on the TB corresponding to each of the plurality of first HARQ processes.

[0107] The second protocol layer of the first device generates codewords for the corresponding second data stream based on the TB corresponding to each of the at least one second HARQ process.

[0108] The second protocol layer of the first device determines the codewords of the first data stream and the second data stream transmitted on at least partially overlapping time-frequency resources;

[0109] The second protocol layer of the first device pre-encodes the symbols corresponding to the codewords of the first data stream and the second data stream respectively, and then superimposes the pre-encoded symbols onto the at least partially overlapping time-frequency resources for transmission.

[0110] In one implementation, the second protocol layer of the first device generates codewords for the first data stream based on the TB corresponding to the HARQ process; the second protocol layer of the first device generates codewords for the corresponding second data stream based on the TB corresponding to each of the at least one second HARQ process. Thus, the second protocol layer (e.g., the physical layer) of the first device provides upper-layer interfaces according to the overall common stream and each private stream. Substreams of the common stream do not have independent HARQ processes; HARQ feedback and retransmission are provided according to the entire common stream.

[0111] The first data stream can be a public stream in RSMA, and the second data stream can be a private stream in RSMA.

[0112] For example, the second protocol layer (such as the physical layer) of the first device performs the following process:

[0113] (1) Generate at least one codeword for a common flow based on the TB of the common flow HARQ Process;

[0114] (2) Generate at least one codeword for each private stream based on each TB of the HARQ Process for each private stream;

[0115] (3) Pairing the codewords of public and private streams that need to be transmitted on at least partially overlapping time-frequency resources;

[0116] (4) The symbols generated by the Codeword of the two types of data streams in the paired transmission are pre-encoded and superimposed on the time-frequency resources that overlap at least partially for transmission.

[0117] In one implementation, the codewords for the first data stream are generated based on the TB corresponding to each of the plurality of first HARQ processes; the second protocol layer of the first device generates the codewords for the corresponding second data stream based on the TB corresponding to each of the at least one second HARQ process. Thus, the second protocol layer (e.g., the physical layer) of the first device provides upper-layer interfaces for each sub-stream of a common stream (sub-data streams belonging to each target device (or, as described, target receiving device) within the common stream) and each private stream, providing independent HARQ processes for each common stream sub-stream and each private stream, and providing HARQ feedback and retransmission for each stream.

[0118] For example, the second protocol layer (such as the physical layer) of the first device performs the following process:

[0119] (1) Generate the codeword (second codeword) of the common stream based on each TB (first TB) from the HARQ Process corresponding to multiple common stream substreams.

[0120] Generate a first codeword based on each first TB, merge at least one first codeword to generate a second codeword.

[0121] Optionally, before generating the second codeword, a cyclic redundancy check (CRC) is added to the first codeword, which corresponds to the CRC of the entire common stream.

[0122] Optionally, when merging the first Codeword, more than one second Codeword is generated.

[0123] It should be noted that the HARQ Process in the embodiments of this application may come from the same HARQ entity or multiple HARQ entities, and there is no limitation here.

[0124] (2) Generate a codeword for each private stream based on each TB from the HARQ Process corresponding to multiple private streams.

[0125] (3) Pairing requires the codewords of public and private streams that are transmitted on at least partially overlapping time-frequency resources.

[0126] (4) The symbols generated by the Codeword of the two types of data streams in the paired transmission are pre-encoded and superimposed on the time-frequency resources that overlap at least partially for transmission.

[0127] Optionally, the first protocol layer of the first device generates a first data stream and a second data stream corresponding to each of the at least one target device based on the SDU of the first protocol layer, including any one of the following:

[0128] The first protocol layer of the first device merges and / or splits the SDUs in multiple channels of the first protocol layer to obtain a first data stream and a second data stream corresponding to each target device in at least one target device;

[0129] The first protocol layer of the first device obtains a first data stream based on the SDU of the first channel among multiple channels of the first protocol layer, and obtains a second data stream corresponding to each target device in at least one target device based on the SDU of the second channel among multiple channels of the first protocol layer. The first channel carries the first data stream, and the second channel carries the second data stream.

[0130] In one embodiment, the first protocol layer of the first device merges and / or splits the SDUs in multiple channels of the first protocol layer to obtain a first data stream and a second data stream corresponding to each of the at least one target device. In this way, the first protocol layer (such as the MAC layer) provides the upper layer with a logical channel carrying each target device. The first protocol layer splits a common stream and a private stream based on at least one logical channel. This data stream splitting through the first protocol layer improves the flexibility of data transmission.

[0131] In one implementation, the first protocol layer of the first device obtains a first data stream based on the SDU of a first channel among multiple channels of the first protocol layer, and obtains a second data stream corresponding to each target device among at least one target device based on the SDU of a second channel among multiple channels of the first protocol layer. In this way, the first protocol layer (such as the MAC layer) provides a logical channel carrying a common stream and private data of each target device to the upper layer (the third protocol layer). By splitting the data stream through the upper layer of the first protocol layer, the flexibility of data transmission can be improved.

[0132] The first channel can be a public stream logical channel, and the second channel can be a private stream logical channel.

[0133] For example, the first protocol layer (such as the MAC layer) generates independent TB / CW for the common stream logical channel and each private stream logical channel: the common stream TB and the private TB per target device; if the same target device has multiple logical channels, the MAC layer can merge them to generate a TB; the common stream TB and the private TB are processed by their respective independent HARQ processes and are independently responsible for transmission / retransmission.

[0134] In addition, the merging and / or splitting process may include merging; or splitting; or merging followed by splitting. This embodiment does not limit this.

[0135] Optionally, the method further includes:

[0136] The third protocol layer of the first device obtains the corresponding SDU of the third protocol layer through at least one first entity;

[0137] The third protocol layer of the first device, through the bridging function of the at least one first entity, performs merging and / or splitting of the SDUs of the third protocol layer to obtain the SDUs of the first channel and the SDUs of the second channel; or,

[0138] The third protocol layer of the first device creates at least one second entity, and performs merging and / or splitting of the SDU of the third protocol layer through the at least one second entity to obtain the SDU of the first channel and the SDU of the second channel.

[0139] The third protocol layer can be the third layer of the protocol layers, that is, the layer above the first protocol layer. The third protocol layer can be the RLC layer. The first entity can be an RLC entity, and the second entity can be an RLC entity.

[0140] In one embodiment, the third protocol layer of the first device performs merging and / or splitting of the SDUs of the third protocol layer through the bridging function of at least one first entity to obtain the SDU of the first channel and the SDU of the second channel. Thus, by incorporating a bridging function spanning multiple RLC entities within the third protocol layer (such as the RLC layer), outputting a common stream and a private stream logical channel for each target device, and achieving data stream splitting through the third protocol layer, the flexibility of data transmission can be improved.

[0141] The bridging function can be used to handle communication between RLC entities, merging or splitting RLC channels / logical channels managed by different RLC entities into common parts and multiple private parts, generating independent logical channels respectively. The splitting method can be based on rules or dynamically, with the first device (sender) indicating the correlation between logical channels to the second device (receiver).

[0142] In one embodiment, the third protocol layer of the first device creates at least one second entity, and performs merging and / or splitting processing on the SDU of the third protocol layer through the at least one second entity to obtain the SDU of the first channel and the SDU of the second channel. In this way, by reconstructing new RLC entities in the third protocol layer (such as the RLC layer) to correspond to the logical channels of the common flow and the private flow of each target device respectively, the splitting of data flow through the third protocol layer can improve the flexibility of data transmission.

[0143] For example, new RLC entities can be reconstructed based on existing RLC entities and their RLC channels. The RLC channels / logical channels responsible for each new RLC entity are derived from the merging and splitting of existing RLC entities and their RLC channels. The splitting method can be based on rules or dynamic splitting, with the first device (transmitter) indicating the correlation between logical channels to the second device (receiver).

[0144] Optionally, the method further includes:

[0145] The third protocol layer of the first device obtains the SDU of the first channel based on the SDU of the third channel among the multiple channels of the third protocol layer, and obtains the SDU of the second channel based on the SDU of the fourth channel among the multiple channels of the third protocol layer. The third channel carries the first data stream, and the fourth channel carries the second data stream.

[0146] The third channel can be a public stream channel, and the fourth channel can be a private stream channel. Before the third protocol layer (such as the RLC layer), the data stream is already divided into public and private parts, with independent RLC channels, which can be transmitted by independent RLC entities.

[0147] In one embodiment, the third protocol layer of the first device can distinguish between public and private flows and their associated relationships based on instructions from the upper layer or the header of the data packet, which facilitates processing by the physical layer and the receiving end.

[0148] Optionally, the method further includes:

[0149] The fourth protocol layer of the first device obtains the corresponding SDU of the fourth protocol layer through at least one third entity;

[0150] The fourth protocol layer of the first device, through the bridging function of the at least one third entity, performs merging and / or splitting of the SDU of the fourth protocol layer to obtain the SDU of the third channel and the SDU of the fourth channel; or,

[0151] The first device creates at least one fourth entity in its fourth protocol layer, and performs merging and / or splitting of the SDUs of the fourth protocol layer through the at least one fourth entity to obtain the SDUs of the third channel and the SDUs of the fourth channel.

[0152] The fourth protocol layer can be the fourth layer of the protocol layers, that is, the layer above the third protocol layer. The fourth protocol layer can be the PDCP layer. The third entity can be a PDCP entity, and the fourth entity can be a PDCP entity.

[0153] In one embodiment, the fourth protocol layer of the first device performs merging and / or splitting of the SDUs of the fourth protocol layer through the bridging function of the at least one third entity. Thus, by incorporating a bridging function spanning multiple PDCP entities within the fourth protocol layer (such as the PDCP layer), outputting a common stream and a private stream logical channel for each target device, and achieving data stream splitting through the fourth protocol layer, the flexibility of data transmission can be improved.

[0154] The bridging function can be used to handle communication between PDCP entities, merging or splitting PDCP channels / logical channels managed by different PDCP entities into common parts and multiple private parts, generating independent logical channels respectively. The splitting method can be based on rules or dynamically, with the first device (sender) indicating the correlation between logical channels to the second device (receiver).

[0155] In one embodiment, the fourth protocol layer of the first device creates at least one fourth entity, and the SDU of the fourth protocol layer is merged and / or split through the at least one fourth entity to obtain the SDU of the third channel and the SDU of the fourth channel. In this way, by reconstructing new PDCP entities in the fourth protocol layer (such as the PDCP layer) to correspond to the logical channels of the common flow and the private flow of each target device respectively, the splitting of the data flow through the fourth protocol layer can improve the flexibility of data transmission.

[0156] For example, new PDCP entities can be reconstructed based on existing PDCP entities and their PDCP channels. The PDCP channels / logical channels responsible for each new PDCP entity are derived from the merging and splitting of existing PDCP entities and their PDCP channels. The splitting method can be based on rules or dynamic splitting, with the first device (transmitter) indicating the correlation between logical channels to the second device (receiver).

[0157] This application provides a system architecture for data transmission, defining the functions of each protocol layer and the interfaces for connecting upper or lower layers, in order to support the implementation of public and private stream transmission in RSMA.

[0158] The following examples will provide further explanation:

[0159] In the example below, the sender is the first device, the receiver is the target device, and the target device may include a second device or a UE. The first protocol layer is the MAC layer, the second protocol layer is the physical layer, the third protocol layer is the RLC layer, and the fourth protocol layer is the PDCP layer.

[0160] Example 1: Physical Layer

[0161] Alt1: As Figure 5a As shown, the physical layer provides upper-layer interfaces for each public stream's sub-streams (the sub-data streams within the public stream belonging to each target device (or, as described, the target receiving device)) and each private stream, providing independent HARQ processes for each public stream sub-stream and each private stream, and providing HARQ feedback and retransmission for each stream. Figure 5a In this code, "C" represents a public flow, "P" represents a private flow, "①", "②", and "③" represent different sub-flows, and "HARQ Proc" refers to the HARQ process.

[0162] Sending end PHY function:

[0163] (1) Generate the codeword (second codeword) of the common stream based on each TB (first TB) from the HARQ Process corresponding to multiple common stream substreams.

[0164] Generate a first codeword based on each first TB, merge at least one first codeword to generate a second codeword.

[0165] Optionally, before generating the second codeword, a cyclic redundancy check (CRC) is added to the first codeword, which corresponds to the CRC of the entire common stream.

[0166] Optionally, when merging the first Codeword, more than one second Codeword is generated.

[0167] It should be noted that the HARQ Process in the embodiments of this application may come from the same HARQ entity or multiple HARQ entities, and there is no limitation here.

[0168] (2) Generate a codeword for each private stream based on each TB from the HARQ Process corresponding to multiple private streams.

[0169] (3) Pairing requires the codewords of public and private streams that are transmitted on at least partially overlapping time-frequency resources.

[0170] (4) The symbols generated by the Codeword of the two types of data streams in the paired transmission are pre-encoded and superimposed on the time-frequency resources that overlap at least partially for transmission.

[0171] (5) Other traditional physical layer functions: layer mapping, resource mapping or waveform generation, etc.

[0172] The receiving end PHY function establishes HARQ processes for receiving data from all sub-streams of the public stream and the private stream, including the following processes:

[0173] (1) Receive the common stream codeword, extract the bits belonging to each sub-stream (corresponding to the first codeword) from the codeword, and submit the receiving HARQ process of each sub-stream;

[0174] (2) Verify common flows;

[0175] Case 1: Verify the overall CRC of the common flow. If it passes, indicate that the HARQ process of each sub-flow can skip the verification.

[0176] Case 2: The HARQ process for receiving each substream restores the first TB based on the received first codeword and verifies the CRC of the first TB.

[0177] (3) Reconstruct and delete common flow signals;

[0178] (4) Receive the private stream Codeword, which is then processed by the corresponding HARQ Process and restored to TB;

[0179] (5) Verify private stream: Verify the CRC of the TB generated based on the private stream Codeword;

[0180] (6) Request retransmission: For data that fails the verification, request the sender to retransmit. The granularity of retransmission includes the entire codeword of the public stream, the TB or codeword of each sub-stream in the public stream, and the TB or codeword of the private stream.

[0181] (7) Other traditional physical layer functions.

[0182] Alt2: as Figure 5bAs shown, the physical layer provides upper-layer interfaces according to the overall public flow and each private flow. Sub-flows of the public flow do not have independent HARQ processes, but provide HARQ feedback and retransmission according to the entire public flow.

[0183] Sending end PHY function:

[0184] (1) Generate at least one codeword for a common flow based on the TB of the common flow HARQ Process;

[0185] (2) Generate at least one codeword for each private stream based on each TB of the HARQ Process for each private stream;

[0186] (3) Pairing the codewords of public and private streams that need to be transmitted on at least partially overlapping time-frequency resources;

[0187] (4) The symbols generated by the Codeword of the two types of data streams in the paired transmission are pre-encoded and superimposed on the time-frequency resources that overlap at least partially for transmission;

[0188] (5) Other traditional physical layer functions: layer mapping, resource mapping, waveform generation, etc.

[0189] Receiver PHY function: Establishes HARQ processes for receiving both the public stream and the private stream, including the following processes:

[0190] (1) Receive the common stream Codeword, process it through the common stream HARQ Process, and restore it to TB;

[0191] (2) Verify common flow: Verify the CRC of common flow TB;

[0192] (3) Reconstruct and delete common flow signals;

[0193] (4) Receive the private stream Codeword, which is then processed by the corresponding HARQ Process and restored to TB;

[0194] (5) Verify private stream: Verify the CRC of the TB generated based on the private stream Codeword;

[0195] (6) Request retransmission: For data that fails the verification, request the sender to retransmit it. The granularity of retransmission includes the entire TB or codeword of the public stream and the TB or codeword of the private stream.

[0196] (7) Other traditional physical layer functions.

[0197] Example 2: MAC Layer

[0198] Alt1-1: As Figure 6a As shown, the MAC layer provides the upper layer with a logical channel to carry each target device. The MAC layer splits the public stream and private stream based on at least one logical channel, and provides independent HARQ processes according to the public stream (without distinguishing sub-streams) and each private stream.

[0199] Sending end MAC layer functions:

[0200] (1) Merge and split multiple logical channels into a common part and multiple private parts, and generate independent TBs respectively.

[0201] The splitting method can be based on rules;

[0202] Alternatively, dynamic splitting can be used, where the sending end needs to indicate the correlation between TBs to the receiving end, guiding the receiving end to merge TBs.

[0203] (2) Submit the public TB and private TB to their respective independent HARQ Processes, which are responsible for transmission and retransmission independently.

[0204] (3) Other traditional MAC layer functions.

[0205] Receiver MAC layer functions:

[0206] (1) Multiple independent HARQ processes perform CRC checks, retransmissions and other operations on the common flow TB and the private flow TB respectively to obtain the common flow TB and the private flow TB belonging to the target device;

[0207] (2) Extract the bits belonging to the target device from the common stream TB;

[0208] (3) Based on the correlation between TBs, the bits belonging to the target device in the public stream and the bits in the private stream TB are merged and restored into a logical channel (RLC PDU / MAC SDU) and delivered to the upper layer.

[0209] (4) Other traditional MAC layer functions.

[0210] Alt1-2: As Figure 6b As shown, the MAC layer provides the upper layer with the logical channel carrying each target device. The MAC layer splits into a public stream and a private stream, and provides an independent HARQ process for each sub-stream of the public stream and each private stream.

[0211] Sending end MAC layer functions:

[0212] (1) Merge multiple logical channels and split them into multiple sub-streams of a common stream and multiple private parts, and generate independent TBs respectively.

[0213] The splitting method can be based on rules;

[0214] Alternatively, dynamic splitting can be used, where the sending end needs to indicate the correlation between TBs to the receiving end, guiding the receiving end to merge TBs.

[0215] (2) Each public sub-stream TB and private sub-stream TB is processed by its own independent HARQ Process, which is responsible for transmission and retransmission independently.

[0216] (3) Other traditional MAC layer functions.

[0217] Receiver MAC layer functions:

[0218] (1) Use multiple independent HARQ Processes to perform CRC check, retransmission and other operations on the sub-stream TB of the common stream and the private stream TB of the private stream respectively, to obtain the sub-stream TB of the common stream and the private stream TB belonging to the target device.

[0219] (2) Extract the bits of the substream that belong to the common stream of the target device;

[0220] (3) Based on the correlation between TBs, the bits of the sub-streams of the public stream belonging to the target device and the bits of the private stream TB are merged and restored into a logical channel (RLC PDU / MAC SDU) and delivered to the upper layer.

[0221] (4) Other traditional MAC layer functions.

[0222] Alt2: as Figure 6c As shown, the MAC layer provides a logical channel to the upper layer to carry the common flow and the private data of each target device. The MAC layer sets up independent HARQ processes for the common flow (without distinguishing between sub-flows) and each private flow.

[0223] Sending end MAC layer functions:

[0224] (1) Generate independent TB / CW for the common flow logical channel and each logical channel: common flow TB and perUE private TB;

[0225] (2) If the same UE has multiple logical channels, the MAC layer can merge them to generate TB;

[0226] (3) Public flow TB and private flow TB are processed by their respective independent HARQ Processes, which are independently responsible for transmission / retransmission.

[0227] Receiver MAC layer functions:

[0228] (1) Multiple independent HARQ Processes are used to perform CRC checks, retransmissions and other operations on the common flow TB and the private flow TB respectively. The MAC layer can obtain the common flow TB and the private flow TB belonging to the UE.

[0229] (2) Restore the public flow TB and private flow TB into their respective logical channels (RLC PDU / MAC SDU) and submit them to the upper layer.

[0230] Example 3: RLC or PDCP Layer

[0231] The RLC and PDCP layers are currently mapped one-to-one:

[0232] One PDCP entity: One upper-layer Bearer corresponds to one lower-layer RLC Channel.

[0233] One RLC entity: One upper-layer RLC channel corresponds to one lower-layer logical channel.

[0234] Therefore, if data stream merging / splitting is required, additional functionality spanning multiple entities needs to be defined in the RLC or PDCP layer to achieve data stream splitting and merging. Since RLC and PDCP are similar, this embodiment uses RLC as an example, but it can be fully extended to PDCP by simply replacing RLC with PDCP.

[0235] Alt1-1: As Figure 7a As shown, the RLC layer has a built-in Bridge function that spans multiple RLC entities, outputting a common stream and a private stream logical channel for each target device.

[0236] Sender RLC layer functions:

[0237] (1) Bridge function: responsible for communication between RLC entities, merging and splitting the RLC channels / logical channels of different RLC entities into common parts and multiple private parts, and generating independent logical channels respectively.

[0238] The splitting method can be based on rules;

[0239] Alternatively, the channels can be dynamically split, requiring the sender to indicate the correlation between logical channels to the receiver.

[0240] (1) Other traditional RLC layer functions.

[0241] Receiver RLC layer functions:

[0242] (1) The receiving end should also have a similar Bridge function, which is the reverse operation of the sending end, to restore the received public stream logic channel and private stream logic channel to RLC channel (PDCP PDU / RLC SDU) and submit it to the upper layer.

[0243] (2) Other traditional RLC layer functions.

[0244] Alt1-2: As Figure 7b As shown, new RLC entities are reconstructed within the RLC layer, corresponding to the logical channels of the common flow and the private flow of each target device, respectively.

[0245] Sender RLC layer functions:

[0246] (1) Based on the existing RLC entities and their RLC channels, new RLC entities are reconstructed. The RLC channels / logical channels responsible for each new RLC entity are derived from the merging and splitting of the existing RLC entities and their RLC channels.

[0247] The splitting method can be based on rules;

[0248] Alternatively, dynamic splitting may be required, in which case the correlation between logical channels needs to be indicated to the receiving end.

[0249] (2) Other traditional RLC layer functions.

[0250] Receiver RLC layer functions:

[0251] (1) For the reverse operation of the sending end, the RLC layer of the receiving end first establishes RLC entities for the public flow and the private flow respectively, and then reconstructs the new RLC entity. The new RLC entity restores the public flow logical channel and the private flow logical channel to the RLC channel (PDCP PDU / RLC SDU) and submits them to the upper layer.

[0252] (2) Other traditional RLC layer functions.

[0253] Alt2: as Figure 7c As shown, before the RLC layer, the data stream is already divided into public and private parts, with independent RLC channels, which can be transmitted by independent RLC entities.

[0254] Sender RLC layer functions:

[0255] Its behavior is basically the same as that of a traditional RLC layer.

[0256] Optionally, based on instructions from the upper layer or the header of the data packet, public and private flows and their relationships can be distinguished by marking, which facilitates processing by the physical layer and the receiving end.

[0257] Receiver RLC layer functions:

[0258] Its behavior is basically the same as that of a traditional RLC layer.

[0259] Optionally, based on the lower-level instructions or the header of the data packet, public and private flows and their relationships can be distinguished to facilitate processing at higher levels.

[0260] This application proposes a novel data transmission architecture. On the one hand, it fully utilizes the functions of higher layers (such as the MAC layer) to perform operations in RSMA such as splitting and merging data streams, which are more suitable for higher-layer processing. On the other hand, it defines the corresponding cooperation operations of the physical layer and the interfaces between layers, which can minimize the addition of redundant functions and reduce cost and complexity while ensuring RSMA gain.

[0261] See Figure 8 , Figure 8 This is a flowchart of a data transmission method provided in an embodiment of this application, such as... Figure 8 As shown, the data transmission method includes the following steps:

[0262] Step 201: The first protocol layer of the second device generates the SDU of the first protocol layer based on the first data stream. The receiving object of the first data stream is at least one target device, and the at least one target device includes the second device.

[0263] Step 202: The first protocol layer of the second device submits the SDU of the first protocol layer to the third protocol layer.

[0264] In this embodiment, the first protocol layer of the second device can generate the SDU of the first protocol layer based on the first data stream and the second data stream corresponding to the second device; or, the first protocol layer of the second device can generate the SDU of the first protocol layer based solely on the first data stream. This embodiment does not limit this.

[0265] Optionally, the first protocol layer of the second device generates the SDU of the first protocol layer based on the first data stream, including:

[0266] The first protocol layer of the second device generates the SDU of the first protocol layer based on the first data stream and the second data stream corresponding to the second device.

[0267] Optionally, the first protocol layer of the second device generates the SDU of the first protocol layer based on the first data stream and the corresponding second data stream of the second device, including any one of the following:

[0268] The first protocol layer of the second device merges the first data stream and the second data stream corresponding to the second device to obtain SDUs for multiple channels of the first protocol layer;

[0269] The first protocol layer of the second device generates an SDU for the fifth channel among the multiple channels of the first protocol layer based on the first data stream, and generates an SDU for the sixth channel among the multiple channels of the first protocol layer based on the second data stream. The fifth channel carries the first data stream, and the sixth channel carries the second data stream.

[0270] In one embodiment, the first protocol layer of the second device merges the first data stream and the second data stream corresponding to the second device to obtain SDUs for multiple channels of the first protocol layer. This allows for the merging of data streams through the first protocol layer.

[0271] The first data stream can be a public stream in RSMA, and the second data stream can be a private stream in RSMA.

[0272] For example, the first protocol layer (such as the MAC layer) of the second device performs CRC checks and retransmissions on the common flow TB and the private flow TB through multiple independent HARQ processes to obtain the common flow TB and the private flow TB belonging to the target device; extracts the bits belonging to the target device from the common flow TB; and, based on the correlation between TBs, merges the bits belonging to the target device in the common flow and the bits in the private flow TB to restore the logical channel (RLC PDU / MAC SDU) and delivers it to the upper layer.

[0273] In one embodiment, the first protocol layer of the second device generates the SDU of the fifth channel among the multiple channels of the first protocol layer based on the first data stream, and generates the SDU of the sixth channel among the multiple channels of the first protocol layer based on the second data stream, and the upper layer of the first protocol layer merges the data streams.

[0274] Among them, the fifth channel can be a public stream logical channel, and the sixth channel can be a private stream logical channel.

[0275] For example, the first protocol layer (such as the MAC layer) of the second device uses multiple independent HARQ processes to perform CRC checks, retransmissions, and other operations on the common flow TB and the private flow TB respectively. The MAC layer can obtain the common flow TB and the private flow TB belonging to the second device; and restore the common flow TB and the private flow TB to their respective logical channels (RLC PDU / MAC SDU) and submit them to the upper layer.

[0276] Optionally, the first protocol layer of the second device merges the first data stream and the second data stream corresponding to the second device to obtain SDUs for multiple channels of the first protocol layer, including:

[0277] The first protocol layer of the second device extracts the sub-data stream corresponding to the second device from the first data stream;

[0278] The first protocol layer of the second device merges the sub-data stream corresponding to the second device and the second data stream corresponding to the second device to obtain the SDU of multiple channels of the first protocol layer.

[0279] The first data stream can be a public stream in RSMA, and the second data stream can be a private stream in RSMA.

[0280] For example, the first protocol layer (such as the MAC layer) of the second device uses multiple independent HARQ processes to perform CRC checks, retransmissions, and other operations on the sub-streams TB of the common flow and the private flow TB of the private flow, respectively, to obtain multiple sub-streams TB of the common flow and the private flow TB belonging to the target device; it extracts the bits of the sub-streams of the common flow belonging to the target device; and according to the correlation between TBs, it merges the bits of the sub-streams of the common flow belonging to the target device and the bits of the private flow TB to restore the logical channel (RLCPDU / MAC SDU) and delivers it to the upper layer.

[0281] Optionally, the method further includes:

[0282] The first or second protocol layer of the second device performs CRC check and / or retransmission operations on the first data stream through a HARQ process; or, the first or second protocol layer of the second device performs CRC check and / or retransmission operations on the first data stream through multiple third HARQ processes, wherein the first data stream includes multiple sub-data streams, and the multiple sub-data streams correspond one-to-one with the multiple third HARQ processes; and / or,

[0283] The first or second protocol layer of the second device performs CRC check and / or retransmission operations on the second data stream corresponding to the second device through the fourth HARQ process.

[0284] In one embodiment, the second protocol layer of the second device performs CRC check and / or retransmission operations on the first data stream through a HARQ process.

[0285] The first data stream can be a public stream in RSMA, and the second data stream can be a private stream in RSMA.

[0286] For example, the second protocol layer (such as the physical layer) of the first device establishes HARQ processes for receiving both the public stream and the private stream, including the following processes:

[0287] (1) Receive the common stream Codeword, process it through the common stream HARQ Process, and restore it to TB;

[0288] (2) Verify common flow: Verify the CRC of common flow TB;

[0289] (3) Reconstruct and delete common flow signals;

[0290] (4) Receive the private stream Codeword, which is then processed by the corresponding HARQ Process and restored to TB;

[0291] (5) Verify private stream: Verify the CRC of the TB generated based on the private stream Codeword;

[0292] (6) Request retransmission: For data that fails the verification, request the sender to retransmit it. The granularity of retransmission includes the entire TB or codeword of the public stream and the TB or codeword of the private stream.

[0293] In one embodiment, the second protocol layer of the second device performs CRC check operations and / or retransmission operations on the first data stream through multiple third HARQ processes.

[0294] For example, the second protocol layer (such as the physical layer) of the first device establishes HARQ processes for receiving all sub-streams of the public stream and private streams respectively, including the following processes:

[0295] (1) Receive the common stream codeword, extract the bits belonging to each sub-stream (corresponding to the first codeword) from the codeword, and submit the receiving HARQ process of each sub-stream;

[0296] (2) Verify common flows;

[0297] Case 1: Verify the overall CRC of the common flow. If it passes, indicate that the HARQ process of each sub-flow can skip the verification.

[0298] Case 2: The HARQ process for receiving each substream restores the first TB based on the received first codeword and verifies the CRC of the first TB.

[0299] (3) Reconstruct and delete common flow signals;

[0300] (4) Receive the private stream Codeword, which is then processed by the corresponding HARQ Process and restored to TB;

[0301] (5) Verify private stream: Verify the CRC of the TB generated based on the private stream Codeword;

[0302] (6) Request retransmission: For data that fails the verification, request the sender to retransmit. The granularity of retransmission includes the entire codeword of the public stream, the TB or codeword of each sub-stream in the public stream, and the TB or codeword of the private stream.

[0303] Optionally, the CRC check operation on the first data stream includes:

[0304] The first data stream's code blocks or code block groups are CRC checked by one HARQ process, or the code blocks or code block groups of the sub-data stream corresponding to each third HARQ process are CRC checked by each third HARQ process.

[0305] or,

[0306] The TB of the first data stream is generated based on the codewords of the first data stream, and the TB of the first data stream is CRC checked by the first HARQ process, or the TB of the sub-data stream corresponding to the third HARQ process is CRC checked by each third HARQ process.

[0307] Optionally, the method further includes:

[0308] The third protocol layer of the second device obtains the SDU of the first protocol layer through at least one fifth entity;

[0309] The third protocol layer of the second device merges the SDUs of the first protocol layer through the bridging function of the at least one fifth entity to obtain the SDUs of the third protocol layer; or,

[0310] The third protocol layer of the second device creates at least one sixth entity, and merges the SDUs of the first protocol layer through the at least one sixth entity to obtain the SDUs of the third protocol layer;

[0311] The third protocol layer of the second device generates the SDU of the seventh channel and the SDU of the eighth channel among the multiple channels of the third protocol layer based on the SDU of the first protocol layer. The seventh channel carries the first data stream, and the eighth channel carries the second data stream.

[0312] The third protocol layer can be an RLC layer. The fifth entity can be an RLC entity, and the sixth entity can be an RLC entity.

[0313] Among them, the seventh channel can be a public flow channel, and the eighth channel can be a private flow channel.

[0314] In one embodiment, the third protocol layer of the second device merges the SDUs of the first protocol layer through the bridging function of the at least one fifth entity to obtain the SDU of the third protocol layer. Thus, by incorporating a bridging function spanning multiple RLC entities within the third protocol layer (such as the RLC layer), the received public flow logical channels and private flow logical channels are restored to RLC channels (PDCP PDU / RLC SDU) and delivered to the upper layer.

[0315] In one embodiment, the third protocol layer of the second device creates at least one sixth entity, and the SDU of the first protocol layer is merged through the at least one sixth entity to obtain the SDU of the third protocol layer.

[0316] For example, the third protocol layer (RLC layer) of the second device first establishes RLC entities for the public flow and the private flow respectively, and then reconstructs the new RLC entities. The new RLC entities restore the public flow logical channel and the private flow logical channel to RLC channels (PDCP PDU / RLC SDU) and submit them to the upper layer.

[0317] Optionally, the method further includes:

[0318] The fourth protocol layer of the second device obtains the SDU of the third protocol layer through at least one seventh entity;

[0319] The fourth protocol layer of the second device merges the SDUs of the third protocol layer through the bridging function of the at least one seventh entity to obtain the SDUs of the fourth protocol layer; or,

[0320] The fourth protocol layer of the second device creates at least one eighth entity, and the SDU of the third protocol layer is merged through the at least one eighth entity to obtain the SDU of the fourth protocol layer.

[0321] Among them, the fourth protocol layer can be the PDCP layer. The seventh entity can be a PDCP entity, and the eighth entity can be a PDCP entity.

[0322] In one embodiment, the fourth protocol layer of the second device merges the SDUs of the third protocol layer through the bridging function of the at least one seventh entity to obtain the SDU of the fourth protocol layer. Thus, by incorporating a bridging function spanning multiple PDCP entities within the fourth protocol layer (such as the PDCP layer), the received public flow logical channels and private flow logical channels are restored to PDCP channels (SDAP PDU / PDCP SDU) and delivered to the upper layer.

[0323] In one embodiment, the fourth protocol layer of the second device creates at least one eighth entity, and the SDU of the third protocol layer is merged through the at least one eighth entity to obtain the SDU of the fourth protocol layer.

[0324] For example, the fourth protocol layer (PDCP layer) of the second device first establishes PDCP entities for the public flow and the private flow respectively, and then constructs a new PDCP entity. The new PDCP entity restores the public flow logical channel and the private flow logical channel to PDCP channels and submits them to the upper layer.

[0325] It should be noted that this embodiment is as a comparison with... Figure 4 The embodiments shown depict the implementation of the corresponding receiving end. For more details, please refer to [link to specific implementation methods]. Figure 4 The related descriptions of the embodiments shown are not repeated here to avoid repetition.

[0326] The data transmission method provided in this application can be executed by a data transmission device. This application uses a data transmission device executing the data transmission method as an example to illustrate the data transmission device provided in this application.

[0327] This application provides a data transmission device. As an example, the data transmission device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0328] The data transmission device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0329] For details, see Figure 9 When the data transmission device is the first device or a component of the first device, the data transmission device 300 includes:

[0330] The processing module 301 is used to generate a first data stream and a second data stream corresponding to each of the at least one target devices through the first protocol layer based on the service data unit (SDU) of the first protocol layer. The first data stream is received by the at least one target device, and the second data stream is received by the corresponding target device.

[0331] The processing module 301 is further configured to deliver the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer through the first protocol layer.

[0332] Optionally, the processing module is specifically used for:

[0333] The first protocol layer submits the transport block (TB) of the first data stream to the second protocol layer through a Hybrid Automatic Repeat Request (HARQ) process; or, the first protocol layer of the first device submits the TB of the first data stream to the second protocol layer through multiple first HARQ processes, wherein the first data stream includes multiple sub-data streams, and the multiple sub-data streams correspond one-to-one with the multiple first HARQ processes.

[0334] The first protocol layer submits the TB of the second data stream corresponding to the at least one target device to the second protocol layer through at least one second HARQ process, and the at least one second HARQ process corresponds one-to-one with the at least one target device.

[0335] Optionally, the processing module is further configured to:

[0336] The codeword of the first data stream is generated by the second protocol layer based on the TB corresponding to the one HARQ process, or the codeword of the first data stream is generated based on the TB corresponding to each of the plurality of first HARQ processes.

[0337] The second protocol layer generates codewords for the corresponding second data stream based on the TB corresponding to each of the at least one second HARQ process.

[0338] The codewords of the first data stream and the second data stream transmitted on at least partially overlapping time-frequency resources are determined by the second protocol layer;

[0339] The symbols corresponding to the codewords of the first data stream and the second data stream are pre-encoded by the second protocol layer, and the pre-encoded symbols are superimposed on the at least partially overlapping time-frequency resources for transmission.

[0340] Optionally, the processing module is specifically used for any of the following:

[0341] The SDUs in multiple channels of the first protocol layer are merged and / or split by the first protocol layer to obtain a first data stream and a second data stream corresponding to each target device in at least one target device.

[0342] A first data stream is obtained by the first protocol layer based on the SDU of the first channel among multiple channels of the first protocol layer, and a second data stream corresponding to each target device in at least one target device is obtained based on the SDU of the second channel among multiple channels of the first protocol layer, wherein the first channel carries the first data stream and the second channel carries the second data stream.

[0343] Optionally, the processing module is further configured to:

[0344] The corresponding SDU of the third protocol layer is obtained through at least one first entity via the third protocol layer;

[0345] The SDUs of the third protocol layer are merged and / or split using the bridging function of the at least one first entity to obtain the SDUs of the first channel and the SDUs of the second channel; or,

[0346] At least one second entity is created through the third protocol layer, and the SDU of the third protocol layer is merged and / or split through the at least one second entity to obtain the SDU of the first channel and the SDU of the second channel.

[0347] Optionally, the processing module is further configured to:

[0348] The SDU of the first channel is obtained by the third protocol layer based on the SDU of the third channel among the multiple channels of the third protocol layer, and the SDU of the second channel is obtained based on the SDU of the fourth channel among the multiple channels of the third protocol layer. The third channel carries the first data stream, and the fourth channel carries the second data stream.

[0349] Optionally, the processing module is further configured to:

[0350] The corresponding SDU of the fourth protocol layer is obtained through at least one third entity via the fourth protocol layer;

[0351] The SDUs of the fourth protocol layer are merged and / or split through the bridging function of the at least one third entity, thereby obtaining the SDUs of the third channel and the SDUs of the fourth channel; or,

[0352] At least one fourth entity is created through the fourth protocol layer, and the SDU of the fourth protocol layer is merged and / or split through the at least one fourth entity to obtain the SDU of the third channel and the SDU of the fourth channel.

[0353] See Figure 10 When the data transmission device is a second device or a component of the second device, the data transmission device 400 includes:

[0354] Processing module 401 is configured to generate SDU of the first protocol layer based on the first data stream through the first protocol layer, wherein the receiving object of the first data stream is at least one target device, and the at least one target device includes the second device;

[0355] The processing module 401 is also used to submit the SDU of the first protocol layer to the third protocol layer through the first protocol layer.

[0356] Optionally, the processing module is specifically used for:

[0357] The first protocol layer generates the SDU based on the first data stream and the second data stream corresponding to the second device.

[0358] Optionally, the processing module is specifically used for any of the following:

[0359] The first data stream and the second data stream corresponding to the second device are merged by the first protocol layer to obtain SDUs for multiple channels of the first protocol layer;

[0360] The first protocol layer generates the SDU of the fifth channel among the multiple channels of the first protocol layer based on the first data stream, and generates the SDU of the sixth channel among the multiple channels of the first protocol layer based on the second data stream. The fifth channel carries the first data stream, and the sixth channel carries the second data stream.

[0361] Optionally, the processing module is specifically used for:

[0362] The sub-data stream corresponding to the second device in the first data stream is extracted through the first protocol layer;

[0363] The first protocol layer merges the sub-data stream corresponding to the second device and the second data stream corresponding to the second device to obtain the SDU of multiple channels of the first protocol layer.

[0364] Optionally, the processing module is further configured to:

[0365] The first data stream is subjected to CRC check and / or retransmission operations via a HARQ process through a first protocol layer or a second protocol layer; or, the first protocol layer or the second protocol layer of the second device performs CRC check and / or retransmission operations on the first data stream through multiple third HARQ processes, wherein the first data stream includes multiple sub-data streams, and the multiple sub-data streams correspond one-to-one with the multiple third HARQ processes; and / or

[0366] The second data stream corresponding to the second device is subjected to CRC verification and / or retransmission operations through the fourth HARQ process via the first or second protocol layer.

[0367] Optionally, the processing module is specifically used for:

[0368] The first data stream's code blocks or code block groups are CRC checked by one HARQ process, or the code blocks or code block groups of the sub-data stream corresponding to each third HARQ process are CRC checked by each third HARQ process.

[0369] or,

[0370] The TB of the first data stream is generated based on the codewords of the first data stream, and the TB of the first data stream is CRC checked by the first HARQ process, or the TB of the sub-data stream corresponding to the third HARQ process is CRC checked by each third HARQ process.

[0371] Optionally, the processing module is further configured to:

[0372] The SDU of the first protocol layer is obtained through at least one fifth entity via the third protocol layer;

[0373] The SDUs of the first protocol layer are merged through the bridging function of the at least one fifth entity at the third protocol layer to obtain the SDU of the third protocol layer; or,

[0374] At least one sixth entity is created through the third protocol layer, and the SDU of the first protocol layer is merged through the at least one sixth entity to obtain the SDU of the third protocol layer;

[0375] The third protocol layer generates the SDU of the seventh channel and the SDU of the eighth channel among the multiple channels of the third protocol layer based on the SDU of the first protocol layer. The seventh channel carries the first data stream, and the eighth channel carries the second data stream.

[0376] Optionally, the processing module is further configured to:

[0377] The SDU of the third protocol layer is obtained through at least one seventh entity via the fourth protocol layer;

[0378] The SDUs of the third protocol layer are merged through the bridging function of the at least one seventh entity at the fourth protocol layer to obtain the SDU of the fourth protocol layer; or,

[0379] At least one eighth entity is created through the fourth protocol layer, and the SDU of the third protocol layer is merged through the at least one eighth entity to obtain the SDU of the fourth protocol layer.

[0380] The data transmission device provided in this application embodiment can achieve... Figure 4 and Figure 8 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0381] like Figure 11As shown, this application embodiment also provides a communication device 500, including a processor 501 and a memory 502. The memory 502 stores a program or instructions that can run on the processor 501. For example, when the communication device 500 is a first device, when the program or instructions are executed by the processor 501, they implement the various steps of the data transmission method embodiment applied to the first device described above, and achieve the same technical effect. When the communication device 500 is a second device, when the program or instructions are executed by the processor 501, they implement the various steps of the data transmission method embodiment applied to the second device described above, and achieve the same technical effect. To avoid repetition, this will not be repeated here.

[0382] This application embodiment also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 4 or Figure 8 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the method embodiment on the first or second device side described above. All implementation processes and methods of the above method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 9 or Figure 10 The data transmission device shown. Specifically, Figure 12 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0383] The terminal 600 includes, but is not limited to, at least some of the following components: radio frequency unit 601, network module 602, audio output unit 603, input unit 604, sensor 605, display unit 606, user input unit 607, interface unit 608, memory 609, and processor 610.

[0384] Those skilled in the art will understand that the terminal 600 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 610 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 12 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0385] It should be understood that, in this embodiment, the input unit 604 may include a graphics processor 6041 and a microphone 6042. The graphics processor 6041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0386] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 601 can transmit it to the processor 610 for processing; in addition, the radio frequency unit 601 can send uplink data to the network-side device. Typically, the radio frequency unit 601 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0387] The memory 609 can be used to store software programs or instructions, as well as various data. The memory 609 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 609 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 609 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0388] Processor 610 may include one or more processing units; optionally, processor 610 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 610.

[0389] In the case where the terminal is the first device:

[0390] The processor 610 is configured to generate a first data stream and a second data stream corresponding to each of the at least one target devices through a first protocol layer based on the service data unit (SDU) of the first protocol layer, wherein the first data stream is received by the at least one target device and the second data stream is received by the corresponding target device.

[0391] The processor 610 is configured to deliver the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer via the first protocol layer.

[0392] Optionally, the processor 610 is specifically used for:

[0393] The first protocol layer submits the transport block (TB) of the first data stream to the second protocol layer through a Hybrid Automatic Repeat Request (HARQ) process; or, the first protocol layer of the first device submits the TB of the first data stream to the second protocol layer through multiple first HARQ processes, wherein the first data stream includes multiple sub-data streams, and the multiple sub-data streams correspond one-to-one with the multiple first HARQ processes.

[0394] The first protocol layer submits the TB of the second data stream corresponding to the at least one target device to the second protocol layer through at least one second HARQ process, and the at least one second HARQ process corresponds one-to-one with the at least one target device.

[0395] Optionally, the processor 610 is further configured to:

[0396] The codeword of the first data stream is generated by the second protocol layer based on the TB corresponding to the one HARQ process, or the codeword of the first data stream is generated based on the TB corresponding to each of the plurality of first HARQ processes.

[0397] The second protocol layer generates codewords for the corresponding second data stream based on the TB corresponding to each of the at least one second HARQ process.

[0398] The codewords of the first data stream and the second data stream transmitted on at least partially overlapping time-frequency resources are determined by the second protocol layer;

[0399] The symbols corresponding to the codewords of the first data stream and the second data stream are pre-encoded by the second protocol layer, and the pre-encoded symbols are superimposed on the at least partially overlapping time-frequency resources for transmission.

[0400] Optionally, the processor 610 is specifically used for any of the following:

[0401] The SDUs in multiple channels of the first protocol layer are merged and / or split by the first protocol layer to obtain a first data stream and a second data stream corresponding to each target device in at least one target device.

[0402] A first data stream is obtained by the first protocol layer based on the SDU of the first channel among multiple channels of the first protocol layer, and a second data stream corresponding to each target device in at least one target device is obtained based on the SDU of the second channel among multiple channels of the first protocol layer, wherein the first channel carries the first data stream and the second channel carries the second data stream.

[0403] Optionally, the processor 610 is further configured to:

[0404] The corresponding SDU of the third protocol layer is obtained through at least one first entity via the third protocol layer;

[0405] The SDUs of the third protocol layer are merged and / or split using the bridging function of the at least one first entity to obtain the SDUs of the first channel and the SDUs of the second channel; or,

[0406] At least one second entity is created through the third protocol layer, and the SDU of the third protocol layer is merged and / or split through the at least one second entity to obtain the SDU of the first channel and the SDU of the second channel.

[0407] Optionally, the processor 610 is further configured to:

[0408] The SDU of the first channel is obtained by the third protocol layer based on the SDU of the third channel among the multiple channels of the third protocol layer, and the SDU of the second channel is obtained based on the SDU of the fourth channel among the multiple channels of the third protocol layer. The third channel carries the first data stream, and the fourth channel carries the second data stream.

[0409] Optionally, the processor 610 is further configured to:

[0410] The corresponding SDU of the fourth protocol layer is obtained through at least one third entity via the fourth protocol layer;

[0411] The SDUs of the fourth protocol layer are merged and / or split through the bridging function of the at least one third entity, thereby obtaining the SDUs of the third channel and the SDUs of the fourth channel; or,

[0412] At least one fourth entity is created through the fourth protocol layer, and the SDU of the fourth protocol layer is merged and / or split through the at least one fourth entity to obtain the SDU of the third channel and the SDU of the fourth channel.

[0413] In the case where the terminal is a second device:

[0414] The processor 610 is configured to generate an SDU of the first protocol layer based on a first data stream through the first protocol layer, wherein the first data stream is received by at least one target device, and the at least one target device includes the second device;

[0415] The processor 610 is also configured to deliver the SDU of the first protocol layer to the third protocol layer via the first protocol layer.

[0416] Optionally, the processor 610 is specifically used for:

[0417] The first protocol layer generates the SDU based on the first data stream and the second data stream corresponding to the second device.

[0418] Optionally, the processor 610 is specifically used for any of the following:

[0419] The first data stream and the second data stream corresponding to the second device are merged by the first protocol layer to obtain SDUs for multiple channels of the first protocol layer;

[0420] The first protocol layer generates the SDU of the fifth channel among the multiple channels of the first protocol layer based on the first data stream, and generates the SDU of the sixth channel among the multiple channels of the first protocol layer based on the second data stream. The fifth channel carries the first data stream, and the sixth channel carries the second data stream.

[0421] Optionally, the processor 610 is specifically used for:

[0422] The sub-data stream corresponding to the second device in the first data stream is extracted through the first protocol layer;

[0423] The first protocol layer merges the sub-data stream corresponding to the second device and the second data stream corresponding to the second device to obtain the SDU of multiple channels of the first protocol layer.

[0424] Optionally, the processor 610 is further configured to:

[0425] The first data stream is subjected to CRC check and / or retransmission operations via a HARQ process through a first protocol layer or a second protocol layer; or, the first protocol layer or the second protocol layer of the second device performs CRC check and / or retransmission operations on the first data stream through multiple third HARQ processes, wherein the first data stream includes multiple sub-data streams, and the multiple sub-data streams correspond one-to-one with the multiple third HARQ processes; and / or

[0426] The second data stream corresponding to the second device is subjected to CRC verification and / or retransmission operations through the fourth HARQ process via the first or second protocol layer.

[0427] Optionally, the processor 610 is specifically used for:

[0428] The first data stream's code blocks or code block groups are CRC checked by one HARQ process, or the code blocks or code block groups of the sub-data stream corresponding to each third HARQ process are CRC checked by each third HARQ process.

[0429] or,

[0430] The TB of the first data stream is generated based on the codewords of the first data stream, and the TB of the first data stream is CRC checked by the first HARQ process, or the TB of the sub-data stream corresponding to the third HARQ process is CRC checked by each third HARQ process.

[0431] Optionally, the processor 610 is further configured to:

[0432] The SDU of the first protocol layer is obtained through at least one fifth entity via the third protocol layer;

[0433] The SDUs of the first protocol layer are merged through the bridging function of the at least one fifth entity at the third protocol layer to obtain the SDU of the third protocol layer; or,

[0434] At least one sixth entity is created through the third protocol layer, and the SDU of the first protocol layer is merged through the at least one sixth entity to obtain the SDU of the third protocol layer;

[0435] The third protocol layer generates the SDU of the seventh channel and the SDU of the eighth channel among the multiple channels of the third protocol layer based on the SDU of the first protocol layer. The seventh channel carries the first data stream, and the eighth channel carries the second data stream.

[0436] Optionally, the processor 610 is further configured to:

[0437] The SDU of the third protocol layer is obtained through at least one seventh entity via the fourth protocol layer;

[0438] The SDUs of the third protocol layer are merged through the bridging function of the at least one seventh entity at the fourth protocol layer to obtain the SDU of the fourth protocol layer; or,

[0439] At least one eighth entity is created through the fourth protocol layer, and the SDU of the third protocol layer is merged through the at least one eighth entity to obtain the SDU of the fourth protocol layer.

[0440] It is understood that the implementation process of each implementation method mentioned in this embodiment can be referred to the method embodiment. Figure 4 or Figure 8 The relevant descriptions and the achievement of the same or corresponding technical effects will not be repeated here to avoid duplication.

[0441] This application embodiment also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement, for example... Figure 4 or Figure 8 The steps of the method embodiment shown are illustrated. This network-side device embodiment corresponds to the first or second device method embodiment described above. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0442] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 12 The data transmission device shown. (For example...) Figure 13 As shown, the network-side device 700 includes: an antenna 701, a radio frequency (RF) device 702, a baseband device 703, a processor 704, and a memory 705. The antenna 701 is connected to the RF device 702. In the uplink direction, the RF device 702 receives information through the antenna 701 and transmits the received information to the baseband device 703 for processing. In the downlink direction, the baseband device 703 processes the information to be transmitted and sends it to the RF device 702. The RF device 702 processes the received information and transmits it through the antenna 701.

[0443] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 703, which includes a baseband processor.

[0444] The baseband device 703 may, for example, include at least one baseband board on which multiple chips are disposed, such as... Figure 13 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 705 via a bus interface to call the program in the memory 705 and execute the network device operations shown in the above method embodiment.

[0445] The network-side device may also include a network interface 706, such as a Common Public Radio Interface (CPRI).

[0446] Specifically, the network-side device 700 in this application embodiment further includes: instructions or programs stored in memory 705 and executable on processor 704, wherein processor 704 calls the instructions or programs in memory 705 to execute. Figure 9 or Figure 10 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0447] Specifically, embodiments of this application also provide a network-side device. For example... Figure 14 As shown, the network-side device 800 includes: a processor 801, a network interface 802, and a memory 803. This network-side device can be... Figure 9 or Figure 10 The data transmission device shown. The network interface 802 is, for example, a common public radio interface (CPRI).

[0448] Specifically, the network-side device 800 in this application embodiment further includes: instructions or programs stored in memory 803 and executable on processor 801, wherein processor 801 calls the instructions or programs in memory 803 to execute. Figure 9 or Figure 10 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0449] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described data transmission method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0450] The processor mentioned above is the processor in the terminal or network-side device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0451] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above data transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0452] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0453] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described data transmission method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0454] This application also provides a wireless communication system, including a first device and a second device. The first device can be used to perform the steps of the data transmission method applied to the first device as described above, and the second device can be used to perform the steps of the data transmission method applied to the second device as described above.

[0455] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0456] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0457] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A data transmission method, characterized by, The method comprises: A first protocol layer of a first device generates a first data stream and a second data stream corresponding to each of at least one target device based on service data units (SDUs) of the first protocol layer, wherein the first data stream is for the at least one target device, and the second data stream is for the corresponding target device; The first protocol layer of the first device submits the first data stream and the second data stream corresponding to the at least one target device to a second protocol layer.

2. The method of claim 1, wherein, The first protocol layer of the first device submits the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer, comprising: The first protocol layer of the first device submits a transport block (TB) of the first data stream to the second protocol layer through one hybrid automatic repeat request (HARQ) process, or the first protocol layer of the first device submits TBs of the first data stream to the second protocol layer through a plurality of first HARQ processes, wherein the first data stream comprises a plurality of sub-data streams, and the plurality of sub-data streams correspond to the plurality of first HARQ processes one by one; The first protocol layer of the first device submits TBs of the second data stream corresponding to the at least one target device to the second protocol layer through at least one second HARQ process, wherein the at least one second HARQ process corresponds to the at least one target device one by one.

3. The method of claim 2, wherein, The method further comprises: The second protocol layer of the first device generates a code word of the first data stream based on the TB corresponding to the one HARQ process, or generates a code word of the first data stream based on the TB corresponding to each of the plurality of first HARQ processes; The second protocol layer of the first device generates a code word of the corresponding second data stream based on the TB corresponding to each of the at least one second HARQ process, respectively; The second protocol layer of the first device determines the code words of the first data stream and the second data stream transmitted on at least partially overlapping time-frequency resources; The second protocol layer of the first device respectively pre-encodes the symbols corresponding to the code words of the first data stream and the second data stream, and superimposes the pre-encoded symbols on the at least partially overlapping time-frequency resources for transmission.

4. The method according to any one of claims 1 to 3, characterized in that, The first protocol layer of the first device generates a first data stream and a second data stream corresponding to each of at least one target device based on service data units (SDUs) of the first protocol layer, comprising any of the following: The first protocol layer of the first device merges and / or splits the SDUs in a plurality of channels of the first protocol layer to obtain the first data stream and the second data stream corresponding to each of the at least one target device; The first protocol layer of the first device obtains the first data stream based on the SDUs of a first channel in a plurality of channels of the first protocol layer, and obtains the second data stream corresponding to each of the at least one target device based on the SDUs of a second channel in the plurality of channels of the first protocol layer, wherein the first channel carries the first data stream, and the second channel carries the second data stream.

5. The method of claim 4, wherein, The method further comprises: The third protocol layer of the first device obtains SDUs corresponding to the third protocol layer through at least one first entity; The third protocol layer of the first device performs merging and / or splitting processing on the SDUs of the third protocol layer through a bridging function of the at least one first entity, to obtain SDUs of the first channel and SDUs of the second channel; or The third protocol layer of the first device creates at least one second entity, and performs merging and / or splitting processing on the SDUs of the third protocol layer through the at least one second entity, to obtain SDUs of the first channel and SDUs of the second channel.

6. The method of claim 4, wherein, The method further comprises: The third protocol layer of the first device obtains SDUs of the first channel based on SDUs of a third channel in a plurality of channels of the third protocol layer, and obtains SDUs of the second channel based on SDUs of a fourth channel in the plurality of channels of the third protocol layer, the third channel carrying the first data stream, and the fourth channel carrying the second data stream.

7. The method of claim 6, wherein, The method further comprises: The fourth protocol layer of the first device obtains SDUs corresponding to the fourth protocol layer through at least one third entity; The fourth protocol layer of the first device performs merging and / or splitting processing on the SDUs of the fourth protocol layer through a bridging function of the at least one third entity, to obtain SDUs of the third channel and SDUs of the fourth channel; or The fourth protocol layer of the first device creates at least one fourth entity, and performs merging and / or splitting processing on the SDUs of the fourth protocol layer through the at least one fourth entity, to obtain SDUs of the third channel and SDUs of the fourth channel.

8. A data transmission method, characterized by, Comprises: The first protocol layer of the second device generates SDUs of the first protocol layer based on a first data stream, a receiving object of the first data stream being at least one target device, the at least one target device comprising the second device; The first protocol layer of the second device submits the SDUs of the first protocol layer to a third protocol layer.

9. The method of claim 8, wherein, The first protocol layer of the second device generates SDUs of the first protocol layer based on a first data stream, comprising: The first protocol layer of the second device generates SDUs of the first protocol layer based on a first data stream and a second data stream corresponding to the second device.

10. The method of claim 9, wherein, The first protocol layer of the second device generates SDUs of the first protocol layer based on a first data stream and a second data stream corresponding to the second device, comprising any one of the following: The first protocol layer of the second device performs merging processing on the first data stream and the second data stream corresponding to the second device, to obtain SDUs of a plurality of channels of the first protocol layer; The first protocol layer of the second device generates SDUs of a fifth channel in a plurality of channels of the first protocol layer based on the first data stream, and generates SDUs of a sixth channel in the plurality of channels of the first protocol layer based on the second data stream, the fifth channel carrying the first data stream, and the sixth channel carrying the second data stream.

11. The method of claim 10, wherein, The first protocol layer of the second device performs merging processing on the first data stream and a second data stream corresponding to the second device, to obtain SDUs of multiple channels of the first protocol layer, including: The first protocol layer of the second device extracts a sub-data stream corresponding to the second device in the first data stream; The first protocol layer of the second device performs merging processing on the sub-data stream corresponding to the second device and the second data stream corresponding to the second device, to obtain SDUs of multiple channels of the first protocol layer.

12. The method according to any one of claims 8-11, characterized in that, The method further includes: The first protocol layer or the second protocol layer of the second device performs CRC check operation and / or retransmission operation on the first data stream through one HARQ process; or, the first protocol layer or the second protocol layer of the second device performs CRC check operation and / or retransmission operation on the first data stream through multiple third HARQ processes, the first data stream includes multiple sub-data streams, and the multiple sub-data streams correspond to the multiple third HARQ processes one by one; and / or, The first protocol layer or the second protocol layer of the second device performs CRC check operation and / or retransmission operation on the second data stream corresponding to the second device through a fourth HARQ process.

13. The method of claim 12, wherein, The CRC check operation on the first data stream includes: CRC check is performed on a code block or a code block group of the first data stream through the one HARQ process, or CRC check is performed on a code block or a code block group of a sub-data stream corresponding to the third HARQ process through each third HARQ process; Or, A TB of the first data stream is generated based on a code word of the first data stream, CRC check is performed on the TB of the first data stream through the one HARQ process, or CRC check is performed on a TB of a sub-data stream corresponding to the third HARQ process through each third HARQ process.

14. The method according to any one of claims 8-13, characterized in that, The method further includes: The third protocol layer of the second device acquires the SDUs of the first protocol layer through at least one fifth entity; The third protocol layer of the second device performs merging processing on the SDUs of the first protocol layer through a bridging function of the at least one fifth entity, to obtain SDUs of the third protocol layer; or, The third protocol layer of the second device creates at least one sixth entity, and performs merging processing on the SDUs of the first protocol layer through the at least one sixth entity, to obtain SDUs of the third protocol layer; The third protocol layer of the second device generates SDUs of a seventh channel and SDUs of an eighth channel in multiple channels of the third protocol layer based on the SDUs of the first protocol layer, the seventh channel carries the first data stream, and the eighth channel carries the second data stream.

15. The method of claim 14, wherein, The method further includes: The fourth protocol layer of the second device acquires the SDUs of the third protocol layer through at least one seventh entity; The fourth protocol layer of the second device performs merging processing on the SDUs of the third protocol layer through a bridging function of the at least one seventh entity, to obtain SDUs of the fourth protocol layer; or, The fourth protocol layer of the second device creates at least one eighth entity through which the SDUs of the third protocol layer are merged to obtain SDUs of the fourth protocol layer.

16. A data transmission apparatus, characterized by comprising: Comprise: The processing module is used for generating, by the first protocol layer, a first data stream and a second data stream corresponding to each of the at least one target device based on service data units (SDUs) of the first protocol layer, the receiving object of the first data stream being the at least one target device, and the receiving object of the second data stream being the corresponding target device. The processing module is used for submitting, by the first protocol layer, the first data stream and the second data stream corresponding to the at least one target device to the second protocol layer.

17. The apparatus of claim 16, wherein, The processing module is specifically used for: submitting, by the first protocol layer, a transport block (TB) of the first data stream to the second protocol layer through one hybrid automatic repeat request (HARQ) process, or submitting TBs of the first data stream to the second protocol layer through a plurality of first HARQ processes, the first data stream comprising a plurality of sub-data streams, and the plurality of sub-data streams corresponding to the plurality of first HARQ processes one by one; submitting, by the first protocol layer, TBs of the second data streams corresponding to the at least one target device to the second protocol layer through at least one second HARQ process, the at least one second HARQ process corresponding to the at least one target device one by one.

18. The apparatus of claim 17, wherein, The processing module is further used for: generating a code word of the first data stream based on the TB corresponding to the one HARQ process, or generating a code word of the first data stream based on the TB corresponding to each of the plurality of first HARQ processes; generating a code word of the corresponding second data stream based on the TB corresponding to each of the at least one second HARQ process respectively through the second protocol layer; determining, by the second protocol layer, the code words of the first data stream and the second data stream transmitted on at least partially overlapped time-frequency resources; performing precoding on the symbols corresponding to the code words of the first data stream and the second data stream respectively through the second protocol layer, and superimposing the precoded symbols onto the at least partially overlapped time-frequency resources for transmission.

19. The apparatus of any one of claims 16-18, wherein, The processing module is specifically used for any one of the following: performing merging and / or splitting processing on the SDUs in a plurality of channels of the first protocol layer through the first protocol layer to obtain the first data stream and the second data stream corresponding to each of the at least one target device; obtaining the first data stream based on the SDUs of a first channel in the plurality of channels of the first protocol layer and obtaining the second data stream corresponding to each of the at least one target device based on the SDUs of a second channel in the plurality of channels of the first protocol layer through the first protocol layer, the first channel carrying the first data stream, and the second channel carrying the second data stream.

20. A data transmission apparatus, characterized by comprising: Comprise: The processing module is used for generating, by the first protocol layer, SDUs of the first protocol layer based on a first data stream, the receiving object of the first data stream being at least one target device, and the at least one target device comprising the second device; The processing module is further configured to submit the SDU of the first protocol layer to a third protocol layer via the first protocol layer.

21. The apparatus of claim 20, wherein, The processing module is specifically configured to: generate the SDU of the first protocol layer based on the first data stream and a second data stream corresponding to the second device via the first protocol layer.

22. The apparatus of claim 21, wherein, The processing module is specifically configured to any one of: perform merging processing on the first data stream and the second data stream corresponding to the second device via the first protocol layer to obtain the SDU of multiple channels of the first protocol layer; generate the SDU of a fifth channel of the multiple channels of the first protocol layer based on the first data stream and generate the SDU of a sixth channel of the multiple channels of the first protocol layer based on the second data stream via the first protocol layer, the fifth channel carrying the first data stream, and the sixth channel carrying the second data stream.

23. A communications device, characterized by A processor and a memory are included, the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the data transmission method according to any one of claims 1-7 or the steps of the data transmission method according to any one of claims 8-15.

24. A readable storage medium characterized by, The readable storage medium stores programs or instructions, and the programs or instructions are executed by the processor to implement the steps of the data transmission method according to any one of claims 1-7 or the steps of the data transmission method according to any one of claims 8-15.

25. A computer program / program product, characterized in that, The computer program / program product is executed by at least one processor to implement the steps of the data transmission method according to any one of claims 1-7 or the steps of the data transmission method according to any one of claims 8-15.

Images