Md transmission method, device and readable storage medium

Abstract

The application discloses an MD transmission method and device and a readable storage medium, and belongs to the technical field of communication. The method comprises the following steps: a terminal determines a binding preconfigured grant (CG) set according to a first configuration obtained from a network device, wherein the binding CG set comprises MD transmission of a same medium access control protocol data unit (MAC PDU) on different carriers, and a plurality of CGs have a binding relationship; and the terminal transmits the same MAC PDU on different carriers according to the binding CG set.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an MD transmission method, device, and readable storage medium. Background Technology

[0002] To enhance the reliability of data transmission, a Media Access Control (MAC) entity generates multiple copies of the same Multiple Access Control Protocol Data Unit (MAC PDU) and transmits them on multiple aggregated carriers. Currently, the protocol does not define a mechanism for implementing Multiple Access Control Duplication (MD) transmission based on pre-configured uplink transmission licenses. Summary of the Invention

[0003] The purpose of this application is to provide an MD transmission method, device, and readable storage medium to solve the problem that existing protocols regarding pre-configured uplink transmission licenses do not define how to implement MD transmission based on pre-configured uplink transmission licenses.

[0004] Firstly, a method for transmitting MD data is provided, including:

[0005] The terminal determines a pre-configured transmission license (CG) set to bind based on a first configuration obtained from the network device. The bound CG set includes multiple CGs that are bound to each other and are used for MD transmission of the same Media Access Control Protocol Data Unit (MAC PDU) on different carriers.

[0006] The terminal transmits the same MAC PDU on different carriers according to the bound CG set.

[0007] Secondly, an MD transmission device is provided, characterized in that it includes:

[0008] The first determining module is used to determine a set of pre-configured transmission licenses (CGs) for binding based on a first configuration obtained from the network device. The set of bound CGs includes multiple CGs that are bound to each other and are used for MD transmission of the same Media Access Control Protocol Data Unit (MACPDU) on different carriers.

[0009] The transmission module is used to transmit the same MAC PDU on different carriers according to the bound CG set.

[0010] Thirdly, a terminal is provided, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, performs the steps of the method described in the first aspect.

[0011] Fourthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the processing method described in the first aspect.

[0012] Fifthly, a computer program product is provided, the program product being stored in a non-transient storage medium, the computer program product being executed by at least one processor to implement the steps of the processing method as described in the first aspect.

[0013] In a sixth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the processing method as described in the first aspect.

[0014] In this embodiment, the terminal determines the binding relationship between pre-configured transmission licenses for MD transmission of the same MACPDU on different carriers according to the first configuration on the network side, thereby determining the binding pre-configured transmission license set. By binding the pre-configured transmission license set, the terminal ensures that the same data is transmitted on different carriers, thereby realizing MD transmission based on pre-configured transmission licenses. Attached Figure Description

[0015] Figure 1a This is a schematic diagram of a wireless communication system architecture provided in an embodiment of this application;

[0016] Figure 1b This is the execution flowchart of the sending end in MD transmission;

[0017] Figure 1c This is the execution flowchart of the receiving end in MD transmission;

[0018] Figure 1d This is a diagram illustrating the uplink transmission license configuration;

[0019] Figure 2 This is a flowchart illustrating the MD method based on pre-configured transport license provided in this application.

[0020] Figures 3a-3c This is a schematic diagram of an application scenario provided in the embodiments of this application;

[0021] Figure 4 This is a schematic diagram of the structure of the MD device based on pre-configured transmission license provided in this application;

[0022] Figure 5 This is a schematic diagram of the terminal provided in this application. Detailed Implementation

[0023] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and are not used to describe a specified 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, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0025] 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), and 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. However, the following description describes New Radio (NR) systems for illustrative purposes, and NR terminology is used in most of the following description. These technologies can also be applied to applications beyond NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0026] Figure 1aThis 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. In this context, terminal 11 can also be referred to as terminal equipment or user equipment (UE). Terminal 11 can be a mobile phone, tablet computer, laptop 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, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication functions, such as refrigerators, televisions, washing machines, or furniture), 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, game consoles, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to the specified technical terms. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0027] To better understand the technical solution of this application, the following will be introduced first:

[0028] MAC duplication

[0029] To enhance data transmission reliability, a MAC entity generates multiple copies of the same MAC PDU (Media Access Control Protocol Data Unit) and transmits them on multiple aggregated carriers. The receiving end receives signals belonging to the same MAC PDU on multiple carriers. Depending on the receiver implementation, the receiver can decode the signal received on a single carrier or perform soft combining of the received signals from multiple carriers before decoding. After correct decoding, the MAC PDU is decomposed into Media Access Control Service Data Units (MAC SDUs) and submitted to the Radio Link Control (RLC) layer. If the same MAC PDU is decoded on multiple carriers and a duplicate MAC SDU is submitted to the RLC layer, the RLC removes the duplicate MAC SDU and submits the corresponding PDCP PDU to the PDCP layer. Alternatively, the RLC can submit all correctly received data to the PDCP layer, and the PDCP layer removes duplicate data. Since the existing PDCP / RLC layers have deduplication capabilities, the discovery and deletion of duplicate data does not increase the complexity of the protocol. See the example flow of a MAC duplication (MD) sender. Figure 1b For an example of the receiving end process, please refer to [link / reference]. Figure 1c .

