CN117769017A

CN117769017A - Method and apparatus in a node for wireless communication

Info

Publication number: CN117769017A
Application number: CN202210592142.6A
Authority: CN
Inventors: 胡杨; 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2022-05-27
Filing date: 2022-05-27
Publication date: 2024-03-26
Also published as: WO2023227047A1

Abstract

A method and apparatus in a node for wireless communication is disclosed. A first receiver that receives a first block of information; a first transmitter that transmits a first PUSCH group in a first time window; wherein the target PUSCH is one PUSCH included in the first PUSCH group, and the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH of the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group.

Description

Method and apparatus in a node for wireless communication

Technical Field

The present application relates to a transmission method and apparatus in a wireless communication system, and more particularly, to a transmission method and apparatus for wireless signals in a wireless communication system supporting a cellular network.

Background

XR (Extended Reality) is considered as a very potential technology, and the best form and development trend for pushing XR to large-scale applications will be one of typical applications for future communications; support for XR services in 5G NR (New Radio) is an important aspect of system design. Quasi-periodic traffic models, high data rate and low latency requirements are three important characteristics of XR traffic; how to match the above characteristics of XR traffic is a critical issue to be addressed.

Disclosure of Invention

The above description takes XR as an example; the present application is also applicable to other scenarios, such as embbe (Enhance Mobile Broadband, enhanced mobile broadband), URLLC (UltraReliable andLow Latency Communication, ultra high reliability and ultra low latency communication), MBS (Multicast and Broadcast Services, multicast and broadcast service), ioT (Internet ofThings ), internet of vehicles, NTN (non-terrestrial networks, non-terrestrial network), shared spectrum (shared spectrum), voIP, etc., and achieves similar technical effects. Furthermore, the adoption of unified solutions for different scenarios (including but not limited to XR, eMBB, URLLC, MBS, ioT, internet of vehicles, NTN, shared spectrum, voIP) also helps to reduce hardware complexity and cost, or to improve performance. Embodiments and features of embodiments in any node of the present application may be applied to any other node without conflict. The embodiments of the present application and features in the embodiments may be combined with each other arbitrarily without conflict.

As an example, the term (terminality) in the present application is explained with reference to the definition of the 3GPP specification protocol TS36 series.

As an embodiment, the term in the present application is explained with reference to the definition of the 3GPP specification protocol TS38 series.

As an embodiment, the term in the present application is explained with reference to the definition of the 3GPP specification protocol TS37 series.

As one example, the term in the present application is explained with reference to the definition of the specification protocol of IEEE (Institute ofElectrical andElectronics Engineers ).

The application discloses a method used in a first node of wireless communication, comprising the following steps:

receiving a first information block;

transmitting a first PUSCH group in a first time window;

wherein the target PUSCH is one PUSCH included in the first PUSCH group, and the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH of the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group.

As one embodiment, the problems to be solved by the present application include: how to determine HARQ process numbers of PUSCHs in the first PUSCH group.

As one embodiment, the problems to be solved by the present application include: whether the second information block is used to indicate a HARQ process number of at least one PUSCH in the first PUSCH group.

As one embodiment, the problems to be solved by the present application include: how to indicate the HARQ process number of the transmitted PUSCH.

As one embodiment, the problems to be solved by the present application include: and the relation between the number of the PUSCHs included in the first PUSCH group and the determination mode of the HARQ process number of the PUSCH in the first PUSCH group.

As one embodiment, the problems to be solved by the present application include: how to achieve transmission matching for (quasi-) periodic traffic with non-fixed packet sizes.

As one embodiment, the problems to be solved by the present application include: how to reasonably use UCI carried by PUSCH to realize the indication of HARQ process number.

As one example, the benefits of the above method include: the transmission performance is improved on the premise of ensuring enough flexibility.

As one example, the benefits of the above method include: the flexibility of the HARQ process use is improved.

As one example, the benefits of the above method include: the dependence of the target PUSCH on the carried second information is avoided, and the probability of the target PUSCH being correctly received is improved.

As one example, the benefits of the above method include: error propagation caused by incorrect reception of PUSCH is avoided.

As one example, the benefits of the above method include: and is beneficial to improving the frequency spectrum efficiency.

According to one aspect of the present application, the above method is characterized in that,

when the number of PUSCHs included in the first PUSCH group is greater than a first value, the second information block is used to indicate a HARQ process number of at least one PUSCH in the first PUSCH group; when the number of PUSCHs included in the first PUSCH group is not greater than a first value, associating the HARQ process number of each PUSCH in the first PUSCH group to a reference time domain resource, and for each PUSCH in the first PUSCH group, associating the reference time domain resource with a time domain resource occupied by the PUSCH; the first value is a configurable positive integer or normal number.

when the number of PUSCHs included in the first PUSCH group is greater than the first value: the second information block is used to indicate HARQ process numbers of all PUSCHs in the first PUSCH subgroup; the first PUSCH subgroup belongs to the first PUSCH group, the first PUSCH subgroup including at least one PUSCH and not including the target PUSCH.

the second information block is used to indicate the number of PUSCHs included in the first PUSCH group.

a third information block is used to determine a first set of HARQ process numbers and a second set of HARQ process numbers, the first set of HARQ process numbers and the second set of HARQ process numbers having no intersection; the HARQ process number of the target PUSCH belongs to the first HARQ process number set; when the second information block is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group, the second information block is used to indicate the HARQ process number of the at least one PUSCH in the first PUSCH group from the second set of HARQ process numbers.

a target reference time domain resource is associated to the target PUSCH, and a HARQ process number of the target PUSCH is associated to the target reference time domain resource.

a first set of uplink grants is configured to the first node, the first set of uplink grants including a target uplink grant; the target PUSCH corresponds to the target uplink grant, and a target index is an ordering index of the target uplink grant in the first set of uplink grants; the HARQ process number of the target PUSCH is associated to the reference time domain resource and the target index.

The application discloses a method used in a second node of wireless communication, comprising the following steps:

transmitting a first information block;

receiving a first PUSCH group in a first time window;

a first set of uplink grants configured to a sender of the first PUSCH group, the first set of uplink grants including a target uplink grant; the target PUSCH corresponds to the target uplink grant, and a target index is an ordering index of the target uplink grant in the first set of uplink grants; the HARQ process number of the target PUSCH is associated to the reference time domain resource and the target index.

The application discloses a first node used for wireless communication, which is characterized by comprising:

a first receiver that receives a first block of information;

a first transmitter that transmits a first PUSCH group in a first time window;

The application discloses a second node for wireless communication, comprising:

a second transmitter transmitting the first information block;

a second receiver that receives the first PUSCH group in a first time window;

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings in which:

FIG. 1 illustrates a process flow diagram of a first node according to one embodiment of the present application;

FIG. 2 shows a schematic diagram of a network architecture according to one embodiment of the present application;

fig. 3 shows a schematic diagram of a radio protocol architecture of a user plane and a control plane according to one embodiment of the present application;

FIG. 4 shows a schematic diagram of a first communication device and a second communication device according to one embodiment of the present application;

FIG. 5 illustrates a signaling flow diagram according to one embodiment of the present application;

fig. 6 shows an explanatory diagram of HARQ process numbers of PUSCHs in a first PUSCH group according to an embodiment of the present application;

fig. 7 shows an explanatory diagram of a second field in a second information block when the number of PUSCHs included in a first PUSCH group is not greater than a first value, according to an embodiment of the present application;

fig. 8 shows an explanatory diagram when the number of PUSCHs included in the first PUSCH group is greater than the first value according to an embodiment of the present application;

fig. 9 shows a schematic diagram of a relationship between a second information block and the number of PUSCHs comprised by a first PUSCH group according to an embodiment of the present application;

fig. 10 shows a schematic diagram of a relationship between a third information block, a first set of HARQ process numbers, a second set of HARQ process numbers, and HARQ process numbers of PUSCH in a first PUSCH group according to an embodiment of the present application;

fig. 11 shows a schematic diagram of a relationship between a target reference time domain resource, a target PUSCH and HARQ process numbers of the target PUSCH according to an embodiment of the present application;

Fig. 12 shows a schematic diagram of a relationship between the HARQ process number, the third value, the fourth value, and the second value of the target PUSCH according to an embodiment of the present application;

fig. 13 shows a schematic diagram of a relationship between a first set of uplink grants, a target uplink grant, a target PUSCH, and a target index according to one embodiment of the application;

fig. 14 shows a block diagram of a processing arrangement in a first node device according to an embodiment of the present application;

fig. 15 shows a block diagram of a processing apparatus in a second node device according to an embodiment of the present application.

Detailed Description

The technical solutions of the present application will be described in further detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments of the present application and the features in the embodiments may be arbitrarily combined with each other.

Example 1

Embodiment 1 illustrates a process flow diagram of a first node according to one embodiment of the present application, as shown in fig. 1.

In embodiment 1, the first node in the present application receives a first information block in step 101; the first PUSCH group is transmitted in a first time window in step 102.

In embodiment 1, the target PUSCH is one PUSCH included in the first PUSCH group, the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH of the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group.

As an embodiment, the first information block comprises physical layer signaling.

As an embodiment, the first information block comprises DCI (Downlink control information ).

As an embodiment, the first information block includes higher layer (higher layer) signaling.

As an embodiment, the first information block comprises a MAC CE (MediumAccess Control layer Control Element ).

As an embodiment, the first information block comprises RRC (Radio Resource Control ) signaling.

As an embodiment, the first information block comprises at least one field in at least one IE (Information Element).

As an embodiment, the first information block comprises configurable grantconfig.

As an embodiment, the first information block comprises at least one field in a configurable grantconfig.

As an embodiment, the first information block includes a parameter periodicity.

As an embodiment, the first information block includes configuration information for a configuration Grant (Configured Grant).

As an embodiment, the first PUSCH group comprises at least one PUSCH (Physical uplink shared channel ).

As an embodiment, in the first PUSCH group, there is no PUSCH earlier in time domain than the target PUSCH.

As an embodiment, in the first PUSCH group, there is no PUSCH later in time domain than the target PUSCH.

As an embodiment, in the first PUSCH group, there is no PUSCH occupying more time domain resources than the target PUSCH.

As an embodiment, in the first PUSCH group, there is no PUSCH occupying less time domain resources than the target PUSCH.

As an embodiment, all PUSCHs in the first PUSCH group are PUSCHs associated to one Configured Grant (Configured Grant).

As an embodiment, the first time window comprises consecutive time domain resources.

As an embodiment, the first time window comprises at least one slot (slot).

As an embodiment, the first time window comprises at least one time domain symbol.

As an embodiment, the time domain Symbol in the present application is an OFDM (Orthogonal FrequencyDivision Multiplexing ) Symbol (Symbol).

As an embodiment, the time domain symbol in the present application is an SC-FDMA (Single Carrier-Frequency Division Multiple Access, single Carrier frequency division multiple access) symbol.

As one embodiment, the time domain symbols in this application are DFT-S-OFDM (Discrete FourierTransform SpreadOFDM, discrete fourier transform orthogonal frequency division multiplexing) symbols.

As an embodiment, the time domain symbol in the present application is an FBMC (FilterBank Multi Carrier ) symbol.

As an embodiment, the time domain symbol in the present application includes consecutive time domain resources.

As an embodiment, the time domain symbol in the present application is one of uplink symbols (uplink symbols), downlink symbols (downlink symbols), flexible symbols (flexible symbols).

As one embodiment, the first time window comprises at least one millisecond (ms).

As an embodiment, the first information block is used to indicate the first time window.

As an embodiment, the first information block is used to determine a plurality of time windows, the first time window being one of the plurality of time windows.

As an embodiment, the first information block is used to configure a plurality of time windows, the first time window being one of the plurality of time windows.

As an embodiment, the plurality of time windows terminate.

As an embodiment, the time length of any 2 time windows of the plurality of time windows is equal.

As an embodiment, there are at least 2 time windows of different time lengths from each other in the plurality of time windows.

As an embodiment, each time window of the plurality of time windows includes at least one time slot reserved for at least one PUSCH.

As an embodiment, the first time window includes a plurality of time slots reserved for a plurality of PUSCHs, respectively.

As an embodiment, the first time window includes time domain resources reserved for one set of uplink grants (uplink grant).

As an embodiment, the first information block is used to determine the first time window.

As an embodiment, the first information block is used to configure the first time window.

As an embodiment, the first information block is used to configure the time length of the first time window.

As an embodiment, the first information block is used to indicate a starting position of the first time window.

As an embodiment, the first information block is used to indicate an end position of the first time window.

As an embodiment, the first information block is used to indicate the number of time slots comprised by the first time window.

As an embodiment, the first information block is used to determine that the target PUSCH carries a second information block.

As an embodiment, one field in the first information block indicates that the target PUSCH carries the second information block.

As an embodiment, one parameter value configured in the first information block indicates that the target PUSCH carries the second information block.

As an embodiment, the first information block explicitly indicates that the target PUSCH carries the second information block.

As an embodiment, the first information block implicitly indicates that the target PUSCH carries the second information block.

As an embodiment, the expressing that the target PUSCH carries (the) the second information block includes: bits in the second information block are CRC-attached (CRC attachment), code block split (Code block segmentation), code block CRC attachment, channel coding (Channel coding), rate matching (Rate mapping), code block concatenation (Codeblock concatenation), scrambling (Scrambling), modulation (Layer mapping), transform Precoding (transform Precoding), precoding (Precoding), mapping to virtual resource blocks (Mappingto virtual resourceblocks), mapping from virtual resource blocks to physical resource blocks (Mapping from virtual to physical resource blocks), multicarrier symbol generation, and Modulation up-conversion with at least part of the output being transmitted on the target PUSCH.

As an embodiment, the expressing that the target PUSCH carries (the) the second information block includes: the second information block is transmitted on the target PUSCH.

As an embodiment, the expressing that the target PUSCH carries (the) the second information block includes: the target PUSCH is used for transmitting the second information block.

As an embodiment, the expressing that the target PUSCH carries (the) the second information block includes: and the second information block is transmitted through the target PUSCH.

As an embodiment, the expression transmitting the first PUSCH group includes: a signal is transmitted on each PUSCH in the first PUSCH group.

As an embodiment, the expression transmitting the first PUSCH group includes: and transmitting a bit block on each PUSCH in the first PUSCH group.

As an embodiment, the second information block comprises uplink control information (Uplink control information, UCI) bits.

As an embodiment, the second information block includes CG-UCI.

As an embodiment, the second information block includes a field for indicating a HARQ Process number (HARQ Process ID/number).

As an embodiment, the second information block comprises a field for indicating RV (Redundancy version ).

As an embodiment, the second information block includes a field for indicating the number of PUSCHs.

As an embodiment, the second information block includes a field for indicating MCS (Modulation and coding scheme, modulation and coding strategy).

As an embodiment, the second information block comprises a field for indicating a frequency domain resource allocation (Frequency domain resource assignment).

As an embodiment, the second information block comprises a field for indicating a time domain resource allocation (Time domain resource assignment).

As an embodiment, the expressing whether the second information block is used to indicate that the HARQ process number of at least one PUSCH in the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group includes:

the second information block includes a first field used to determine a number of PUSCHs included in the first PUSCH group; the first field is used to determine whether the second information block is used to indicate a HARQ process number for at least one PUSCH in the first PUSCH group.

As an embodiment, the second information block is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group only if the number of PUSCHs included in the first PUSCH group is greater than a first value; the first value is a configurable positive integer or normal number.

As an embodiment, when the number of PUSCHs included in the first PUSCH group is not greater than a first value, the second information block is not used to indicate the HARQ process number of any PUSCH in the first PUSCH group; the first value is a configurable positive integer or normal number.

As an embodiment, the second information block is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group only if the number of PUSCHs included in the first PUSCH group is not greater than a first value; the first value is a configurable positive integer or normal number.

As an embodiment, when the number of PUSCHs included in the first PUSCH group is greater than a first value, the second information block is not used to indicate the HARQ process number of any PUSCH in the first PUSCH group; the first value is a configurable positive integer or normal number.

As an embodiment, the second information block is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group only if the number of PUSCHs comprised by the first PUSCH group belongs to a first set of values; the first set of values includes at least one value.

As an embodiment, when the number of PUSCHs included in the first PUSCH group does not belong to the first value set, the second information block is not used to indicate the HARQ process number of any PUSCH in the first PUSCH group; the first set of values includes at least one value.

As an embodiment, the first set of values comprises only one positive integer.

As an embodiment, the first set of values comprises a plurality of positive integers.

As an embodiment, the first set of values comprises a plurality of consecutive positive integers.

As an embodiment, the first set of values is configurable.

As one embodiment, the first set of values comprises {1}.

As an embodiment, the first set of values comprises {1,2}.

As one embodiment, the first set of values includes {1,2,3,4}.

As an embodiment, the expressing that the second information block (only) is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group comprises: the second information block includes a second field used to indicate HARQ process numbers of at least one PUSCH in the first PUSCH group.

As an embodiment, the expressing that the second information block is not used to indicate HARQ process numbers of any PUSCH in the first PUSCH group includes: the second information block includes a second field that is not used to indicate HARQ process numbers of any PUSCH in the first PUSCH group.

As an embodiment, the expressing that the second information block is not used to indicate HARQ process numbers of any PUSCH in the first PUSCH group includes: the second information block includes a second field whose bit is set to a fixed value or is used to indicate information other than the HARQ process number.

As an embodiment, the expressing that the second information block is not used to indicate HARQ process numbers of any PUSCH in the first PUSCH group includes: the HARQ process number of each PUSCH in the first PUSCH group is associated to each time domain resource in a reference time domain resource group, and for each PUSCH in the first PUSCH group, the corresponding reference time domain resource belongs to the time domain resource occupied by the PUSCH.

As an embodiment, when the second information block is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group, the first node determines the HARQ process number of the at least one PUSCH in the first PUSCH group by itself.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in fig. 2.

Fig. 2 illustrates a diagram of a network architecture 200 of a 5g nr, LTE (Long-Term Evolution) and LTE-a (Long-Term Evolution Advanced, enhanced Long-Term Evolution) system. The 5G NR or LTE network architecture 200 may be referred to as EPS (Evolved Packet System ) 200 as some other suitable terminology. EPS 200 may include one or more UEs (User Equipment) 201, ng-RAN (next generation radio access Network) 202, epc (Evolved Packet Core )/5G-CN (5G Core Network) 210, hss (Home Subscriber Server ) 220, and internet service 230. The EPS may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, EPS provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit-switched services or other cellular networks. The NG-RAN includes NR node bs (gnbs) 203 and other gnbs 204. The gNB203 provides user and control plane protocol termination towards the UE 201. The gNB203 may be connected to other gnbs 204 via an Xn interface (e.g., backhaul). The gNB203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmit receive node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the EPC/5G-CN 210. Examples of UE201 include a cellular telephone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a non-terrestrial base station communication, a satellite mobile communication, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, an drone, an aircraft, a narrowband internet of things device, a machine-type communication device, a land-based vehicle, an automobile, a wearable device, or any other similar functional device. Those of skill in the art may also refer to the UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. The gNB203 is connected to the EPC/5G-CN 210 through an S1/NG interface. EPC/5G-CN 210 includes MME (Mobility Management Entity )/AMF (Authentication Management Field, authentication management domain)/UPF (User Plane Function ) 211, other MME/AMF/UPF214, S-GW (Service Gateway) 212, and P-GW (Packet Date Network Gateway, packet data network Gateway) 213. The MME/AMF/UPF211 is a control node that handles signaling between the UE201 and the EPC/5G-CN 210. In general, the MME/AMF/UPF211 provides bearer and connection management. All user IP (Internet Protocal, internet protocol) packets are transported through the S-GW212, which S-GW212 itself is connected to P-GW213. The P-GW213 provides UE IP address assignment as well as other functions. The P-GW213 is connected to the internet service 230. Internet services 230 include operator-corresponding internet protocol services, which may include, in particular, the internet, intranets, IMS (IP Multimedia Subsystem ) and packet-switched streaming services.

As an embodiment, the UE201 corresponds to the first node in the present application.

As an embodiment, the UE201 corresponds to the second node in the present application.

As an embodiment, the gNB203 corresponds to the first node in the present application.

As an embodiment, the gNB203 corresponds to the second node in the present application.

As an embodiment, the UE201 corresponds to the first node in the present application, and the gNB203 corresponds to the second node in the present application.

As an embodiment, the gNB203 is a macro cell (marcocelluar) base station.

As one example, the gNB203 is a Micro Cell (Micro Cell) base station.

As an embodiment, the gNB203 is a PicoCell (PicoCell) base station.

As an example, the gNB203 is a home base station (Femtocell).

As an embodiment, the gNB203 is a base station device supporting a large delay difference.

As an embodiment, the gNB203 is a flying platform device.

As one embodiment, the gNB203 is a satellite device.

As an embodiment, the first node and the second node in the present application both correspond to the UE201, for example, V2X communication is performed between the first node and the second node.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture according to one user plane and control plane of the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300, fig. 3 shows the radio protocol architecture for the control plane 300 for a first communication node device (UE, RSU in gNB or V2X) and a second communication node device (gNB, RSU in UE or V2X), or between two UEs, in three layers: layer 1, layer 2 and layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY301. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first communication node device and the second communication node device and the two UEs through PHY301. The L2 layer 305 includes a MAC (MediumAccess Control ) sublayer 302, an RLC (Radio Link Control, radio link layer control protocol) sublayer 303, and a PDCP (Packet Data Convergence Protocol ) sublayer 304, which terminate at the second communication node device. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by ciphering the data packets and handover support for the first communication node device between second communication node devices. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out of order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the first communication node devices. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control ) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second communication node device and the first communication node device. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer), the radio protocol architecture for the first communication node device and the second communication node device in the user plane 350 is substantially the same for the physical layer 351, PDCP sublayer 354 in the L2 layer 355, RLC sublayer 353 in the L2 layer 355 and MAC sublayer 352 in the L2 layer 355 as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. Also included in the L2 layer 355 in the user plane 350 is an SDAP (Service DataAdaptationProtocol ) sublayer 356, the SDAP sublayer 356 being responsible for mapping between QoS flows and data radio bearers (DRBs, data Radio Bearer) to support diversity of traffic. Although not shown, the first communication node apparatus may have several upper layers above the L2 layer 355, including a network layer (e.g., IP layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., remote UE, server, etc.).

As an embodiment, the radio protocol architecture in fig. 3 is applicable to the first node in the present application.

As an embodiment, the radio protocol architecture in fig. 3 is applicable to the second node in the present application.

