# US 12,119,936 B2 · Data transmission method, terminal, and network device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,119,936 B2 - Document ID: US12119936B2 - Status: Granted - Kind: B2 - Application number: 17/196,452 - Filed: 2021-03-09 - Published: 2021-07-15 - Granted: 2024-10-15 - Earliest claimed: 2018-09-21 - Assignees: Vivo Mobile Communication Co., Ltd. - Applicants: Vivo Mobile Communication Co., Ltd. - Inventors: Yumin Wu; Xueming Pan; Peng Sun - Web page: https://patentgrep.com/patent/US12119936B2 ## CPC - H04L 1/1812: Hybrid protocols; Hybrid automatic repeat request [HARQ] - H04W 72/046: {the resource being in the space domain, e.g. beams} - H04L 1/1822: involving configuration of automatic repeat request [ARQ] with parallel processes - H04L 1/1893: {Physical mapping arrangements (physical resource mapping in general H04L5/00)} - H04L 5/001: {the frequencies being arranged in component carriers} - H04L 5/0053: {Allocation of signalling, i.e. of overhead other than pilot signals} - H04L 5/0055: {Physical resource allocation for ACK/NACK (for physical mapping arrangements in ARQ protocols H04L1/1861)} - H04W 72/0453: Resources in frequency domain, e.g. a carrier in FDMA - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A data transmission method includes: obtaining HARQ entities and MAC entities corresponding to a plurality of transmission carriers; and performing data transmission between the transmission carriers and the HARQ entities and MAC entities corresponding to the transmission carriers. ## Claims ### Claim 1 A data transmission method, applied to a terminal and comprising: obtaining hybrid automatic repeat request (HARQ) entities and medium access control (MAC) entities corresponding to a plurality of transmission carriers, wherein the transmission carriers are beams; and performing data transmission between the transmission carriers and the HARQ entities and MAC entities corresponding to the transmission carriers; wherein the obtaining HARQ entities and the MAC entities corresponding to the plurality of transmission carriers comprises: configuring the HARQ entities and the MAC entities for the plurality of transmission carriers based on mapping relationship information between HARQ and transmission carriers; or obtaining the HARQ entities and the MAC entities configured by a network device for the plurality of transmission carriers based on the mapping relationship information between HARQ and transmission carriers; wherein the mapping relationship information between HARQ and transmission carriers comprises: information about a transmission carrier; and HARQ configuration information corresponding to the information about the transmission carrier, wherein the information about the transmission carrier comprises at least one of a frequency identifier corresponding to the transmission carrier, a bandwidth part (BWP) identifier corresponding to the transmission carrier, or a control channel identifier corresponding to the transmission carrier. ### Claim 2 (depends on 1) The data transmission method according to claim 1, wherein the information about the transmission carrier further comprises at least one of a transmission carrier identifier, a cell identifier corresponding to the transmission carrier, or a MAC entity identifier corresponding to the transmission carrier. ### Claim 3 (depends on 2) The data transmission method according to claim 2, wherein the configuring the HARQ entities and MAC entities for the plurality of transmission carriers comprises: configuring different HARQ entities for different transmission carriers. ### Claim 4 (depends on 3) The data transmission method according to claim 3, wherein the HARQ configuration information corresponding to the information about the transmission carrier comprises a quantity of HARQ processes. ### Claim 5 (depends on 2) The data transmission method according to claim 2, wherein the configuring the HARQ entities and MAC entities for the plurality of transmission carriers comprises: configuring a same HARQ entity for the plurality of transmission carriers, and configuring different HARQ process IDs for different transmission carriers. ### Claim 6 (depends on 5) The data transmission method according to claim 5, wherein the HARQ configuration information corresponding to the information about the transmission carrier comprises at least one of an identifier of a HARQ entity corresponding to the transmission carrier, a HARQ process ID available to the transmission carrier, a total quantity of available HARQ processes of a HARQ entity corresponding to the transmission carrier, or a quantity of HARQ processes available to the transmission carrier. ### Claim 7 (depends on 2) The data transmission method according to claim 2, wherein the configuring the HARQ entities and MAC entities for the plurality of transmission carriers comprises: configuring different HARQ entities for different transmission carriers, and configuring different MAC entities for different transmission carriers. ### Claim 8 (depends on 7) The data transmission method according to claim 7, wherein the mapping relationship information between HARQ and transmission carriers further comprises MAC configuration information corresponding to the transmission carrier, and the HARQ configuration information corresponding to the information about the transmission carrier comprises a quantity of HARQ processes. ### Claim 9 (depends on 8) The data transmission method according to claim 8, wherein the MAC configuration information corresponding to the transmission carrier comprises at least one of: identifier information of a MAC entity; one or more logical channel identifiers corresponding to identifier information of a MAC entity; one or more data radio bearer (DRB) identifiers corresponding to identifier information of a MAC entity; one or more data flow identifiers corresponding to identifier information of a MAC entity; or one or more session identifiers corresponding to identifier information of a MAC entity. ### Claim 10 (depends on 2) The data transmission method according to claim 2, wherein the transmission carrier identifier comprises at least one of a synchronization signal block (SSB) identifier, a channel state information reference signal (CSI-RS) identifier, or a port number identifier corresponding to a reference signal, and the reference signal comprises an SSB and/or a CSI-RS. ### Claim 11 (depends on 2) The data transmission method according to claim 2, wherein the control channel identifier corresponding to the transmission carrier comprises at least one of a control channel type identifier, a resource position identifier of a control channel, a reference signal identifier of a control channel, or a port number identifier corresponding to a reference signal of a control channel. ### Claim 12 (depends on 2) The data transmission method according to claim 2, wherein the performing data transmission between the transmission carriers and the HARQ entities and MAC entities corresponding to the transmission carriers comprises: in a case of downlink data reception, transmitting data received by each transmission carrier to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing; and/or in a case of uplink data transmission, transmitting data to be transmitted to each transmission carrier, to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing. ### Claim 13 (depends on 12) The data transmission method according to claim 12, wherein the transmitting data received by each transmission carrier to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing in a case of downlink data reception comprises: in the case of downlink data reception, obtaining information about a first target transmission carrier; determining the first target transmission carrier based on the information about the first target transmission carrier; transmitting data received by the first target transmission carrier to a MAC entity and a HARQ entity corresponding to the first target transmission carrier, for processing; and the transmitting data to be transmitted to each transmission carrier, to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing in a case of uplink data transmission comprises: in the case of uplink data transmission, obtaining information about a second target transmission carrier; and determining the second target transmission carrier based on the information about the second target transmission carrier; transmitting data to be transmitted to the second target transmission carrier, to a MAC entity and a HARQ entity corresponding to the second target transmission carrier, for processing. ### Claim 14 A data transmission method, applied to a network device and comprising: obtaining hybrid automatic repeat request (HARQ) entities and medium access control (MAC) entities corresponding to a plurality of transmission carriers, wherein the transmission carriers are beams; and performing data transmission between the transmission carriers and the HARQ entities and MAC entities corresponding to the transmission carriers; wherein the obtaining the HARQ entities and the MAC entities corresponding to the plurality of transmission carriers comprises: configuring the HARQ entities and the MAC entities for the plurality of transmission carriers based on mapping relationship information between HARQ and transmission carriers; or obtaining the HARQ entities and the MAC entities configured by a terminal for the plurality of transmission carriers based on the mapping relationship information between HARQ and transmission carriers; wherein the mapping relationship information between HARQ and transmission carriers comprises: information about a transmission carrier; and HARQ configuration information corresponding to the information about the transmission carrier, wherein the information about the transmission carrier comprises at least one of a frequency identifier corresponding to the transmission carrier, a bandwidth part (BWP) identifier corresponding to the transmission carrier, or a control channel identifier corresponding to the transmission carrier. ### Claim 15 A terminal, comprising: a processor configured to obtain hybrid automatic repeat request (HARQ) entities and medium access control (MAC) entities corresponding to a plurality of transmission carriers, wherein the transmission carriers are beams; and a radio frequency unit configured to perform data transmission between the transmission carriers and the HARQ entities and MAC entities corresponding to the transmission carriers; wherein the processor is configured to: configure the HARQ entities and the MAC entities for the plurality of transmission carriers based on mapping relationship information between HARQ and transmission carriers; or the processor is configured to: obtain the HARQ entities and the MAC entities configured by a network device for the plurality of transmission carriers based on the mapping relationship information between HARQ and transmission carriers; wherein the mapping relationship information between HARQ and transmission carriers comprises: information about a transmission carrier; and HARQ configuration information corresponding to the information about the transmission carrier, wherein the information about the transmission carrier comprises at least one of a frequency identifier corresponding to the transmission carrier, a bandwidth part (BWP) identifier corresponding to the transmission carrier, or a control channel identifier corresponding to the transmission carrier. ### Claim 16 (depends on 15) The terminal according to claim 15, wherein the information about the transmission carrier further comprises at least one of a transmission carrier identifier, a cell identifier corresponding to the transmission carrier, or a MAC entity identifier corresponding to the transmission carrier. ### Claim 17 (depends on 16) The terminal according to claim 16, wherein the processor is configured to configure different HARQ entities for different transmission carriers; the processor is configured to configure a same HARQ entity for the plurality of transmission carriers, and configure different HARQ process IDs for different transmission carriers; or the processor is configured to configure different HARQ entities for different transmission carriers, and configure different MAC entities for different transmission carriers. ### Claim 18 (depends on 16) The terminal according to claim 16, wherein the transmission carrier identifier comprises at least one of a synchronization signal block (SSB) identifier, a channel state information reference signal (CSI-RS) identifier, or a port number identifier corresponding to a reference signal, and the reference signal comprises an SSB and/or a CSI-RS. ### Claim 19 (depends on 16) The terminal according to claim 16, wherein the control channel identifier corresponding to the transmission carrier comprises at least one of a control channel type identifier, a resource position identifier of a control channel, a reference signal identifier of a control channel, or a port number identifier corresponding to a reference signal of a control channel. ### Claim 20 (depends on 16) The terminal according to claim 16, wherein the processor is configured to: in a case of downlink data reception, transmit data received by each transmission carrier to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing; and/or in a case of uplink data transmission, transmit data to be transmitted to each transmission carrier, to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing.