Uplink data transmission device and method, and uplink data reception device and method

Abstract

The embodiment of the invention provides an uplink data sending device and method and an uplink data receiving device and method. The method comprises the following steps: determining an HARQ (Hybrid Automatic Repeat Request) process identifier associated with one CG (Channel Gateway) in at least two CG (Channel Gateway) transmission opportunities (CGs) in a configuration authorization (CG) configuration period, the HARQ process identifier being different from HARQ process identifiers associated with other CG (Channel Gateway) in the at least two CG (Channel Gateway) transmission opportunities except the CG transmission opportunities (CGs) transmission opportunities (CGs) transmission opportunities (CGs) transmission opportunities (CGs) transmission opportunities (CGs) transmission opportunities (CGs); and according to the determined HARQ process identifier associated with the one CG case, sending uplink data on the one CG case. The HARQ process identifier associated with the one CG case comprises the HARQ process identifier associated with the one CG case, the HARQ process identifier associated with the one CG case. Therefore, the situation that the data is delayed to be sent and does not meet the quality of service (QoS) requirement is avoided; and the situation that the data cannot be retransmitted and is lost is avoided.

Description

Uplink data sending and receiving device and method Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is working on the standardization of 5th Generation Mobile Communication Technology (5G), examining key issues, solutions, and conclusions for supporting advanced media services such as High Data Rate Low Latency (HDRLL), extended reality (XR), and tactile / multimodal communication.

[0003] For example, in the research on XR business, XR is a general term for different types of reality, and the different application areas of XR include entertainment, medical care, education, etc.

[0004] Virtual Reality (VR) is a rendered version of a published visual and audio scene. The rendering aims to simulate the visual and auditory sensory stimulation of the real world as naturally as possible, as the observer or user moves within the limitations defined by the application. Augmented Reality (AR) provides users with additional information or artificially generated items or content overlaid on their current environment. Mixed Reality (MR) is an advanced form of AR in which some virtual elements are inserted into the physical scene to provide the illusion that these elements are part of the real scene.

[0005] Extended reality (XR) refers to all real and virtual environments and human-computer interactions generated by computer technology and wearable devices, including representative forms such as AR, MR, VR and hybrid cross-fields.

[0006] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of this application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because these solutions are explained in the background technology part of this application.

[0007] Summary of the Invention

[0008] During the 3GPP standardization process, Configured Grant (CG) was added for uplink support. Using CG, the gNB can allocate uplink resources to the user equipment (UE). CG is a good feature for periodic services and services with strict latency requirements. Most services generated by XR applications meet these two criteria.

[0009] The inventors discovered that because XR services have more complex service patterns, this new service pattern requires enhancements to traditional CG configuration and processes. Therefore, when there are more than one CG transmission opportunity within a configuration grant (CG) configuration cycle, how to accurately transmit uplink data or ensure uplink data transmission latency is a problem that needs to be solved.

[0010] To address at least one of the above problems, embodiments of the present application provide an apparatus and method for sending and receiving uplink data.

[0011] According to one aspect of an embodiment of the present application, a method for sending uplink data is provided, which is applied to a terminal device, wherein the method includes:

[0012] Determine a HARQ process identifier associated with a CG occasion in at least two CG transmission occasions in a period configured by a configuration grant (CG), wherein the HARQ process identifier is different from the HARQ process identifiers associated with other CG occasions in the at least two CG occasions except the one CG occasion;

[0013] According to the determined HARQ process identifier associated with the CG occasion, uplink data is sent on the CG occasion.

[0014] According to another aspect of an embodiment of the present application, a method for receiving uplink data is provided, which is applied to a network device, wherein the method includes:

[0015] Receive uplink data sent on a CG occasion,

[0016] The HARQ process identifier of the uplink data is the HARQ process identifier associated with the one CG occasion in at least two CG occasions in a CG configured period, wherein the HARQ process identifier associated with the one CG occasion is different from the HARQ process identifiers associated with other CG occasions in the at least two CG occasions except the one CG occasion.

[0017] According to another aspect of an embodiment of the present application, there is provided an uplink data sending apparatus, configured in a terminal device, the uplink data sending apparatus comprising:

[0018] a determining unit, which determines a hybrid automatic repeat request (HARQ) process identifier associated with one of at least two configured grant sending opportunities (CG occasions) in a period configured by a configured grant (CG), wherein the hybrid automatic repeat request (HARQ) process identifier is different from hybrid automatic repeat request (HARQ) process identifiers associated with other configured grant sending opportunities (CG occasions) in the at least two configured grant sending opportunities (CG occasions) except the one configured grant sending opportunity (CG occasion);

[0019] A sending unit, which sends uplink data on a configured grant sending opportunity (CG occasion) according to a determined hybrid automatic repeat request (HARQ) process identifier associated with the configured grant sending opportunity (CG occasion).

[0020] According to another aspect of an embodiment of the present application, an uplink data receiving apparatus is provided, which is applied to a network device, wherein the uplink data receiving apparatus includes:

[0021] a receiving unit, which receives uplink data sent on a configuration grant sending opportunity (CG occasion),

[0022] The hybrid automatic repeat request (HARQ) process identifier of the uplink data is a hybrid automatic repeat request (HARQ) process identifier associated with one of the at least two configured grant sending opportunities (CG occasions) in a period configured by a configured grant (CG), wherein the hybrid automatic repeat request (HARQ) process identifier associated with the one configured grant sending opportunity (CG occasion) is different from the hybrid automatic repeat request (HARQ) process identifiers associated with other configured grant sending opportunities (CG occasions) in the at least two configured grant sending opportunities (CG occasions) except the one configured grant sending opportunity (CG occasion).

[0023] According to another aspect of an embodiment of the present application, a communication system is provided, comprising:

[0024] A terminal device, which determines a hybrid automatic repeat request (HARQ) process identifier associated with one of at least two configuration grant sending opportunities (CG occasions) in a period configured by a configuration grant (CG), wherein the hybrid automatic repeat request (HARQ) process identifier is different from the hybrid automatic repeat request (HARQ) process identifiers associated with other configuration grant sending opportunities (CG occasions) in the at least two configuration grant sending opportunities (CG occasions) except the one configuration grant sending opportunity (CG occasion);

[0025] The terminal device sends uplink data on the one configured grant to send opportunity (CG occasion) according to the determined hybrid automatic repeat request (HARQ) process identifier associated with the one configured grant to send opportunity (CG occasion);

[0026] A network device receives the uplink data.

[0027] One of the beneficial effects of the embodiments of the present application is that: the terminal device determines the HARQ process identifier associated with one CG occasion in at least two CG transmission opportunities (occasion) in a period configured by a configuration grant (CG), wherein the HARQ process identifier is different from the HARQ process identifiers associated with other CG occasions in the at least two CG occasions except the one CG occasion; and sends uplink data on the one CG occasion according to the determined HARQ process identifier associated with the one CG occasion. Thus, when there are more than one CG transmission opportunities (occasion) in a period configured by a configuration grant (CG), each CG transmission opportunity (occasion) can use a different HARQ process identifier (using a different HARQ process) to send data, which can avoid the XR service data from being delayed in sending and not meeting the quality of service (QoS) requirements of the XR service, and can avoid the situation where the XR service data is lost due to the inability to be retransmitted.

[0028] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0029] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0030] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0032] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application;

[0033] FIG2 is an example diagram of the technical problem to be solved by the embodiment of the present application;

[0034] FIG3 is another example diagram of the technical problem to be solved by the embodiments of the present application;

[0035] FIG4 is another example diagram of the technical problem to be solved by the embodiments of the present application;

[0036] FIG5 is a schematic diagram of a method for transmitting uplink data according to an embodiment of the present application;

[0037] FIG6 is an example diagram of determining a HARQ process identifier according to an embodiment of the present application;

[0038] FIG7 is another example diagram of determining a HARQ process identifier according to an embodiment of the present application;

[0039] FIG8 is another example diagram of determining a HARQ process identifier according to an embodiment of the present application;

[0040] FIG9 is another example diagram of determining a HARQ process identifier according to an embodiment of the present application;

[0041] FIG10 is a schematic diagram of a data sending method according to an embodiment of the present application;

[0042] FIG11 is a schematic diagram of an uplink data transmitting device according to an embodiment of the present application;

[0043] FIG12 is a schematic diagram of an uplink data receiving device according to an embodiment of the present application;

[0044] FIG13 is a schematic diagram of the structure of a network device according to an embodiment of the present application;

[0045] FIG14 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0047] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0048] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0049] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0050] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0051] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0052] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0053] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0054] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0055] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0056] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0057] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0058] The 3GPP standard defines two types of configuration grants, also known as configured uplink grants, which are not restricted in this application:

[0059] CG Type 1: Radio Resource Control (RRC) directly provides a configured uplink grant (including period);

[0060] CG Type 2: Radio Resource Control (RRC) defines the period of the configured uplink grant, and the Physical Downlink Control Channel (PDCCH) (or Downlink Control Information) addressed to the configured scheduling (CS)-RNTI can notify and activate the configured uplink grant, or deactivate it; that is, the PDCCH (or DCI) addressed to the CS-RNTI indicates that the uplink grant can be implicitly reused according to the period defined by RRC until it is deactivated.

[0061] CG is a good feature for periodic and latency-critical services. Most services generated by XR applications meet these two criteria. For example, CG's resource size is fixed, while XR's service packet size is also relatively fixed.

[0062] Figure 1 is a schematic diagram of an application scenario of an embodiment of the present application; as shown in Figure 1, some XR services have a more complex service pattern than the CG design. For example, a video streaming service may include a periodic Protocol Data Unit burst (PDU burst) or a PDU set (PDU set) instead of a single PDU. This new service pattern may require enhancements to traditional CG configurations and processes. For example, an XR burst size in Figure 1 may contain more than one data packet, and if only one configured authorized resource is used, these more than one data packet cannot be sent out; in addition, in the XR frame period, there is an arrival interval between different PDU data packets (called the PDU intra-arrival interval), as shown in Figure 1, and the configuration of CG resources with this arrival interval is not currently supported.

[0063] Therefore, the 3GPP standard agrees to support more than one configured grant transmission opportunity (CG PUSCH transmission occasion or CG transmission occasion or CG occasion or uplink transmission occasion, etc.) in a CG configured period (or referred to as a CG period). In this case, more than one data packet in an XR burst or PDU set can be transmitted on more than one configured grant transmission opportunity in a CG configured period.

[0064] The inventors found that when more than one CG PUSCH transmission occasion is supported in a single CG configuration period, assuming that different data can be sent in different CG PUSCH transmission occasions, how to determine the HARQ process identifier used by the data in a CG PUSCH transmission occasion needs to be solved.

[0065] If the HARQ process identifier is calculated using the record in the following Table 1 in the existing standard, some problems may arise.

[0066] Table 1:

[0067] The relevant parameters in Table 1 above will be introduced in detail later.

[0068] FIG2 is an example diagram of the technical problem to be solved by the embodiment of the present application. As shown in FIG2, if the method for determining the HARQ process identifier (HARQ process ID) in the current standard is still used, then more than one CG PUSCH transmission occasion in a CG configuration period will use the same HARQ process ID. As shown in FIG2, a CG configuration period (assuming 10 symbols) includes 3 CG PUSCH transmission occasions (the figure shows the 1st, 3rd and 5th symbols in the period of each CG configuration), and the HARQ process ID used by each CG PUSCH transmission occasion in the figure is shown in FIG2.

[0069] FIG3 is an example diagram of the technical problem to be solved by the embodiments of the present application. As shown in FIG3, if the value of the configured Grant Timer is greater than the interval of the CG PUSCH transmission occasion, then in a CG configured period, when the second CG PUSCH transmission occasion arrives, the configured Grant Timer is still running, that is, the configured Grant Timer corresponding to the same HARQ process (for example, process 0) has not timed out. Therefore, the resources (grant) of the second CG PUSCH transmission occasion using the same HARQ process cannot be used for data transmission, resulting in delayed transmission of XR service data and possible failure to meet the QoS requirements of the XR service.

[0070] FIG4 is an example diagram of the technical problem to be solved by the embodiments of the present application. As shown in FIG4, if the value of the configured Grant Timer (configuredGrantTimer) is not greater than the CG PUSCH transmission occasion, then in a CG configured period, the second CG PUSCH transmission occasion uses the same HARQ process as the first CG PUSCH transmission occasion to send data. That is, the HARQ process will be used by the new data (e.g., Data 2). Therefore, the data corresponding to the previous (first) CG PUSCH transmission occasion (Data 1, Data 1) cannot be retransmitted. If the network device has not correctly received Data 1, data loss may occur.

[0071] Therefore, when there is more than one CG transmission opportunity (occasion) in a configuration grant (CG) configuration cycle, how to determine the HARQ process identifier associated with a CG transmission opportunity (occasion) to avoid delayed transmission or loss of service data is a problem that needs to be solved.

[0072] To address at least one of the above problems, embodiments of the present application provide an apparatus and method for sending and receiving uplink data.

[0073] Embodiments of the first aspect

[0074] An embodiment of the present application provides a method for sending uplink data.

[0075] FIG5 is a schematic diagram of a method for sending uplink data according to an embodiment of the present application. As shown in FIG5 , the method is applied in a terminal device, and the method includes:

[0076] 501, determining a HARQ process identifier associated with a CG occasion in at least two CG transmission occasions in a period configured by a configuration grant (CG), wherein the HARQ process identifier is different from HARQ process identifiers associated with other CG occasions in the at least two CG occasions except the one CG occasion;

[0077] 502. Send uplink data on the CG occasion according to the determined HARQ process identifier associated with the CG occasion.

[0078] Therefore, when there is more than one CG sending opportunity (occasion) in a configuration grant (CG) configuration cycle, each CG sending opportunity (occasion) can use a different HARQ process identifier (use a different HARQ process) to send data, which can avoid the data being delayed and not meeting the Quality of Service (QoS) requirements, and can avoid the data being lost due to the inability to be retransmitted.

[0079] It is worth noting that FIG5 above is merely a schematic illustration of an embodiment of the present application, using a terminal device as an example, but the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, other operations may be added or some operations may be reduced, and the objects of the aforementioned operations may be adjusted. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG5 above.

[0080] For example, the situation where a configuration grant (CG) configuration period includes at least two CG transmission opportunities (occasion) can be referred to the examples of Figures 2 to 3, and no repetitive explanation is given here; for example, the expression "CG transmission opportunity (occasion)" recorded in this application can be replaced by "CG PUSCH transmission opportunity (occasion)", "CG Occasion", "CG PUSCH Occasion", "CG PUSCH transmission occasion", etc.; the expression "configuration grant (CG) configuration period" recorded in this application can be replaced by "CG period", "CG period / periodicity", "CG Type 1 period", "CG Type 2 period", etc.; the expression "CG" recorded in this application can also be replaced by "configured uplink grant", and this application does not impose any restrictions on this.

[0081] For example, a CG configuration or a CG occasion recorded later in this application uses (or "corresponds to" or "is configured with") x HARQ processes, which can be understood as that a transmission on a CG occasion uses one of the x HARQ processes, and this application does not impose any restrictions on this.

[0082] In some embodiments, the CG configuration includes a first CG configuration and / or a second CG configuration, wherein the first CG configuration is a configuration that does not include a second offset value (harq-ProcID-Offset2) and a second timer (cg-RetransmissionTimer); and the second CG configuration is a configuration that includes a second offset value (harq-ProcID-Offset2).

[0083] For example, referring to Table 1, the existing standard defines a method for calculating the HARQ process identifier corresponding to two types of grants (two CG configurations). The first CG configuration is: the uplink grant (configured uplink grant) is not configured with the HARQ process identifier offset (harq-ProcID-Offset2) and is not configured with the "configured grant retransmission timer (cg-RetransmissionTimer)" configuration; the second CG configuration is: the uplink grant (configured uplink grant) is configured with the HARQ process identifier offset (harq-ProcID-Offset2) configuration.

[0084] For example, the first CG configuration is used for a single CG configuration (CG configuration); the second CG configuration is used for more than one CG configuration, and the HARQ process identifier corresponding to the configuration authorization in different CG configurations is distinguished by the HARQ process identifier offset (harq-ProcID-Offset2). In addition, for details such as "configuration authorization retransmission timer (cg-RetransmissionTimer)" and "HARQ process identifier offset (harq-ProcID-Offset2)", please refer to the records in the existing standards, and this application does not impose any restrictions on this.

[0085] For example, there are a total of 8 HARQ processes, and the value range of the HARQ process identifier is an integer from 0 to 7. In the first CG configuration case, if the CG is configured with nrofHARQ-Processes of 4, then the CG is configured with a HARQ process identifier of "0-3"; in the second CG configuration case, assuming that the values ​​of the "HARQ process identifier offset (harq-ProcID-Offset2)" configured for the two CG configurations (ConfiguredGrantConfig) are "0" and "4" respectively, and the nrofHARQ-Processes configured for the two CG configurations are both 4, then the CG with the "HARQ process identifier offset (harq-ProcID-Offset2)" configured to "0" is configured with a HARQ process identifier of "0-3", and the CG with the "HARQ process identifier offset (harq-ProcID-Offset2)" configured to "4" is configured with a HARQ process identifier of "4-7". Optionally, the number of HARQ processes can be other numbers, such as 4 HARQ processes or 16 HARQ processes or 32 HARQ processes, etc., and the corresponding HARQ process identifiers are 0 to 3 or 0 to 15 or 0 to 31, etc., and this application does not limit this.

[0086] In some embodiments, determining the HARQ process identifier associated with one CG occasion in at least two CG occasions in a CG configured period includes: determining the HARQ process identifier associated with the CG occasion based on the first parameter and the second parameter; and / or determining the HARQ process identifier associated with the CG occasion based on the first offset value or the third offset value; and / or determining the HARQ process identifier associated with the CG occasion based on the third parameter; and / or determining the first HARQ process identifier associated with the CG occasion in the time domain in a CG configured period; and / or selecting the HARQ process identifier associated with a CG occasion in a CG configured period.

[0087] In some embodiments, the terminal device further receives indication information sent by the network device, wherein the indication information indicates: the second parameter, and / or the first offset value or the third offset value, and / or the third parameter. In some embodiments, the indication information is configured via a Radio Resource Control (RRC) message or carried via a Physical Downlink Control Channel (PDCCH) (or Downlink Control Information).

[0088] The following provides examples for respectively determining the HARQ process identifier associated with one CG occasion in at least two CG occasions in a period of a CG configuration.

[0089] The following example illustrates how to determine the HARQ process identifier associated with a CG occasion according to the first parameter and the second parameter.

[0090] In some embodiments, the first parameter is the index of a CG occasion in a CG configured cycle, for example, the CG occasion is the i-th CG occasion in a CG cycle, where i is an integer starting from 0; the second parameter is the number (k) of CG occasions in a CG configured cycle.

[0091] In some embodiments, determining a HARQ process identifier associated with a CG occasion according to the first parameter and the second parameter includes: determining the HARQ process identifier associated with the CG occasion according to the first parameter, the second parameter, and a first formula, wherein the first formula includes:

[0092] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]*K+i] modulo nrofHARQ-Processes; or

[0093] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]*K+i]modulo nrofHARQ-Processes+harq-ProcID-Offset2,

[0094] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a CG occasion symbol index in a CG configuration cycle; periodicity represents a period of a CG configuration, nrofHARQ-Processes represents the number of HARQ processes that can be used in a CG configuration; harq-ProcID-Offset2 represents the second offset value; i represents the first parameter, and K represents the second parameter.

[0095] For example, for the first CG configuration (CG is not configured with harq-ProcID-Offset2 and is not configured with cg-RetransmissionTimer), for the i-th CG PUSCH transmission occasion, the HARQ Process ID associated with the first symbol of the uplink transmission (UL transmission) is obtained according to the following equation of the first formula:

[0096] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]*K+i]modulo nrofHARQ-Processes;

[0097] For the second CG configuration (CG configured with harq-ProcID-Offset2), for the i-th CG PUSCH transmission occasion, the HARQ Process ID associated with the first symbol of the uplink transmission (UL transmission) is obtained according to the following equation of the first formula:

[0098] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]*K+i]modulo nrofHARQ-Processes+harq-ProcID-Offset2.

[0099] For example, floor() represents a rounding down operation, modulo() represents a modulo operation; CURRENT_symbol represents a CG PUSCH transmission occasion or the first CG PUSCH transmission occasion symbol index in a CG configuration period, which can be calculated by the following formula:

[0100] CURRENT_symbol=(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+(slot number in the frame)×numberOfSymbolsPerSlot+(symbol number in the slot));

[0101] Among them, "numberOfSlotsPerFrame and numberOfSymbolsPerSlot" refer to the number of consecutive time slots (slots) in each wireless frame (frame) and the number of consecutive symbols (symbol) in each slot; "slot number in the frame" represents the time slot number of a CG PUSCH transmission occasion or the first CG PUSCH transmission occasion in the period of CG configuration, and "symbol number in the slot" represents the symbol number of the first symbol in the slot of a CG PUSCH transmission occasion or the first CG PUSCH transmission occasion in the period of CG configuration.

[0102] For example, i can be an integer starting from 0, K is the number of CG PUSCH transmission occasions in a CG configured period, which can be notified to the UE by the network, for example, through RRC message configuration or through PDCCH (for example, PDCCH that activates CG).

[0103] Figure 6 is an example diagram of determining a HARQ process identifier according to an embodiment of the present application. As shown in Figure 6 , for a first CG configuration, when there are three CG PUSCH transmission occasions in a CG configuration period and the CG configuration uses four HARQ processes, the process of determining a HARQ process identifier for each "CG PUSCH transmission occasion" is shown.

[0104] For example, for the first CG configuration, "periodicity" is 10ms, K=3, and "nrofHARQ-Processes"=4. For the first CG cycle, assuming that the value of "CURRENT_symbol" is "0", and "i" starts from "0" for the 0th CG PUSCH transmission occasion of the first CG cycle, the "HARQ process identifier = 0" is calculated according to the first formula; for the second CG cycle, assuming that the value of "CURRENT_symbol" is 11, for the 0th CG PUSCH transmission occasion of the second CG cycle, the "HARQ process identifier = 3" is calculated according to the first formula.

[0105] For the second CG configuration, for example, for the CG in which "harq-ProcID-Offset2" is configured as "0", the HARQ process identifier used for the CG occasion of the CG is the same as the determined HARQ process identifier shown in Figure 6. For example, for the CG in which "harq-ProcID-Offset2" is configured as "4", the HARQ process identifier used for the CG occasion of the CG is the determined HARQ process identifier shown in Figure 6 plus 4, which are not listed again here.

[0106] Therefore, different CG PUSCH transmission occasions in a CG configuration period use different HARQ processes to send data, thereby avoiding delayed data transmission or data loss due to inability to retransmit.

[0107] The following example illustrates how to determine the HARQ process identifier associated with a CG occasion according to the first offset value or the third offset value.

[0108] In some embodiments, determining a HARQ process identifier associated with a CG occasion based on a first offset value or a third offset value includes: setting a first offset value or a third offset value for a CG occasion in a CG configured period; and / or setting the number of available HARQ processes for the CG occasion in a CG configured period.

[0109] In some embodiments, determining a HARQ process identifier associated with a CG occasion based on a first offset value or a third offset value also includes: determining the first offset value or the third offset value based on an index or order of the CG occasion in a CG configured period and / or the number of HARQ processes that can be used for the CG occasion in a CG configured period.

[0110] In some embodiments, the first offset value and / or the third offset value represents an offset value of a HARQ process identifier associated with a CG occasion.

[0111] The following example illustrates determining a HARQ process identifier associated with a CG occasion according to the first offset value:

[0112] In some embodiments, determining a HARQ process identifier associated with a CG occasion according to the first offset value includes: determining the HARQ process identifier associated with the CG occasion according to the first offset value and a second formula, wherein the second formula includes:

[0113] HARQ process identifier = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3; or

[0114] HARQ process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3 + harq-ProcID - Offset2,

[0115] Among them, floor represents the rounding down operation, modulo represents the modulo operation; CURRENT_symbol represents the symbol index of a CG occasion in a CG configuration cycle; periodicity represents the period of a CG configuration, nrofHARQ-Processes represents the number of HARQ processes that can be used or configured for a CG occasion in a CG configuration cycle; harq-ProcID-Offset2 represents the second offset value; offset3 represents the offset value of the HARQ process identifier of a CG occasion in a CG configuration cycle, that is, the first offset value.

[0116] For example, for the first CG configuration (CG is not configured with harq-ProcID-Offset2 and is not configured with cg-RetransmissionTimer), for a CG PUSCH transmission occasion, the HARQ Process ID associated with the first symbol of the uplink transmission (UL transmission) is obtained according to the following equation of the second formula:

[0117] HARQ process identifier = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3;

[0118] For the second CG configuration (CG is configured with harq-ProcID-Offset2), for one CG PUSCH transmission occasion, the HARQ Process ID associated with the first symbol of the uplink transmission (UL transmission) is obtained according to the following equation of the second formula:

[0119] HARQ process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3 + harq-ProcID - Offset2,

[0120] For example, the first offset offset3 is the offset value of the HARQ process identifier corresponding to a CG PUSCH transmission occasion in a CG configured period, and nrofHARQ-Processes is the number of HARQ processes that can be used or configured for a CG PUSCH transmission occasion in a CG configured period.

[0121] For example, the index of the CG occasion is i, and "i" starts from 0 or "1", and this application does not impose any restrictions on this. For example, the correspondence between offset3, nrofHARQ-Processes and i can be shown in the following table.

[0122] Table 2

[0123] For example, Table 2 is only an exemplary configuration, and the value of nrofHARQ-Processes may also be the same for different CG PUSCH transmission occasions in a period of a CG configuration.

[0124] For another example, the correspondence between offset3, nrofHARQ-Processes and CG occasion is set in the order of CG occasion (ie, the CG occasion index does not appear explicitly), as shown in the following table.

[0125] Table 2A

[0126] For example, the first offset value (offset3) and / or "nrofHARQ-Processes" can be network configured, for example, by carrying the above configuration information through RRC reconfiguration, RRC resume, RRC setup and / or RRC re-establishment messages; for example, in at least one CG configuration (Configured grant configuration) configured by the network, at least one CG PUSCH transmission occasion in a CG cycle can be configured, and each CG PUSCH transmission occasion in a CG cycle can be configured. In addition, when the network configures more than one CG configuration (ConfiguredGrantConfig), the offset3 and / or "nrofHARQ-Processes" configured for the i-th CG occasion in one CG configuration can be the same as or different from the offset3 and / or "nrofHARQ-Processes" configured for the i-th CG occasion in another CG configuration, and this application does not impose any restrictions on this.

[0127] For another example, the first offset value (offset3) and / or "nrofHARQ-Processes" may be predefined, and this application does not impose any restrictions on this. For example, in the second CG configuration, the correspondence between offset3, nrofHARQ-Processes, harq-ProcID-Offset2, and the CG occasion index and the CG configuration index may be as shown in Table 2B or 2C below.

[0128] Table 2B

[0129] In Table 2B, the offset3 configured for CG occasion index 0 of CG configuration index 0 is the same as the offset3 configured for CG occasion index 0 of CG configuration index 1, and nrofHARQ-Processes is also the same; the offset3 configured for CG occasion index 1 of CG configuration index 0 is the same as the offset3 configured for CG occasion index 1 of CG configuration index 1, and nrofHARQ-Processes is also the same; the offset3 configured for CG occasion index 2 of CG configuration index 0 is the same as the offset3 configured for CG occasion index 2 of CG configuration index 1, and nrofHARQ-Processes is also the same; the second offset value of CG configuration index 0 is configured to "0", and the second offset value of CG configuration index 0 is configured to "9".

[0130] Table 2C

[0131] In Table 2B, for different CG configurations (for example, CG configuration index 0 and CG configuration index 1), the offset3 and nrofHARQ-Processes configured for CG occasion index 0 are the same; the offset3 configured for CG occasion index 1 is the same, and the nrofHARQ-Processes are different; the offset3 configured for CG occasion index 2 is different, and the nrofHARQ-Processes are also different; the second offset value of CG configuration index 0 is configured to "0", and the second offset value of CG configuration index 0 is configured to "9".

[0132] Similar to the first formula above, floor() in the second formula represents a rounding-down operation, and modulo() represents a modulo operation; CURRENT_symbol represents the symbol index of a CG PUSCH transmission occasion or the first CG PUSCH transmission occasion in a CG configuration period, which can be calculated by the following formula:

[0133] CURRENT_symbol=(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+(slot number in the frame)×numberOfSymbolsPerSlot+(symbol number in the slot));

[0134] Among them, "numberOfSlotsPerFrame and numberOfSymbolsPerSlot" refer to the number of consecutive time slots (slots) in each wireless frame (frame) and the number of consecutive symbols (symbol) in each slot; "slot number in the frame" represents the time slot number of a CG PUSCH transmission occasion or the first CG PUSCH transmission occasion in the period of CG configuration, and "symbol number in the slot" represents the symbol number of the first symbol in the slot of a CG PUSCH transmission occasion or the first CG PUSCH transmission occasion in the period of CG configuration.

[0135] Figure 7 is another example diagram of determining the HARQ process identifier in an embodiment of the present application. As shown in Figure 7, there are 3 CG PUSCH transmission occasions in a CG configuration period. In the CG configuration period, it can be known from Table 2 or Table 2A that in each CG configuration period, the first CG PUSCH transmission occasion (for example, CG occasion index 0) uses or is configured with 2 HARQ processes, offset3=0, and the corresponding "HARQ process identifier=0" or "HARQ process identifier=1" can be obtained according to the second formula, which appears cyclically in different CG configuration periods. For example, the first CG PUSCH transmission occasion uses or is configured with 2 HARQ processes, including using one of the two HARQ processes to send data on the first CG PUSCH transmission occasion. For example, the first CG PUSCH transmission in the first CG period shown in Figure 7 uses the HARQ process with "HARQ process identifier=0"; the second CG PUSCH transmission Occasionally, 3 HARQ processes are used or configured, offset3=2. According to the second formula, the corresponding "HARQ process identifier=2" to "HARQ process identifier=4" can be obtained, which appear cyclically in different CG configuration cycles; the third CG PUSCH transmission occasion uses or is configured with 4 HARQ processes, offset3 is 5. According to the second formula, the corresponding "HARQ process identifier=5" to "HARQ process identifier=8" can be obtained, which appear cyclically in different CG configuration cycles.

[0136] For the second CG configuration, for example, in combination with Table 2B, for the CG in which "harq-ProcID-Offset2" is configured as "0", the HARQ process identifier used for the CG occasion of the CG is the same as the determined HARQ process identifier shown in Figure 7. For example, for the CG in which "harq-ProcID-Offset2" is configured as "9", the HARQ process identifier used for the CG occasion of the CG is the determined HARQ process identifier shown in Figure 7 plus 9, which are not listed again here.

[0137] For the second CG configuration, for example, in combination with Table 2C, for the CG in which "harq-ProcID-Offset2" is configured as "0", the HARQ process identifier used by the CG occasion of the CG is the same as the determined HARQ process identifier shown in Figure 7, for example, for the CG in which "harq-ProcID-Offset2" is configured as "9", the HARQ process identifiers used by the CG occasion index 0 of the CG are 9 and 10, the HARQ process identifiers used by the CG occasion index 1 are 11 and 12, and the HARQ process identifier used by the CG occasion index 2 is 13.

[0138] For example, the table in the corresponding standard is as follows:

[0139] Table 3

[0140] Or as shown in Form 3A:

[0141] Table 3A

[0142] Therefore, different CG PUSCH transmission occasions in a CG configuration period use different HARQ processes to send data, thereby avoiding delayed data transmission or data loss due to inability to retransmit.

[0143] The following is an example of determining a HARQ process identifier associated with a CG occasion according to the third offset value:

[0144] In some embodiments, determining a HARQ process identifier associated with a CG occasion according to the third offset value includes: determining the HARQ process identifier associated with the CG occasion according to the third offset value and a third formula, wherein the third formula includes:

[0145] HARQ process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset4,

[0146] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a CG occasion symbol index in a CG configuration cycle; periodicity represents a CG configuration cycle, nrofHARQ-Processes represents the number of HARQ processes that can be used or configured in the i-th CG occasion in a CG configuration cycle; offset4 represents the third offset value.

[0147] For example, the third offset (offset4) = the first offset (offset3) + the second offset (harq-ProcID-Offset2); "i" starts at "0" or "1":

[0148] Table 4

[0149] For example, for CG occasion index 0 of CG configuration index 0, offset4 is configured to 0, nrofHARQ-Processes is 2, so the HARQ process identifiers that CG occasion index 0 of CG configuration index 0 can use or be configured are 0 and 1; for CG occasion index 1 of CG configuration index 0, offset4 is configured to 2, nrofHARQ-Processes is 3, so the HARQ process identifiers that CG occasion index 1 of CG configuration index 0 can use or be configured are 2, 3 and 4; for CG occasion index 2 of CG configuration index 0, offset4 is configured to 5, nrofHARQ-Processes is 4, so the HARQ process identifiers that CG occasion index 2 of CG configuration index 0 can use or be configured are 4, 6, 7 and 8; for CG occasion index 0 of CG configuration index 1, offset4 is configured to 9, nrofHARQ-Processes is 3, so the HARQ process identifiers that CG occasion index 0 of CG configuration index 1 can use or be configured are 9, 10 and 11; occasion index 1, offset4 is configured to 12, nrofHARQ-Processes is 2, so the CG occasion index 0 of CG configuration index 1 can use or be configured with HARQ process identifiers 12 and 13; for the CG occasion index 2 of CG configuration index 1, offset4 is configured to 14, nrofHARQ-Processes is 1, so the CG occasion index 2 of CG configuration index 1 can use or be configured with HARQ process identifier 14.

[0150] In some embodiments, an offset 4 and / or nrofHARQ-Processes are configured for each CG PUSCH transmission occasion corresponding to each CG configuration in more than one CG configuration, and / or, an offset 4 and / or nrofHARQ-Processes are configured for each CG PUSCH transmission occasion corresponding to at least one CG configuration, and / or, an offset 4 and / or nrofHARQ-Processes are configured for each CG PUSCH transmission occasion corresponding to a CG configuration, and / or, an offset 4 and / or nrofHARQ-Processes are configured for at least one CG PUSCH transmission occasion corresponding to a CG configuration; this application does not impose any restrictions on this. As a result, different CG PUSCH transmission occasions in a CG configuration period use different HARQ processes for data transmission, thereby avoiding delayed data transmission or data loss due to inability to retransmit.

[0151] The following example illustrates how to determine the HARQ process identifier associated with the CG occasion according to the third parameter.

[0152] In some embodiments, the third parameter (Kn) is the number of CG occasions configured or used in the nth CG cycle, wherein the third parameter (Kn) is counted from the first CG occasion in a CG cycle.

[0153] In some embodiments, determining the HARQ process identifier associated with the one CG occasion according to the third parameter includes: determining the HARQ process identifier associated with the one CG occasion according to the sum of at least two third parameters and a fourth formula, wherein the fourth formula includes:

[0154] HARQ process identifier = [sum(K1, K2, ... KN) + i] modulo nrofHARQ-Processes; or

[0155] HARQ process identifier == [sum(K1, K2, ... KN) + i] modulo nrofHARQ-Processes + harq-ProcID-Offset2,

[0156] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a CG occasion symbol index in a CG configuration cycle; nrofHARQ-Processes represents the number of HARQ processes that can be used in the i-th CG occasion in a CG configuration cycle; sum(K1, K2, ... KN) represents the sum of at least two third parameters.

[0157] For example, for the first CG configuration (CG is not configured with harq-ProcID-Offset2 and is not configured with cg-RetransmissionTimer), for the i-th CG PUSCH transmission occasion, the HARQ Process ID associated with the first symbol of the uplink transmission (UL transmission) is obtained according to the following equation of the fourth formula:

[0158] HARQ process ID = [sum(K1, K2, ... KN) + i] modulo nrofHARQ-Processes;

[0159] For the second CG configuration (CG is configured with harq-ProcID-Offset2), for the i-th CG PUSCH transmission occasion, the HARQ Process ID associated with the first symbol of the uplink transmission (UL transmission) is obtained according to the following equation of the fourth formula:

[0160] HARQ process ID == [sum(K1, K2, ...KN)+i]modulo nrofHARQ-Processes+harq-ProcID-Offset2.

[0161] In some embodiments, a HARQ process identifier associated with a CG occasion is determined based on the third parameter when at least one of the following conditions is met: the number of CG occasions configured in a CG configuration period is different; or an unused CG occasion in a CG configuration period is indicated to the network side.

[0162] For example, the above K1 to KN are configured by the network device, and their corresponding values ​​can be the same or different; and the terminal device indicates to the network side the number of unused CG occasions in a CG configuration cycle, and then the network device determines the specific values ​​of the above K1 to KN.

[0163] For example, for the first CG configuration, counting starts from the first CG PUSCH transmission occasion (or CG or CG resource) of a CG configuration. For example, for Type 1CG, counting can be started from the first CG configured by RRC. For Type 2CG, counting can be started from the first CG after the PDCCH of the CG configuration is activated; Kn (1<=n<=N) represents the number of CG PUSCH transmission occasions configured or used in the nth CG cycle.

[0164] FIG8 is another example diagram of determining the HARQ process identifier according to an embodiment of the present application.

[0165] As shown in FIG8 , it shows the HARQ process identifier determined for each “CG PUSCH transmission occasion” when there are 3 CG PUSCH transmission occasions in one CG configuration period and the CG configuration uses 4 HARQ processes for the first CG configuration.

[0166] For example, for the first CG configuration, the period is 10ms, "nrofHARQ-Processes" = 4, for the first CG period to the third CG period K1 = K2 = K3 = 3, "i" starts from 0 or 1, for the first CG PUSCH transmission occasion of the first CG period, sum(K1) = 3, i = 0 or 1, nrofHARQ-Processes = 4, according to the fourth formula, it is calculated that "HARQ process identifier = 0"; for the first CG PUSCH transmission occasion of the second CG period, sum(K1, K2) = 6, i = 0 or 1, nrofHARQ-Processes = 4, according to the fourth formula, it is calculated that "HARQ process identifier = 3".

[0167] For the second CG configuration, for example, for the CG in which "harq-ProcID-Offset2" is configured as "0", the HARQ process identifier used for the CG occasion of the CG is the same as the determined HARQ process identifier shown in Figure 8. For example, for the CG in which "harq-ProcID-Offset2" is configured as "4", the HARQ process identifier used for the CG occasion of the CG is the determined HARQ process identifier shown in Figure 8 plus 4, which are not listed again here.

[0168] Therefore, different CG PUSCH transmission occasions in a CG configuration period use different HARQ processes to send data, thereby avoiding delayed data transmission or data loss due to inability to retransmit.

[0169] The following examples illustrate determining the HARQ process identifier associated with the first CG occasion in the time domain in a CG configured period, and / or selecting the HARQ process identifier associated with a CG occasion in a CG configured period.

[0170] In some embodiments, determining the HARQ process identifier associated with the first CG occasion in the time domain in a period of a CG configuration includes: determining the HARQ process identifier associated with the first CG occasion in the time domain in a period of a CG configuration according to a fifth formula, wherein the fifth formula includes:

[0171] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]] modulo nrofHARQ-Processes; or

[0172] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]] modulo nrofHARQ-Processes+harq-ProcID-Offset2,

[0173] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a CG occasion symbol index in a CG configuration cycle; periodicity represents a CG configuration cycle, nrofHARQ-Processes represents the number of HARQ processes that can be used in the first CG occasion in a CG configuration cycle; harq-ProcID-Offset2 represents the second offset value.

[0174] For example, the specific meanings of the parameters in the fifth formula can be found in the examples in the first formula and will not be repeated here.

[0175] In some embodiments, after determining the first CG occasion associated HARQ process identifier in the time domain in a CG configured period according to the fifth formula, the terminal device can select a CG occasion associated HARQ process identifier in a CG configured period.

[0176] In some implementations, the selected HARQ process identifier satisfies at least one of the following conditions:

[0177] Unused HARQ process identifier;

[0178] a HARQ process identifier different from the HARQ process identifier calculated by the fifth formula;

[0179] A HARQ process identifier that is different from the HARQ process identifier already used for the CG occasion in the period configured by the one CG;

[0180] The HARQ process identifier for which the corresponding first timer (configuredGrantTimer) has timed out;

[0181] A HARQ process identifier that can be used for the one CG configuration.

[0182] In some implementations, the terminal device sends the selected HARQ process identifier to the network device, for example, by carrying the selected HARQ process identifier via UCI and sending the selected HARQ process identifier to the network device via a PUCCH or PUSCH channel.

[0183] FIG9 is another example diagram of determining a HARQ process identifier according to an embodiment of the present application. As shown in FIG9 , for a first CG configuration, when there are three CG PUSCH transmission occasions in a CG configuration period and the CG configuration uses four HARQ processes, the process of determining a HARQ process identifier for each "CG PUSCH transmission occasion" is shown.