[0030] Through MAC duplication, network devices can transmit multiple copies of the same data block on different carriers. The receiving end can obtain the diversity gain between carriers and the soft information merging gain between multiple copies by merging and decoding the multiple copies. At the same time, network devices can schedule dense multi-copy transmissions on multiple aggregated carriers, reducing the probability of HARQ retransmissions and shortening data transmission latency.

[0031] NR HARQ mechanism

[0032] Each uplink aggregated carrier of NR (or one NR uplink carrier and one auxiliary uplink carrier) has a Hybrid Automatic Repeat reQuest (HARQ) entity. Each HARQ entity has a set of HARQ processes, and a single HARQ entity supports a maximum of 16 HARQ processes. Each HARQ process has a process identification identifier (HARQ Process ID, HARQ PID), and the network device indicates the HARQ process used for scheduled transmissions in the PDCCH.

[0033] For uplink transmission, the network device notifies the UE of the HARQ process it uses, and the UE uses that HARQ process for transmission. If a reception error occurs, the network device reschedules the HARQ process for retransmission. During retransmission, the NewData Indicator (NDI) and the transmission buffer size remain the same as the initial transmission. In this case, it is determined that the retransmission is a HARQ retransmission, and the MAC PDU in the HARQ buffer is directly submitted to the physical layer for encoding and transmission. If the NDI is reversed (i.e., NDI changes from 0 to 1 or from 1 to 0), it indicates that the scheduled data is newly transmitted data, and the UE's MAC entity will request new data from the RLC layer to assemble a new MAC PDU. For licensed frequencies, NR uplink only supports asynchronous HARQ transmission and does not have explicit HARQ ACK / NACK feedback.

[0034] Methods for NR uplink pre-configuration scheduling of licensed frequencies

[0035] Corresponding to LTE's semi-static uplink scheduling, NR also defines a method for uplink pre-configuration scheduling. The parameters for pre-configuring uplink transmission licenses can be those configured in the ConfiguredGrantConfig IE. Network devices can pre-configure semi-static periodic uplink transmission licenses and the corresponding set of HARQ processes for the UE. Figure 1d An example of uplink transport license configuration is provided.

[0036] The network device also configures the UE with a set of HARQ processes for using pre-configured uplink transmission licenses, including a HARQ process number offset harq-ProcID-Offset2 and the number of HARQ processes nrofHARQ-Processes. When data needs to be transmitted, after determining the uplink transmission license to use, the UE also needs to determine the HARQ process to use based on the sequence number of the pre-configured uplink transmission license.

[0037] Regarding pre-configured uplink transmission licenses, NR provides two configuration methods. Type 1 configuration involves configuring all parameters via RRC signaling, including the pre-configured uplink transmission license period and offset, HARQ process, Configured Scheduling Radio Network Temporary Identity (CS-RNTI), time-frequency resources, and Modulation and Coding Scheme (MCS). Type 2 configuration involves configuring some parameters via RRC signaling, such as the pre-configured uplink transmission license period, power control parameters, HARQ process, and CS-RNTI. Other physical layer parameters, such as MCS and time-frequency resources, are configured by the network device via the CS-RNTI-based Physical Downlink Control Channel (PDCCH). The network device can activate, deactivate, and reactivate the pre-configured uplink transmission license using the CS-RNTI-based PDCCH. If a reception error occurs, the network device uses the CS-RNTI-based PDCCH to schedule retransmissions.

[0038] When a MAC PDU transmission based on a pre-configured uplink transmission grant occurs, the UE starts a pre-configured grant timer (CGT) corresponding to the HARQ process used. During the execution of the CGT, the UE cannot use the same HARQ process for transmissions of other MAC PDUs based on the pre-configured uplink transmission grant. When the CGT expires, the UE determines that the MAC PDU transmission was correct and releases the HARQ process. When the UE receives a retransmission request from the network device using a CS-RNTI-based PDCCH, scheduling the retransmission of the HARQ process, the UE performs a HARQ retransmission of the MAC PDU.

[0039] Autonomous transmission mechanism based on pre-configured uplink transmission license

[0040] When a MAC PDU is generated using a pre-configured uplink transmission license, if a higher-priority data needs to be transmitted, the transmission of this MAC PDU is determined to be of low priority and ultimately not performed or not completed over-the-air transmission. In this case, the corresponding HARQ process is locked, and the corresponding CGT timer is stopped. This MAC PDU can then be transmitted using a subsequent HARQ process that matches this HARQ process.

[0041] Existing protocols regarding pre-configured uplink transmission licenses do not define how to implement MAC Duplication (MD) transmission based on pre-configured uplink transmission licenses. To obtain the gain from MAC duplication, relevant mechanisms and signaling procedures need to be defined.

[0042] The methods and apparatus provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0043] See Figure 2 This application provides an MD transmission method, the execution subject of which can be a terminal, and the specific steps include:

[0044] Step 201: The terminal determines the binding CG set based on the first configuration obtained from the network device. The binding CG set includes multiple pre-configured transmission grants (CGs) that are bound to the same MAC PDU on different carriers.

[0045] Step 202: The terminal transmits the same MAC PDU on different carriers according to the bound CG set;

[0046] In this embodiment of the application, the terminal determines the binding relationship between CGs used for MD transmission of the same MACPDU on different carriers according to the first configuration on the network side, thereby determining the binding CG set. By binding the CG set, the same data is transmitted on different carriers, thus realizing CG-based MD transmission.

[0047] The aforementioned set of bound CGs includes multiple CGs that are bound together and used for the same MAC PDU on different carriers.