As an embodiment, at least part of the first information block in the present application is generated in the RRC sublayer 306.

As an embodiment, at least part of the first information block in the present application is generated in the MAC sublayer 302.

As an embodiment, at least part of the first information block in the present application is generated in the MAC sublayer 352.

As an embodiment, at least part of the first information block in the present application is generated in the PHY301.

As an embodiment, at least part of the first information block in the present application is generated in the PHY351.

As an embodiment, at least part of the second information block in the present application is generated in the RRC sublayer 306.

As an embodiment, at least part of the second information block in the present application is generated in the MAC sublayer 302.

As an embodiment, at least part of the second information block in the present application is generated in the MAC sublayer 352.

As an embodiment, at least part of the second information block in the present application is generated in the PHY301.

As an embodiment, at least part of the second information block in the present application is generated in the PHY351.

As an embodiment, at least part of the third information block in the present application is generated in the RRC sublayer 306.

As an embodiment, at least part of the third information block in the present application is generated in the MAC sublayer 302.

As an embodiment, at least part of the third information block in the present application is generated in the MAC sublayer 352.

As an embodiment, at least part of the third information block in the present application is generated in the PHY301.

As an embodiment, at least part of the third information block in the present application is generated in the PHY351.

Example 4

Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in fig. 4. Fig. 4 is a block diagram of a first communication device 410 and a second communication device 450 in communication with each other in an access network.

The first communication device 410 includes a controller/processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter/receiver 418, and an antenna 420.

The second communication device 450 includes a controller/processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter/receiver 454, and an antenna 452.

In the transmission from the first communication device 410 to the second communication device 450, upper layer data packets from the core network are provided to a controller/processor 475 at the first communication device 410. The controller/processor 475 implements the functionality of the L2 layer. In the transmission from the first communication device 410 to the first communication device 450, a controller/processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the second communication device 450 based on various priority metrics. The controller/processor 475 is also responsible for retransmission of lost packets and signaling to the second communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., physical layer). Transmit processor 416 performs coding and interleaving to facilitate Forward Error Correction (FEC) at the second communication device 450, as well as mapping of signal clusters based on various modulation schemes, e.g., binary Phase Shift Keying (BPSK), quadrature Phase Shift Keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM). The multi-antenna transmit processor 471 digitally space-precodes the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. A transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying the time domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multiple antenna transmit processor 471 to a radio frequency stream and then provides it to a different antenna 420.

In a transmission from the first communication device 410 to the second communication device 450, each receiver 454 receives a signal at the second communication device 450 through its respective antenna 452. Each receiver 454 recovers information modulated onto a radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream that is provided to a receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various signal processing functions for the L1 layer. A multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multicarrier symbol stream after receiving the analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receive processor 456, wherein the reference signal is to be used for channel estimation, and the data signal is subjected to multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial stream destined for the second communication device 450. The symbols on each spatial stream are demodulated and recovered in a receive processor 456 and soft decisions are generated. A receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals that were transmitted by the first communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller/processor 459. The controller/processor 459 implements the functions of the L2 layer. The controller/processor 459 may be associated with a memory 460 that stores program codes and data. Memory 460 may be referred to as a computer-readable medium. In the transmission from the first communication device 410 to the second communication device 450, the controller/processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the core network. The upper layer packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

In the transmission from the second communication device 450 to the first communication device 410, a data source 467 is used at the second communication device 450 to provide upper layer data packets to a controller/processor 459. Data source 467 represents all protocol layers above the L2 layer. Similar to the transmit functions at the first communication device 410 described in the transmission from the first communication device 410 to the second communication device 450, the controller/processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations, implementing L2 layer functions for the user and control planes. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to the first communication device 410. The transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming, with the multi-antenna transmit processor 457 performing digital multi-antenna spatial precoding, after which the transmit processor 468 modulates the resulting spatial stream into a multi-carrier/single-carrier symbol stream, which is analog precoded/beamformed in the multi-antenna transmit processor 457 before being provided to the different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and provides it to an antenna 452.

In the transmission from the second communication device 450 to the first communication device 410, the function at the first communication device 410 is similar to the receiving function at the second communication device 450 described in the transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals to baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement the functions of the L1 layer. The controller/processor 475 implements L2 layer functions. The controller/processor 475 may be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In the transmission from the second communication device 450 to the first communication device 410, a controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from the controller/processor 475 may be provided to the core network.

As an embodiment, the first node in the present application includes the second communication device 450, and the second node in the present application includes the first communication device 410.

As a sub-embodiment of the above embodiment, the first node is a user equipment and the second node is a user equipment.

As a sub-embodiment of the above embodiment, the first node is a user equipment and the second node is a relay node.

As a sub-embodiment of the above embodiment, the first node is a relay node and the second node is a user equipment.

As a sub-embodiment of the above embodiment, the first node is a user equipment and the second node is a base station device.

As a sub-embodiment of the above embodiment, the first node is a relay node and the second node is a base station device.

As a sub-embodiment of the above embodiment, the second node is a user equipment and the first node is a base station device.

As a sub-embodiment of the above embodiment, the second node is a relay node, and the first node is a base station apparatus.

As a sub-embodiment of the above embodiment, the second communication device 450 includes: at least one controller/processor; the at least one controller/processor is responsible for HARQ operations.

As a sub-embodiment of the above embodiment, the first communication device 410 includes: at least one controller/processor; the at least one controller/processor is responsible for HARQ operations.

As a sub-embodiment of the above embodiment, the first communication device 410 includes: at least one controller/processor; the at least one controller/processor is responsible for error detection using a positive Acknowledgement (ACK) and/or Negative Acknowledgement (NACK) protocol to support HARQ operations.

As an embodiment, the second communication device 450 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 450 means at least: receiving a first information block; transmitting a first PUSCH group in a first time window; wherein the target PUSCH is one PUSCH included in the first PUSCH group, and the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH of the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group.

As a sub-embodiment of the above embodiment, the second communication device 450 corresponds to the first node in the present application.

As an embodiment, the second communication device 450 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: receiving a first information block; transmitting a first PUSCH group in a first time window; wherein the target PUSCH is one PUSCH included in the first PUSCH group, and the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH of the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group.

As one embodiment, the first communication device 410 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The first communication device 410 means at least: transmitting a first information block; receiving a first PUSCH group in a first time window; wherein the target PUSCH is one PUSCH included in the first PUSCH group, and the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH of the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group.

As a sub-embodiment of the above embodiment, the first communication device 410 corresponds to the second node in the present application.

As one embodiment, the first communication device 410 includes: a memory storing a program of computer-readable instructions that, when executed by at least one processor, produce acts comprising: transmitting a first information block; receiving a first PUSCH group in a first time window; wherein the target PUSCH is one PUSCH included in the first PUSCH group, and the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH of the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group.

As an embodiment at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, the data source 467 is used for receiving the first information block in the present application.

As an example, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, the memory 476 is used for transmitting the first information block in the present application.

As an embodiment at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, the data source 467 is used for receiving the third information block in the present application.

As an example, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, the memory 476 is used for transmitting the third information block in the present application.

As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmit processor 458, the transmit processor 468, the controller/processor 459, the memory 460, the data source 467 is used to transmit the first PUSCH group in the present application.

As an embodiment, at least one of { the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, the memory 476} is used to receive the first PUSCH group in the present application.

Example 5

Embodiment 5 illustrates a signaling flow diagram according to one embodiment of the present application, as shown in fig. 5. In fig. 5, the first node U1 and the second node U2 communicate over an air interface.

The first node U1 receives the first information block in step S511; the first PUSCH group is transmitted in a first time window in step S512.