[0184] For example, for the first CG configuration, "periodicity" is 10ms, K=3, and "nrofHARQ-Processes"=4; for the first CG PUSCH transmission occasion of the first CG period, assuming that the value of "CURRENT_symbol" is 0, "HARQ process identifier = 0" is calculated according to the fifth formula; for the second CG period, assuming that the value of "CURRENT_symbol" is 11, for the first CG PUSCH transmission occasion of the second CG period, "HARQ process identifier = 1" is calculated according to the fifth formula; for the third CG period, assuming that the value of "CURRENT_symbol" is 21, for the first CG PUSCH transmission occasion of the third CG period, "HARQ process identifier = 2" is calculated according to the fifth formula; for example, within a CG period, the second CG PUSCH transmission occasion can select a HARQ process identifier different from the HARQ process identifier corresponding to the first CG PUSCH transmission occasion, for example, select "HARQ process identifier = 2", and similarly, the third CG PUSCH transmission occasion can select a HARQ process identifier that is different from the HARQ process identifier corresponding to the first CG PUSCH transmission occasion and the second CG PUSCH transmission occasion. The HARQ process identifier corresponding to the occasion is different, for example, "HARQ process identifier = 3" is selected; in addition, similar selection is made for the HARQ process identifier of the CG PUSCH transmission occasion in the second CG cycle and the third CG cycle, and no repeated explanation is given here.

[0185] For the second CG configuration, for example, for a CG in which "harq-ProcID-Offset2" is configured as "0", the HARQ process identifier used for the CG occasion of the CG is the same as the HARQ process identifier determined as shown in FIG9. For example, for a CG in which "harq-ProcID-Offset2" is configured as "4", the HARQ process identifier used for the CG occasion of the CG is the HARQ process identifier determined as shown in FIG7 plus 9, which are not repeated here. As a result, different CG PUSCH transmission occasions in a CG configuration period use different HARQ processes for data transmission, thereby avoiding delayed data transmission or data loss due to inability to retransmit.

[0186] In some embodiments, for example, “determining the HARQ process identifier associated with the first CG occasion in the time domain in a period of a CG configuration” and “selecting a HARQ process identifier associated with a CG occasion in a period of a CG configuration” can be used in conjunction, such as the example shown in FIG. 9 above;

[0187] In some embodiments, the terminal device selects a HARQ process identifier associated with a CG occasion in a period of a CG configuration.

[0188] In some implementations, the selected HARQ process identifier satisfies at least one of the following conditions:

[0189] Unused HARQ process identifier;

[0190] a HARQ process identifier different from the HARQ process identifier calculated by the fifth formula;

[0191] A HARQ process identifier that is different from the HARQ process identifier already used for the CG occasion in the period configured by the one CG;

[0192] The HARQ process identifier for which the corresponding first timer (configuredGrantTimer) has timed out;

[0193] A HARQ process identifier that can be used for the one CG configuration.

[0194] In some implementations, the terminal device sends the selected HARQ process identifier to the network device, for example, by carrying the selected HARQ process identifier via UCI and sending the selected HARQ process identifier to the network device via a PUCCH or PUSCH channel.

[0195] For example, after selecting "the HARQ process identifier associated with the first CG occasion in a CG configured period", select "the HARQ process identifier associated with other CG occasions in a CG configured period" based on the above "conditions"; for another example, after selecting "the HARQ process identifier associated with any CG occasion in a CG configured period", select "the HARQ process identifier associated with other CG occasions in a CG configured period" based on the above "conditions". This application does not list them one by one.

[0196] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0197] It can be seen from the above embodiments that when there is more than one CG sending opportunity (occasion) in a configuration grant (CG) configuration cycle, each CG sending opportunity (occasion) can use a different HARQ process identifier (using a different HARQ process) to send data, which can avoid the data being delayed and not meeting the quality of service (QoS) requirements, and can avoid the data being lost due to the inability to be retransmitted.

[0198] Embodiments of the second aspect

[0199] The embodiment of the present application provides an uplink data receiving method, which is applied to a network device. The embodiment of the present application can be combined with the embodiment of the first aspect, or can be implemented independently. The contents that are the same as those of the embodiment of the first aspect are not repeated here.

[0200] FIG10 is a schematic diagram of a data sending method according to an embodiment of the present application. As shown in FIG10 , the method includes:

[0201] 1001, receiving uplink data sent on a CG occasion;

[0202] The HARQ process identifier of the uplink data is the HARQ process identifier associated with one of the at least two CG occasions in a CG configured period, wherein the HARQ process identifier associated with the one CG occasion is different from the HARQ process identifiers associated with other CG occasions in the at least two CG occasions except the one CG occasion.

[0203] Therefore, when there is more than one CG sending opportunity (occasion) in a configuration grant (CG) configuration cycle, each CG sending opportunity (occasion) can use a different HARQ process identifier (use a different HARQ process) to send data, which can avoid the data being delayed and not meeting the Quality of Service (QoS) requirements, and can avoid the data being lost due to the inability to be retransmitted.

[0204] It is worth noting that FIG10 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG10 above.

[0205] In some embodiments, the method further comprises:

[0206] 1002: Send indication information, where the indication information indicates: the second parameter, and / or the first offset value or the third offset value, and / or the third parameter.

[0207] In some implementations, the indication information is configured via an RRC message or carried via a PDCCH.

[0208] In some embodiments, the second parameter is the number (k) of CG occasions in a CG configured cycle; the first offset or the third offset is set for the CG occasion in a CG configured cycle; the third parameter (Kn) is the number of CG occasions configured or used in the nth CG cycle, wherein the third parameter (Kn) is counted from the first CG occasion in a CG cycle.

[0209] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0210] It can be seen from the above embodiments that when there is more than one CG sending opportunity (occasion) in a configuration grant (CG) configuration cycle, each CG sending opportunity (occasion) can use a different HARQ process identifier (using a different HARQ process) to send data, which can avoid the data being delayed and not meeting the quality of service (QoS) requirements, and can avoid the data being lost due to the inability to be retransmitted.

[0211] Embodiments of the third aspect

[0212] The embodiment of the present application provides an uplink data transmission device configured in a terminal device. The device can be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. In addition, the same contents as the embodiment of the first aspect are not repeated here.

[0213] FIG11 is a schematic diagram of an uplink data transmitting apparatus according to an embodiment of the present application. As shown in FIG11 , the uplink data transmitting apparatus 1100 includes:

[0214] a determining unit 1101, which determines a hybrid automatic repeat request (HARQ) process identifier associated with one of at least two configured grant sending opportunities (CG occasions) in a period configured by a configured grant (CG), wherein the hybrid automatic repeat request (HARQ) process identifier is different from hybrid automatic repeat request (HARQ) process identifiers associated with other configured grant sending opportunities (CG occasions) in the at least two configured grant sending opportunities (CG occasions) except the one configured grant sending opportunity (CG occasion);

[0215] The sending unit 1102 sends uplink data on the configured grant sending opportunity (CG occasion) according to the determined hybrid automatic repeat request (HARQ) process identifier associated with the configured grant sending opportunity (CG occasion).

[0216] Therefore, when there is more than one CG sending opportunity (occasion) in a configuration grant (CG) configuration cycle, each CG sending opportunity (occasion) can use a different HARQ process identifier (use a different HARQ process) to send data, which can avoid the data being delayed and not meeting the Quality of Service (QoS) requirements, and can avoid the data being lost due to the inability to be retransmitted.

[0217] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0218] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The uplink data sending device 1100 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0219] In addition, for the sake of simplicity, FIG11 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0220] In some embodiments, the determination unit 1101: determines the hybrid automatic repeat request (HARQ) process identifier associated with the configured grant sending opportunity (CG occasion) based on the first parameter and the second parameter; and / or determines the hybrid automatic repeat request (HARQ) process identifier associated with the configured grant sending opportunity (CG occasion) based on the first offset value or the third offset value; and / or determines the hybrid automatic repeat request (HARQ) process identifier associated with the configured grant sending opportunity (CG occasion) based on the third parameter; and / or determines the hybrid automatic repeat request (HARQ) process identifier associated with the first configured grant sending opportunity (CG occasion) in the time domain in a period configured by a configured grant (CG); and / or selects the hybrid automatic repeat request (HARQ) process identifier associated with the configured grant sending opportunity (CG occasion) in a period configured by a configured grant (CG).

[0221] In some embodiments, the uplink data sending device 1100 further includes: a receiving unit 1103, which receives indication information sent by the network device, wherein the indication information indicates: the second parameter, and / or the first offset value or the third offset value, and / or the third parameter.

[0222] In some implementations, the indication information is configured via a radio resource control (RRC) message or carried via a physical downlink control channel (PDCCH).

[0223] In some embodiments, the first parameter is an index of a configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG), where i is an integer starting from 0; the second parameter is the number (k) of configuration grant sending opportunities (CG occasion) in a period configured by a configuration grant (CG).

[0224] In some implementations, the determining unit 1101 determines a hybrid automatic repeat request (HARQ) process identifier associated with the configured grant to send opportunity (CG occasion) based on the first parameter, the second parameter, and a first formula, wherein the first formula includes:

[0225] Hybrid Automatic Repeat Request (HARQ) process identifier = [[floor(CURRENT_symbol / periodicity)]*K+i]modulo nrofHARQ-Processes; or

[0226] Hybrid Automatic Repeat Request (HARQ) process identifier = [[floor(CURRENT_symbol / periodicity)]*K+i]modulo nrofHARQ-Processes+harq-ProcID-Offset2,

[0227] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a configuration grant sending opportunity (CG occasion) symbol index in a configuration grant (CG) configuration period; periodicity represents a configuration grant (CG) configuration period, nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used for a configuration grant (CG) configuration; harq-ProcID-Offset2 represents a second offset value; i represents the first parameter, and K represents the second parameter.

[0228] In some embodiments, the determination unit 1101 sets a first offset value or a third offset value for a configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG); and / or sets the number of hybrid automatic repeat request (HARQ) processes that can be used for a configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG).

[0229] In some embodiments, the determination unit 1101 determines the first offset value or the third offset value based on the index or order of the one configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG) and / or the number of hybrid automatic repeat request (HARQ) processes that can be used for the one configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG).

[0230] In some implementations, the determining unit 1101 determines a hybrid automatic repeat request (HARQ) process identifier associated with the configured grant to send opportunity (CG occasion) based on the first offset value and a second formula, wherein the second formula includes:

[0231] Hybrid Automatic Repeat Request (HARQ) process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3; or

[0232] Hybrid Automatic Repeat Request (HARQ) process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3 + harq-ProcID-Offset2,

[0233] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a symbol index of a configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration period; periodicity represents a period of configuration grant (CG) configuration, nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used or configured in a configuration grant sending opportunity (CG occasion) in a period of configuration grant (CG) configuration; harq-ProcID-Offset2 represents a second offset value; offset3 represents the first offset value, which represents the offset value of the hybrid automatic repeat request (HARQ) process identifier of a configuration grant sending opportunity (CG occasion) in a period of configuration grant (CG) configuration.

[0234] In some implementations, the determining unit 1101 determines a hybrid automatic repeat request (HARQ) process identifier associated with the one configured grant to send opportunity (CG occasion) according to the third offset value and a third formula, wherein the third formula includes:

[0235] Hybrid Automatic Repeat Request (HARQ) process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset4,

[0236] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol is a symbol index of a configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration period; periodicity represents a configuration grant (CG) configuration period, nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used or configured in the i-th configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration period; offset4 represents the third offset value.

[0237] In some embodiments, the third parameter is the number of configuration grant sending opportunities (CG occasions) configured or used in the nth configuration grant (CG) cycle, wherein the third parameter starts counting from the first configuration grant sending opportunity (CG occasion) in a configuration grant (CG) cycle.

[0238] In some implementations, the determining unit 1101 determines a hybrid automatic repeat request (HARQ) process identifier associated with the one configured grant to send opportunity (CG occasion) based on a sum of at least two third parameters and a fourth formula, wherein the fourth formula includes:

[0239] Hybrid Automatic Repeat Request (HARQ) process identifier = [sum(K1, K2, ... KN) + i] modulo nrofHARQ-Processes; or

[0240] Hybrid Automatic Repeat Request (HARQ) process identifier = [sum(K1, K2, ... KN) + i] modulo nrofHARQ-Processes + harq-ProcID-Offset2,

[0241] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a configuration grant sending opportunity (CG occasion) symbol index in a configuration grant (CG) configuration period; nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used for the i-th configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration period; sum(K1, K2, ... KN) represents the sum of at least two third parameters.

[0242] In some implementations, the determining unit 1101 determines, based on the third parameter, a hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant send opportunity (CG occasion) when at least one of the following conditions is met:

[0243] The number of configuration grant sending opportunities (CG occasions) configured in a configuration grant (CG) configuration period is different; or

[0244] Indicates to the network side an unused configuration grant sending opportunity (CG occasion) in a configuration period of a configuration grant (CG).

[0245] In some implementations, the determining unit 1101 determines a hybrid automatic repeat request (HARQ) process identifier associated with a first configuration grant transmission opportunity (CG occasion) in a time domain in a period configured by a configuration grant (CG) according to a fifth formula, wherein the fifth formula includes:

[0246] Hybrid Automatic Repeat Request (HARQ) process identifier = [[floor(CURRENT_symbol / periodicity)]] modulo nrofHARQ-Processes; or

[0247] Hybrid Automatic Repeat Request (HARQ) process identifier = [[floor(CURRENT_symbol / periodicity)]] modulo nrofHARQ-Processes+harq-ProcID-Offset2,

[0248] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a configuration grant sending opportunity (CG occasion) symbol index in a configuration grant (CG) configuration period; periodicity represents a configuration grant (CG) configuration period, nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used in the first configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration period; harq-ProcID-Offset2 represents the second offset value.

[0249] In some implementations, the determining unit 1101 selecting a hybrid automatic repeat request (HARQ) process identifier associated with a configuration grant transmission opportunity (CG occasion) in a period configured by a configuration grant (CG) includes: the selected hybrid automatic repeat request (HARQ) process identifier satisfies at least one of the following conditions:

[0250] Unused Hybrid Automatic Repeat Request (HARQ) process identifier;

[0251] a hybrid automatic repeat request (HARQ) process identifier different from the hybrid automatic repeat request (HARQ) process identifier calculated by the fifth formula;

[0252] A hybrid automatic repeat request (HARQ) process identifier that is different from a hybrid automatic repeat request (HARQ) process identifier that has been used for a configuration grant transmission opportunity (CG occasion) in a period configured by the configuration grant (CG);

[0253] The identifier of the Hybrid Automatic Repeat Request (HARQ) process whose corresponding first timer (configuredGrantTimer) has timed out;

[0254] A hybrid automatic repeat request (HARQ) process identifier that can be used for the one configuration grant (CG) configuration.

[0255] In some embodiments, the sending unit 1102 carries the selected hybrid automatic repeat request (HARQ) process identifier through uplink control information (UCI) and sends the selected hybrid automatic repeat request (HARQ) process identifier to the network device through a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

[0256] In some embodiments, the configuration authorization (CG) configuration includes a first configuration authorization (CG) configuration and / or a second configuration authorization (CG) configuration, wherein the first configuration authorization (CG) configuration is a configuration that does not include a second offset value (harq-ProcID-Offset2) and a second timer (cg-RetransmissionTimer); and the second configuration authorization (CG) configuration is a configuration that includes a second offset value (harq-ProcID-Offset2).

[0257] It can be seen from the above embodiments that when there is more than one CG sending opportunity (occasion) in a configuration grant (CG) configuration cycle, each CG sending opportunity (occasion) can use a different HARQ process identifier (using a different HARQ process) to send data, which can avoid the data being delayed and not meeting the quality of service (QoS) requirements, and can avoid the data being lost due to the inability to be retransmitted.

[0258] Embodiments of the fourth aspect

[0259] The present embodiment provides an uplink data receiving device configured in a network device. The device may be, for example, a network device, or one or more components or assemblies configured in the network device. Details common to the first and second aspects of the embodiment are not repeated here.

[0260] FIG12 is a schematic diagram of an uplink data receiving apparatus according to an embodiment of the present application. As shown in FIG12 , the uplink data receiving apparatus 1200 includes:

[0261] The receiving unit 1201 receives uplink data sent on a configuration grant sending opportunity (CG occasion),

[0262] The hybrid automatic repeat request (HARQ) process identifier of the uplink data is a hybrid automatic repeat request (HARQ) process identifier associated with one of the at least two configured authorization sending opportunities (CG occasions) in a period configured by a configuration authorization (CG), wherein the hybrid automatic repeat request (HARQ) process identifier associated with the one configured authorization sending opportunity (CG occasion) is different from the hybrid automatic repeat request (HARQ) process identifiers associated with other configured authorization sending opportunities (CG occasions) in the at least two configured authorization sending opportunities (CG occasions) except the one configured authorization sending opportunity (CG occasion).

[0263] Therefore, when there is more than one CG sending opportunity (occasion) in a configuration grant (CG) configuration cycle, each CG sending opportunity (occasion) can use a different HARQ process identifier (use a different HARQ process) to send data, which can avoid the data being delayed and not meeting the Quality of Service (QoS) requirements, and can avoid the data being lost due to the inability to be retransmitted.

[0264] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0265] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The uplink data receiving apparatus 1200 may also include other components or modules, and for the specific contents of these components or modules, reference may be made to the relevant art.

[0266] In addition, for the sake of simplicity, FIG12 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0267] In some embodiments, the uplink data receiving apparatus 1200 further includes: a sending unit 1202, which sends indication information, wherein the indication information indicates: the second parameter, and / or the first offset value or the third offset value, and / or the third parameter.

[0268] In some implementations, the indication information is configured via an RRC message or carried via a PDCCH.

[0269] In some embodiments, the second parameter is the number (k) of CG occasions in a CG configured cycle; the first offset or the third offset is set for the CG occasion in a CG configured cycle; the third parameter (Kn) is the number of CG occasions configured or used in the nth CG cycle, wherein the third parameter (Kn) starts counting from the first CG occasion in a CG cycle.

[0270] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0271] It can be seen from the above embodiments that when there is more than one CG sending opportunity (occasion) in a configuration grant (CG) configuration cycle, each CG sending opportunity (occasion) can use a different HARQ process identifier (using a different HARQ process) to send data, which can avoid the data being delayed and not meeting the quality of service (QoS) requirements, and can avoid the data being lost due to the inability to be retransmitted.

[0272] Embodiments of the fifth aspect

[0273] An embodiment of the present application also provides a communication system, and the contents that are the same as those in the embodiments of the first to fourth aspects are not repeated here.

[0274] In some embodiments, the communication system may include at least:

[0275] A terminal device, which determines a hybrid automatic repeat request (HARQ) process identifier associated with one of at least two configuration grant sending opportunities (CG occasions) in a period configured by a configuration grant (CG), wherein the hybrid automatic repeat request (HARQ) process identifier is different from the hybrid automatic repeat request (HARQ) process identifiers associated with other configuration grant sending opportunities (CG occasions) in the at least two configuration grant sending opportunities (CG occasions) except the one configuration grant sending opportunity (CG occasion);

[0276] The terminal device sends uplink data on the one configuration grant sending opportunity (CG occasion) according to the determined hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion);

[0277] A network device receives the uplink data.

[0278] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0279] Figure 13 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 13 , network device 1300 may include a processor 1310 (e.g., a central processing unit (CPU)) and a memory 1320. Memory 1320 is coupled to processor 1310. Memory 1320 may store various data and may also store an information processing program 1330, which is executed under the control of processor 1310.

[0280] In addition, as shown in FIG13 , network device 1300 may further include: a transceiver 1340 and an antenna 1350, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that network device 1300 does not necessarily include all the components shown in FIG13 ; in addition, network device 1300 may also include components not shown in FIG13 , and reference may be made to the prior art for details.

[0281] The embodiment of the present application also provides a terminal device, but the present application is not limited thereto and may also be other devices.

[0282] Figure 14 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 14 , terminal device 1400 may include a processor 1410 and a memory 1420. Memory 1420 stores data and programs and is coupled to processor 1410. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0283] For example, the processor 1410 may be configured to execute a program to implement the uplink data sending method as described in the embodiment of the first aspect. For example, the processor 1410 may be configured to perform the following control: determining a HARQ process identifier associated with a CG occasion in at least two CG transmission opportunities (occasion) in a period configured by a configuration grant (CG), wherein the HARQ process identifier is different from the HARQ process identifiers associated with other CG occasions in the at least two CG occasions except the one CG occasion; and sending uplink data on the one CG occasion according to the determined HARQ process identifier associated with the one CG occasion.

[0284] As shown in Figure 14 , the terminal device 1400 may further include: a communication module 1430, an input unit 1440, a display 1450, and a power supply 1460. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1400 does not necessarily include all of the components shown in Figure 14 , and these components are not essential. Furthermore, the terminal device 1400 may also include components not shown in Figure 14 , for which reference may be made to the prior art.

[0285] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program enables the terminal device to execute the uplink data sending method described in the embodiment of the first aspect.

[0286] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the uplink data sending method described in the embodiment of the first aspect.

[0287] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program enables the terminal device to execute the uplink data receiving method described in the embodiment of the second aspect.

[0288] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the uplink data receiving method described in the embodiment of the third aspect.

[0289] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0290] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0291] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and storage medium may be located in an ASIC. The software module may be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if a device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0292] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0293] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0294] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0295] 1. A method for transmitting uplink data, applied to a terminal device, wherein the method comprises:

[0296] Determine a HARQ process identifier associated with a CG occasion in at least two CG transmission occasions in a period configured by a configuration grant (CG), wherein the HARQ process identifier is different from the HARQ process identifiers associated with other CG occasions in the at least two CG occasions except the one CG occasion;

[0297] According to the determined HARQ process identifier associated with the CG occasion, uplink data is sent on the CG occasion.

[0298] 2. The method according to Supplementary Note 1, wherein determining the HARQ process identifier associated with one of the at least two CG occasions in a period of a CG configuration comprises:

[0299] Determine the HARQ process identifier associated with the CG occasion according to the first parameter and the second parameter; and / or

[0300] Determine the HARQ process identifier associated with the one CG occasion according to the first offset value or the third offset value; and / or

[0301] Determine the HARQ process identifier associated with the CG occasion according to the third parameter; and / or

[0302] Determine the HARQ process identifier associated with the first CG occasion in the time domain in a CG configured period; and / or

[0303] Select a HARQ process identifier associated with the CG occasion in a CG configured period.

[0304] 3. The method according to Supplementary Note 2, wherein the method further comprises:

[0305] Receive indication information sent by a network device, wherein the indication information indicates: the second parameter, and / or the first offset value or the third offset value, and / or the third parameter.

[0306] 4. The method according to Supplementary Note 3, wherein the method further comprises:

[0307] The indication information is configured through an RRC message or carried through a PDCCH.

[0308] 5. The method according to Supplementary Note 3, wherein:

[0309] The first parameter is an index of a CG occasion in a period of a CG configuration, where i is an integer starting from 0;

[0310] The second parameter is the number (k) of CG occasions in a cycle of a CG configuration.

[0311] 6. The method according to Note 3 or 5, wherein determining the HARQ process identifier associated with the CG occasion according to the first parameter and the second parameter comprises:

[0312] Determine the HARQ process identifier associated with the CG occasion according to the first parameter, the second parameter and the first formula,

[0313] The first formula includes:

[0314] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]*K+i] modulo nrofHARQ-Processes; or

[0315] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]*K+i]modulo nrofHARQ-Processes+harq-ProcID-Offset2,

[0316] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a CG occasion symbol index in a CG configuration cycle; periodicity represents a period of a CG configuration, nrofHARQ-Processes represents the number of HARQ processes that can be used in a CG configuration; harq-ProcID-Offset2 represents the second offset value; i represents the first parameter, and K represents the second parameter.

[0317] 7. The method according to Note 3, wherein determining the HARQ process identifier associated with the one CG occasion according to the first offset value or the third offset value comprises:

[0318] Setting a first offset value or a third offset value for the one CG occasion in a period of one CG configuration; and / or

[0319] The number of HARQ processes that can be used is set for the CG occasion in a CG configured period.

[0320] 8. The method according to Supplementary Note 7, wherein determining the HARQ process identifier associated with the CG occasion according to the first offset value or the third offset value further comprises:

[0321] The first offset value or the third offset value is determined according to the index or order of the CG occasion in a period of a CG configuration and / or the number of HARQ processes that can be used for the CG occasion in a period of a CG configuration.

[0322] 9. The method according to note 7 or 8, wherein determining the HARQ process identifier associated with the one CG occasion according to the first offset value comprises:

[0323] Determine the HARQ process identifier associated with the CG occasion according to the first offset value and the second formula,

[0324] The second formula includes:

[0325] HARQ process identifier = [floor(CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3; or

[0326] HARQ process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3 + harq-ProcID - Offset2,

[0327] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a CG occasion symbol index in a CG configuration period; periodicity represents a CG configuration period, nrofHARQ-Processes represents the number of HARQ processes that can be used or configured for a CG occasion in a CG configuration period; harq-ProcID-Offset2 represents a second offset value; offset3 represents the first offset value, which represents the offset value of the hybrid automatic repeat request (HARQ) process identifier of a configuration authorization sending opportunity (CG occasion) in a configuration authorization (CG) configuration period.

[0328] 10. The method according to note 7 or 8, wherein determining the HARQ process identifier associated with the one CG occasion according to the third offset value comprises:

[0329] Determine the HARQ process identifier associated with the CG occasion according to the third offset value and the third formula,

[0330] Wherein, the third formula includes:

[0331] HARQ process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset4,

[0332] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a CG occasion symbol index in a CG configuration cycle; periodicity represents a CG configuration cycle, nrofHARQ-Processes represents the number of HARQ processes that can be used or configured in the i-th CG occasion in a CG configuration cycle; offset4 represents the third offset value.

[0333] 11. The method according to Supplementary Note 3, wherein:

[0334] The third parameter (Kn) is the number of CG occasions configured or used in the nth CG cycle, wherein the third parameter (Kn) is counted from the first CG occasion of a CG cycle.

[0335] 12. The method according to note 11, wherein determining the HARQ process identifier associated with the one CG occasion according to the third parameter comprises:

[0336] Determine the HARQ process identifier associated with the one CG occasion according to the sum of at least two third parameters and a fourth formula,

[0337] Wherein, the fourth formula includes:

[0338] HARQ process identifier = [sum(K1, K2, ... KN) + i] modulo nrofHARQ-Processes; or

[0339] HARQ process identifier == [sum(K1, K2, ... KN) + i] modulo nrofHARQ-Processes + harq-ProcID-Offset2,

[0340] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a CG occasion symbol index in a CG configuration cycle; nrofHARQ-Processes represents the number of HARQ processes that can be used in the i-th CG occasion in a CG configuration cycle; sum(K1, K2, ... KN) represents the sum of at least two third parameters.

[0341] 13. The method according to Supplementary Note 11, wherein the HARQ process identifier associated with the one CG occasion is determined according to the third parameter when at least one of the following conditions is met:

[0342] The number of configured CG occasions in a CG configuration cycle is different; or

[0343] Indicates to the network side the unused CG occasions in a CG configured period.

[0344] 14. The method according to Note 3, wherein determining the HARQ process identifier associated with the first CG occasion in the time domain in a period of a CG configuration comprises:

[0345] The HARQ process identifier associated with the first CG occasion in the time domain in a CG configured period is determined according to the fifth formula, wherein,

[0346] The fifth formula includes:

[0347] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]] modulo nrofHARQ-Processes; or

[0348] HARQ process identifier = [[floor(CURRENT_symbol / periodicity)]] modulo nrofHARQ-Processes+harq-ProcID-Offset2,

[0349] Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a CG occasion symbol index in a CG configuration cycle; periodicity represents a CG configuration cycle, nrofHARQ-Processes represents the number of HARQ processes that can be used in the first CG occasion in a CG configuration cycle; harq-ProcID-Offset2 represents the second offset value.

[0350] 15. The method according to note 3 or 14, wherein selecting a HARQ process identifier associated with a CG occasion in a period of a CG configuration comprises:

[0351] The selected HARQ process ID meets at least one of the following conditions:

[0352] Unused HARQ process identifier;

[0353] a HARQ process identifier different from the HARQ process identifier calculated by the fifth formula;

[0354] A HARQ process identifier that is different from the HARQ process identifier already used for the CG occasion in the period configured by the one CG;

[0355] The HARQ process identifier for which the corresponding first timer (configuredGrantTimer) has timed out;

[0356] A HARQ process identifier that can be used for the one CG configuration.

[0357] 16. The method according to Supplementary Note 15, further comprising:

[0358] The selected HARQ process identifier is carried by the UCI and is sent to the network device via the PUCCH or PUSCH channel.

[0359] 17. The method according to Note 1, wherein the CG configuration includes a first CG configuration and / or a second CG configuration,

[0360] The first CG configuration is a configuration that does not include a second offset value (harq-ProcID-Offset2) and a second timer (cg-RetransmissionTimer);

[0361] The second CG configuration is a configuration including a second offset value (harq-ProcID-Offset2).

[0362] 18. A method for receiving uplink data, applied to a network device, wherein the method comprises:

[0363] Receive uplink data sent on a CG occasion,

[0364] The HARQ process identifier of the uplink data is the HARQ process identifier associated with the one CG occasion in at least two CG occasions in a CG configured period, wherein the HARQ process identifier associated with the one CG occasion is different from the HARQ process identifiers associated with other CG occasions in the at least two CG occasions except the one CG occasion.

[0365] 19. The method according to Supplementary Note 18, wherein the method further comprises:

[0366] Send indication information, wherein the indication information indicates: the second parameter, and / or the first offset value or the third offset value, and / or the third parameter.

[0367] 20. The method according to Supplementary Note 19, further comprising:

[0368] The indication information is configured through an RRC message or carried through a PDCCH.

[0369] 21. The method according to Supplement 19 or 20, wherein:

[0370] The second parameter is the number of CG occasions (k) in a period of a CG configuration;

[0371] The first offset or the third offset is set for the one CG occasion in a period of one CG configuration;

[0372] The third parameter (Kn) is the number of CG occasions configured or used in the nth CG cycle, wherein the third parameter (Kn) is counted from the first CG occasion of a CG cycle.

[0373] 22. A terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the uplink data sending method as described in any one of Notes 1 to 17.

[0374] 23. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the uplink data receiving method as described in any one of Notes 18 to 21.

[0375] 24. A communication system comprising:

[0376] A terminal device, which determines a HARQ process identifier associated with a CG occasion in at least two CG transmission opportunities (occasion) in a period configured by a configuration grant (CG), wherein the HARQ process identifier is different from the HARQ process identifiers associated with other CG occasions in the at least two CG occasions except the one CG occasion;

[0377] The terminal device sends uplink data on the CG occasion according to the determined HARQ process identifier associated with the CG occasion;

[0378] A network device receives the uplink data.

Claims

1. An uplink data sending device, configured in a terminal device, the uplink data sending device comprising: A determination unit, which determines a hybrid automatic repeat request (HARQ) process identifier associated with one of at least two configured grant sending opportunities (CG occasion) in a period configured by a configured grant (CG), wherein the hybrid automatic repeat request (HARQ) process identifier is different from hybrid automatic repeat request (HARQ) process identifiers associated with other configured grant sending opportunities (CG occasion) in the at least two configured grant sending opportunities (CG occasion) except the one configured grant sending opportunity (CG occasion); A sending unit, which sends uplink data on a configured grant to send opportunity (CG occasion) according to a determined hybrid automatic repeat request (HARQ) process identifier associated with the determined configured grant to send opportunity (CG occasion).

2. The device according to claim 1, wherein: The determining unit: Determine a hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion) according to the first parameter and the second parameter; and / or Determine a hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion) according to the first offset value or the third offset value; and / or Determine a hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion) according to a third parameter; and / or Determine a hybrid automatic repeat request (HARQ) process identifier associated with the first configuration grant transmission opportunity (CG occasion) in the time domain in a configuration period of a configuration grant (CG); and / or A hybrid automatic repeat request (HARQ) process identifier associated with a configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG) is selected.

3. The device according to claim 2, wherein: The uplink data sending device also includes: A receiving unit, which receives instruction information sent by the network device, The indication information indicates: the second parameter, and / or the first offset value or the third offset value, and / or the third parameter.

4. The device according to claim 3, wherein: The indication information is configured through a radio resource control (RRC) message or carried through a physical downlink control channel (PDCCH).

5. The device according to claim 3, wherein: The first parameter is an index of a configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG), wherein i is an integer starting from 0; The second parameter is the number (k) of configuration grant sending opportunities (CG occasion) in a configuration period of a configuration grant (CG).

6. The device according to claim 5, wherein: The determining unit determines a hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion) according to the first parameter, the second parameter and a first formula, Wherein, the first formula includes: Hybrid Automatic Repeat Request (HARQ) process identifier = [[floor(CURRENT_symbol / periodicity)]*K+i]modulo nrofHARQ-Processes; or Hybrid Automatic Repeat Request (HARQ) process ID = [[floor(CURRENT_symbol / periodicity)]*K+i]modulo nrofHARQ-Processes+harq-ProcID-Offset2, Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a configuration grant sending opportunity (CG occasion) symbol index in a configuration grant (CG) configuration period; periodicity represents a configuration grant (CG) configuration period, nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used for a configuration grant (CG) configuration; harq-ProcID-Offset2 represents the second offset value; i represents the first parameter, and K represents the second parameter.

7. The device according to claim 5, wherein: The determining unit: Setting a first offset value or a third offset value for a configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG); and / or The number of hybrid automatic repeat request (HARQ) processes that can be used is set for the configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG).

8. The device according to claim 7, wherein: The determination unit determines the first offset value or the third offset value based on the index or order of the configuration grant sending opportunity (CG occasion) in a configuration period of a configuration grant (CG) and / or the number of hybrid automatic repeat request (HARQ) processes that can be used for the configuration grant sending opportunity (CG occasion) in a configuration period of a configuration grant (CG).

9. The device according to claim 8, wherein: The determining unit determines a hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion) according to the first offset value and the second formula, Wherein, the second formula includes: Hybrid Automatic Repeat Request (HARQ) process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3; or Hybrid Automatic Repeat Request (HARQ) process ID = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset3 + harq-ProcID-Offset2, Among them, floor represents a round-down operation, modulo represents a modulo operation; CURRENT_symbol represents a configuration grant sending opportunity (CG occasion) symbol index in a configuration grant (CG) configuration period; periodicity represents a configuration grant (CG) configuration period, nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used or configured in a configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration period; harq-ProcID-Offset2 represents the second offset value; offset3 represents the first offset value, which represents the offset value of the hybrid automatic repeat request (HARQ) process identifier of a configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration period.

10. The device according to claim 8, wherein: The determining unit determines a hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion) according to the third offset value and a third formula, Wherein, the third formula includes: Hybrid Automatic Repeat Request (HARQ) process identifier = [floor (CURRENT_symbol / periodicity)] modulo nrofHARQ-Processes + offset4, Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol is a configuration grant sending opportunity (CG occasion) symbol index in a configuration grant (CG) configuration cycle; periodicity represents a configuration grant (CG) configuration cycle, nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used or configured for the i-th configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration cycle; offset4 represents the third offset value.

11. The device according to claim 3, wherein: The third parameter is the number of configuration grant sending opportunities (CG occasions) configured or used in the nth configuration grant (CG) cycle, wherein the third parameter starts counting from the first configuration grant sending opportunity (CG occasion) in a configuration grant (CG) cycle.

12. The device according to claim 11, wherein The determining unit determines a hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion) according to the sum of at least two third parameters and a fourth formula, Wherein, the fourth formula includes: Hybrid Automatic Repeat Request (HARQ) process identifier = [sum(K1, K2, ... KN) + i] modulo nrofHARQ-Processes; or Hybrid Automatic Repeat Request (HARQ) process ID = = [sum (K1, K2, ... KN) + i] modulo nrofHARQ-Processes + harq-ProcID-Offset2, Among them, floor represents a rounding-down operation, modulo represents a modulo operation; CURRENT_symbol represents a configuration grant sending opportunity (CG occasion) symbol index in a configuration grant (CG) configuration cycle; nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used for the i-th configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration cycle; sum(K1, K2, …KN) represents the sum of at least two third parameters.

13. The device according to claim 11, wherein: The determining unit determines the hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion) according to the third parameter when at least one of the following conditions is met: The number of configuration grant sending opportunities (CG occasions) configured in a configuration grant (CG) configuration cycle is different; or Indicates to the network side an unused configuration grant sending opportunity (CG occasion) in a configuration period of a configuration grant (CG).

14. The device according to claim 3, wherein: The determining unit determines the hybrid automatic repeat request (HARQ) process identifier associated with the first configuration grant sending opportunity (CG occasion) in the time domain in a configuration period of a configuration grant (CG) according to the fifth formula, wherein: The fifth formula includes: Hybrid Automatic Repeat Request (HARQ) process identifier = [[floor(CURRENT_symbol / periodicity)]] modulo nrofHARQ-Processes; or Hybrid Automatic Repeat Request (HARQ) process identifier = [[floor(CURRENT_symbol / periodicity)]] modulo nrofHARQ-Processes+harq-ProcID-Offset2, Among them, floor represents the rounding down operation, modulo represents the modulo operation; CURRENT_symbol represents the symbol index of a configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration cycle; periodicity represents the period of a configuration grant (CG) configuration, nrofHARQ-Processes represents the number of hybrid automatic repeat request (HARQ) processes that can be used in the first configuration grant sending opportunity (CG occasion) in a configuration grant (CG) configuration cycle; harq-ProcID-Offset2 represents the second offset value.

15. The device according to claim 3, wherein: The determination unit selects a hybrid automatic repeat request (HARQ) process identifier associated with a configuration grant sending opportunity (CG occasion) in a period configured by a configuration grant (CG) including: The selected hybrid automatic repeat request (HARQ) process identifier satisfies at least one of the following conditions: Unused Hybrid Automatic Repeat Request (HARQ) process identifier; a hybrid automatic repeat request (HARQ) process identifier different from the hybrid automatic repeat request (HARQ) process identifier calculated by the fifth formula; A hybrid automatic repeat request (HARQ) process identifier that is different from a hybrid automatic repeat request (HARQ) process identifier that has been used for a configuration grant transmission opportunity (CG occasion) in a period configured by the one configuration grant (CG); A Hybrid Automatic Repeat Request (HARQ) process identifier for which the corresponding first timer (configuredGrantTimer) has timed out; A hybrid automatic repeat request (HARQ) process identifier that can be used for the one configuration grant (CG) configuration.

16. The device according to claim 15, wherein: The sending unit carries the selected hybrid automatic repeat request (HARQ) process identifier through uplink control information (UCI) and sends the selected hybrid automatic repeat request (HARQ) process identifier to the network device through a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

17. The device according to claim 1, wherein: The configuration authorization (CG) configuration includes a first configuration authorization (CG) configuration and / or a second configuration authorization (CG) configuration, The first configuration authorization (CG) configuration is a configuration that does not include a second offset value (harq-ProcID-Offset2) and a second timer (cg-RetransmissionTimer); The second configuration authorization (CG) configuration is a configuration including a second offset value (harq-ProcID-Offset2). Set.

18. An uplink data receiving device, configured in a network device, wherein: The uplink data receiving device comprises: a receiving unit, which receives uplink data sent on a configuration grant sending opportunity (CG occasion), Among them, the hybrid automatic repeat request (HARQ) process identifier of the uplink data is a hybrid automatic repeat request (HARQ) process identifier associated with the one configured authorization sending opportunity (CG occasion) in at least two configured authorization sending opportunities (CG occasion) in a period configured by a configured authorization (CG), wherein the hybrid automatic repeat request (HARQ) process identifier associated with the one configured authorization sending opportunity (CG occasion) is different from the hybrid automatic repeat request (HARQ) process identifiers associated with other configured authorization sending opportunities (CG occasion) in the at least two configured authorization sending opportunities (CG occasion) except the one configured authorization sending opportunity (CG occasion).

19. The device according to claim 18, wherein: The device also includes: A sending unit, which sends indication information, wherein the indication information indicates: a second parameter, and / or a first offset value or a third offset value, and / or a third parameter.

20. A communication system, comprising: A terminal device, which determines a hybrid automatic repeat request (HARQ) process identifier associated with one of at least two configured grant sending opportunities (CG occasions) in a period of a configured grant (CG) configuration, wherein the hybrid automatic repeat request (HARQ) process identifier is different from the hybrid automatic repeat request (HARQ) process identifiers associated with other configured grant sending opportunities (CG occasions) in the at least two configured grant sending opportunities (CG occasions) except the one configured grant sending opportunity (CG occasion); The terminal device sends uplink data on the one configuration grant sending opportunity (CG occasion) according to the determined hybrid automatic repeat request (HARQ) process identifier associated with the one configuration grant sending opportunity (CG occasion); A network device receives the uplink data.

Images