Communication methods, communication equipment, communication systems, storage media and software products

Abstract

This disclosure relates to a communication method, communication device, communication system, storage medium, and program product. The method includes: during the transmission of a first Physical Uplink Shared Channel (PUSCH), receiving first information, the first information indicating a first Hybrid Automatic Repeat Request (HARQ) process identifier, the first HARQ process identifier being the HARQ process identifier corresponding to the first PUSCH; and stopping the transmission of the first PUSCH. In other words, after receiving the first HARQ process identifier sent by the network device, the terminal can prematurely terminate the transmission of the first PUSCH, thereby saving uplink resources.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] The Physical Uplink Shared Channel (PUSCH) is a critical wireless communication resource that allows user equipment (UE) to send data to the base station (BS). Improving PUSCH performance to enable networks to meet higher user expectations and more complex application scenarios, ultimately achieving faster, smarter, and more reliable global communication connections, is a problem that needs to be solved. Summary of the Invention

[0003] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0004] According to a first aspect of the present disclosure, a communication method is provided, the method comprising:

[0005] During the transmission of the first Physical Uplink Shared Channel (PUSCH), first information is received, which is used to indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier, and the first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH.

[0006] Stop sending the first PUSCH.

[0007] According to a second aspect of the present disclosure, a communication method is provided, the method comprising:

[0008] During the reception of the first Physical Uplink Shared Channel (PUSCH), a first message is transmitted. The first message is used to indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier. The first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH. The first HARQ process identifier is used to indicate that the transmission of the first PUSCH should be stopped.

[0009] According to a third aspect of the present disclosure, a communication method is provided for a communication system, the communication system including a terminal and a network device, the method comprising:

[0010] During the period when the network device receives the first Physical Uplink Shared Channel (PUSCH) sent by the terminal, it sends first information to the terminal. The first information is used to indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier, and the first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH.

[0011] The terminal stops sending the first PUSCH.

[0012] According to a fourth aspect of the embodiments of this disclosure, a communication device is provided that can be used to perform the methods described in an optional implementation of the first or second aspect.

[0013] According to a fifth aspect of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to perform the method described in the optional implementation of the first aspect, and the network device is configured to perform the method described in the optional implementation of the second aspect.

[0014] According to a sixth aspect of the present disclosure, a storage medium is provided that stores instructions which, when executed on a communication device, cause the communication device to perform the method as described in an optional implementation of the first or second aspect.

[0015] According to a seventh aspect of the present disclosure, a program product is provided, including at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the method described in an optional implementation of the first or second aspect.

[0016] The technical solution provided in this disclosure can produce the following beneficial effects: During the transmission of the first Physical Uplink Shared Channel (PUSCH), first information is received, the first information being used to indicate a first Hybrid Automatic Repeat Request (HARQ) process identifier, the first HARQ process identifier being the HARQ process identifier corresponding to the first PUSCH; the transmission of the first PUSCH is stopped. In other words, after the terminal receives the first HARQ process identifier sent by the network device, it can terminate the transmission of the first PUSCH in advance, thereby saving uplink resources.

[0017] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0019] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0020] Figure 1B is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure.

[0021] Figure 1C is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure.

[0022] Figure 1D is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure.

[0023] Figure 1E is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure.

[0024] Figure 1F is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure.

[0025] Figure 1G is a schematic diagram illustrating a HARQ mechanism according to an embodiment of the present disclosure.

[0026] Figure 1H is a schematic diagram of a CI according to an embodiment of the present disclosure.

[0027] Figure 1I is a schematic diagram of a CI according to an embodiment of the present disclosure.

[0028] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0029] Figure 2B is a schematic diagram of a time slot allocation according to an embodiment of the present disclosure.

[0030] Figure 2C is a schematic diagram illustrating a HARQ process identifier transmission according to an embodiment of the present disclosure.

[0031] Figure 2D is a schematic diagram illustrating a HARQ process identifier transmission according to an embodiment of the present disclosure.

[0032] Figure 2E is a schematic diagram illustrating an NDI indicator according to an embodiment of the present disclosure.

[0033] Figure 3 is a flowchart illustrating a communication method according to an embodiment of the present disclosure.

[0034] Figure 4A is a schematic diagram of the structure of the terminal proposed in an embodiment of this disclosure.

[0035] Figure 4B is a schematic diagram of the structure of the network device proposed in an embodiment of this disclosure.

[0036] Figure 5A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure.

[0037] Figure 5B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0038] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0039] In a first aspect, embodiments of this disclosure provide a communication method, the method comprising:

[0040] During the transmission of the first Physical Uplink Shared Channel (PUSCH), first information is received, which is used to indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier, and the first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH.

[0041] Stop sending the first PUSCH.

[0042] In the above embodiments, after the terminal receives the first HARQ process identifier sent by the network device, it can terminate the transmission of the first PUSCH in advance, thereby saving uplink resources.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following:

[0044] Downlink Control Information (DCI), wherein the DCI is used to indicate the identifier of the first HARQ process;

[0045] Media access control - control element MAC-CE, wherein the MAC-CE includes the first HARQ process identifier.

[0046] In the above embodiments, the network can indicate the first HARQ process identifier through DCI or MAC-CE, so that the transmission of the first PUSCH can be terminated in advance without increasing the overhead, thereby further saving resources.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the DCI indicates the first HARQ process identifier in a manner that includes at least one of the following:

[0048] The DCI includes the first HARQ process identifier;

[0049] The search space SS where the physical downlink control channel PDCCH carrying the DCI is located is associated with the first HARQ process identifier;

[0050] The control resource set CORESET containing the PDCCH carrying the DCI is associated with the first HARQ process identifier.

[0051] In the above embodiments, the DCI may include a first HARQ process identifier, or the SS or CORESET where the PDCCH carrying the DCI is located may be associated with the first HARQ process identifier, making the indication method of the first HARQ process identifier more flexible.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments,

[0053] The DCI is used to schedule the second PUSCH, the HARQ process identifier corresponding to the second PUSCH is the same as the first HARQ process identifier, and the transport block TB carried by the second PUSCH is different from the TB carried by the first PUSCH; or...

[0054] The DCI is used to schedule the Physical Downlink Shared Channel (PDSCH); or...

[0055] The DCI is a proprietary DCI format.

[0056] In the above embodiments, DCI can also be used to schedule the second PUSCH, or to schedule the PDSCH, or it can be a dedicated DCI format used to indicate the cessation of sending the first PUSCH, thereby further reducing the overhead and complexity of DCI.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the DCI is used to schedule the second PUSCH, and the method further includes:

[0058] Send the second PUSCH.

[0059] In the above embodiments, the terminal can stop sending the first PUSCH and send the second PUSCH to the network device based on the DCI sent by the network device, thereby using the saved uplink resources and improving system performance.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the DCI further includes a New Data Indicator (NDI), and the method further includes:

[0061] The NDI in the DCI is different from the NDI corresponding to the first PUSCH, thus determining that the DCI is used to schedule the second PUSCH.

[0062] In the above embodiments, the terminal can determine whether to schedule the second PUSCH based on the NDI carried in the DCI, making the scheduling of the second PUSCH simpler.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the first PUSCH is at least one of the following: PUSCH repetition type A, PUSCH repetition type B, and Trans-Time Slot Transport Block Processing (TBoMS).

[0064] In the above embodiments, when the first PUSCH is any of PUSCH repetition type A, PUSCH repetition type B, or cross-timeslot transport block processing TBoMS, it can be terminated in advance by indicating the first HARQ process identifier, thus saving uplink resources.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the first PUSCH is PUSCH repetition type A and / or TBoMS, and the first PUSCH is allocated across multiple time slots; or,

[0066] The first PUSCH is of PUSCH repetition type B, the first PUSCH is allocated on at least one time slot, and the first PUSCH includes multiple nominal repetitions or multiple actual repetitions.

[0067] Secondly, embodiments of this disclosure provide a communication method, the method comprising:

[0068] During the reception of the first Physical Uplink Shared Channel (PUSCH), a first message is transmitted. The first message is used to indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier. The first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH. The first HARQ process identifier is used to indicate that the transmission of the first PUSCH should be stopped.

[0069] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0070] Stop receiving the first PUSCH.

[0071] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes at least one of the following:

[0072] Downlink Control Information (DCI), wherein the DCI is used to indicate the identifier of the first HARQ process;

[0073] Media access control - control element MAC-CE, wherein the MAC-CE includes the first HARQ process identifier.