The second node U2 transmitting the first information block in step S521; a first PUSCH group is received in a first time window in step S522.

In embodiment 5, the target PUSCH is one PUSCH included in the first PUSCH group, the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH in the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group; when the number of PUSCHs included in the first PUSCH group is greater than a first value, the second information block is used to indicate HARQ process numbers of all PUSCHs in the first PUSCH subgroup; the first PUSCH subgroup belongs to the first PUSCH subgroup, the first PUSCH subgroup including at least one PUSCH and not including the target PUSCH; when the number of PUSCHs included in the first PUSCH group is not greater than a first value, associating the HARQ process number of each PUSCH in the first PUSCH group to a reference time domain resource, and for each PUSCH in the first PUSCH group, associating the reference time domain resource with a time domain resource occupied by the PUSCH; the first value is a configurable positive integer or normal number; the second information block is used to indicate the number of PUSCHs included in the first PUSCH group; a target reference time domain resource is associated to the target PUSCH, and a HARQ process number of the target PUSCH is associated to the target reference time domain resource.

As a sub-embodiment of embodiment 5, a first set of uplink grants is configured to the first node U1, the first set of uplink grants comprising a target uplink grant; the target PUSCH corresponds to the target uplink grant, and a target index is an ordering index of the target uplink grant in the first set of uplink grants; the HARQ process number of the target PUSCH is associated to the reference time domain resource and the target index.

As an embodiment, the first node U1 is the first node in the present application.

As an embodiment, the second node U2 is the second node in the present application.

As an embodiment, the first node U1 is a UE.

As an embodiment, the first node U1 is a base station.

As an embodiment, the second node U2 is a base station.

As an embodiment, the second node U2 is a UE.

As an embodiment, the air interface between the second node U2 and the first node U1 is a Uu interface.

As an embodiment, the air interface between the second node U2 and the first node U1 comprises a cellular link.

As an embodiment, the air interface between the second node U2 and the first node U1 is a PC5 interface.

As an embodiment, the air interface between the second node U2 and the first node U1 comprises a sidelink.

As an embodiment, the air interface between the second node U2 and the first node U1 comprises a radio interface between a base station device and a user equipment.

As an embodiment, the air interface between the second node U2 and the first node U1 comprises a wireless interface between a satellite device and a user device.

As an embodiment, the air interface between the second node U2 and the first node U1 comprises a wireless interface between user equipment and user equipment.

Example 6

Embodiment 6 illustrates an explanatory diagram of HARQ process numbers of PUSCHs in the first PUSCH group according to an embodiment of the present application, as shown in fig. 6. In fig. 6, it is determined in S61 whether the number of PUSCHs included in the first PUSCH group is greater than a first value; the HARQ process number of each PUSCH in the first PUSCH group is associated to one reference time domain resource in S62, and the second information block is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group in S63.

In embodiment 6, when the number of PUSCHs included in the first PUSCH group is greater than a first value, the second information block is used to indicate a HARQ process number of at least one PUSCH in the first PUSCH group; when the number of PUSCHs included in the first PUSCH group is not greater than a first value, associating the HARQ process number of each PUSCH in the first PUSCH group to a reference time domain resource, and for each PUSCH in the first PUSCH group, associating the reference time domain resource with a time domain resource occupied by the PUSCH; the first value is a configurable positive integer or normal number.

As an embodiment, the first value is equal to 1.

As an embodiment, the first value is equal to 2.

As an embodiment, the first value is equal to 3.

As an embodiment, the first value is equal to 4.

As an embodiment, the first value is a positive integer not greater than 8.

As an embodiment, the first value is not greater than 1024.

As an embodiment, the associating the HARQ process number of each PUSCH in the first PUSCH group to one reference time domain resource includes: for each PUSCH in the first PUSCH group, the corresponding HARQ process number is equal to a result of a downward rounding of a ratio of a value corresponding to the associated reference time domain resource to a first period value modulo a fourth value plus a second value, the first information block being used to determine the first period value and the fourth value, the second value being a configurable non-negative integer or non-negative constant.

As an embodiment, the associating the HARQ process number of each PUSCH in the first PUSCH group to one reference time domain resource includes: for each PUSCH in the first PUSCH group, the corresponding HARQ process number is equal to a result of a downward rounding of a ratio of a value corresponding to the associated reference time domain resource to a first period value multiplied by a sum of K and the corresponding ordering index modulo a fourth value plus a second value, the first information block being used to determine the first period value and the fourth value, the second value being a configurable non-negative integer or non-negative constant, the K being configurable.

As an embodiment, for each PUSCH in the first PUSCH group, the ordering index corresponding is a positive integer and is not greater than the K.

As an embodiment, for each PUSCH in the first PUSCH group, the corresponding ordering index is a non-negative integer and less than the K.

As an embodiment, for each PUSCH in the first PUSCH group, the ordering index corresponding to is an ordering index of an uplink grant corresponding to this PUSCH in an uplink grant set.

As an embodiment, the associating the HARQ process number of each PUSCH in the first PUSCH group to one reference time domain resource includes: for each PUSCH in the first PUSCH group, the corresponding HARQ process number is equal to a value that is not less than a downward rounding of a ratio of a value corresponding to the associated reference time domain resource to a first period value multiplied by a value of K modulo a fourth value plus a second value, the first information block being used to determine the first period value and the fourth value, the second value being a configurable non-negative integer or non-negative constant, the K being configurable.

As an embodiment, the first information block is used to configure the K.

As an embodiment, the K is configured by RRC signaling.

As an embodiment, the K is configured for higher layer signaling.

As an embodiment, K is a positive integer.

As an embodiment, the K is equal to 1.

As an embodiment, the K is greater than 1.

As an embodiment, the first information block is used to determine a first period value.

As an embodiment, the first information block is used to indicate a first period value.

As an embodiment, the first information block is used to configure a first period value.

As an embodiment, the first period value is expressed in terms of a number of time domain symbols.

As an embodiment, the first period value is expressed in terms of the number of time slots.

As an embodiment, the first period value is expressed in milliseconds.

As an embodiment, the first information block is used to determine a fourth value.

As an embodiment, the first information block is used to indicate a fourth value.

As an embodiment, the first information block is used to configure a fourth value.

As one example, the fourth value is equal to one of 1,2,3, 16.

As an embodiment, the fourth value is not greater than 16.

As an embodiment, the fourth value is not greater than 32.

As an embodiment, the fourth value is not greater than 1024.

As an embodiment, the fourth value is a positive integer.

As an embodiment, the first information block is used to determine a second value.

As an embodiment, the first information block is used to indicate a second value.

As an embodiment, the first information block is used to configure a second value.

As one embodiment, the second value is equal to one of 0,1,2,3, 15.

As an embodiment, the second value is not greater than 15.

As an embodiment, the second value is not greater than 31.

As an embodiment, the second value is not greater than 1023.

As an embodiment, the second value is a non-negative integer.

As an embodiment, the second information block is not used to indicate the HARQ process number of the target PUSCH, regardless of the number of PUSCHs included in the first PUSCH group.

As an embodiment, the HARQ process number of the target PUSCH is associated to the target reference time domain resource, irrespective of the number of PUSCHs comprised by the first PUSCH group.

As an embodiment, for each PUSCH in the first PUSCH group, the associated reference time domain resource is the first time domain symbol occupied by this PUSCH.

As an embodiment, for each PUSCH in the first PUSCH group, the associated reference time domain resource is the first time domain symbol of the corresponding UL transmission.