[0048] It should be noted that the CG-based MD method provided in this application can be applied to both uplink and downlink communication scenarios. For ease of description, the following embodiments will be described using the uplink scenario as an example. It can be understood that the downlink communication scenario can be understood by referring to the uplink communication scenario.

[0049] In one possible implementation, the first configuration includes one or more of the following:

[0050] (1) MD configuration sequence number;

[0051] (2) CG configuration list, in which each CG configuration can be jointly identified by carrier sequence number, BWP sequence number and CG configuration sequence number;

[0052] (3) HARQ process configuration for MD transmission, specifically, may include:

[0053] Start process identifier: The start HARQ process number can be configured with an offset parameter, or it can be the default start HARQ process configured for each CG;

[0054] The number of HARQ processes X used for MD transfer in each CG configuration is not greater than the number of HARQ processes in the CG configuration list with the fewest HARQ processes.

[0055] (4) CGT initial value configuration for MD transmission;

[0056] (5) RNTI corresponding to MD transmission, which is used to transmit scheduling commands, activation / deactivation commands and retransmission scheduling commands based on MD transmission corresponding to the MD configuration;

[0057] (6) A list of carriers or cells used for MD transmission, so that in carrier aggregation scenarios, the terminal can know which carriers or cells are used for MD transmission through this list.

[0058] This application provides several specific methods for a terminal to determine a first binding relationship based on a first configuration:

[0059] Method 1: The terminal determines the set of bound CGs based on the binding relationship of HARQ processes configured in CGs on different carriers;

[0060] Specifically, these can be divided into two categories: Method 1a and Method 1b;

[0061] Method 1a: The network sends a first configuration to the UE via RRC signaling, the first configuration including at least one of the following parameters:

[0062] (1) MD configuration sequence number;

[0063] (2) CG configuration list, in which each CG configuration can be jointly identified by carrier sequence number, BWP sequence number and CG configuration sequence number;

[0064] (3) HARQ process configuration for MD transmission, specifically, may include:

[0065] Starting entry number: The starting HARQ entry number can be configured with an offset parameter, or it can be the default starting HARQ process configured for each CG;

[0066] The number of HARQ processes X used for MD transfer in each CG configuration is not greater than the number of HARQ processes in the CG configuration list with the fewest HARQ processes.

[0067] (4) CGT initial value configuration for MD transmission;

[0068] (5) RNTI corresponding to MD transmission, which is used to transmit scheduling commands, activation / deactivation commands and retransmission scheduling commands based on MD transmission corresponding to the MD configuration;

[0069] (6) List of carriers or cells used for MD transmission.

[0070] After receiving the CG configuration and MD configuration, the UE can determine the binding relationship between HARQ processes on different carriers according to the order of HARQ process numbers. The pre-configured uplink transmission licenses of the corresponding HARQ processes belonging to the same bound HARQ process set are the bound pre-configured uplink transmission license sets.

[0071] In one possible implementation, the HARQ process configuration for MD transmission includes the starting HARQ process identifier ID on different carriers;

[0072] The terminal determines the set of bound CGs based on the binding relationship of HARQ processes configured in CGs on different carriers, including:

[0073] The terminal binds the starting HARQ process on different carriers according to the starting HARQ process ID on different carriers, and then binds the i-th HARQ process used for MD transmission on different carriers in sequence, where i is a positive integer;

[0074] The terminal determines the set of bound CGs based on the HARQ processes that have binding relationships on different carriers.

[0075] The HARQ process used for MD transmission can be specifically determined by combining the CG configuration list in the first configuration and the HARQ process configuration for MD transmission. For example, HARQ processes with HARQ IDs of 3, 4, 5, and 6 can be configured in the CG configuration list, and then HARQ processes with HARQ IDs of 3, 4, and 5 can be configured in the HARQ process configuration for MD transmission for MD transmission.

[0076] In this embodiment, for different carriers, the starting HARQ processes on different carriers are bound together using the starting HARQ process ID configured in each CG configuration list, forming a bound HARQ process set. Specifically, the binding of starting HARQ processes on different carriers is determined based on their starting HARQ process IDs. Then, the binding of the i-th HARQ process used for MD transmission on different carriers is determined sequentially according to the order of the HARQ process IDs. For example, the second HARQ process used for MD transmission on carrier 1 is bound to the second HARQ process used for MD transmission on carrier 2. Finally, the bound CG set is determined according to the bound HARQ process set. This achieves a method of implicitly indicating HARQ process binding relationships through the starting HARQ process ID.

[0077] In one possible implementation, the first configuration also includes: a list of bound HARQ processes;

[0078] The terminal determines the set of bound CGs based on the binding relationship of HARQ processes configured in CGs on different carriers, including:

[0079] The terminal determines the set of CGs to be bound based on the list of bound HARQ processes.

[0080] In this embodiment, the network device can display a list of bound HARQ processes. This list includes HARQ processes on different carriers used for repeated transmission of the same MAC PDU. The terminal can directly determine the bound HARQ processes based on this list, and thus determine the bound CG set.

[0081] Optionally, the bound HARQ process can be defined as a super HARQ process, which can have a corresponding HARQ sequence number.

[0082] Method 1b: Configure a network MD configuration that contains only HARQ binding relationship configuration;

[0083] In one possible implementation, each HARQ process of a CG configuration in the CG configuration list corresponds to a different MD configuration sequence number;

[0084] The terminal determines the set of bound CGs based on the binding relationship of HARQ processes configured in CGs on different carriers, including:

[0085] The terminal determines the bound HARQ process based on the MD configuration sequence number;

[0086] The terminal determines the set of bound CGs based on the bound HARQ process.

[0087] Compared to method 1a, this method includes an MD configuration sequence number in each CG configuration within the CG configuration list, indicating the MD configuration to which that CG configuration belongs. Thus, for CG configurations with the same MD configuration sequence number, the HARQ processes of that CG configuration can be understood as having a binding relationship. In other words, the MD configuration sequence number implicitly indicates the HARQ process binding relationship. Other configuration parameters are described in the configuration parameter description of method 1a. The terminal determines the bound CG set using the same mechanism as method 1a.

[0088] It should be noted that in the actual application scenario of Method 1, the first configuration can include both CG configuration and MD configuration, or it can include an enhanced CG configuration, that is, adding the information content of the MD configuration to the CG configuration. This application embodiment does not specifically limit these two implementation methods.

[0089] See Figure 3a The figure shows an application scenario for uplink transmission licenses used for MD transmission based on pre-configured HARQ process binding. In this scenario, there are two carriers (denoted as component carrier (CC)1 and CC2). It should be noted that, for the sake of description, Figure 3a The HARQ process IDs on each carrier correspond to the HARQ processes used for MD transmission. The HARQ IDs on CC1 are 3, 4, 5, 3, 4 in sequence; and the HARQ IDs on CC2 are 4, 5, 6, 4, 5 in sequence. The UE determines the binding CG set by binding the HARQ process ID 3 of the starting HARQ process of CC1 with the HARQ ID 4 of the starting HARQ process of CC1, thus obtaining a HARQ process binding relationship. Then, based on this HARQ process binding relationship, the binding relationship of the CG is determined, thereby determining a binding CG set. Similarly, the HARQ IDs on CC1 and CC2 can be bound sequentially.

[0090] In this way, the UE determines the binding relationship of CG based on the binding relationship of HARQ process according to the network pre-configuration. When performing MD transmission, the same data will be transmitted on the corresponding carriers for HARQ processes with binding relationship, thereby realizing MD transmission based on CG.

[0091] Method 2: The terminal determines the binding CG set based on the binding relationship of HARQ processes of different carriers within the time window;

[0092] Compared to the parameters included in the first configuration of Method 1 above, the first configuration in this method also includes: periodic time-domain window configuration.

[0093] In this embodiment, the first configuration includes a CG configuration list and a periodic time window configuration. Each time window contains a pre-configured uplink transmission license set used for repeatedly transmitting the same MAC PDU, meaning they belong to the same bound pre-configured uplink transmission license set. Compared to the first configuration in Method 1, this method does not use a fixed binding relationship between HARQ processes in the pre-configured CG configurations. The UE determines the bound HARQ process set based on the HARQ process corresponding to the pre-configured uplink transmission license in the bound pre-configured uplink transmission license set. For example, when transmitting, the UE determines the uplink transmission licenses belonging to the same MD configuration and located within the same pre-configured time window as the bound pre-configured uplink transmission license set used for MD transmission of the same MAC PDU, and performs MD transmission. When the network device receives, it merges and detects the signals received within the pre-configured time window based on the uplink licenses belonging to the same MD configuration, and performs MAC PDU decoding. Figure 3b This demonstrates a method for determining uplink transmission clearance for MD transmission based on a time-domain window. The time-domain window can be configured using parameters such as time-domain offset, window length, and period. It is understood that by configuring an appropriate time-domain window, each carrier can contain only one or more HARQ processes within the window's range.

[0094] In this way, the UE determines the binding CG set based on the network pre-configuration and the time domain window. During MD transmission, the UE will transmit the same data on the corresponding carriers within the time domain window, thereby realizing MD transmission based on CG.

[0095] In one implementation, the terminal determines a set of bound CGs based on a first configuration obtained from a network device, including:

[0096] The terminal determines the set of bound CGs based on the CG configuration of different carriers within the time window;

[0097] In this embodiment of the application, since the CG configuration corresponds to the HARQ process, the terminal can also determine the binding CG set based on the CG configuration of all different carriers contained in the time domain window.

[0098] Method 3: The terminal determines the set of bound CGs based on the binding relationship between the sequence numbers of CGs on different carriers;

[0099] Compared to the parameters included in the first configuration in Method 1 above, the first configuration in this method also includes: the sequence number of CG.

[0100] In this embodiment, compared to method 1 and method 2, the terminal can determine the binding relationship between pre-configured licenses of different carriers based on the sequence number of the pre-configured uplink transmission license in the first configuration. The configuration methods in method 1 and method 2 can be reused for the CG configuration included in the first configuration. See an example. Figure 3c A first configuration includes a CG configuration on CC1 and a CG configuration on CC2. The pre-configured uplink transmission license with sequence number X on CC1 is bound to the CG configuration license with sequence number X+(mn) on CC2. Similar to Method 2, the UE and network device determine the binding HARQ process set based on the bound pre-configured uplink transmission license set. For example, when X=n, the pre-configured uplink transmission license sequence number n on CC1 is bound to the pre-configured uplink transmission license sequence number m on CC2, and correspondingly, the subsequent pre-configured uplink transmission license sequence number n+1 on CC1 is bound to the pre-configured uplink transmission license sequence number m+1 on CC2, and so on.

[0101] In one possible implementation, the operations for the configuredGrantTimer (CGT) under the first configuration described above include:

[0102] (1) The CGT is shared between the bound HARQ processes;

[0103] In this embodiment, the bound HARQ processes share a CGT timer, which starts based on the earliest HARQ transmission. When the CGT times out, it is determined that the MAC PDU transmission is correct, and all bound HARQ processes corresponding to the CGT timer are released to an idle state (i.e., a state that can be used for new MAC PDU transmissions). The initial value of the shared CGT timer is configured separately from the initial value of the CGT timer for non-MD transmissions, or it is determined based on the initial value of the CGT timer of one of the CG configurations belonging to the same first configuration. For example, the initial value of the CGT timer of the largest or smallest CG configuration belonging to the first configuration can be determined as the initial value of the shared CGT timer.

[0104] (2) The bound HARQ processes correspond to different CGTs. If any CGT times out, the terminal stops other CGTs.

[0105] In this embodiment, the bound HARQ processes start CGT timers according to their respective CG configurations and HARQ transmissions; when any of the CGT timers expires, the CGT timers corresponding to other bound HARQ processes are stopped, which also means that all bound HARQ processes used for the current MAC PDU repetitive transmission are released to the idle state.

[0106] In one possible implementation, for the above-described first configuration of autonomous transmission, when a MAC PDU for an MD transmission has been generated, but one or more of the corresponding bound pre-configured uplink transmission licenses are determined to be of low priority and cannot be transmitted, the method further includes:

[0107] (1) If one or more CGs in the bound CG set are of low priority, the terminal cancels or stops the transmission of other CGs in the bound CG set.

[0108] In this embodiment, to prevent the network device from merging received signals belonging to different MAC PDUs during reception, the UE should cancel / stop using uplink transmissions of other pre-configured uplink transmission licenses that are not determined to be of low priority in the corresponding bound pre-configured uplink transmission license set. When autonomousTransmission is enabled, the UE can actively perform MD transmission of the MAC PDU in subsequent bound uplink transmission licenses.

[0109] (2) If one or more CGs in the bound CG set are of low priority, and the transmission of one or more CGs includes a target demodulation reference signal (DMRS) or a target orthogonal cover code (OCC), the terminal maintains the transmission of other CGs in the bound CG set; wherein the target DMRS or target OCC is different from the DMRS or OCC corresponding to the non-MD transmission.

[0110] In this embodiment of the application, the network device can configure an identification method for MD transmission and non-MD transmission, including configuring different DMRS or OCC for MD transmission and non-MD transmission. When the terminal sends data, it can carry the corresponding DMRS or OCC to indicate whether the current transmission is MD transmission or non-MD transmission. When the network device receives data, it determines whether the transmission on a pre-configured uplink transmission license is MD transmission or non-MD transmission based on the matched DMRS or OCC.

[0111] When one or more preconfigured uplink transport licenses in a bound preconfigured uplink transport license set are determined to be low priority and transmission is stopped or canceled, the corresponding MAC PDU can still use other preconfigured uplink transport licenses in the bound preconfigured uplink transport license set to transmit.

[0112] Optionally, as long as at least one copy of a MAC PDU has been sent out over the air interface, other untransmitted or incompletely transmitted copies will no longer be actively transmitted.

[0113] Optionally, when none of the copies have been transferred or have been fully transferred, the uplink transfer should be performed using a subsequent pre-configured set of binding uplink transfer licenses.

[0114] Optionally, the network device can pre-configure whether the UE can transmit based on the method in (2) by using an indication parameter.

[0115] In one possible implementation, regarding the activation and deactivation operations, the method further includes:

[0116] (1) When the CG is activated based on the RNTI corresponding to the MD transmission, the terminal obtains the RNTI corresponding to the MD transmission from the network device and determines that the activated CG is used for MD transmission based on the RNTI corresponding to the MD transmission; if the pre-configured uplink transmission license is not activated based on the RNTI corresponding to the MD transmission, the activated uplink transmission license cannot be used for MD transmission.

[0117] (2) The terminal obtains the PDCCH from the network device. The PDCCH includes an indication for activating the CG. The terminal determines the activated CG for MD transmission based on the indication.

[0118] (3) The terminal obtains MAC CE or RRC signaling from the network device. The MAC CE or RRC signaling includes an indication for activating the CG. The terminal determines the activated CG for MD transmission based on the indication.

[0119] See Figure 4 This application provides an MD transmission device, including:

[0120] The first determining module 401 is used to determine a set of bound CGs based on a first configuration obtained from the network device. The set of bound CGs includes multiple CGs that are bound to each other and are used for MD transmission of the same MAC PDU on different carriers.

[0121] Transmission module 402 is used to transmit the same MAC PDU on different carriers according to the bound CG set.

[0122] In one possible implementation, the first configuration includes one or more of the following:

[0123] MD configuration sequence number;

[0124] CG configuration list;

[0125] HARQ process configuration for MD transfer;

[0126] CGT initial value configuration for MD transmission;

[0127] RNTI corresponding to MD transmission;

[0128] A list of carriers or cells used for MD transmission.

[0129] In one possible implementation, the first determining module is further configured to:

[0130] The set of bound CGs is determined based on the binding relationship between HARQ processes configured with CGs on different carriers.

[0131] In one possible implementation, the HARQ process configuration for MD transmission includes the starting HARQ process identifier ID on different carriers;

[0132] The first determining module is further configured to:

[0133] Based on the starting HARQ process ID on the different carriers, the starting HARQ processes on the different carriers are bound together, and then the i-th HARQ process used for MD transmission on the different carriers is bound together in sequence, where i is a positive integer;

[0134] The set of bound CGs is determined based on the HARQ processes that have binding relationships on the different carriers.

[0135] In one possible implementation, the first configuration further includes: a list of bound HARQ processes;

[0136] The first determining module is further configured to:

[0137] The bound CG set is determined based on the bound HARQ process list.

[0138] In one possible implementation, each HARQ process of the CG configuration in the CG configuration list corresponds to a different MD configuration sequence number;

[0139] The first determining module is further configured to:

[0140] The bound HARQ process is determined based on the MD configuration sequence number;

[0141] The bound CG set is determined based on the bound HARQ process.

[0142] In one possible implementation, the first configuration further includes: a periodic time-domain window configuration;

[0143] The first determining module is further configured to:

[0144] The binding CG set is determined based on the binding relationship of HARQ processes on different carriers within the time-domain window.

[0145] In one possible implementation, the first configuration further includes: the sequence number of the CG;

[0146] The first determining module is further configured to:

[0147] The set of bound CGs is determined based on the binding relationship between the sequence numbers of CGs located on different carriers;

[0148] In one possible implementation, the CGT is shared between bound HARQ processes;

[0149] or,

[0150] Each bound HARQ process corresponds to a different CGT. If any CGT times out, the other CGTs will be stopped.

[0151] In one possible implementation, the device further includes:

[0152] The first processing module is configured to cancel or stop the transmission of other CGs in the bound CG set if one or more CGs in the bound CG set are of low priority.

[0153] In one possible implementation, the device further includes:

[0154] The second processing module is used to maintain the transmission of other CGs in the bound CG set when one or more CGs in the bound CG set are of low priority and the transmission of one or more CGs includes a target demodulation reference signal DMRS or a target orthogonal coverage code OCC.

[0155] The target DMRS or target OCC is different from the DMRS or OCC corresponding to non-MD transmission.

[0156] In one possible implementation, the device further includes:

[0157] The second determining module is used for:

[0158] Obtain the RNTI corresponding to the MD transmission from the network device, and determine the activated CG for MD transmission based on the RNTI corresponding to the MD transmission;

[0159] or,

[0160] A PDCCH is obtained from the network device, the PDCCH including a first indication for activating the CG, and the activated CG is determined to be used for MD transmission based on the first indication;

[0161] or,

[0162] Obtain MAC CE or RRC signaling from the network device, wherein the MAC CE or RRC signaling includes a second indication for activating the CG, and determine, based on the second indication, that the activated CG is used for MD transmission.

[0163] In this embodiment, the terminal determines the binding relationship between pre-configured transmission licenses for MD transmission of the same MACPDU on different carriers according to the first configuration on the network side, thereby determining the binding pre-configured transmission license set. By binding the pre-configured transmission license set, the terminal ensures that the same data is transmitted on different carriers, thereby realizing MD transmission based on pre-configured transmission licenses.

[0164] Figure 5 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0165] The terminal 500 includes, but is not limited to, components such as: radio frequency unit 501, network module 502, audio output unit 503, input unit 504, sensor 505, display unit 506, user input unit 507, interface unit 508, memory 509, and processor 510.

[0166] Those skilled in the art will understand that the terminal 500 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 510 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 5 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.

[0167] It should be understood that, in this embodiment, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042. The GPU 5041 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 506 may include a display panel 5061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 507 includes a touch panel 5061 and other input devices 5072. The touch panel 5061 is also called a touch screen. The touch panel 5061 may include a touch detection device and a touch controller. Other input devices 5072 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.

[0168] In this embodiment, the radio frequency unit 501 receives downlink data from the network-side device and processes it for the processor 510; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0169] The memory 509 can be used to store software programs or instructions and various data. The memory 509 may primarily include a program or instruction storage area and a data storage area. The program or instruction 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 509 may include high-speed random access memory and non-volatile memory, which 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. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

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

[0171] The processor 510 is used in the first determining module to determine a set of bound CGs based on a first configuration obtained from the network device. The set of bound CGs includes multiple CGs that are bound to each other and are used for MD transmission of the same MAC PDU on different carriers.

[0172] The transmission module is used to transmit the same MAC PDU on different carriers according to the bound CG set.

[0173] Optionally, the first configuration includes one or more of the following:

[0174] MD configuration sequence number;

[0175] CG configuration list;

[0176] HARQ process configuration for MD transfer;

[0177] CGT initial value configuration for MD transmission;

[0178] RNTI corresponding to MD transmission;

[0179] A list of carriers or cells used for MD transmission.

[0180] Optionally, the processor 510 is further configured to:

[0181] The set of bound CGs is determined based on the binding relationship between HARQ processes configured with CGs on different carriers.

[0182] Optionally, the HARQ process configuration for MD transmission includes the starting HARQ process identifier ID on different carriers;

[0183] The processor 510 is further configured to:

[0184] Based on the starting HARQ process ID on the different carriers, the starting HARQ processes on the different carriers are bound together, and then the i-th HARQ process used for MD transmission on the different carriers is bound together in sequence, where i is a positive integer;

[0185] The set of bound CGs is determined based on the HARQ processes that have binding relationships on the different carriers.

[0186] Optionally, the first configuration may also include: a list of bound HARQ processes;

[0187] The processor 510 is further configured to:

[0188] The bound CG set is determined based on the bound HARQ process list.

[0189] Optionally, each HARQ process in the CG configuration list corresponds to a different MD configuration sequence number;

[0190] The processor 510 is further configured to:

[0191] The bound HARQ process is determined based on the MD configuration sequence number;

[0192] The bound CG set is determined based on the bound HARQ process.

[0193] Optionally, the first configuration further includes: a periodic time-domain window configuration;

[0194] The processor 510 is further configured to:

[0195] The binding CG set is determined based on the binding relationship of HARQ processes on different carriers within the time-domain window.

[0196] Optionally, the first configuration further includes: the sequence number of the CG;

[0197] The processor 510 is further configured to:

[0198] The set of bound CGs is determined based on the binding relationship between the sequence numbers of CGs located on different carriers;

[0199] Optionally, the CGT is shared between bound HARQ processes;

[0200] or,

[0201] Each bound HARQ process corresponds to a different CGT. If any CGT times out, the other CGTs will be stopped.

[0202] Optionally, the processor 510 is further configured to:

[0203] If one or more CGs in the bound CG set have low priority, cancel or stop the transmission of other CGs in the bound CG set.

[0204] Optionally, the processor 510 is further configured to:

[0205] If one or more CGs in the bound CG set are of low priority, and the transmission of one or more CGs includes the target demodulation reference signal DMRS or the target orthogonal coverage code OCC, the transmission of other CGs in the bound CG set is maintained.

[0206] The target DMRS or target OCC is different from the DMRS or OCC corresponding to non-MD transmission.

[0207] Optionally, the processor 510 is further configured to:

[0208] Obtain the RNTI corresponding to the MD transmission from the network device, and determine the activated CG for MD transmission based on the RNTI corresponding to the MD transmission;

[0209] or,

[0210] A PDCCH is obtained from the network device, the PDCCH including a first indication for activating the CG, and the activated CG is determined to be used for MD transmission based on the first indication;

[0211] or,

[0212] Obtain MAC CE or RRC signaling from the network device, wherein the MAC CE or RRC signaling includes a second indication for activating the CG, and determine, based on the second indication, that the activated CG is used for MD transmission.

[0213] In this embodiment, the terminal determines the binding relationship between pre-configured transmission licenses for MD transmission of the same MACPDU on different carriers according to the first configuration on the network side, thereby determining the binding pre-configured transmission license set. By binding the pre-configured transmission license set, the terminal ensures that the same data is transmitted on different carriers, thereby realizing MD transmission based on pre-configured transmission licenses.

[0214] This application also provides a program product, which is stored in a non-volatile storage medium and executed by at least one processor to implement the following: Figure 2 The steps of the processing method described above.

[0215] This application embodiment also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the above-described functionality. Figure 2 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0216] The processor mentioned above is the processor in the terminal 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.

[0217] This application embodiment also provides a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run network-side device programs or instructions to achieve the above-mentioned... Figure 2 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0218] 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.

[0219] 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.

[0220] Through 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 software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0221] 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 forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for repeating Media Access Control (MD) transmission, characterized in that, include: The terminal determines a pre-configured transmission license (CG) set to be bound based on a first configuration obtained from the network device. The bound CG set includes multiple CGs that are bound to each other and are used for MD transmission of the same Media Access Control Protocol Data Unit (MAC PDU) on different carriers. The terminal transmits the same MAC PDU on different carriers using the corresponding DMRS or OCC via MD transmission according to the bound CG set. The first configuration includes one or more of the following: MD configuration sequence number; Pre-configured license timer CGT initial value configuration for MD transmission; The temporary radio identifier (RNTI) corresponding to MD transmission; A list of carriers or cells used for MD transmission.

2. The method according to claim 1, characterized in that, The first configuration further includes one or more of the following: CG configuration list; Hybrid Automatic Repeat Request (HARQ) process configuration for MD transmission.

3. The method according to claim 2, characterized in that, The terminal determines the bound CG set based on a first configuration obtained from the network device, including: The terminal determines the set of bound CGs based on the binding relationship of HARQ processes configured in CGs on different carriers.

4. The method according to claim 3, characterized in that, The HARQ process configuration for MD transmission includes the starting HARQ process identifier ID on different carriers; The terminal determines the set of bound CGs based on the binding relationship of HARQ processes configured in CGs on different carriers, including: The terminal binds the starting HARQ process on the different carriers according to the starting HARQ process ID on the different carriers, and then binds the i-th HARQ process used for MD transmission on the different carriers in sequence, where i is a positive integer; The terminal determines the set of bound CGs based on the HARQ processes that have a binding relationship on different carriers.

5. The method according to claim 3, characterized in that, The first configuration also includes: a list of bound HARQ processes; The terminal determines the set of bound CGs based on the binding relationship of HARQ processes configured in CGs on different carriers, including: The terminal determines the bound CG set based on the bound HARQ process list.

6. The method according to claim 1, characterized in that, Each HARQ process in the CG configuration list corresponds to a different MD configuration sequence number; The terminal determines the set of bound CGs based on the binding relationship of HARQ processes configured in CGs on different carriers, including: The terminal determines the bound HARQ process based on the MD configuration sequence number; The terminal determines the bound CG set based on the bound HARQ process.

7. The method according to claim 2, characterized in that, The first configuration also includes: periodic time-domain window configuration; The terminal determines the bound CG set based on a first configuration obtained from the network device, including: The terminal determines the binding CG set based on the binding relationship of HARQ processes of different carriers within the time domain window.

8. The method according to claim 1, characterized in that, The first configuration also includes: the CG serial number; The terminal determines the bound CG set based on a first configuration obtained from the network device, including: The terminal determines the set of bound CGs based on the binding relationship between the sequence numbers of CGs on different carriers.

9. The method according to any one of claims 3 to 8, characterized in that, The CGT is shared between bound HARQ processes; or, The bound HARQ processes each correspond to a different CGT. If any CGT times out, the terminal stops the other CGTs.

10. The method according to any one of claims 1 to 8, further characterized in that, The method further includes: If one or more CGs in the bound CG set have low priority, the terminal cancels or stops the transmission of other CGs in the bound CG set.

11. The method according to any one of claims 1 to 8, further characterized in that the method further comprises: If one or more CGs in the bound CG set are of low priority, and the transmission of one or more CGs includes a target demodulation reference signal DMRS or a target orthogonal coverage code OCC, the terminal maintains the transmission of other CGs in the bound CG set. The target DMRS or target OCC is different from the DMRS or OCC corresponding to non-MD transmission.

12. The method according to any one of claims 1 to 8, further characterized in that, The method further includes: The terminal obtains the RNTI corresponding to the MD transmission from the network device, and determines the activated CG for MD transmission based on the RNTI corresponding to the MD transmission. or, The terminal obtains a PDCCH from the network device. The PDCCH includes a first indication for activating the CG. The terminal determines, based on the first indication, that the activated CG is used for MD transmission. or, The terminal obtains MAC CE or RRC signaling from the network device. The MAC CE or RRC signaling includes a second indication for activating the CG. The terminal determines the activated CG for MD transmission based on the second indication.

13. An MD device, characterized in that, include: The first determining module is used to determine a set of bound CGs based on a first configuration obtained from the network device. The set of bound CGs includes multiple CGs that are bound to each other and are used for MD transmission of the same MAC PDU on different carriers. The transmission module is used to transmit the same MAC PDU on different carriers using the corresponding DMRS or OCC via MD transmission according to the bound CG set. The first configuration includes one or more of the following: MD configuration sequence number; Pre-configured license timer CGT initial value configuration for MD transmission; The temporary radio identifier (RNTI) corresponding to MD transmission; A list of carriers or cells used for MD transmission.

14. The apparatus according to claim 13, characterized in that, The first configuration further includes one or more of the following: CG configuration list; HARQ process configuration for MD transfer.

15. The apparatus according to claim 14, characterized in that, The first determining module is further configured to: The set of bound CGs is determined based on the binding relationship between HARQ processes configured with CGs on different carriers.

16. The apparatus according to claim 15, characterized in that, The HARQ process configuration for MD transmission includes the starting HARQ process identifier ID on different carriers; The first determining module is further configured to: Based on the starting HARQ process ID on the different carriers, the starting HARQ processes on the different carriers are bound together, and then the i-th HARQ process used for MD transmission on the different carriers is bound together in sequence, where i is a positive integer; The set of bound CGs is determined based on the HARQ processes that have binding relationships on the different carriers.

17. The apparatus according to claim 15, characterized in that, The first configuration also includes: a list of bound HARQ processes; The first determining module is further configured to: The bound CG set is determined based on the bound HARQ process list.

18. The apparatus according to claim 13, characterized in that, Each HARQ process in the CG configuration list corresponds to a different MD configuration sequence number; The first determining module is further configured to: The bound HARQ process is determined based on the MD configuration sequence number; The bound CG set is determined based on the bound HARQ process.

19. The apparatus according to claim 14, characterized in that, The first configuration also includes: periodic time-domain window configuration; The first determining module is further configured to: The binding CG set is determined based on the binding relationship of HARQ processes on different carriers within the time-domain window.

20. The apparatus according to claim 13, characterized in that, The first configuration also includes: the CG serial number; The first determining module is further configured to: The set of bound CGs is determined based on the binding relationship between the sequence numbers of CGs located on different carriers.

21. The apparatus according to any one of claims 15 to 20, characterized in that, The CGT is shared between bound HARQ processes; or, Each bound HARQ process corresponds to a different CGT. If any CGT times out, the other CGTs will be stopped.

22. The apparatus according to any one of claims 13 to 20, further characterized in that, The device further includes: The first processing module is configured to cancel or stop the transmission of other CGs in the bound CG set if one or more CGs in the bound CG set are of low priority.

23. The apparatus according to any one of claims 13 to 20, further characterized in that, The device further includes: The second processing module is used to maintain the transmission of other CGs in the bound CG set when one or more CGs in the bound CG set are of low priority and the transmission of one or more CGs includes a target demodulation reference signal DMRS or a target orthogonal coverage code OCC. The target DMRS or target OCC is different from the DMRS or OCC corresponding to non-MD transmission.

24. The apparatus according to any one of claims 13 to 20, further characterized in that, The device further includes: The second determining module is used for: Obtain the RNTI corresponding to the MD transmission from the network device, and determine the activated CG for MD transmission based on the RNTI corresponding to the MD transmission; or, A PDCCH is obtained from the network device, the PDCCH including a first indication for activating the CG, and the activated CG is determined to be used for MD transmission based on the first indication; or, Obtain MAC CE or RRC signaling from the network device, wherein the MAC CE or RRC signaling includes a second indication for activating the CG, and determine, based on the second indication, that the activated CG is used for MD transmission.

25. A terminal, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 12.

26. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 12.

Images