[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the DCI indicates the first HARQ process identifier in a manner that includes at least one of the following:

[0075] The DCI includes the first HARQ process identifier;

[0076] The search space SS where the physical downlink control channel PDCCH carrying the DCI is located is associated with the first HARQ process identifier;

[0077] The control resource set CORESET containing the PDCCH carrying the DCI is associated with the first HARQ process identifier.

[0078] In conjunction with some embodiments of the second aspect, in some embodiments,

[0079] The DCI is used to schedule the second PUSCH, the HARQ process identifier corresponding to the second PUSCH is the same as the first HARQ process identifier, and the transport block TB carried by the second PUSCH is different from the TB carried by the first PUSCH; or...

[0080] The DCI is used to schedule the Physical Downlink Shared Channel (PDSCH); or...

[0081] The DCI is a proprietary DCI format.

[0082] In conjunction with some embodiments of the second aspect, in some embodiments, the DCI is used to schedule the second PUSCH, and the method further includes:

[0083] Receive the second PUSCH.

[0084] In conjunction with some embodiments of the second aspect, in some embodiments, the DCI further includes a New Data Indicator (NDI) for determining whether to send the second PUSCH.

[0085] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0086] Based on the received first PUSCH, it is determined that the transport block TB carried on the first PUSCH can be correctly decoded.

[0087] In the above embodiments, when the network device determines that it can correctly decode the TB carried on the first PUSCH, it can send a first HARQ process identifier to the terminal so that the terminal can terminate the transmission of the first PUSCH in advance and save uplink resources.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, the first PUSCH is at least one of the following: PUSCH repetition type A, PUSCH repetition type B, and Trans-Time Slot Transport Block Processing (TBoMS).

[0089] In conjunction with some embodiments of the second aspect, in some embodiments, the first PUSCH is PUSCH repetition type A and / or TBoMS, and the first PUSCH is allocated across multiple time slots; or,

[0090] The first PUSCH is of PUSCH repetition type B, the first PUSCH is allocated on at least one time slot, and the first PUSCH includes multiple nominal repetitions or multiple actual repetitions.

[0091] Thirdly, embodiments of this disclosure provide a communication method for a communication system, the communication system including a terminal and a network device, the method comprising:

[0092] During the period when the network device receives the first Physical Uplink Shared Channel (PUSCH) sent by the terminal, it sends first information to the terminal. The first information is used to indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier, and the first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH.

[0093] The terminal stops sending the first PUSCH.

[0094] Fourthly, embodiments of this disclosure provide a terminal that may include at least one of a transceiver module and a processing module; wherein the terminal may be used to execute an optional implementation of the first aspect.

[0095] Fifthly, embodiments of this disclosure provide a network device that may include at least one of a transceiver module and a processing module; wherein the network device may be used to perform an optional implementation of the second aspect.

[0096] In a sixth aspect, embodiments of this disclosure provide a terminal that may include one or more processors; wherein the terminal may be used to execute an optional implementation of the first aspect.

[0097] In a seventh aspect, embodiments of this disclosure provide a network device that may include one or more processors; wherein the network device may be used to perform an optional implementation of the second aspect.

[0098] Eighthly, embodiments of this disclosure provide a communication system that may include: a terminal and a network device; wherein the terminal is configured to perform the method described in the optional implementation of the first aspect, and the network device is configured to perform the method described in the optional implementation of the second aspect.

[0099] In a ninth aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in an optional implementation of the first or second aspect.

[0100] In a tenth aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in an optional implementation of the first or second aspect.

[0101] In one aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in an optional implementation of the first or second aspect.

[0102] In a twelfth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described in optional implementations of the first or second aspect.

[0103] It is understood that the aforementioned terminals, network devices, communication devices, communication systems, storage media, program products, computer programs, chips, or chip systems can all be used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0104] This disclosure provides a communication method, communication device, communication system, storage medium, and program product. In some embodiments, the terms information transmission method, information processing method, and communication method can be used interchangeably.

[0105] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0106] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0107] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0108] In some embodiments, "multiple" can refer to two or more.

[0109] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0110] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0111] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0112] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0113] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0114] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0115] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0116] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0117] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0118] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0119] In some embodiments, the terms "Access Network Device (AN Device)," "Radio Access Network Device (RAN Device)," "Base Station (BS)," "Radio Base Station," "Fixed Station," "Node," "Access Point," "Transmission Point (TP)," "Reception Point (RP)," "Transmission / Reception Point (TRP)," "Panel," "Antenna Panel," "Antenna Array," "Cell," "Macro Cell," "Small Cell," "Femto Cell," "Pico Cell," "Sector," "Cell Group," "Serving Cell," "Carrier," "Component Carrier," and "Bandwidth Part (BWP)" can be used interchangeably.

[0120] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0121] In some embodiments, access network devices, core network devices, or network devices can be replaced with terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced with communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel or direct channel, and uplink link, downlink, etc., can be replaced with sidelink link or direct link.

[0122] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0123] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0124] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0125] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0126] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 may include a terminal 101 and a network device 102.

[0127] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.

[0128] In some embodiments, the access network device is, for example, a node or device that connects a terminal device to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0129] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0130] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0131] In some embodiments, the core network equipment may be a single device, multiple devices, or a group of devices. The core network may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0132] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0133] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are examples. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is an example. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0134] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0135] In some embodiments of this disclosure, 6G will inherit and extend the functionality of 5G—New Radio (NR)—bringing higher speeds, lower latency, and greater connectivity to future communication networks. In 6G, the PUSCH will play a crucial role. The PUSCH is a key wireless communication resource that allows the UE to send data to the base station.

[0136] In the development of 6G networks, the International Telecommunication Union (ITU) has defined a series of indicators and parameters to guide and evaluate the performance of 6G technology. Among these, the indicators and parameters related to 6G PUSCH include:

[0137] Peak uplink rate: The 6G PUSCH is expected to support a peak uplink rate of 500Gbps. This metric reflects the high data transmission rate requirements of 6G to support large-scale data transmission and high-bandwidth applications.

[0138] Uplink latency: The goal of 6G is to reduce uplink latency to less than 0.5 milliseconds to support real-time applications and low-latency communication. This metric requires the PUSCH to maintain extremely low latency during data transmission.

[0139] Device connections per square kilometer: 6G PUSCH needs to support 10 million device connections per square kilometer. This indicates that 6G networks will maintain stable uplink performance even with extremely high connection density.

[0140] Spectrum bandwidth: The 6G PUSCH will support spectrum bandwidths exceeding 100GHz. This wider bandwidth can provide greater data transmission capacity and improve spectrum utilization efficiency.

[0141] Energy consumption per bit: The energy efficiency target for 6G PUSCH is to reduce energy consumption per bit of data transmission by more than 10 times. This means that PUSCH will have higher energy efficiency at high data transmission rates, supporting the goal of green networks.

[0142] Resource scheduling granularity: 6G PUSCH will support finer-grained dynamic resource allocation, capable of adjusting resource allocation based on real-time network load and user demand. This will include flexible time slot allocation and spectrum allocation mechanisms.

[0143] These requirements have not only driven technological innovation but also provided a clear direction for future 6G networks. By continuously improving the performance of PUSCH, 6G networks will be able to meet higher user expectations and more complex application scenarios, ultimately achieving faster, smarter, and more reliable global communication connections.

[0144] In some embodiments, 5G NR PUSCH Time Domain Resource Allocation (TDRA) includes the following:

[0145] The network device schedules the terminal device to send PUSCH. The network device notifies the terminal device of the time-domain resources for sending the PUSCH, including: the time slot for sending the PUSCH, the start symbol of the PUSCH within the time slot, and the number of symbols in the PUSCH; wherein the symbols of the PUSCH are contiguous in the time domain. Based on these parameters, the terminal device can uniquely determine the time-domain resources for sending the PUSCH, and the network device will also receive the PUSCH sent by the terminal device on those time-domain resources.

[0146] Optionally, the network device notifies the terminal device of the slot offset (k2), start symbol (S), and allocation length (L) for sending the PUSCH. k2 determines the slot for sending the PUSCH, S determines the start symbol, and L determines the number of symbols in the PUSCH. Additionally, in some cases (e.g., PUSCH mapping type A, described later), S and L can be replaced with a Start and Length Indicator Value (SLIV). SLIV is determined based on S and L as follows: if (L-1)≤7, then SLIV=14×(L-1)+S; otherwise, SLIV=14×(14-L+1)+(14-1-S), where 0 ≤ k2 ≤ k2 ≤ k3 ≤ k4 ≤ k5 ≤ k6 ≤ k7 ≤ k2 ≤ k6 ≤ k7 ≤ k2 ≤ k6 ≤ k7 ≤ k2 ≤ k6 ≤ k2 ≤ k6 ≤ k7 ≤ k2 ≤ k6 ≤ k2 ≤ k6 ≤ k2 ≤ k6 ≤ k6 ≤ k7 ≤ k6 ... <L≤14-S。