As an embodiment, for each PUSCH in the first PUSCH group, the associated reference time domain resource is a time domain symbol, and the value corresponding to the time domain symbol is equal to: a system frame number (SystemFrame Number, SFN) x number ofslotsperframe x number ofsymbol slot number + the time slot number (slot number) of the time slot to which the time domain symbol belongs in the frame to which the time domain symbol belongs x number of the symbol number (symbol number) of the time domain symbol in the time slot to which the time domain symbol belongs; the numberOfSlotsPerFrame and the numberOfSymbolsPerSlot are the number of consecutive slots per frame and the number of consecutive time domain symbols per slot, respectively.

As an embodiment, for each PUSCH in the first PUSCH group, the value corresponding to the associated reference time domain resource is a value representing the time domain position of this reference time domain resource.

Example 7

Embodiment 7 illustrates a schematic diagram of the second field in the second information block when the number of PUSCHs included in the first PUSCH group is not greater than the first value, as shown in fig. 7, according to an embodiment of the present application.

In embodiment 7, the second information block includes a second field; when the number of PUSCHs included in the first PUSCH group is not greater than a first value: the bit in the second field is set to a fixed value or the second field is used to indicate information other than the HARQ process number.

As an embodiment, said expressing that the bits in the second domain are set to a fixed value comprises: each bit in the second field is fixedly set to 0.

As an embodiment, said expressing that the bits in the second domain are set to a fixed value comprises: each bit in the second field is fixedly set to 1.

As an embodiment, said expressing that the bits in the second domain are set to a fixed value comprises: each bit in the second field is fixedly set to one of 0 or 1.

As an embodiment, the expressing that the second field is used to indicate information other than HARQ process number includes: the second field is used to indicate the MCS.

As an embodiment, the expressing that the second field is used to indicate information other than HARQ process number includes: the second field is used to indicate RV.

As an embodiment, the expressing that the second field is used to indicate information other than HARQ process number includes: the second domain is used to indicate at least one of time domain resources or frequency domain resources.

As an embodiment, the expressing that the second field is used to indicate information other than HARQ process number includes: the second field is not used to indicate HARQ process numbers for any PUSCH in the first PUSCH group.

As an embodiment, the second field comprises 1 bit.

As an embodiment, the second field comprises 2 bits.

As an embodiment, the second field comprises 3 bits.

As an embodiment, the second field comprises 4 bits.

As an embodiment, the second field comprises no more than 8 bits.

Example 8

Embodiment 8 illustrates an explanatory diagram when the number of PUSCHs included in the first PUSCH group is greater than the first value, as shown in fig. 8, according to an embodiment of the present application.

In embodiment 8, when the number of PUSCHs included in the first PUSCH group is greater than the first value: the second information block is used to indicate HARQ process numbers of all PUSCHs in a first PUSCH subgroup, the first PUSCH subgroup belonging to the first PUSCH subgroup, the first PUSCH subgroup including at least one PUSCH and not including the target PUSCH.

As an embodiment, the expressing that the second information block (only) is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group comprises: the second information block is used to indicate HARQ process numbers of all PUSCHs in a first PUSCH subgroup, the first PUSCH subgroup belonging to the first PUSCH subgroup, the first PUSCH subgroup including at least one PUSCH and not including the target PUSCH.

As an embodiment, the first PUSCH subgroup includes all PUSCHs in the first PUSCH group except the target PUSCH.

As an embodiment, the expressing that the second information block is used to indicate HARQ process numbers of all PUSCHs in the first PUSCH subgroup includes: the second information block includes a second field indicating a HARQ process number of a first PUSCH in the first PUSCH subgroup, if the first PUSCH subgroup includes a plurality of PUSCHs, for an mth PUSCH in the first PUSCH subgroup, the corresponding HARQ process number= (the HARQ process number of the first PUSCH in the first PUSCH subgroup +m-1) modN; the N is a configurable positive integer or normal number.

As an embodiment, the expressing that the second information block is used to indicate HARQ process numbers of all PUSCHs in the first PUSCH subgroup includes: the second information block includes a second domain, and for an mth PUSCH in the first PUSCH subgroup, the corresponding HARQ process number= (value of the second domain +m-1) modn+n; the N is a configurable positive integer or normal number, and the N is a configurable non-negative integer or non-negative constant.

As an embodiment, the mth PUSCH in the first PUSCH subgroup is a PUSCH in the first PUSCH subgroup arranged in the mth bit in the time domain from first to second order, and m is a positive integer and is not greater than the total number of PUSCHs included in the first PUSCH subgroup.

As an embodiment, the first information block is used to configure the N.

As an embodiment, the N is configured by RRC signaling.

As an embodiment, the N is configured for higher layer signaling.

As an embodiment, said N is equal to 1.

As an embodiment, the N is greater than 1.

As an embodiment, N is equal to 16.

As an embodiment, the N is not greater than 16.

As an embodiment, the N is not greater than 32.

As an embodiment, the first information block is used to configure the n.

As an embodiment, the n is configured by RRC signaling.

As an embodiment, the n is configured for higher layer signaling.

As an embodiment, n is equal to 0.

As an embodiment, n is greater than 0.

As an embodiment, said n is not greater than 15.

As an embodiment, said n is not greater than 31.

Example 9

Embodiment 9 illustrates a schematic diagram of a relationship between the second information block and the number of PUSCHs included in the first PUSCH group according to an embodiment of the present application, as shown in fig. 9.

In embodiment 9, the second information block is used to indicate the number of PUSCHs included in the first PUSCH group.

As an embodiment, the second information block includes a first field, which is used to indicate the number of PUSCHs included in the first PUSCH group.

As an embodiment, the first field comprises 1 bit.

As an embodiment, the first field comprises 2 bits.

As an embodiment, the first field comprises 3 bits.

As an embodiment, the first field comprises 4 bits.

As an embodiment, the first field comprises no more than 8 bits.

As an embodiment, the second information block includes a first field, which is used to indicate the number of PUSCHs included in the first PUSCH group other than the target PUSCH.

As an embodiment, the second information block explicitly indicates the number of PUSCHs included in the first PUSCH group.

As an embodiment, the second information block implicitly indicates the number of PUSCHs included in the first PUSCH group.

Example 10

Embodiment 10 illustrates a schematic diagram of the relationship among the third information block, the first set of HARQ process numbers, the second set of HARQ process numbers, and HARQ process numbers of PUSCH in the first PUSCH group, as shown in fig. 10, according to an embodiment of the present application.

In embodiment 10, a third information block is used to determine a first set of HARQ process numbers and a second set of HARQ process numbers, the first set of HARQ process numbers and the second set of HARQ process numbers having no intersection; the HARQ process number of the target PUSCH belongs to the first HARQ process number set; when the second information block is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group, the second information block is used to indicate the HARQ process number of the at least one PUSCH in the first PUSCH group from the second set of HARQ process numbers.

As an embodiment, the third information block comprises physical layer signaling.

As an embodiment, the third information block comprises DCI (Downlink control information ).

As an embodiment, the third information block comprises higher layer (higher layer) signaling.

As an embodiment, the third information block comprises a MAC CE (MediumAccess Control layer Control Element ).

As an embodiment, the third information block comprises RRC (Radio Resource Control ) signaling.

As an embodiment, the third information block comprises at least one field in at least one IE (InformationElement).

As an embodiment, the third information block comprises configurable grantconfig.

As an embodiment, the third information block comprises at least one field in configurable grantconfig.

As an embodiment, the third information block comprises a parameter nrofHARQ-Processes.

As an embodiment, the third information block comprises a parameter harq-ProcID-Offset.

As an embodiment, the third information block comprises a parameter harq-ProcID-Offset2.

As an embodiment, the third information block belongs to the first information block.

As an embodiment, the third information block does not belong to the first information block.

As an embodiment, the third information block comprises the first information block.

As an embodiment, the first set of HARQ process numbers is configurable.

As an embodiment, the second set of HARQ process numbers is configurable.

As an embodiment, the third information block is used to indicate the first set of HARQ process numbers.

As an embodiment, the third information block is used to indicate the number of HARQ process numbers comprised by the first set of HARQ process numbers.

As an embodiment, the third information block is used to indicate the second set of HARQ process numbers.

As an embodiment, the third information block is used to indicate the number of HARQ process numbers comprised by the second set of HARQ process numbers.

As an embodiment, the first set of HARQ process numbers comprises { the second value, the second value +1,..the second value +the fourth value-1 }.

As an embodiment, the second set of HARQ process numbers comprises { N, n+1, & gt, n+n-1}.

Example 11

Embodiment 11 illustrates a schematic diagram of the relationship between the target reference time domain resource, the target PUSCH and the HARQ process number of the target PUSCH according to an embodiment of the present application, as shown in fig. 11.

In embodiment 11, a target reference time domain resource is associated to the target PUSCH, and a HARQ process number of the target PUSCH is associated to the target reference time domain resource.

As an embodiment, the target reference time domain resource belongs to a time domain resource occupied by the target PUSCH.

As an embodiment, the target reference time domain resource belongs to a time domain resource occupied by UL transmission corresponding to the target PUSCH.

As one embodiment, the target reference time domain resource is one time domain symbol.

As an embodiment, the target reference time domain resource is the first time domain symbol occupied by the target PUSCH.

As an embodiment, the target reference time domain resource is the first time domain symbol of UL transmission corresponding to the target PUSCH.

As an embodiment, the target reference time domain resource corresponds to a target value, the target value being equal to: a system frame number (System Frame Number, SFN) x number ofslotsperframe x number ofsymbol perslot + a slot number (slotnumber) of a frame to which the target reference time domain resource belongs in the frame to which the target reference time domain resource belongs x number of slots (symbol number) of the slot to which the target reference time domain resource belongs; the numberOfSlotsPerFrame and the numberOfSymbolsPerSlot are the number of consecutive slots per frame and the number of consecutive time domain symbols per slot, respectively.

As an embodiment, the target value is a value representing a time domain position of the target reference time domain resource.

As an embodiment, the HARQ process number of the target PUSCH is associated to the target reference time domain resource.

As an embodiment, the target reference time domain resource is used to indicate the HARQ process number of the target PUSCH.

Example 12

Embodiment 12 illustrates a schematic diagram of the relationship among the HARQ process number, the third value, the fourth value, and the second value of the target PUSCH according to an embodiment of the present application, as shown in fig. 12.

In embodiment 12, the HARQ process number of the target PUSCH is equal to a result of modulo a third value, which is associated to the target reference time domain resource, by the fourth value plus the second value.

As one embodiment, the third value is associated with the target value.

As an embodiment, the target value is used to determine the third value.

As an embodiment, the associating the third numerical value to the target reference time domain resource comprises: the third value is equal to the result of rounding down the ratio of the target value to the first period value.

As an embodiment, the fourth value is a configurable positive integer or normal number.

As an embodiment, the fourth value is equal to the number of HARQ processes granted for the configuration.

As an embodiment, the second value is a configurable non-negative integer or non-negative constant.

As an embodiment, the second value is equal to an offset (offset) for the HARQ process granted for the configuration.

As an embodiment, the fourth value is configured by the parameter nrofHARQ-Processes.

As an embodiment, the second value is configured by the parameter harq-ProcID-Offset 2.

As an embodiment, the second value is configured by the parameter harq-ProcID-Offset.

As an embodiment, the first period value is expressed in milliseconds.

As one example, the fourth value is equal to one of 1,2,3, 16.

As an embodiment, the fourth value is not greater than 16.

As an embodiment, the fourth value is not greater than 32.

As an embodiment, the fourth value is not greater than 1024.

As an embodiment, the fourth value is a positive integer.

As one embodiment, the second value is equal to one of 0,1,2,3, 15.

As an embodiment, the second value is not greater than 15.

As an embodiment, the second value is not greater than 31.

As an embodiment, the second value is not greater than 1023.

As an embodiment, the second value is a non-negative integer.

Example 13

Embodiment 13 illustrates a schematic diagram of the relationship between a first set of uplink grants, a target uplink grant, a target PUSCH, and a target index, as shown in fig. 13, according to one embodiment of the present application.

In embodiment 13, a first set of uplink grants is configured to the first node, the first set of uplink grants comprising a target uplink grant; the target PUSCH corresponds to the target uplink grant, and the target index is an ordering index of the target uplink grant in the first set of uplink grants.

As an embodiment, the third value is associated to the reference time domain resource and the target index.

As an embodiment, the associating the third numerical value to the target reference time domain resource comprises: the third value is equal to the result of rounding down the ratio of the target value to the first period value multiplied by K plus the target index.

As an embodiment, said expressing said third value associated to said reference time domain resource and said target index comprises: the third value is equal to the result of rounding down the ratio of the target value to the first period value multiplied by K plus the target index.

As an embodiment, the associating the third numerical value to the target reference time domain resource comprises: the third value is not less than the result of rounding down the ratio of the target value to the first period value multiplied by K.

As an embodiment, the K is equal to the number of uplink grants comprised by the first set of uplink grants.

As an embodiment, each PUSCH in the first PUSCH group corresponds to one uplink grant in the first set of uplink grants.

Example 14

Embodiment 14 illustrates a block diagram of the processing means in a first node device, as shown in fig. 14. In fig. 14, a first node device processing apparatus 1400 includes a first receiver 1401 and a first transmitter 1402.

As an embodiment, the first node device 1400 is a base station.

As an embodiment, the first node device 1400 is a user device.

As an embodiment, the first node device 1400 is a relay node.

As one embodiment, the first node device 1400 is an in-vehicle communication device.

As an embodiment, the first node device 1400 is a user device supporting V2X communication.

As an embodiment, the first node device 1400 is a relay node supporting V2X communication.

As an embodiment, the first node device 1400 is a user device supporting operation over a high frequency spectrum.

As one embodiment, the first node device 1400 is a user device supporting operation on a shared spectrum.

As an embodiment, the first node device 1400 is a user device supporting XR services.

As an example, the first receiver 1401 includes at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460 and the data source 467 of fig. 4 of the present application.

As an example, the first receiver 1401 includes at least the first five of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As an example, the first receiver 1401 includes at least the first four of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As an example, the first receiver 1401 includes at least one of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As one example, the first receiver 1401 includes at least two of the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As an example, the first transmitter 1402 includes at least one of the antenna 452, the transmitter 454, the multi-antenna transmitter processor 457, the transmission processor 468, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As one example, the first transmitter 1402 includes at least the first five of the antenna 452, the transmitter 454, the multi-antenna transmitter processor 457, the transmit processor 468, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As one example, the first transmitter 1402 includes at least the first four of the antenna 452, the transmitter 454, the multi-antenna transmitter processor 457, the transmit processor 468, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As one example, the first transmitter 1402 includes at least one of the antenna 452, the transmitter 454, the multi-antenna transmitter processor 457, the transmission processor 468, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As one example, the first transmitter 1402 includes at least two of the antenna 452, the transmitter 454, the multi-antenna transmitter processor 457, the transmit processor 468, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

As an embodiment, the first receiver 1401 receives a first information block; the first transmitter 1402 sends a first PUSCH group in a first time window; wherein the target PUSCH is one PUSCH included in the first PUSCH group, and the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH of the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group.