[0147] For example, Figure 1B is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure. As shown in Figure 1B, all symbols in the downlink slot are downlink symbols, all symbols in the uplink slot are uplink symbols, the first 8 symbols in the special slot are downlink symbols, the last 2 symbols are uplink symbols, and the remaining symbols are flexible symbols. k2 indicates that the time slot for sending PUSCH is time slot #3 in Figure 1B, S indicates that the starting symbol of PUSCH is the 3rd symbol in the time slot (i.e., S=2, where S is the symbol index of the starting symbol in a time slot, and the symbol index starts counting from 0, with a value of 0 corresponding to the first symbol in the time slot, and so on, until the last symbol of the time slot), and L indicates that the number of symbols in PUSCH is 10 (i.e., L=10). Therefore, the time-domain resource allocation of PUSCH is 10 consecutive symbols starting from the 3rd symbol in time slot #3 in Figure 1B.

[0148] 5G NR PUSCH supports repetition transmission, including two repetition types: PUSCH repetition type A and PUSCH repetition type B.

[0149] PUSCH Repetition Type A: When a network device configures the PUSCH repetition type of a terminal device to PUSCH repetition type A through higher-layer parameters, the terminal device sends PUSCH using PUSCH repetition type A. The network device will indicate the repetition number – K – to the terminal device. The K repetitions are sequentially allocated across K time slots, and the K time slots use the same symbol allocation, i.e., the symbol on each time slot is determined based on S and L (or SLIV). There are two methods for determining the K time slots: physical time slot counting and available time slot counting, as detailed below:

[0150] Physical timeslot count: K consecutive timeslots starting from the timeslot indicated by k2. It's important to note that due to the conflict criteria defined in 5G NR, not all K timeslots may be used for PUSCH transmission; for example, if the symbols indicated by S and L (or SLIV) in one of the K timeslots include downlink symbols or a synchronization signal block (SSB), then PUSCH cannot be transmitted in that timeslot.

[0151] Available slot count: If the symbols indicated by S and L (or SLIV) in a slot include downlink symbols or the same SSB, then the slot cannot be used to send PUSCH; otherwise, the slot can be used to send. According to the above criteria, starting from the slot indicated by k2, each slot is judged one by one until K slots that can be used to send PUSCH are found.

[0152] For example, Figure 1C is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure. As shown in Figure 1C, PUSCH repetition type A under physical time slot count is given. Figure 1D is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure. As shown in Figure 1D, PUSCH repetition type A under available time slot count is given. Where k2, S, and L are the same as in Figure 1B, and K = 4. As shown in Figure 1C, time slots #3 to #6 are allocated to PUSCH repetition type A. In time slot #3 / 4, the symbols indicated by S and L (or SLIV) do not include downlink symbols and SSB symbols. In time slot #5 / 6, the symbols indicated by S and L (or SLIV) include downlink symbols. Therefore, the terminal device will send PUSCH in time slot #3 / 4, but will not send PUSCH in time slot #5 / 6. As shown in Figure 1D, starting from time slot #3, the first four time slots that do not include downlink symbols and SSB symbols in the symbols indicated by S and L (or SLIV) are time slots #3 / 4 / 8 / 9 in sequence. Therefore, the terminal device will send PUSCH on these four time slots.

[0153] PUSCH Repetition Type B: When a network device configures the PUSCH repetition type of a terminal device to PUSCH repetition type B through higher-layer parameters, the terminal device sends PUSCH using PUSCH repetition type B. The network device will indicate the repetition number – K – to the terminal device. The time-domain resource allocation for PUSCH repetition type B consists of two steps: the first step is to determine the nominal repetition, and the second step is to determine the actual repetition, as detailed below:

[0154] Nominal repetition: The number of nominal repetitions is K. Each nominal repetition consists of L consecutive symbols. The starting symbol of the first nominal repetition is the symbol indicated by S in the time slot indicated by k2. The second nominal repetition is the symbol following the last symbol of the first nominal repetition, and so on.

[0155] Actual repetition: A nominal repetition includes at least one actual repetition. Each actual repetition is a consecutive set of all potentially valid symbols available for PUSCH transmission within a time slot. Potentially valid symbols are symbols other than invalid symbols. Invalid symbols include downlink symbols, SSB symbols, symbols indicated by higher-layer signaling, etc. If an actual repetition includes only one symbol, it is ignored.

[0156] Furthermore, PUSCH repeat type B can only use PUSCH mapping type B, so only S and L can be used to indicate time-domain resources, and SLIV cannot be used to indicate time-domain resources.

[0157] For example, FIG1E is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure. As shown in FIG1E, PUSCH repetition type B is given, where k2 indicates time slot #3 in FIG1E, S=12, L=4, K=4. PUSCH consists of 4 nominal repeats, each containing 4 symbols. These 4 nominal repeats are contiguous in the time domain. Due to crossing time slot boundaries, nominal repeat #0 includes two actual repeats (Act #0 / 1). The 4th / 9th symbol of time slot #4 is an invalid symbol. Since the number of symbols in an actual repeat must be greater than 1, nominal repeat #1 includes one actual repeat (Act #2), located on the 5th / 6th symbol of time slot #4. Nominal repeat #2 includes one actual repeat (Act #3), located on the 7th / 8th symbol of time slot #4. Since nominal repeat #3 has no invalid symbols and does not cross time slot boundaries, nominal repeat #3 is simply one actual repeat (Act #4).

[0158] 5G NR PUSCH supports Transport Block Processing over Multiple Slots (TBoMS). For single-slot PUSCH and PUSCH repetition type A, one time slot processes one transport block (TB), meaning the transport block size (TBS) is determined based on the time-domain resources on one time slot. The TB is transmitted on one time slot (single-slot PUSCH), or the TB is repeatedly transmitted on K time slots (PUSCH repetition type A). For TBoMS, multiple time slots process one TB, meaning the TBS is determined based on the time-domain resources on multiple time slots, and the TB is transmitted on these multiple time slots. Therefore, the network device informs the terminal device of the number of time slots N for TBoMS. The terminal device determines the TBS based on the time-domain resources on N time slots and transmits the TB on N time slots. The time-domain resource allocation method for TBoMS (N time slots and symbol allocation within each time slot) is the same as for PUSCH repetition type A, but only the available time slot count can be used. TBoMS can be used in conjunction with PUSCH repetition type A. When TBoMS and PUSCH repetition type A are used in conjunction, the terminal device will determine N×K time slots according to the available time slot counting method, where K groups of N time slots are K repetitions of one TBoMS (N time slots).

[0159] For example, Figure 1F is a schematic diagram of PUSCH time-domain resource allocation according to an embodiment of the present disclosure. As shown in Figure 1F, an example of combining TBoMS and PUSCH repetition type A is given, where k2 indicates time slot #3 in Figure 1F, N=2, K=2, S=2, L=10. According to the time-domain resource allocation method of PUSCH repetition type A, TBoMS uses the same symbol allocation in each time slot, that is, the 3rd to 12th symbols of each time slot; according to the available time slot counting method, TBoMS is allocated in time slots #3 / 4 / 8 / 9, wherein the first TBoMS repetition is allocated in time slot #3 / 4, and the second TBoMS repetition is allocated in time slot #8 / 9.

[0160] In some embodiments, the 5G NR Hybrid Automatic Repeat request (HARQ) mechanism includes the following:

[0161] The HARQ mechanism consists of multiple HARQ processes supporting the Stop-and-Wait Protocol, with each process supporting one or two Data Points (TBs). Taking the above example, in the Stop-and-Wait Protocol, the terminal device stops and waits for acknowledgment after each TB transmission. This simple mechanism only requires 1 bit to indicate a positive acknowledgment (ACK) or a negative acknowledgment (NACK) for the TB. Note: If PUSCH transmission supporting Code Block Groups (CBGs) is supported, N bits are needed to indicate the ACK / NACK of N CBGs, where N represents the number of CBGs. However, because the terminal device stops after each transmission, the throughput is low. Therefore, multiple Stop-and-Wait processes are used in parallel, also known as HARQ processes. While one HARQ process is waiting for acknowledgment, the terminal device can use another HARQ process to send a TB.

[0162] Assuming a HARQ process supports one TB, after the terminal device sends a TB using this HARQ process, it waits for confirmation (ACK) before sending a new TB. Conversely, if the HARQ process waits for confirmation (NACK), the terminal device needs to retransmit the TB if it wants to use this HARQ process.

[0163] Each HARQ process has an identifier called the HARQ process ID, used to distinguish different HARQ processes. Network devices need to indicate the HARQ process ID when scheduling PUSCH transmissions from terminal devices. For example, if the PUSCH is scheduled via Downlink Control Information (DCI), the HARQ process ID needs to be included in the DCI.

[0164] On the other hand, to inform the terminal device whether to use the HARQ process to send a new data unit (TB) or retransmit the previous TB, the network device also needs to send a New Data Indicator (NDI) to the terminal device. For example, if it is a DCI-scheduled PUSCH, the DCI needs to include the NDI. The NDI corresponds one-to-one with the TB: if a HARQ process supports one TB, the network device sends one NDI to the terminal device, corresponding to that TB; if a HARQ process supports two TBs, the network device sends two NDIs to the terminal device, each corresponding to one of the two TBs. Suppose the network device instructs the terminal device to use a HARQ process to send one TB and indicates the NDI. If the NDI has flipped (from 0 to 1, or from 1 to 0) compared to the terminal device's previous use of this HARQ process to send a TB, then the terminal device is instructed to use this HARQ process to send a new TB; otherwise, the terminal device is instructed to use this HARQ process to retransmit the previous TB. Note: When a HARQ process has never been used to send a TB, the NDI defaults to 0.

[0165] Figure 1G is a schematic diagram of a HARQ mechanism according to an embodiment of the present disclosure. As shown in Figure 1G, the uplink and downlink time slot ratio is DUUUU, where D represents the downlink time slot and U represents the uplink time slot. Taking the uplink as an example, the terminal device sequentially uses a HARQ process to send one TB in each uplink time slot. In the first four U time slots, since the HARQ process has never been used, NDI is 0 by default. Therefore, NDI is 1 (i.e., NDI flips) to indicate the transmission of a new TB. Among them, TB#0 was not received correctly (NACK), while TB#1 to TB#3 were all received correctly (ACK). Therefore, in the last four U time slots, HARQ#0 is used to retransmit TB#0, where NDI is 1 (i.e., NDI is not flipped) to indicate the retransmission of the previous TB (i.e., TB#0). HARQ#1 to HARQ#3 are used to transmit TB#4 to TB#6, where NDI is 0 (i.e., NDI flips) to indicate the transmission of a new TB (i.e., TB#4 to TB#6).

[0166] In some embodiments, for DCI format 2_4: Cancellation Indicator (CI), the following is included:

[0167] In NR, to support Ultra-Reliable and Low-Latency Communications (URLLC) services, DCI format 2_4, also known as CI, is introduced to cancel PUSCH transmissions on the indicated time-frequency resources. Figure 1H is a schematic diagram of a CI according to an embodiment of this disclosure. As shown in Figure 1H, on the first downlink time slot, the DCI schedules a PUSCH repetition type A with a repetition count of 8; on the second downlink time slot, the CI indicates that the time-frequency resources of the fifth and sixth uplink time slots cannot be used to transmit PUSCH; therefore, the PUSCH transmissions on the fifth and sixth uplink time slots are canceled / dropped.

[0168] Furthermore, the time-frequency resources indicated by the DCI cannot be used to transmit new PUSCH. Figure 1I is a schematic diagram of a CI according to an embodiment of the present disclosure. As shown in Figure 1I, in the first downlink time slot, the DCI schedules a PUSCH repetition type A with a repetition count of 6; in the second downlink time slot, the CI indicates that the time-frequency resources of the fifth and sixth uplink time slots should not be used to transmit PUSCH; simultaneously, in the second downlink time slot, another DCI schedules another PUSCH to be transmitted in the fifth time slot; however, no newly scheduled PUSCH will still be transmitted in the fifth time slot.

[0169] In some embodiments, to improve the transmission efficiency of PUSCH repetition type A, PUSCH repetition type B, and TBoMS, subsequent transmissions of the above PUSCH types can be canceled via CI after TB is correctly decoded, as shown in Figures 1H and 1I. However, using CI to cancel PUSCH transmissions presents two problems. First, CI requires indicating multiple time-frequency resources on which PUSCH transmissions will be canceled. Since this indication information is designed for URLLC service, not specifically for early PUSCH termination, it is too flexible and complex, resulting in significant signaling overhead. Second, new PUSCHs cannot be scheduled on the time-frequency resources canceled by CI, causing the saved time-domain resources to be unusable and failing to improve uplink performance.

[0170] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the embodiments of the present disclosure relate to a communication method, which includes:

[0171] Step S2101: Network device 102 sends first information to terminal 101.

[0172] In some embodiments, terminal 101 receives first information sent by network device 102, but is not limited thereto. Terminal 101 may also receive first information sent by other entities, in which case step S2101 may be omitted.

[0173] In some embodiments, the terminal 101 obtains the first information from the upper layer(s), in which case step S2101 can be omitted.

[0174] Optionally, during the period when receiving the first PUSCH sent by the terminal 101, the network device 102 sends the first information to the terminal 101.

[0175] In some embodiments, the first PUSCH is at least one of the following: PUSCH repeat type A, PUSCH repeat type B, or TBoMS.

[0176] In some embodiments, when the first PUSCH is of PUSCH repetition type A and / or TBoMS, the first PUSCH is allocated on multiple time slots; when the first PUSCH is of PUSCH repetition type B, the first PUSCH is allocated on at least one time slot, and the first PUSCH includes multiple nominal repetitions or multiple actual repetitions.

[0177] In some embodiments, when the first PUSCH is of PUSCH repetition type A, the terminal 101 may send the first PUSCH using PUSCH repetition type A. The network device 102 may indicate the number of repetitions K to the terminal 101, with the K repetitions sequentially allocated to K time slots, and the K time slots using the same symbol allocation, for example, determining the symbol on each time slot based on the start symbol S and the allocation length L.

[0178] In some embodiments, when the first PUSCH is of PUSCH repetition type B, terminal 101 can send the first PUSCH using PUSCH repetition type B. Network device 102 can indicate the repetition count K to terminal 101. Based on the repetition count K, the temporal resources of PUSCH repetition type B can be determined, for example, by first determining the nominal repetition and then determining the actual repetition.

[0179] In some embodiments, when the first PUSCH is TBoMS, multiple time slots process one TB, meaning that the TB can be transmitted on multiple time slots. The network device 102 can indicate the number of time slots N of TBoMS to the terminal 101. The terminal 101 can determine the TBS based on the time domain resources on the N time slots and complete the transmission of the TB on the N time slots.

[0180] In some embodiments, the period during which terminal 101 sends the first PUSCH can be understood as the process during which terminal 101 sends the first PUSCH, that is, terminal 101 starts sending the first PUSCH, but the first PUSCH has not been completely sent.

[0181] In some embodiments, the period during which terminal 101 sends the first PUSCH can be understood as a time period, such as a first time period, which is the time period corresponding to multiple time slots allocated to the first PUSCH. For example, if the first PUSCH is allocated on K time slots, then the first time period can be the time period corresponding to time slot #0 to time slot #K-1. For example, if the time corresponding to time slot #0 is t1 and the time corresponding to time slot #K-1 is t2, then the first time period is t1 to t2.

[0182] Figure 2B is a schematic diagram of time slot allocation according to an embodiment of the present disclosure. As shown in Figure 2B, in the first downlink time slot, network device 102 schedules a first PUSCH via DCI. This first PUSCH is of PUSCH repetition type A, with a repetition count of 8. The 8 repetitions are sequentially allocated to 8 uplink time slots, and the time period encompassed by these 8 uplink time slots is the first time period. For example, the second downlink time slot in Figure 2B is the period during which network device 102 receives the first PUSCH sent by terminal 101.

[0183] In some embodiments, network device 102 can schedule a first PUSCH via DCI and send the time domain resources of the first PUSCH to terminal 101. Terminal 101 sends the first PUSCH to network device 102 according to the time domain resources indicated by network device 102.

[0184] In some embodiments, during the period when the network device 102 receives the first PUSCH sent by the terminal 101, it can determine whether it can correctly decode the TB carried on the first PUSCH based on the received first PUSCH. If the network device 102 determines based on the received first PUSCH that it can correctly decode the TB carried on the first PUSCH, it sends the first information to the terminal 101.

[0185] As shown in Figure 2B, after receiving the first PUSCH sent by the terminal 101 in the third uplink time slot, the network device 102 determines that it can correctly decode the TB carried on the first PUSCH and sends the first information to the terminal 101 in the second downlink time slot.

[0186] In some embodiments, the first information is used to indicate a first HARQ process identifier.

[0187] In some embodiments, the first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH.

[0188] In some embodiments, the HARQ process identifier is the identifier corresponding to the HARQ process, used to distinguish different HARQ processes, and different HARQ processes correspond to different HARQ process identifiers.

[0189] In some embodiments, when instructing a terminal to send a PUSCH, the network device 102 may indicate a HARQ process identifier.

[0190] In some embodiments, the first information may include at least one of the following:

[0191] DCI, which is used to indicate the identifier of the first HARQ process;

[0192] MAC-CE, which includes the identifier of the first HARQ process.

[0193] In some embodiments, network device 102 may send DCI to terminal 101, and terminal 101 may determine the first HARQ process identifier based on the DCI.

[0194] In some embodiments, the DCI indicates the first HARQ process identifier in at least one of the following ways:

[0195] The DCI includes the identifier of the first HARQ process;

[0196] The search space (SS) where the PDCCH carrying the DCI resides is associated with the identifier of the first HARQ process;

[0197] The control resource set (CORESET) where the PDCCH carrying the DCI resides is associated with the identifier of the first HARQ process.

[0198] In some embodiments, network device 102 determines that it can correctly decode the TB carried on the first PUSCH based on the received first PUSCH, and can send DCI to terminal 101, the DCI including the first HARQ process identifier.

[0199] Optionally, the DCI may include a field that indicates the identifier of the first HARQ process.

[0200] FIG. 2C is a schematic diagram showing the transmission of HARQ process identifiers according to an embodiment of the present disclosure. As shown in FIG. 2C, the network device (gNB) 102 indicates to the terminal 101 to transmit PUSCH repetition type A on the first downlink slot, with a repetition count of 8, allocated on 8 uplink slots in FIG. 2C, carrying TB#0, and the corresponding first HARQ process identifier is HARQ#0. The network device 102 can correctly decode when receiving the third first PUSCH transmission, parse out TB#0, and send DCI carrying HARQ#0 on the second downlink slot to indicate to the terminal 101 to stop transmitting the first PUSCH.

[0201] In some embodiments, when the network device 102 determines that it can correctly decode the TB carried on the first PUSCH based on the received first PUSCH, it can send DCI to the terminal 101, and the SS where the PDCCH carrying the DCI is located is associated with the first HARQ process identifier.

[0202] Optionally, M SSs can be associated with N HARQ process identifiers, and the association relationship can include at least one of the following:

[0203] N≥M, and the association between the HARQ process identifier and the SS is a one-to-one or many-to-one relationship;

[0204] N<M, and the association between the HARQ process identifier and the SS is a one-to-many relationship.

[0205] In some embodiments, one SS identifier (ID) can be associated with one HARQ process identifier (ID).

[0206] In some embodiments, the association relationship between the SSID and the HARQ process ID satisfies: HARQ process ID = mod(SS ID, M).

[0207] In some embodiments, the association relationship between the SSID and the HARQ process ID satisfies: HARQ process ID = [SS ID / N × M], where [] represents rounding up, rounding down, or rounding to the nearest integer.

[0208] In some embodiments, the association relationship between the SSID and the HARQ process ID satisfies: SSID = mod(HARQ process ID, N).

[0209] In some embodiments, the association relationship between the SSID and the HARQ process ID satisfies: SSID = [HARQ process ID / M × N], where [] represents rounding up, rounding down, or rounding to the nearest integer.

[0210] In some embodiments, if the SS is associated with a HARQ process identifier, and the network device 102 determines that it can correctly decode the TB carried on the first PUSCH according to the received first PUSCH, it may send DCI on the SS associated with the first HARQ process identifier.

[0211] In some embodiments, the network device 102 determines that it can correctly decode the TB carried on the first PUSCH according to the received first PUSCH, and may send DCI to the terminal 101. The CORESET where the PDCCH carrying the DCI is located is associated with the first HARQ process identifier.

[0212] Optionally, M CORESETs may be associated with N HARQ process identifiers, and the association relationship may include at least one of the following:

[0213] N≥M, and the association between the HARQ process identifier and the CORESET is a one-to-one association relationship or a many-to-one association relationship;

[0214] N<M, and the association between the HARQ process identifier and the CORESET is a one-to-many association relationship.

[0215] In some embodiments, one CORESET identifier (ID) may be associated with one HARQ process identifier (ID).

[0216] In some embodiments, the association relationship between the CORESET ID and the HARQ process ID satisfies: HARQ process ID = mod(CORESET ID, M).

[0217] In some embodiments, the association relationship between the CORESET ID and the HARQ process ID satisfies: HARQ process ID = [CORESET ID / N × M], where [] represents rounding up, rounding down, or rounding to the nearest integer.

[0218] In some embodiments, the association relationship between the CORESET ID and the HARQ process ID satisfies: CORESET ID = mod(HARQ process ID, N).

[0219] In some embodiments, the association relationship between the CORESET ID and the HARQ process identifier satisfies: CORESET ID = [HARQ process ID / M × N], where [] represents rounding up, rounding down, or rounding to the nearest integer.

[0220] In some embodiments, if the CORESET is associated with a HARQ process identifier, and the network device 102 determines that it can correctly decode the TB carried on the first PUSCH based on the received first PUSCH, then it can send the DCI on the CORESET associated with the first HARQ process identifier.

[0221] In some embodiments, network device 102 determines that it can correctly decode the TB carried on the first PUSCH based on the received first PUSCH, and can send MAC-CE to terminal 101, the MAC-CE including the first HARQ process identifier.

[0222] Optionally, the MAC-CE can be carried on the PDSCH.

[0223] Figure 2D is a schematic diagram illustrating HARQ process identifier transmission according to an embodiment of this disclosure. As shown in Figure 2D, network device 102 instructs terminal 101 to send PUSCH repetition type A with 8 repetitions on the first downlink time slot, allocated across the 8 uplink time slots in Figure 2D, carrying TB#0, with the corresponding first HARQ process identifier being HARQ#0. When network device 102 receives the third first PUSCH transmission, it can correctly decode and parse TB#0, and carry the first HARQ process identifier (HARQ#0) via MAC-CE on the second downlink time slot, instructing the terminal device to stop sending the first PUSCH. The MAC-CE is carried on the PDSCH, which is scheduled by the DCI on the same time slot, and the DCI is carried on the PDCCH.

[0224] In some embodiments, DCI is used to schedule a second PUSCH, the HARQ process identifier corresponding to the second PUSCH being the same as the first HARQ process identifier, and the TB carried by the second PUSCH being different from the TB carried by the first PUSCH.

[0225] In some embodiments, DCI is used to schedule PDSCH.

[0226] In some embodiments, DCI is a proprietary DCI format.

[0227] In some embodiments, the DCI is used to schedule the second PUSCH, indicating that terminal 101 needs to terminate the first PUSCH in advance and send the second PUSCH.

[0228] In some embodiments, the DCI may further include an NDI. If the NDI in the DCI is different from the NDI corresponding to the first PUSCH, then the DCI is determined to be used to schedule the second PUSCH.

[0229] In some embodiments, NDI corresponds one-to-one with TB. If a HARQ process supports one TB, the network device 102 sends an NDI to the terminal 101, which corresponds to the TB. If a HARQ process supports two TBs, the network device 102 sends two NDIs to the terminal 101, which correspond one-to-one with the two TBs respectively.

[0230] In some embodiments, network device 102 determines, based on the received first PUSCH, that it can correctly decode the TB carried on the first PUSCH, and may instruct terminal 101 to send a new TB using the first HARQ process identifier. For example, if the first PUSCH carries TB#0, and network device 102 determines, based on the received first PUSCH, that it can correctly decode TB#0, it may instruct terminal 101 to send a second PUSCH carrying TB#1 using the first HARQ process identifier.

[0231] In some embodiments, network device 102 can instruct terminal 101 to send a new TB by flipping NDI.

[0232] In some embodiments, when network device 102 instructs terminal 101 to schedule a second PUSCH, it may send a DCI to terminal 101. The DCI carries an NDI, which may be a flip of the NDI corresponding to the first PUSCH. For example, the NDI corresponding to the first PUSCH is 0, and the NDI carried in the DCI is 1; or the NDI corresponding to the first PUSCH is 1, and the NDI carried in the DCI is 0.

[0233] Figure 2E is a schematic diagram illustrating an NDI indicator according to an embodiment of the present disclosure. As shown in Figure 2E, the first HARQ process identifier is HARQ#0, and the NDI corresponding to the first PUSCH sent through HARQ#0 is 0. When the network device 102 receives the third first PUSCH transmission, it can correctly decode and parse TB#0, and send a DCI carrying HARQ#0 and NDI on the second downlink time slot, with the NDI carried by the DCI being 1. In this way, the network device 102 can instruct the terminal 101 to stop sending the first PUSCH through the DCI, and send the second PUSCH through the first HARQ process identifier, further reducing the overhead and complexity of the DCI.

[0234] In some embodiments, the DCI is used to schedule PDSCH, that is, the network device 102 instructs the terminal 101 to terminate the transmission of the first PUSCH in advance through the DCI for scheduling PDSCH. In this way, the DCI for scheduling PDSCH can instruct the terminal to terminate the transmission of the first PUSCH in advance without increasing the overhead.

[0235] In some embodiments, the HARQ process identifier corresponding to the PDSCH is indicated by the DCI. It should be understood that the HARQ process identifier corresponding to the PDSCH is unrelated to the first HARQ process identifier.

[0236] Optionally, if the DCI indicates the first HARQ process identifier in such a way that the DCI includes the first HARQ process identifier, then the DCI needs to carry two HARQ process identifiers, one for instructing terminal 101 to stop sending the first PUSCH, and the other for instructing the HARQ process of its scheduled PDSCH.

[0237] Optionally, if the DCI indicates the first HARQ process identifier in such a way that the DCI includes the first HARQ process identifier, then the DCI needs to carry two HARQ process identifiers, one for instructing terminal 101 to stop sending the first PUSCH, and the other for instructing the HARQ process of its scheduled PDSCH.

[0238] In some embodiments, the DCI is a dedicated DCI format used to instruct terminal 101 to stop sending the first PUSCH.

[0239] Step S2102: Network device 102 stops receiving the first PUSCH sent by terminal 101.

[0240] In some embodiments, steps S2102 and S2101 may be performed in an alternate order or simultaneously.

[0241] In some embodiments, network device 102 determines, based on the received first PUSCH, that it can correctly decode the TB carried on the first PUSCH and stops receiving the first PUSCH sent by terminal 101.

[0242] As shown in Figure 2C, after receiving the first PUSCH sent by terminal 101 in the third uplink time slot, network device 102 determines that it can correctly decode the TB carried on the first PUSCH and no longer needs to receive the first PUSCH. Therefore, the last 5 uplink time slots in Figure 2C stop receiving the first PUSCH.

[0243] Step S2103: Terminal 101 stops sending the first PUSCH to network device 102.

[0244] In some embodiments, after receiving the first information sent by the network device 102, the terminal 101 stops sending the first PUSCH to the network device 102.

[0245] In some embodiments, the first information received by terminal 101 is DCI, and the DCI includes a first HARQ process identifier, and the terminal stops sending the first PUSCH corresponding to the first HARQ process identifier to network device 102.

[0246] As shown in Figure 2C, when terminal 101 receives the DCI carrying HARQ#0 sent by network device 102 in the second downlink time slot, it stops sending the PUSCH corresponding to HARQ#0. No PUSCH is sent in the last 4 uplink time slots in Figure 2C.

[0247] In some embodiments, if terminal 101 detects DCI on SS and the first PUSCH corresponding to the first HARQ process identifier associated with this SS is being sent, the terminal device will stop sending the first PUSCH.

[0248] In some embodiments, if terminal 101 detects DCI on CORESET and the first PUSCH corresponding to the first HARQ process identifier associated with this CORESET is being sent, the terminal device will stop sending the first PUSCH.

[0249] In some embodiments, the first information received by terminal 101 is MAC-CE, and the MAC-CE includes a first HARQ process identifier, and the terminal stops sending the first PUSCH corresponding to the first HARQ process identifier to network device 102.

[0250] As shown in Figure 2D, when terminal 101 receives MAC-CE carrying HARQ#0 sent by network device 102 in the second downlink time slot, it stops sending the PUSCH corresponding to HARQ#0. Therefore, no PUSCH is sent in the last four uplink time slots in Figure 2D.

[0251] In some embodiments, the first information received by terminal 101 is DCI, and it is determined that the DCI is used to schedule the second PUSCH, and the first PUSCH is stopped from being sent to the network device.

[0252] In some embodiments, the first information received by terminal 101 is DCI, and it is determined that the DCI is used to schedule PDSCH, and the first PUSCH is stopped from being sent to the network device.

[0253] In some embodiments, the first information received by the terminal 101 is DCI, and the terminal determines that the DCI is a proprietary DCI format, and stops sending the first PUSCH to the network device.

[0254] Step S2104: Terminal 101 sends a second PUSCH to network device 102.

[0255] In some embodiments, terminal 101 determines that the DCI sent by network device 102 is used to schedule the second PUSCH, and sends the second PUSCH to network device 102.

[0256] In some embodiments, terminal 101 receives a DCI sent by network device 102, wherein the HARQ process identifier indicated by the DCI is the first HARQ process identifier, the DCI also carries an NDI, and the NDI carried by the DCI is different from the NDI corresponding to the first PUSCH, and sends a second PUSCH to network device 102.

[0257] For example, the HARQ process identifier indicated by the DCI is the first HARQ process identifier, and the NDI carried by the DCI is obtained by flipping the NDI corresponding to the first PUSCH. For example, the NDI carried by the DCI is 1, the NDI corresponding to the first PUSCH is 0, and the second PUSCH is sent to the network device 102.

[0258] As shown in Figure 2E, the NDI corresponding to the first PUSCH is 0. The terminal 101 receives the DCI carrying HARQ#0 and NDI sent by the network device 102 in the second downlink time slot. The NDI carried by the DCI is 1, that is, the NDI carried by the DCI has been flipped. The terminal 101 stops sending the PUSCH carrying TB#0 (first PUSCH) to the network device 102, and then sends the PUSCH carrying TB#1 (second PUSCH).

[0259] In some embodiments, the HARQ process identifier sent by terminal 101 for the second PUSCH is the first HARQ process identifier.

[0260] In some embodiments, if the DCI sent by network device 102 is not for scheduling the second PUSCH, then step S2104 can be omitted.

[0261] Using the above method, network devices can instruct terminals to terminate the transmission of the first PUSCH in advance through the first information, saving uplink resources. Alternatively, they can send the second PUSCH while instructing terminals to terminate the transmission of the first PUSCH in advance, thus merging the early termination and scheduling of the new PUSCH into a single DCI, thereby further reducing the overhead and complexity of the DCI. In particular, network devices can instruct terminals to terminate the transmission of the first PUSCH in advance through the DCI that schedules the PDSCH, further saving resources.

[0262] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0263] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0264] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0265] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0266] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0267] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.

[0268] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0269] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0270] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0271] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", and "panel" can be used interchangeably.

[0272] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0273] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0274] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0275] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0276] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0277] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0278] The methods involved in the embodiments of this disclosure may include at least one of the steps S2101 to S2104 described above. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, step S2104 may be implemented as an independent embodiment, step S2101 + step S2102 may be implemented as an independent embodiment, step S2101 + step S2103 may be implemented as an independent embodiment, step S2102 + step S2104 may be implemented as an independent embodiment, and step S2103 + step S2104 may be implemented as an independent embodiment, but are not limited thereto.

[0279] In some embodiments, the order of any two steps S2101 to S2104 can be interchanged or they can be performed simultaneously. For example, the order of steps S2101 and S2102 can be interchanged or they can be performed simultaneously, the order of steps S2102 and S2103 can be interchanged or they can be performed simultaneously, and the order of steps S2103 and S2104 can be interchanged or they can be performed simultaneously.

[0280] In some embodiments, steps S2101 to S2104 are optional, and one or more of these steps may be omitted or substituted in different embodiments. For example, steps S2101, S2102, and S2104 may be omitted.

[0281] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0282] Figure 3 is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3, the present disclosure relates to a communication method that can be executed by a terminal. The method may include:

[0283] Step S3101: Receive the first information.

[0284] The optional implementation of step S3101 can be found in the optional implementation of step S2101 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0285] Optionally, the first message may be received during the transmission of the first PUSCH.

[0286] Step S3102: Stop sending the first PUSCH.

[0287] The optional implementation of step S3102 can be found in the optional implementation of step S2103 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0288] In some embodiments, the above steps are all optional.

[0289] In some embodiments of this disclosure, a method for early termination of PUSCH transmission is proposed, specifically including:

[0290] The terminal device sends a first PUSCH to the network device. The first PUSCH is allocated on at least one time slot and corresponds to a first HARQ process identifier. The network device sends the first HARQ process identifier to the terminal device. The terminal device receives the first HARQ process identifier sent by the network device. Then, the terminal device stops sending the first PUSCH to the network device. At the same time, the network device also stops receiving the first PUSCH.

[0291] Optionally, the first PUSCH is at least one of the following: PUSCH repeat type A, PUSCH repeat type B, or TBoMS;

[0292] Optionally, if the first PUSCH is a PUSCH repetition type A or TBoMS, then the first PUSCH is allocated across multiple time slots.

[0293] Optionally, if the first PUSCH is a PUSCH repetition type B, then the first PUSCH is allocated on at least one time slot, and the first PUSCH includes multiple nominal repetitions or actual repetitions.

[0294] Optionally, the network device sends the first HARQ process identifier to the terminal device, including the following possible methods:

[0295] Method 1: The network device sends a DCI to the terminal device, the DCI including the first HARQ process identifier;

[0296] Method 2: The network device sends a DCI to the terminal device, and the SS where the Physical Downlink Control Channel (PDCCH) carrying the DCI is located is associated with the first HARQ process identifier;

[0297] Method 3: The network device sends a DCI to the terminal device, and the CORESET containing the PDCCH carrying the DCI is associated with the first HARQ process identifier;

[0298] Method 4: The network device sends a Medium Access Control (MAC) control element (CE) to the terminal device, wherein the MAC-CE includes the first HARQ process identifier.

[0299] Optionally, for methods 1 to 4, the DCI is at least one of the following:

[0300] Method a: The DCI is used to schedule the second PUSCH, and the HARQ process identifier corresponding to the second PUSCH is the first HARQ process identifier; the terminal device stops sending the first PUSCH and sends the second PUSCH.

[0301] Method b: The DCI is used to schedule PDSCH; wherein, the HARQ process identifier corresponding to the PDSCH is unrelated to the first HARQ process identifier;

[0302] Optionally, the HARQ process identifier corresponding to the PDSCH is indicated by the DCI;

[0303] Method c, wherein the DCI is a dedicated DCI format.

[0304] In some embodiments, a method for early termination of PUSCH transmission is proposed, specifically including:

[0305] Step 1: The terminal device sends the first PUSCH to the network device. The first PUSCH corresponds to the first HARQ process identifier.

[0306] Step 2: The network device sends the first HARQ process identifier to the terminal device, and the network device stops receiving the first PUSCH sent by the terminal device.

[0307] Step 3: The terminal device receives the first HARQ process identifier sent by the network device.

[0308] Step 4: The terminal device stops sending the PUSCH corresponding to the first HARQ process identifier, i.e., the first PUSCH, to the network device according to the first HARQ process identifier.

[0309] Optionally, the first PUSCH is allocated on at least one time slot.

[0310] Optionally, the first PUSCH is at least one of the following: PUSCH repeat type A, PUSCH repeat type B, or TBoMS.

[0311] Optionally, if the first PUSCH is a PUSCH repetition type A or TBoMS, then the first PUSCH is allocated on multiple time slots; if the first PUSCH is a PUSCH repetition type B, then the first PUSCH includes multiple nominal repetitions or actual repetitions.

[0312] Optionally, step 2 is executed during the period when the terminal device is sending the first PUSCH. It should be understood that for PUSCH repetition types A and TBoMS, a PUSCH includes at least one PUSCH transmission, each PUSCH transmission located on a time slot. If the network device can correctly receive the TB it carries in the first few PUSCH transmissions, the network device does not need to continue receiving the PUSCH, and can also instruct the terminal device not to send the PUSCH again.

[0313] Optionally, the network device sends the first HARQ process identifier to the terminal device, including the following possible methods:

[0314] Method 1: The network device sends a DCI to the terminal device, the DCI including the first HARQ process identifier.

[0315] It should be understood that a field is included in the DCI to indicate the HARQ process identifier.

[0316] Exemplarily, as shown in Figure 2C, the network device indicates to the terminal device to send PUSCH repetition type A in the first downlink time slot, with the repetition number being 8, allocated on 8 uplink time slots in Figure 2C, carrying TB#0, and the corresponding HARQ process identifier being HARQ#0; the network device can correctly decode when receiving the third PUSCH transmission and parse out TB#0; at this time, the network device no longer needs to continue receiving this PUSCH repetition type A, so the latter 5 uplink time slots in Figure 2C do not receive PUSCH; the network device sends DCI carrying HARQ#0 in the second downlink time slot to indicate the terminal device to stop sending this PUSCH; when the terminal device receives HARQ#0 carried in the DCI, it stops sending the PUSCH corresponding to HARQ#0, so there is no PUSCH sent on the latter 4 uplink time slots in Figure 2C.

[0317] Method 2: The network device sends DCI to the terminal device, and the SS where the PDCCH carrying the DCI is located is associated with the first HARQ process identifier.

[0318] Exemplarily, the HARQ process identifier is associated with the SS. If the network device wants to terminate the terminal device from sending a PUSCH corresponding to a HARQ process identifier, the network device will send DCI on the SS associated with this HARQ process identifier; if the terminal device detects DCI on this SS and the PUSCH corresponding to the HARQ process identifier associated with this SS is being sent, the terminal device will stop sending this PUSCH.

[0319] Optionally, the association relationship between (N) HARQ process identifiers and (M) SSs may include the following possibilities: If N≥M, the association relationship between the HARQ process identifier and the SS is a one-to-one or many-to-one association relationship; if N<M, the association relationship between the HARQ process identifier and the SS is a one-to-many association relationship.

[0320] Exemplarily:

[0321] Example 1: One SSID is associated with one HARQ process ID.

[0322] Example 2: The association relationship between the SSID and the HARQ process ID satisfies: HARQ process ID = mod(SS ID, M).

[0323] Example 3: The association relationship between the SSID and the HARQ process ID satisfies: HARQ process ID = [SS ID / N×M], where [] represents rounding up, rounding down, or rounding to the nearest integer.

[0324] Example 4: The association between SSID and HARQ process ID satisfies: SSID = mod(HARQ process ID, N).

[0325] Example 5: The association between SSID and HARQ process ID satisfies: SSID = [HARQ process ID / M × N], where [] indicates rounding up, rounding down, or rounding to the nearest integer.

[0326] Method 3: The network device sends a DCI to the terminal device, and the control resource set (CORESET) where the PDCCH carrying the DCI is located is associated with the first HARQ process identifier;

[0327] It should be understood that Method 3 is similar to Method 2, except that SS is replaced with CORESET. (Please have your agent complete the information using Method 2 as a reference.)

[0328] Method 4: The network device sends a MAC-CE to the terminal device, wherein the MAC-CE includes the first HARQ process identifier.

[0329] It should be understood that the MAC-CE is carried on the PDSCH.

[0330] For example, as shown in Figure 2D, the difference from Figure 2C is that the network device carries the HARQ process identifier via MAC-CE in the second downlink time slot, instructing the terminal device to stop sending PUSCH. Here, MAC-CE is carried on PDSCH, and PDSCH is scheduled by DCI in the same time slot, which is carried on PDCCH.

[0331] Optionally, for methods 1 to 4, the DCI is at least one of the following:

[0332] Method a: The DCI is used to schedule the second PUSCH, and the HARQ process identifier corresponding to the second PUSCH is the first HARQ process identifier; after receiving the DCI, the terminal device stops sending the first PUSCH and sends the second PUSCH.

[0333] It should be understood that the network device stops the terminal device from sending the first PUSCH by instructing the terminal device to send a second PUSCH with the same HARQ process identifier as the first PUSCH, and then sends the second PUSCH.

[0334] Optionally, the DCI also includes an NDI, where the NDI corresponding to the second PUSCH is flipped compared to the NDI corresponding to the first PUSCH. It should be understood that an NDI flip can instruct the terminal device to send a new TB without any DCI miss detection.

[0335] For example, as shown in Figure 2E, the network device instructs the terminal device to send PUSCH repetition type A on the first downlink time slot, with a repetition count of 8, allocated across the 8 uplink time slots in Figure 2E, carrying TB#0, with the corresponding HARQ process identifier being HARQ#0 and NDI=0; the network device can decode normally and parse TB#0 when it receives the third PUSCH transmission; at this time, the network device does not need to continue receiving this PUSCH repetition type A, so no PUSCH is received in the 4th uplink time slot in Figure 2E; the network device sends DCI on the second downlink time slot, instructing the terminal device to schedule another PUSCH repetition type A on the last 4 uplink time slots, and the HARQ process corresponding to this PUSCH repetition type A is also HARQ#0 (optionally, and the NDI in the DCI is flipped), then the terminal device will stop sending PUSCH repetition type A carrying TB#0, and then send PUSCH repetition type A carrying TB#1.

[0336] Method b: The DCI is used to schedule PDSCH.

[0337] Optionally, the HARQ process identifier corresponding to the PDSCH is indicated by the DCI. It should be understood that the HARQ process identifier corresponding to the PDSCH is unrelated to the first HARQ process identifier.

[0338] It should be understood that if method b is combined with method 1, the DCI needs to carry two HARQ process identifiers: one to instruct the terminal device to stop sending PUSCH, and the other to instruct the HARQ process of its scheduled PDSCH, which increases overhead. This problem can be solved if method b is combined with method 2, method 3, or method 4.

[0339] Method c: The DCI is a proprietary DCI format.

[0340] In some embodiments, early termination of PUSCH repeat type A, PUSCH repeat type B and TBoMS saves uplink resources.

[0341] In some embodiments, the early termination of PUSCH repetition type A, PUSCH repetition type B and TBoMS and the scheduling of new PUSCH are merged into a single DCI, further reducing DCI overhead and complexity.

[0342] In some embodiments, the DCI that schedules PDSCH can also terminate PUSCH repetition type A, PUSCH repetition type B and TBoMS early without increasing overhead.

[0343] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0344] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0345] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0346] Figure 4A is a schematic diagram of the structure of a terminal proposed in an embodiment of this disclosure. Terminal 4100 is used to execute any of the above methods. In some embodiments, as shown in Figure 4A, terminal 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module is used to receive first information during the transmission of a first Physical Uplink Shared Channel (PUSCH), the first information indicating a first Hybrid Automatic Repeat Request (HARQ) process identifier, the first HARQ process identifier being the HARQ process identifier corresponding to the first PUSCH; and to stop transmitting the first PUSCH. Optionally, the transceiver module is used to execute at least one of the communication steps (e.g., steps S2101, S2104, S3101, S3102, but not limited thereto) performed by terminal 4100 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to execute at least one of other steps (e.g., step S2103, but not limited thereto) performed by terminal 4100 in any of the above methods, which will not be elaborated here.

[0347] Figure 4B is a schematic diagram of the structure of a network device proposed in an embodiment of this disclosure. The network device 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the network device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module is used to send first information during the reception of a first Physical Uplink Shared Channel (PUSCH), the first information being used to indicate a first Hybrid Automatic Repeat Request (HARQ) process identifier, the first HARQ process identifier being the HARQ process identifier corresponding to the first PUSCH, and the first HARQ process identifier being used to indicate stopping the transmission of the first PUSCH. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S2101, S2104, S3101, but not limited thereto) performed by the network device 4200 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of other steps (e.g., step S2102, but not limited thereto) performed by the network device 4200 in any of the above methods, which will not be elaborated here.

[0348] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0349] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0350] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0351] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0352] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0353] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2104, S3101, S3102, but not limited thereto), and the processor 5101 performs at least one of other steps (e.g., steps S2102, S2103, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0354] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5103 and can be used to receive data and / or instructions from the memory 5103 or other devices, and can be used to send data and / or instructions to the memory 5103 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5103 and send the data and / or instructions to the processor 5101.

[0355] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0356] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of chip 5200 shown in Figure 5B, but it is not limited thereto.

[0357] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0358] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0359] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2104, S3101, S3102, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 5202 performing data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps S2102, S2103, but not limited thereto).

[0360] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0361] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0362] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0363] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, characterized in that, The method includes: During the transmission of the first Physical Uplink Shared Channel (PUSCH), first information is received, which is used to indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier, and the first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH. Stop sending the first PUSCH.

2. The method according to claim 1, characterized in that, The first information includes at least one of the following: Downlink Control Information (DCI), wherein the DCI is used to indicate the identifier of the first HARQ process; Media access control - control element MAC-CE, wherein the MAC-CE includes the first HARQ process identifier.

3. The method according to claim 2, characterized in that, The method by which the DCI indicates the identifier of the first HARQ process includes at least one of the following: The DCI includes the first HARQ process identifier; The search space SS where the physical downlink control channel PDCCH carrying the DCI is located is associated with the first HARQ process identifier; The control resource set CORESET containing the PDCCH carrying the DCI is associated with the first HARQ process identifier.

4. The method according to claim 2 or 3, characterized in that, The DCI is used to schedule the second PUSCH, the HARQ process identifier corresponding to the second PUSCH is the first HARQ process identifier, and the transport block TB carried by the second PUSCH is different from the TB carried by the first PUSCH. or, The DCI is used to schedule the Physical Downlink Shared Channel (PDSCH); or... The DCI is a proprietary DCI format.

5. The method according to claim 4, characterized in that, The DCI is used to schedule the second PUSCH, and the method further includes: Send the second PUSCH.

6. The method according to claim 5, characterized in that, The DCI includes New Data Indicator (NDI), and the method further includes: The NDI in the DCI is different from the NDI corresponding to the first PUSCH, thus determining that the DCI is used to schedule the second PUSCH.

7. The method according to any one of claims 1-6, characterized in that, The first PUSCH is at least one of the following: PUSCH repetition type A, PUSCH repetition type B, and Trans-Time Slot Transport Block Processing (TBoMS).

8. The method according to claim 7, characterized in that, The first PUSCH is of PUSCH repetition type A and / or TBoMS, and the first PUSCH is allocated across multiple time slots; or, The first PUSCH is of PUSCH repetition type B, the first PUSCH is allocated on at least one time slot, and the first PUSCH includes multiple nominal repetitions or multiple actual repetitions.

9. A communication method, characterized in that, The method includes: During the reception of the first Physical Uplink Shared Channel (PUSCH), a first message is transmitted. The first message is used to indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier. The first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH. The first HARQ process identifier is used to indicate that the transmission of the first PUSCH should be stopped.

10. The method according to claim 9, characterized in that, The method further includes: Stop receiving the first PUSCH.

11. The method according to claim 9 or 10, characterized in that, The first information includes at least one of the following: Downlink Control Information (DCI), wherein the DCI is used to indicate the identifier of the first HARQ process; Media access control - control element MAC-CE, wherein the MAC-CE includes the first HARQ process identifier.

12. The method according to claim 11, characterized in that, The method by which the DCI indicates the identifier of the first HARQ process includes at least one of the following: The DCI includes the first HARQ process identifier; The search space SS where the physical downlink control channel PDCCH carrying the DCI is located is associated with the first HARQ process identifier; The control resource set CORESET containing the PDCCH carrying the DCI is associated with the first HARQ process identifier.

13. The method according to claim 11 or 12, characterized in that, The DCI is used to schedule the second PUSCH, the HARQ process identifier corresponding to the second PUSCH is the first HARQ process identifier, and the transport block TB carried by the second PUSCH is different from the TB carried by the first PUSCH. or, The DCI is used to schedule the Physical Downlink Shared Channel (PDSCH); or... The DCI is a proprietary DCI format.

14. The method according to claim 13, characterized in that, The DCI is used to schedule the second PUSCH, and the method further includes: Receive the second PUSCH.

15. The method according to claim 14, characterized in that, The DCI also includes a New Data Indicator (NDI) used to determine whether to send the second PUSCH.

16. The method according to any one of claims 9-15, characterized in that, The method further includes: Based on the received first PUSCH, it is determined that the transport block TB carried on the first PUSCH can be correctly decoded.

17. The method according to any one of claims 9-16, characterized in that, The first PUSCH is at least one of the following: PUSCH repetition type A, PUSCH repetition type B, and Trans-Time Slot Transport Block Processing (TBoMS).

18. The method according to claim 17, characterized in that, The first PUSCH is of PUSCH repetition type A and / or TBoMS, and the first PUSCH is allocated across multiple time slots; or, The first PUSCH is of PUSCH repetition type B, the first PUSCH is allocated on at least one time slot, and the first PUSCH includes multiple nominal repetitions or multiple actual repetitions.

19. A communication method for a communication system, the communication system comprising a terminal and a network device, characterized in that, The method includes: During the period when the network device receives the first Physical Uplink Shared Channel (PUSCH) sent by the terminal, it sends first information to the terminal. The first information is used to indicate the first Hybrid Automatic Repeat Request (HARQ) process identifier, and the first HARQ process identifier is the HARQ process identifier corresponding to the first PUSCH. The terminal stops sending the first PUSCH.

20. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1-8 and 9-18.

21. A communication system, characterized in that, The device includes a terminal and a network device, wherein the terminal is configured to implement the communication method of any one of claims 1-8, and the network device is configured to implement the communication method of any one of claims 9-18.

22. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-8 and 9-18.

23. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the method according to any one of claims 1-8 and 9-18.

Images