As an embodiment, when the number of PUSCHs included in the first PUSCH group is greater than a first value, the second information block is used to indicate a HARQ process number of at least one PUSCH in the first PUSCH group; when the number of PUSCHs included in the first PUSCH group is not greater than a first value, associating the HARQ process number of each PUSCH in the first PUSCH group to a reference time domain resource, and for each PUSCH in the first PUSCH group, associating the reference time domain resource with a time domain resource occupied by the PUSCH; the first value is a configurable positive integer or normal number.

As an embodiment, when the number of PUSCHs included in the first PUSCH group is greater than the first value: the second information block is used to indicate HARQ process numbers of all PUSCHs in the first PUSCH subgroup; the first PUSCH subgroup belongs to the first PUSCH group, the first PUSCH subgroup including at least one PUSCH and not including the target PUSCH.

As an embodiment, the second information block is used to indicate the number of PUSCHs included in the first PUSCH group.

As one embodiment, a third information block is used to determine a first set of HARQ process numbers and a second set of HARQ process numbers, the first set of HARQ process numbers and the second set of HARQ process numbers having no intersection; the HARQ process number of the target PUSCH belongs to the first HARQ process number set; when the second information block is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group, the second information block is used to indicate the HARQ process number of the at least one PUSCH in the first PUSCH group from the second set of HARQ process numbers.

As an embodiment, a target reference time domain resource is associated to the target PUSCH, and a HARQ process number of the target PUSCH is associated to the target reference time domain resource.

As one embodiment, a first set of uplink grants is configured to the first node, the first set of uplink grants including a target uplink grant; the target PUSCH corresponds to the target uplink grant, and a target index is an ordering index of the target uplink grant in the first set of uplink grants; the HARQ process number of the target PUSCH is associated to the reference time domain resource and the target index.

Example 15

Embodiment 15 illustrates a block diagram of the processing means in a second node device, as shown in fig. 15. In fig. 15, the second node device processing apparatus 1500 includes a second transmitter 1501 and a second receiver 1502.

As an embodiment, the second node device 1500 is a user device.

As an embodiment, the second node device 1500 is a base station.

As an embodiment, the second node device 1500 is a satellite device.

As an embodiment, the second node device 1500 is a relay node.

As an embodiment, the second node device 1500 is an in-vehicle communication device.

As an embodiment, the second node device 1500 is a user device supporting V2X communication.

As an embodiment, the second node device 1500 is a device supporting operation on a high frequency spectrum.

As an embodiment, the second node device 1500 is a device that supports operations on a shared spectrum.

As an embodiment, the second node device 1500 is a device supporting XR services.

As an embodiment, the second node device 1500 is one of a testing apparatus, a testing device, and a testing meter.

As an example, the second transmitter 1501 includes at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second transmitter 1501 includes at least the first five of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second transmitter 1501 includes at least the first four of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second transmitter 1501 includes at least three of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As one example, the second transmitter 1501 includes at least two of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second receiver 1502 includes at least one of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second receiver 1502 includes at least the first five of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second receiver 1502 includes at least the first four of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an example, the second receiver 1502 includes at least three of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As one example, the second receiver 1502 includes at least two of the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

As an embodiment, the second transmitter 1501 sends a first information block; the second receiver 1502 receives a first PUSCH group in a first time window; wherein the target PUSCH is one PUSCH included in the first PUSCH group, and the first information block is used to determine the first time window and the target PUSCH carries a second information block; the second information block includes uplink control information bits, and whether the second information block is used to indicate that a HARQ process number of at least one PUSCH of the first PUSCH group is related to the number of PUSCHs included in the first PUSCH group.

As an embodiment, a first set of uplink grants is configured to a sender of the first PUSCH group, the first set of uplink grants including a target uplink grant; the target PUSCH corresponds to the target uplink grant, and a target index is an ordering index of the target uplink grant in the first set of uplink grants; the HARQ process number of the target PUSCH is associated to the reference time domain resource and the target index.

Those of ordinary skill in the art will appreciate that all or a portion of the steps of the above-described methods may be implemented by a program that instructs associated hardware, and the program may be stored on a computer readable storage medium, such as a read-only memory, a hard disk or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment may be implemented in a hardware form or may be implemented in a software functional module form, and the application is not limited to any specific combination of software and hardware. The first node device in the application includes, but is not limited to, a mobile phone, a tablet computer, a notebook, an internet card, a low power consumption device, an eMTC device, an NB-IoT device, a vehicle-mounted communication device, an aircraft, an airplane, an unmanned aerial vehicle, a remote control airplane and other wireless communication devices. The second node device in the application includes, but is not limited to, a mobile phone, a tablet computer, a notebook, an internet card, a low power consumption device, an eMTC device, an NB-IoT device, a vehicle-mounted communication device, an aircraft, an airplane, an unmanned aerial vehicle, a remote control airplane and other wireless communication devices. The user equipment or UE or terminal in the present application includes, but is not limited to, a mobile phone, a tablet computer, a notebook, an internet card, a low power device, an eMTC device, an NB-IoT device, an on-board communication device, an aircraft, an airplane, an unmanned aerial vehicle, a remote control airplane, and other wireless communication devices. The base station equipment or base station or network side equipment in the application includes, but is not limited to, macro cell base station, micro cell base station, home base station, relay base station, eNB, gNB, transmission receiving node TRP, GNSS, relay satellite, satellite base station, air base station, testing device, testing equipment, testing instrument and the like.

It will be appreciated by those skilled in the art that the invention can be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Accordingly, the presently disclosed embodiments are considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims rather than by the foregoing description, and all changes that come within the meaning and range of equivalents are intended to be embraced therein.

Claims

1. A first node for wireless communication, comprising:

a first receiver that receives a first block of information;

a first transmitter that transmits a first PUSCH group in a first time window;

2. The first node of claim 1, wherein the second information block is used to indicate a HARQ process number for at least one PUSCH in the first PUSCH group when the number of PUSCHs included in the first PUSCH group is greater than a first value; when the number of PUSCHs included in the first PUSCH group is not greater than a first value, associating the HARQ process number of each PUSCH in the first PUSCH group to a reference time domain resource, and for each PUSCH in the first PUSCH group, associating the reference time domain resource with a time domain resource occupied by the PUSCH; the first value is a configurable positive integer or normal number.

3. The first node of claim 2, wherein when the number of PUSCHs included in the first PUSCH group is greater than the first value: the second information block is used to indicate HARQ process numbers of all PUSCHs in the first PUSCH subgroup; the first PUSCH subgroup belongs to the first PUSCH group, the first PUSCH subgroup including at least one PUSCH and not including the target PUSCH.

4. A first node according to any of claims 1-3, characterized in that the second information block is used to indicate the number of PUSCHs comprised by the first PUSCH group.

5. The first node according to any of claims 1 to 4, characterized in that a third information block is used for determining a first set of HARQ process numbers and a second set of HARQ process numbers, the first set of HARQ process numbers and the second set of HARQ process numbers being free of intersections; the HARQ process number of the target PUSCH belongs to the first HARQ process number set; when the second information block is used to indicate the HARQ process number of at least one PUSCH in the first PUSCH group, the second information block is used to indicate the HARQ process number of the at least one PUSCH in the first PUSCH group from the second set of HARQ process numbers.

6. The first node according to any of claims 1-5, characterized in that a target reference time domain resource is associated to the target PUSCH, the HARQ process number of the target PUSCH being associated to the target reference time domain resource.

7. The first node of claim 6, wherein a first set of uplink grants is configured for the first node, the first set of uplink grants comprising a target uplink grant; the target PUSCH corresponds to the target uplink grant, and a target index is an ordering index of the target uplink grant in the first set of uplink grants; the HARQ process number of the target PUSCH is associated to the reference time domain resource and the target index.

8. A second node for wireless communication, comprising: