Communication method, communication device, communication system, and storage medium

Abstract

The present disclosure provides a communication method, a communication device, a communication system, and a storage medium. The method comprises: when multi-user multiplexing transmission is performed on a physical uplink shared channel (PUSCH) on the basis of an orthogonal cover code (OCC) sequence, wherein the repetition type of the PUSCH is PUSCH repetition type B, transmitting the PUSCH on the basis of a first transmission mode or a second transmission mode, wherein the first transmission mode comprises: a time-domain unit boundary is not used to divide one nominal repetition into two actual repetitions, and the second transmission mode comprises: any repetition of the PUSCH does not cross a time-domain unit. The method of the present disclosure can prevent the orthogonality during OCC mapping from being compromised, thereby ensuring the transmission performance of the PUSCH.

Description

Communication method, communication device, communication system, storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and particularly relates to a communication method, a communication device, a communication system and a storage medium. BACKGROUND

[0002] In a non-terrestrial network (NTN) system, an orthogonal cover code (OCC) technology is introduced for a physical uplink shared channel (PUSCH) transmitted by a terminal, so as to perform multi-user multiplexing transmission of the PUSCH on the same time-frequency resource, and to realize uplink capacity enhancement.

[0003] SUMMARY

[0004] The present disclosure provides a communication method, a communication device, a communication system and a storage medium.

[0005] According to a first aspect of an embodiment of the present disclosure, a communication method is provided, executed by a terminal, comprising:

[0006] When a physical uplink shared channel (PUSCH) is multiplexed and transmitted by a terminal based on an OCC sequence, the repetition transmission type of the PUSCH is PUSCH repetition type B, and the PUSCH is transmitted based on a first transmission mode or a second transmission mode; wherein the first transmission mode comprises that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions; and the second transmission mode comprises that any one repetition transmission of the PUSCH does not cross a time domain unit.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is provided, executed by a network device, comprising:

[0008] When a physical uplink shared channel (PUSCH) is multiplexed and transmitted by a terminal based on an OCC sequence, the repetition transmission type of the PUSCH is PUSCH repetition type B, and the terminal is configured with a transmission mode of the PUSCH as a first transmission mode or a second transmission mode; wherein the first transmission mode comprises that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions; and the second transmission mode comprises that any one repetition transmission of the PUSCH does not cross a time domain unit.

[0009] determine a first receiving manner corresponding to the first sending manner, or determine a second receiving manner corresponding to the second sending manner;

[0010] receive the PUSCH based on the first receiving manner or the second receiving manner.

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

[0012] When the terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, a repetition transmission type of the PUSCH is PUSCH repetition type B, and the network device configures a sending manner of the PUSCH as a first sending manner or a second sending manner, wherein the first sending manner includes that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions, and the second sending manner includes that any one repetition transmission of the PUSCH will not cross a time domain unit.

[0013] The terminal sends the PUSCH based on the first sending manner or the second sending manner.

[0014] The network device determines a first receiving manner corresponding to the first sending manner, or determines a second receiving manner corresponding to the second sending manner.

[0015] The network device receives the PUSCH based on the first receiving manner or the second receiving manner.

[0016] According to a fourth aspect of an embodiment of the present disclosure, a terminal is provided, comprising:

[0017] A processing module is configured to, when the terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, a repetition transmission type of the PUSCH is PUSCH repetition type B, and the network device configures a sending manner of the PUSCH as a first sending manner or a second sending manner, wherein the first sending manner includes that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions, and the second sending manner includes that any one repetition transmission of the PUSCH will not cross a time domain unit.

[0018] According to a fifth aspect of an embodiment of the present disclosure, a network device is provided, comprising:

[0019] The processing module is configured to configure, for a terminal, a first transmission mode or a second transmission mode for a physical uplink shared channel (PUSCH) when the terminal performs multi-user multiplexing transmission on the PUSCH based on an orthogonal cover code (OCC) sequence, and a repetition transmission type of the PUSCH is a PUSCH repetition type B; the first transmission mode includes that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions; and the second transmission mode includes that any one repetition transmission of the PUSCH does not cross a time domain unit.

[0020] The processing module is further configured to determine a first reception mode corresponding to the first transmission mode, or determine a second reception mode corresponding to the second transmission mode.

[0021] The transceiver module is configured to receive the PUSCH based on the first reception mode or the second reception mode.

[0022] According to a sixth aspect of the embodiments of the present disclosure, a communication device is provided, including:

[0023] One or more processors;

[0024] The processor is configured to invoke instructions to cause the communication device to perform the communication method according to any one of the first aspect to the second aspect.

[0025] According to a seventh aspect of the embodiments of the present disclosure, a communication system is provided, including a terminal and a network device, wherein the terminal is configured to implement the communication method according to the first aspect, and the network device is configured to implement the communication method according to the second aspect.

[0026] According to an eighth aspect of the embodiments of the present disclosure, a storage medium is provided, and the storage medium stores instructions, when the instructions run on a communication device, causing the communication device to perform the communication method according to any one of the first aspect to the second aspect.

[0027] According to a ninth aspect, the embodiments of the present disclosure provide a program product, including a computer program, and the computer program is executed by a communication device to implement the communication method according to the first aspect and the second aspect.

[0028] According to a tenth aspect, the embodiments of the present disclosure provide a computer program, and when the computer program runs on a computer, the computer program causes the computer to perform the communication method according to the first aspect and the second aspect.

[0029] It can be understood that the terminal, network device, communication device, communication system, storage medium, program product and computer program described above are used to execute the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects achieved thereby can refer to the beneficial effects in the corresponding method, which will not be described here again. BRIEF DESCRIPTION OF DRAWINGS

[0030] The above described and / or additional aspects and advantages of the present disclosure will become apparent and are easily understood from the following description of the embodiments, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the present disclosure.

[0031] FIG. 1 is a schematic diagram of the architecture of some communication systems according to an embodiment of the present disclosure;

[0032] FIG. 2A is a schematic diagram of a communication method according to an embodiment of the present disclosure;

[0033] FIG. 2B is a schematic diagram of the structure of PUSCH in a second transmission mode according to an embodiment of the present disclosure;

[0034] FIG. 3 is a schematic diagram of a communication method according to another embodiment of the present disclosure;

[0035] FIG. 4 is a schematic diagram of a communication method according to another embodiment of the present disclosure;

[0036] FIG. 5 is a schematic diagram of a communication method according to another embodiment of the present disclosure;

[0037] FIG. 6A is a schematic diagram of a terminal according to an embodiment of the present disclosure;

[0038] FIG. 6B is a schematic diagram of a network device according to an embodiment of the present disclosure;

[0039] FIG. 7A is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0040] FIG. 7B is a schematic diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0041] The embodiments of the present disclosure propose a communication method, a communication device, a communication system and a storage medium.

[0042] In a first aspect, the embodiments of the present disclosure propose a communication method, performed by a terminal, comprising:

[0043] When a physical uplink shared channel (PUSCH) is multiplexed and transmitted by a terminal based on an orthogonal cover code (OCC) sequence, the repetition transmission type of the PUSCH is a PUSCH repetition type B, and the PUSCH is transmitted based on a first transmission manner or a second transmission manner. The first transmission manner includes that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions. The second transmission manner includes that any one repetition transmission of the PUSCH does not cross a time domain unit.

[0044] In the above embodiment, when the terminal multiplexes and transmits the PUSCH based on the OCC sequence, if the repetition transmission type of the PUSCH is the PUSCH repetition type B, the terminal transmits the PUSCH based on the first transmission manner or the second transmission manner. The first transmission manner includes that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions. The second transmission manner includes that any one repetition transmission of the PUSCH does not cross a time domain unit. Optionally, in the first transmission manner, the time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions, so the situation that the time domain unit boundary divides one nominal repetition transmission into two actual repetition transmissions with different time domain lengths does not occur. That is, even if one nominal repetition transmission crosses a time domain unit, the nominal repetition transmission is not divided into two actual repetition transmissions based on the time domain unit boundary, so that the time domain lengths between different actual repetition transmissions are the same. When the OCC sequence is mapped based on the actual repetition transmission, it can be ensured that the time domain lengths mapped by different sequence values of the OCC sequence are the same, and the orthogonality during OCC mapping is not damaged, ensuring the transmission performance of the PUSCH. In the second transmission manner, any one repetition transmission of the PUSCH does not cross a time domain unit, so the situation that the time domain unit boundary divides one nominal repetition transmission into two actual repetition transmissions with different time domain lengths does not occur. Similarly, the orthogonality during OCC mapping can be ensured not to be damaged, and the transmission performance of the PUSCH is ensured.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the second transmission manner includes that the PUSCH occupies N time domain units, the PUSCH performs S times of repetition transmission in each time domain unit, and the symbol positions occupied by the PUSCH in different time domain units are the same. S and N are positive integers, and S and N are greater than or equal to 1.

[0046] In the above embodiments, the specific sending method of the second sending mode is explained, so that the terminal can successfully send the PUSCH in the second sending mode, so as to ensure the orthogonality of OCC mapping is not destroyed, and ensure the transmission performance of the PUSCH.

[0047] In some embodiments of the first aspect, the method further comprises at least one of:

[0048] determining, based on a first parameter sent by the network device, that the sending mode of the PUSCH is the second sending mode; the first parameter being related to the OCC sequence;

[0049] determining, based on a first radio resource control (RRC) parameter sent by the network device, that the sending mode of the PUSCH is the second sending mode; the first RRC parameter being used to indicate whether the PUSCH is sent based on the second sending mode;

[0050] determining, based on a first indication signaling sent by the network device, that the sending mode of the PUSCH is the second sending mode; the first indication signaling being used to indicate that the PUSCH is sent based on the second sending mode;

[0051] determining, based on a first time domain resource allocation (TDRA) table or a second RRC parameter sent by the network device, that the sending mode of the PUSCH is the second sending mode;

[0052] determining, based on a first field of a first downlink control information (DCI) signaling sent by the network device, that the sending mode of the PUSCH is the second sending mode.

[0053] In the above embodiments, it is explained how the terminal determines the sending mode of the PUSCH to be the second sending mode, so that the terminal can successfully determine to send the PUSCH in the second sending mode, so as to ensure the orthogonality of OCC mapping is not destroyed, and ensure the transmission performance of the PUSCH.

[0054] In some embodiments of the first aspect, the method further comprises:

[0055] the sending mode of the PUSCH being the second sending mode, determining the time domain resource of the PUSCH.

[0056] the sending mode of the PUSCH being the second sending mode, determining the time domain resource of the PUSCH.

[0057] In some embodiments of the first aspect, in some embodiments, the determining the time domain resource of the PUSCH comprises at least one of:

[0058] determining a number of repetitions of the PUSCH in one time domain unit and symbol resources occupied by the PUSCH transmission;

[0059] determining a number of time domain units occupied by the PUSCH.

[0060] In some embodiments of the first aspect, in some embodiments, the determining the number of repetitions of the PUSCH in one time domain unit comprises at least one of:

[0061] determining the number of repetitions of the PUSCH in one time domain unit based on a sequence length of the OCC sequence;

[0062] determining the number of repetitions of the PUSCH in one time domain unit based on a second TDRA table and a second DCI signaling sent by the network device, wherein the second TDRA table is used to configure at least one candidate number of repetitions, and the second DCI signaling is used to indicate any candidate number of repetitions as the number of repetitions of the PUSCH in one time domain unit;

[0063] determining the number of repetitions of the PUSCH in one time domain unit based on a second RRC parameter sent by the network device.

[0064] In some embodiments of the first aspect, in some embodiments, the determining the symbol resources occupied by the PUSCH transmission in one time domain unit comprises:

[0065] determining a starting symbol position and a symbol length of the PUSCH transmission in one time domain unit based on a third TDRA table and a third DCI signaling sent by the network device, wherein the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate first length, and the third DCI signaling is used to indicate any candidate starting symbol position as the starting symbol position of the first transmission of the PUSCH in one time domain unit and any candidate first length as the symbol length corresponding to all transmissions of the PUSCH in one time domain unit; or the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate second length, and the third DCI signaling is used to indicate any candidate starting symbol position as the starting symbol position of the first transmission of the PUSCH in one time domain unit and any candidate second length as the symbol length corresponding to one transmission of the PUSCH in one time domain unit;

[0066] determine a symbol resource occupied by the PUSCH transmission in one of the time domain units based on the starting symbol position and the symbol length.

[0067] In some embodiments of the first aspect, the determining the number of time domain units occupied by the PUSCH comprises at least one of:

[0068] determining the number of time domain units occupied by the PUSCH based on a third RRC parameter sent by the network device;

[0069] determining the number of time domain units occupied by the PUSCH based on at least one of a fourth table, a fourth RRC parameter, and a fourth DCI signaling, wherein the fourth table and the fourth RRC parameter are used to configure at least one alternative value, and the fourth DCI signaling is used to indicate any alternative value as the number of time domain units occupied by the PUSCH, and wherein the fourth table is configured by the network device and / or pre-set by a protocol.

[0070] determining the number of time domain units occupied by the PUSCH based on a fifth DCI signaling sent by the network device.

[0071] In some embodiments of the first aspect, the fourth table comprises a TDRA table and / or a transmit power control (TPC) table.

[0072] In the above embodiments, it is explained how the terminal determines the time domain resource of the PUSCH in the second transmission mode, so that the terminal can successfully transmit the PUSCH in the second transmission mode based on the time domain resource, ensuring the orthogonality in OCC mapping is not destroyed, and ensuring the transmission performance of the PUSCH.

[0073] In some embodiments of the first aspect, the method further comprises any one of:

[0074] when transmitting the PUSCH, enabling an available slot counting mechanism, and transmitting the PUSCH based on the available slot counting mechanism;

[0075] when transmitting the PUSCH, transmitting the PUSCH based on the available slot counting mechanism.

[0076] In some embodiments of the first aspect, the method further comprises:

[0077] sending first information to the network device, wherein the first information is used to indicate whether the terminal supports the available slot counting mechanism;

[0078] receive second information sent by the network device, the second information being used for enabling the available slot counting mechanism.

[0079] In the above embodiments, the terminal can also send the PUSCH based on the available slot counting mechanism. Thus, when the terminal sends the PUSCH, the terminal mainly counts the available slots and does not count the unavailable slots, thereby ensuring the accuracy and effectiveness of the terminal slot counting and improving the transmission performance of the PUSCH. In addition, the terminal can avoid counting the unavailable resources, thereby saving the counting resources of the terminal.

[0080] In some embodiments of the first aspect, in some embodiments, the same redundancy version is used between different repeated transmissions in one time domain unit, and redundancy version cycling (RV cycling) is performed between different time domain units; or

[0081] the same redundancy version is used between different repeated transmissions in the first window, and RV cycling is performed between repeated transmissions in different first windows; the first window includes L repeated transmissions, and L is the sequence length of the OCC sequence; or

[0082] the same redundancy version is used between different repeated transmissions in the second window, and RV cycling is performed between repeated transmissions in different second windows; the second window includes LxB repeated transmissions, L is the sequence length of the OCC sequence, and B is a positive integer and B>1.

[0083] In the above embodiments, it is explained how the redundancy version is used when the terminal sends the PUSCH, so that the terminal can successfully send the PUSCH based on the redundancy version, thereby ensuring the transmission performance of the PUSCH.

[0084] In some embodiments of the first aspect, in some embodiments, the method further includes:

[0085] determining whether to perform frequency hopping on the PUSCH;

[0086] performing frequency hopping on the PUSCH, and determining a first frequency hopping manner;

[0087] sending the PUSCH based on the first frequency hopping manner.

[0088] In some embodiments of the first aspect, in some embodiments, the determining whether to perform frequency hopping on the PUSCH includes:

[0089] receiving sixth DCI signaling sent by the network device, the sixth DCI signaling being used for indicating whether to perform frequency hopping on the PUSCH.

[0090] In some embodiments of the first aspect, in some embodiments, the sixth DCI signaling is further used to indicate a frequency offset value between adjacent two hops.

[0091] In some embodiments of the first aspect, in some embodiments, the first frequency hopping manner comprises:

[0092] different frequency domain resources are used for the repetition transmissions in different time domain units; or

[0093] different frequency domain resources are used for the repetition transmissions in different time domain units; or

[0094] different frequency domain resources are used for the repetition transmissions in different time domain units; or

[0095] In some embodiments of the first aspect, in some embodiments, the determining the first frequency hopping manner comprises:

[0096] the repetition transmission number S of the PUSCH in one time domain unit and L satisfy S ÷ L = 2^k, k >= 1, a fifth RRC parameter sent by the receiving network device is received, the fifth RRC parameter is used to configure the first frequency hopping manner as: different frequency domain resources are used for the repetition transmissions in different time domain units, or the fifth RRC parameter is used to configure the first frequency hopping manner as: different frequency domain resources are used for the repetition transmissions in different time domain units, or the fifth RRC parameter is used to configure the first frequency hopping manner as: different frequency domain resources are used for the repetition transmissions in different time domain units.

[0097] In the above embodiments, how the terminal transmits the PUSCH by frequency hopping is explained in detail, so that the terminal can successfully transmit the PUSCH by frequency hopping, thereby reducing the interference between the PUSCHs in different time domain units and improving the transmission performance of the PUSCH.

[0098] In some embodiments of the first aspect, in some embodiments, the total repetition transmission number of the PUSCH in one time domain unit is divisible by L, L being the sequence length of the OCC sequence.

[0099] In the above embodiments, by making the total number of repeated transmissions of the PUSCH in one time domain unit divisible by L, it can be ensured that the OCC sequence is mapped to the PUSCH for an integer number of rounds of repetition mapping, thereby ensuring orthogonality in OCC mapping and improving the transmission performance of the PUSCH.

[0100] In some embodiments of the first aspect, in some embodiments, the sending the PUSCH based on the first sending mode comprises:

[0101] mapping one sequence value of the OCC sequence to one or more repeated transmissions; wherein one repeated transmission across a time domain unit boundary is mapped by the same sequence value.

[0102] In a second aspect, the embodiments of the present disclosure provide a communication method, performed by a network device, the method comprising:

[0103] When a terminal performs multi-user multiplexing sending of a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, the repetition transmission type of the PUSCH is PUSCH repetition type B, and a sending mode of the PUSCH is configured to the terminal as a first sending mode or a second sending mode; wherein the first sending mode comprises: a time domain unit boundary is not used to divide one nominal repeated transmission into two actual repeated transmissions; and the second sending mode comprises: any one repeated transmission of the PUSCH does not cross a time domain unit.

[0104] determining a first receiving mode corresponding to the first sending mode, or determining a second receiving mode corresponding to the second sending mode;

[0105] receiving the PUSCH based on the first receiving mode or the second receiving mode.

[0106] In some embodiments of the second aspect, in some embodiments, the second sending mode comprises: the PUSCH occupies N time domain units, the PUSCH performs S repeated transmissions in each time domain unit, and the symbol positions occupied by the PUSCH in different time domain units are the same; wherein S and N are positive integers, and S and N are greater than or equal to 1.

[0107] In some embodiments of the second aspect, in some embodiments, the configuring the sending mode of the PUSCH to the terminal as the second sending mode comprises at least one of:

[0108] sending a first parameter to the terminal; the first parameter is used to configure the sending mode of the PUSCH as the second sending mode, and the first parameter is related to the OCC sequence;

[0109] configuring the PUSCH repetition type B for the repetition transmission of the PUSCH;

[0110] sending a first radio resource control (RRC) parameter to the terminal, wherein the first RRC parameter is used to indicate whether the PUSCH is transmitted based on the second transmission manner;

[0111] sending a first indication signaling to the terminal, wherein the first indication signaling is used to indicate that the PUSCH is transmitted based on the second transmission manner;

[0112] sending a first time domain resource allocation (TDRA) table or a second RRC parameter to the terminal, wherein the first TDRA table or the second RRC parameter is used to determine that the transmission manner of the PUSCH is the second transmission manner;

[0113] sending a first downlink control information (DCI) signaling to the terminal, wherein a first field of the first DCI signaling is used to determine that the transmission manner of the PUSCH is the second transmission manner.

[0114] In some embodiments of the second aspect, the method further comprises at least one of the following:

[0115] sending a second TDRA table and a second DCI signaling to the terminal, wherein the second TDRA table is used to configure at least one alternative repetition transmission number, and the second DCI signaling is used to indicate any alternative repetition transmission number as the repetition transmission number of the PUSCH in one time domain unit;

[0116] sending a second RRC parameter to the terminal, wherein the second RRC parameter is used to determine the repetition transmission number of the PUSCH in one time domain unit.

[0117] In some embodiments of the second aspect, the method further comprises:

[0118] sending, to the terminal, a third TDRA table and a third DCI signaling, wherein the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate first length, and the third DCI signaling is used to indicate any candidate starting symbol position as a starting symbol position of a first PUSCH transmission in a time domain unit and indicate any candidate first length as a length of symbols corresponding to all PUSCH transmissions in the time domain unit; or the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate second length, and the third DCI signaling is used to indicate any candidate starting symbol position as a starting symbol position of a first PUSCH transmission in a time domain unit and indicate any candidate second length as a length of symbols corresponding to a PUSCH transmission in the time domain unit.

[0119] In some embodiments in combination with the second aspect, the method further comprises at least one of:

[0120] sending, to the terminal, a third RRC parameter, wherein the third RRC parameter is used to determine a number of time domain units occupied by the PUSCH.

[0121] sending, to the terminal, at least one of a fourth table, a fourth RRC parameter, and a fourth DCI signaling, wherein the fourth table and the fourth RRC parameter are used to configure at least one candidate value, and the fourth DCI signaling is used to indicate any candidate value as the number of time domain units occupied by the PUSCH.

[0122] sending, to the terminal, a fifth DCI signaling, wherein the fifth DCI signaling is used to determine the number of time domain units occupied by the PUSCH.

[0123] In some embodiments in combination with the second aspect, the fourth table comprises a TDRA table and / or a transmit power control (TPC) table.

[0124] In some embodiments in combination with the second aspect, the method further comprises:

[0125] sending, to the terminal, second information, wherein the second information is used to enable an available slot counting mechanism.

[0126] In some embodiments in combination with the second aspect, the method further comprises:

[0127] receiving, from the terminal, first information, wherein the first information is used to indicate whether the terminal supports the available slot counting mechanism.

[0128] In some embodiments of the second aspect, in some embodiments, the same redundancy version is used between different repeated transmissions within one time domain unit, and RV cycling is performed between repeated transmissions in different time domain units; or

[0129] the same redundancy version is used between different repeated transmissions within one time domain unit, and RV cycling is performed between repeated transmissions in different time domain units; the first window includes L repeated transmissions, L being the sequence length of the OCC sequence; or

[0130] the same redundancy version is used between different repeated transmissions within one time domain unit, and RV cycling is performed between repeated transmissions in different time domain units; the second window includes L repeated transmissions, L being the sequence length of the OCC sequence, and B being a positive integer, B > 1.

[0131] In some embodiments of the second aspect, in some embodiments, the method further comprises:

[0132] sending sixth DCI signaling to the terminal, the sixth DCI signaling being used to indicate whether frequency hopping is performed on the PUSCH.

[0133] In some embodiments of the second aspect, in some embodiments, the sixth DCI signaling is further used to indicate a frequency offset value between two adjacent hops.

[0134] In some embodiments of the second aspect, in some embodiments, the method further comprises:

[0135] the number of repeated transmissions S of the PUSCH within one time domain unit and L satisfy S ÷ L = 2^k, k >= 1, L being the sequence length of the OCC sequence, and a fifth RRC parameter is sent to the terminal, the fifth RRC parameter being used to configure the first frequency hopping mode as: the same frequency domain resource is used for different repeated transmissions within one time domain unit, or different frequency domain resources are used for repeated transmissions in different time domain units, or the fifth RRC parameter is used to configure the first frequency hopping mode as: the same frequency domain resource is used for different repeated transmissions within one time domain unit, or different frequency domain resources are used for repeated transmissions in different time domain units, or the fifth RRC parameter is used to configure the first frequency hopping mode as: the same frequency domain resource is used for different repeated transmissions within one time domain unit, or different frequency domain resources are used for repeated transmissions in different time domain units.

[0136] In some embodiments of the second aspect, in some embodiments, the total number of repeated transmissions of the PUSCH within one time domain unit is divisible by L, L being the sequence length of the OCC sequence.

[0137] In a third aspect, the embodiments of the present disclosure provide a communication method for a communication system, the communication system comprising a terminal and a network device, the method comprising:

[0138] When the terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, a repetition transmission type of the PUSCH is PUSCH repetition type B, and the network device configures a transmission mode of the PUSCH as a first transmission mode or a second transmission mode; wherein the first transmission mode comprises that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions; and the second transmission mode comprises that any one repetition transmission of the PUSCH does not cross a time domain unit.

[0139] The terminal transmits the PUSCH based on the first transmission mode or the second transmission mode.

[0140] The network device determines a first reception mode corresponding to the first transmission mode, or determines a second reception mode corresponding to the second transmission mode.

[0141] The network device receives the PUSCH based on the first reception mode or the second reception mode.

[0142] In a fourth aspect, the embodiments of the present disclosure provide a terminal, comprising:

[0143] A processing module is configured to, when the terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, a repetition transmission type of the PUSCH is PUSCH repetition type B, and the network device configures a transmission mode of the PUSCH as a first transmission mode or a second transmission mode; wherein the first transmission mode comprises that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions; and the second transmission mode comprises that any one repetition transmission of the PUSCH does not cross a time domain unit.

[0144] In combination with some embodiments of the fourth aspect, in some embodiments, the second transmission mode comprises that the PUSCH occupies N time domain units, the PUSCH performs S times of repetition transmission in each time domain unit, and the symbol positions occupied by the PUSCH in different time domain units are the same; wherein S and N are positive integers, and S and N are greater than or equal to 1.

[0145] In combination with some embodiments of the fourth aspect, in some embodiments, the method further comprises at least one of the following:

[0146] determine, based on a first parameter sent by the network device, the transmission manner of the PUSCH as the second transmission manner; the first parameter is related to the OCC sequence;

[0147] determine, based on the network device configuring a repetition transmission type of the PUSCH as PUSCH repetition type B, the transmission manner of the PUSCH as the second transmission manner;

[0148] determine, based on a first radio resource control (RRC) parameter sent by the network device, the transmission manner of the PUSCH as the second transmission manner; the first RRC parameter is used to indicate whether the PUSCH is sent based on the second transmission manner;

[0149] determine, based on first indication signaling sent by the network device, the transmission manner of the PUSCH as the second transmission manner; the first indication signaling is used to indicate that the PUSCH is sent based on the second transmission manner;

[0150] determine, based on a first time domain resource allocation (TDRA) table or a second RRC parameter sent by the network device, the transmission manner of the PUSCH as the second transmission manner;

[0151] determine, based on a first field of first downlink control information (DCI) signaling sent by the network device, the transmission manner of the PUSCH as the second transmission manner.

[0152] In some embodiments of the fourth aspect, the method further comprises:

[0153] the transmission manner of the PUSCH is the second transmission manner, and determining time domain resources of the PUSCH.

[0154] In some embodiments of the fourth aspect, the determining the time domain resources of the PUSCH comprises at least one of:

[0155] determining a number of repetitions of the PUSCH in a time domain unit and symbol resources occupied by the PUSCH transmission;

[0156] determining a number of time domain units occupied by the PUSCH.

[0157] In some embodiments of the fourth aspect, the determining the number of repetitions of the PUSCH in a time domain unit comprises at least one of:

[0158] determining the number of repetitions of the PUSCH in the time domain unit based on a sequence length of the OCC sequence;

[0159] determining the number of repetitions of the PUSCH in one time domain unit based on a second TDRA table and a second DCI signaling sent by the network device, wherein the second TDRA table is used to configure at least one candidate number of repetitions, and the second DCI signaling is used to indicate any candidate number of repetitions as the number of repetitions of the PUSCH in one time domain unit;

[0160] determining the number of repetitions of the PUSCH in one time domain unit based on a second RRC parameter sent by the network device.

[0161] In some embodiments in combination with the fourth aspect, in some embodiments, the determining the symbol resources occupied by the PUSCH transmission in one time domain unit comprises:

[0162] determining the starting symbol position and the symbol length of the PUSCH transmission in one time domain unit based on a third TDRA table and a third DCI signaling sent by the network device, wherein the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate first length, and the third DCI signaling is used to indicate any candidate starting symbol position as the starting symbol position of the first transmission of the PUSCH in one time domain unit and any candidate first length as the symbol length corresponding to all transmissions of the PUSCH in one time domain unit; or the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate second length, and the third DCI signaling is used to indicate any candidate starting symbol position as the starting symbol position of the first transmission of the PUSCH in one time domain unit and any candidate second length as the symbol length corresponding to one transmission of the PUSCH in one time domain unit;

[0163] determining the symbol resources occupied by the PUSCH transmission in one time domain unit based on the starting symbol position and the symbol length.

[0164] In some embodiments in combination with the fourth aspect, in some embodiments, the determining the number of time domain units occupied by the PUSCH comprises at least one of:

[0165] determining the number of time domain units occupied by the PUSCH based on a third RRC parameter sent by the network device;

[0166] determining the number of time domain units occupied by the PUSCH based on at least one of a fourth table, a fourth RRC parameter, and a fourth DCI signaling; the fourth table and the fourth RRC parameter are used to configure at least one candidate value, and the fourth DCI signaling is used to indicate any candidate value as the number of time domain units occupied by the PUSCH; wherein the fourth table is configured by a network device and / or pre-set by a protocol;

[0167] determining the number of time domain units occupied by the PUSCH based on fifth DCI signaling sent by the network device.

[0168] In some embodiments of the fourth aspect, in some embodiments, the fourth table includes a TDRA table and / or a transmit power control (TPC) table.

[0169] In some embodiments of the fourth aspect, in some embodiments, the method further includes any one of the following:

[0170] When the PUSCH is sent, an available slot counting mechanism is enabled, and the PUSCH is sent based on the available slot counting mechanism;

[0171] When the PUSCH is sent, the PUSCH is sent based on the available slot counting mechanism.

[0172] In some embodiments of the fourth aspect, in some embodiments, the method further includes:

[0173] sending first information to the network device, the first information being used to indicate whether the terminal supports the available slot counting mechanism;

[0174] receiving second information sent by the network device, the second information being used to enable the available slot counting mechanism.

[0175] In some embodiments of the fourth aspect, in some embodiments, the same redundancy version is used between different repeated transmissions within one time domain unit, and redundancy version cycling (RV cycling) is performed between different time domain units; or

[0176] the same redundancy version is used between different repeated transmissions within a first window, and RV cycling is performed between repeated transmissions of different first windows; the first window includes L repeated transmissions, and L is the sequence length of the OCC sequence; or

[0177] The same redundancy version is used between different repeated transmissions in a second window, and RV cycling is performed between repeated transmissions in different second windows; the second window includes LxB repeated transmissions, L is a sequence length of the OCC sequence, and B is a positive integer, B>1.

[0178] In some embodiments in combination with the fourth aspect, in some embodiments, the method further includes:

[0179] Determining whether to frequency hop the PUSCH;

[0180] Frequency hopping the PUSCH, and determining a first frequency hopping manner;

[0181] Transmitting the PUSCH based on the first frequency hopping manner.

[0182] In some embodiments in combination with the fourth aspect, in some embodiments, the determining whether to frequency hop the PUSCH includes:

[0183] Receiving sixth DCI signaling transmitted by the network device, the sixth DCI signaling being used to indicate whether to frequency hop the PUSCH.

[0184] In some embodiments in combination with the fourth aspect, in some embodiments, the sixth DCI signaling is further used to indicate a frequency offset value between two adjacent hops.

[0185] In some embodiments in combination with the fourth aspect, in some embodiments, the first frequency hopping manner includes:

[0186] Different repeated transmissions in one time domain unit use the same frequency domain resource, and repeated transmissions in different time domain units use different frequency domain resources; or

[0187] Different repeated transmissions in a first window use the same frequency domain resource, and repeated transmissions in different first windows use different frequency domain resources; the first window includes L repeated transmissions, L being a sequence length of the OCC sequence; or

[0188] Different repeated transmissions in a second window use the same frequency domain resource, and repeated transmissions in different second windows use different frequency domain resources; the second window includes LxB repeated transmissions, L being a sequence length of the OCC sequence, and B being a positive integer, B>1.

[0189] In some embodiments in combination with the fourth aspect, in some embodiments, the determining the first frequency hopping manner includes:

[0190] The number of repeated transmissions S of the PUSCH in one time domain unit and L satisfy S ÷ L = 2^k, k >= 1, a fifth RRC parameter sent by the network device is received, and the fifth RRC parameter is used to configure the first frequency hopping manner as: different repeated transmissions in one time domain unit use the same frequency domain resource, repeated transmissions between different time domain units use different frequency domain resources, or the fifth RRC parameter is used to configure the first frequency hopping manner as: different repeated transmissions in a first window use the same frequency domain resource, repeated transmissions between different first windows use different frequency domain resources, or the fifth RRC parameter is used to configure the first frequency hopping manner as: different repeated transmissions in a second window use the same frequency domain resource, and repeated transmissions between different second windows use different frequency domain resources.

[0191] In combination with some embodiments of the fourth aspect, in some embodiments, the total number of repeated transmissions of the PUSCH in one time domain unit is divisible by L, and L is the sequence length of the OCC sequence.

[0192] In combination with some embodiments of the fourth aspect, in some embodiments, the PUSCH is sent based on the first sending manner, including:

[0193] mapping one sequence value of the OCC sequence to one or more repeated transmissions, wherein one repeated transmission across a time domain unit boundary is mapped by the same sequence value.

[0194] In the fifth aspect, the embodiments of the present disclosure provide a network device, which is characterized by comprising:

[0195] The processing module is configured to, when a terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, the repetition type of the PUSCH is PUSCH repetition type B, and the terminal is configured with a sending manner of the PUSCH as a first sending manner or a second sending manner, wherein the first sending manner includes that a time domain unit boundary is not used to divide one nominal repeated transmission into two actual repeated transmissions, and the second sending manner includes that any repeated transmission of the PUSCH does not cross a time domain unit.

[0196] The processing module is further configured to determine a first receiving manner corresponding to the first sending manner, or determine a second receiving manner corresponding to the second sending manner.

[0197] The transceiver module is configured to receive the PUSCH based on the first receiving manner or the second receiving manner.

[0198] In some embodiments of the fifth aspect, in some embodiments, the second transmission manner comprises: the PUSCH occupies N time domain units, the PUSCH performs S times of repeated transmission in each of the time domain units, and the PUSCH occupies the same symbol position in different time domain units; wherein S and N are positive integers, and S and N are greater than or equal to 1.

[0199] In some embodiments of the fifth aspect, in some embodiments, the transmission manner of the PUSCH configured to the terminal is a second transmission manner, and the second transmission manner comprises at least one of the following:

[0200] sending a first parameter to the terminal, wherein the first parameter is used to configure the transmission manner of the PUSCH as the second transmission manner, and the first parameter is related to the OCC sequence;

[0201] configuring a repeated transmission type of the PUSCH as a PUSCH repetition type B;

[0202] sending a first radio resource control (RRC) parameter to the terminal, wherein the first RRC parameter is used to indicate whether the PUSCH is transmitted based on the second transmission manner;

[0203] sending a first indication signaling to the terminal, wherein the first indication signaling is used to indicate that the PUSCH is transmitted based on the second transmission manner;

[0204] sending a first time domain resource allocation (TDRA) table or a second RRC parameter to the terminal, wherein the first TDRA table or the second RRC parameter is used to determine that the transmission manner of the PUSCH is the second transmission manner;

[0205] sending a first downlink control information (DCI) signaling to the terminal, wherein a first field of the first DCI signaling is used to determine that the transmission manner of the PUSCH is the second transmission manner.

[0206] In some embodiments of the fifth aspect, in some embodiments, the method further comprises at least one of the following:

[0207] sending a second TDRA table and a second DCI signaling to the terminal, wherein the second TDRA table is used to configure at least one alternative repeated transmission number, and the second DCI signaling is used to indicate any alternative repeated transmission number as a repeated transmission number of the PUSCH in one time domain unit;

[0208] sending a second RRC parameter to the terminal, wherein the second RRC parameter is used to determine a repeated transmission number of the PUSCH in one time domain unit.

[0209] In some embodiments in combination with the fifth aspect, in some embodiments, the method further comprises:

[0210] sending, to the terminal, a third TDRA table and a third DCI signaling, wherein the third TDRA table is configured to configure at least one candidate starting symbol position and at least one candidate first length; the third DCI signaling is configured to indicate any candidate starting symbol position as a starting symbol position of the first PUSCH transmission within a time domain unit, and indicate any candidate first length as a symbol length corresponding to all the PUSCH transmissions within a time domain unit; or the third TDRA table is configured to configure at least one candidate starting symbol position and at least one candidate second length; the third DCI signaling is configured to indicate any candidate starting symbol position as a starting symbol position of the first PUSCH transmission within a time domain unit, and indicate any candidate second length as a symbol length corresponding to one PUSCH transmission within a time domain unit.

[0211] In some embodiments in combination with the fifth aspect, in some embodiments, the method further comprises at least one of:

[0212] sending, to the terminal, a third RRC parameter; the third RRC parameter is configured to determine a number of time domain units occupied by the PUSCH;

[0213] sending, to the terminal, at least one of a fourth table, a fourth RRC parameter, and a fourth DCI signaling; the fourth table and the fourth RRC parameter are configured to configure at least one candidate value, and the fourth DCI signaling is configured to indicate any candidate value as the number of time domain units occupied by the PUSCH;

[0214] sending, to the terminal, a fifth DCI signaling; the fifth DCI signaling is configured to determine the number of time domain units occupied by the PUSCH.

[0215] In some embodiments in combination with the fifth aspect, in some embodiments, the fourth table comprises a TDRA table and / or a transmit power control (TPC) table.

[0216] In some embodiments in combination with the fifth aspect, in some embodiments, the method further comprises:

[0217] sending, to the terminal, second information configured to enable an available slot counting mechanism.

[0218] In some embodiments in combination with the fifth aspect, in some embodiments, the method further comprises:

[0219] receive first information sent by the terminal, the first information being used for indicating whether the terminal supports the available slot counting mechanism.

[0220] In some embodiments of the fifth aspect, in some embodiments, the same redundancy version is used between different repeated transmissions within one time domain unit, and redundancy version cycling is performed between different time domain units; or

[0221] In some embodiments of the fifth aspect, in some embodiments, the same redundancy version is used between different repeated transmissions within one time domain unit, and redundancy version cycling is performed between different time domain units; or

[0222] In some embodiments of the fifth aspect, in some embodiments, the same redundancy version is used between different repeated transmissions within one time domain unit, and redundancy version cycling is performed between different time domain units; or

[0223] In some embodiments of the fifth aspect, in some embodiments, the method further comprises:

[0224] sending sixth DCI signaling to the terminal, the sixth DCI signaling being used for indicating whether frequency hopping is performed on the PUSCH.

[0225] In some embodiments of the fifth aspect, in some embodiments, the sixth DCI signaling is further used for indicating a frequency offset value between two adjacent hops.

[0226] In some embodiments of the fifth aspect, in some embodiments, the method further comprises:

[0227] In one time domain unit, the number S of repeated transmissions of the PUSCH and the sequence length L of the OCC sequence satisfy S ÷ L = 2^k, k >= 1, and a fifth RRC parameter is sent to the terminal, the fifth RRC parameter being used for configuring the first frequency hopping mode as: the same frequency domain resource is used for different repeated transmissions within one time domain unit, or different frequency domain resources are used for repeated transmissions between different time domain units, or the fifth RRC parameter is used for configuring the first frequency hopping mode as: the same frequency domain resource is used for different repeated transmissions within a first window, or different frequency domain resources are used for repeated transmissions between different first windows, or the fifth RRC parameter is used for configuring the first frequency hopping mode as: the same frequency domain resource is used for different repeated transmissions within a second window, or different frequency domain resources are used for repeated transmissions between different second windows.

[0228] In some embodiments of the fifth aspect, in some embodiments, the total number of repeated transmissions of the PUSCH in one of the time domain units is divisible by L, where L is the length of the OCC sequence.

[0229] In the sixth aspect, the embodiments of the present disclosure provide a communication device, which comprises one or more processors, one or more memories for storing instructions, wherein the processor is configured to invoke the instructions to enable the communication device to perform the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0230] In the seventh aspect, the embodiments of the present disclosure provide a communication system, which comprises a terminal and a network device, wherein the terminal is configured to perform the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to perform the method described in the second aspect and the optional implementation of the second aspect.

[0231] In the eighth aspect, the embodiments of the present disclosure provide a storage medium, which stores instructions, when the instructions are executed on a communication device, enable the communication device to perform the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0232] In the ninth aspect, the embodiments of the present disclosure provide a program product, which comprises a computer program, when the computer program is executed by a processor, enables the processor to perform the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0233] In the tenth aspect, the embodiments of the present disclosure provide a computer program, when the computer program is executed on a computer, enables the computer to perform the method described in the first aspect, the optional implementation of the first aspect, the second aspect, and the optional implementation of the second aspect.

[0234] It can be understood that the terminal, the network device, the communication device, the communication system, the storage medium, the program product, and the computer program are all used to perform the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects they can achieve can refer to the beneficial effects in the corresponding method, which will not be described here.

[0235] The embodiments of the present disclosure propose a communication method, a communication device, a communication system, and a storage medium. In some embodiments, the communication method and the information processing method, the information sending method, and the information receiving method can be replaced with each other, the communication device and the information processing device, the information sending device, and the information receiving device can be replaced with each other, and the information processing system, the communication system, the information sending system, and the information receiving system can be replaced with each other.

[0236] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing part of the steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, part or all steps of different embodiments can be combined arbitrarily, an embodiment can be combined with optional implementation of other embodiments.

[0237] In each embodiment of the present disclosure, the terms and / or descriptions between the embodiments are consistent if there is no special description and logical conflict, and can be referred to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0238] The terms used in the embodiments of the present disclosure are only for the purpose of describing the specific embodiments, and not as a limitation on the present disclosure.

[0239] In the embodiments of the present disclosure, unless otherwise specified, the elements expressed in singular form, such as "one", "a", "the", "above", "said", "preceding", "this" and the like, can represent "one and only one", and can also represent "one or more", "at least one" and the like. For example, in the case of using articles such as "a", "an", "the" and the like in English, the noun after the article can be understood as singular expression, and can also be understood as plural expression.

[0240] In the embodiments of the present disclosure, "a plurality of" means two or more.

[0241] In some embodiments, the terms "at least one of", "at least one of", "at least one of", "one or more", "a plurality of", "multiple" and the like can be replaced with each other.

[0242] The description manner such as "at least one of A, B, C, …", "A and / or B and / or C, …" and the like in the embodiments of the present disclosure includes any one of A, B, C, … existing alone, and also includes any combination of any multiple of A, B, C, …, each of which can exist alone; for example, "at least one of A, B, C" includes a case of A alone, a case of B alone, a case of C alone, a case of combination of A and B, a case of combination of A and C, a case of combination of B and C, and a case of combination of A and B and C; for example, A and / or B includes a case of A alone, a case of B alone, and a case of combination of A and B.

[0243] In some embodiments, the description manner such as "A in a case, B in another case", "in response to a case A, in response to another case B" and the like can include the following technical solutions according to the case: A is executed regardless of B, that is, A in some embodiments; B is executed regardless of A, that is, B in some embodiments; A and B are selectively executed, that is, from A and B, execution is selected in some embodiments; A and B are both executed, that is, A and B in some embodiments. When there are more branches of A, B, C and the like, it is similar to the above.

[0244] The prefix words "first", "second" and the like in the embodiments of the present disclosure are only used to distinguish different description objects, and do not constitute limitation on the position, order, priority, quantity or content of the description objects. The description of the description objects should refer to the description in the context of the claims or embodiments, and should not constitute redundant limitation because of the use of the prefix words. For example, the description object is "field", and the ordinal words before "field" in "first field" and "second field" do not limit the position or order between "fields", and "first" and "second" do not limit whether the "fields" modified thereby are in the same message or not, nor limit the order of "first field" and "second field". For another example, the description object is "level", and the ordinal words before "level" in "first level" and "second level" do not limit the priority between "levels". For another example, the quantity of the description object is not limited by the ordinal words, and can be one or more. For example, "first device", wherein the quantity of "device" can be one or more. In addition, the objects modified by different prefix words can be the same or different, for example, the description object is "device", and "first device" and "second device" can be the same device or different devices, and the types thereof can be the same or different; for another example, the description object is "information", and "first information" and "second information" can be the same information or different information, and the contents thereof can be the same or different.

[0245] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A, or indirectly indicating A.

[0246] In some embodiments, the terms "in response to", "in response to determining", "in the case of", "when", "if", "if", etc. can be replaced with each other.

[0247] 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", "above", etc. can be replaced with each other, and 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", "below", etc. can be replaced with each other.

[0248] In some embodiments, the device, etc. can be interpreted as an entity, and can also be interpreted as virtual, and the name is not limited to the name described in the embodiments. The terms "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc. can be replaced with each other.

[0249] In some embodiments, "network" can be interpreted as a device (e.g., access network device, core network device, etc.) contained in the network.

[0250] 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,” “carrier,” “component carrier,” “bandwidth part (BWP),” and the like can be used interchangeably.

[0251] 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," "client," and so on can be replaced with each other.

[0252] In some embodiments, an access network device, a core network device, or a network device can be replaced with a terminal. For example, for a structure in which communication between an access network device, a core network device, or a network device and a terminal is replaced with communication between a plurality of terminals (for example, also referred to as device-to-device (D2D), vehicle-to-everything (V2X), and so on), embodiments of the present disclosure can also be applied. In this case, a structure in which a terminal has all or part of the functions of an access network device can also be provided. Furthermore, the language of "uplink," "downlink," and so on can also be replaced with language corresponding to communication between terminals (for example, "side"). For example, an uplink channel, a downlink channel, and so on can be replaced with a side channel, and an uplink, a downlink, and so on can be replaced with a side link.

[0253] In some embodiments, a terminal can be replaced with an access network device, a core network device, or a network device. In this case, a structure in which an access network device, a core network device, or a network device has all or part of the functions of a terminal can also be provided.

[0254] In some embodiments, the data, information, etc. can be obtained in compliance with the laws and regulations of the country where the location is situated.

[0255] In some embodiments, the data, information, etc. can be obtained after obtaining the consent of the user.

[0256] In addition, each element, each row, or each column in the table of the embodiments of the present 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.

[0257] The correspondence shown in each table in the present disclosure can be configured or predefined. The values of the information in each table are merely examples, and other values can be configured, and the present disclosure is not limited thereto. When configuring the correspondence between the information and each parameter, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows in the table in the present disclosure can also not be configured. For another example, the above table can be appropriately deformed, adjusted, etc., for example, split, merged, etc. The names of the parameters shown in the titles of the above tables can also use other names understandable by the communication device, and the values or representations of the parameters can also use other values or representations understandable by the communication device. When implementing the above tables, other data structures can also be used, for example, arrays, queues, containers, stacks, linear tables, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, etc.

[0258] The predefinition in the present disclosure can be understood as defining, predefining, storing, pre-storing, pre-negotiating, pre-configuring, solidifying, or pre-burning.

[0259] FIG. 1 is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG. 1, the communication system 100 can include a terminal, a network device. Optionally, the network device described above can include at least one of an access network device, a core network device.

[0260] In some embodiments, the terminal includes at least one of a mobile phone, a wearable device, an Internet of Things (IoT) device, a Narrow Band IoT (NB-IoT) device, a communication-capable automobile, a smart automobile, a tablet (Pad), a wireless transceiver-equipped computer, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and the like, but is not limited thereto.

[0261] In some embodiments, the access network device is at least one of a node or a device that accesses a terminal to a wireless network, and can include an evolved NodeB (eNB) in a 5G communication system, a next generation eNB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an Open RAN, a Cloud RAN, a base station in other communication systems, an access node in a wireless fidelity (WiFi) system, and the like, but is not limited thereto.

[0262] In some embodiments, the technical solutions of the present disclosure can be applied to an Open RAN architecture, at this time, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0263] In some embodiments, the access network device can be composed of a central unit (CU) and a distributed unit (DU), where the CU can also be referred to as a control unit. The CU-DU structure can split the protocol layers of the access network device, and some of the protocol layers are controlled by the CU, and the rest or all of the protocol layers are distributed in the DU and controlled by the CU, but not limited thereto.

[0264] In some embodiments, the core network device can be one device including one or more network elements, or can be multiple devices or device groups including all or part of one or more network elements. The network element can be virtual or physical. The core network includes at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next-generation core (NGC), for example. Alternatively, the core network device can also be a location management function network element. Exemplarily, the location management function network element includes a location server, which can be implemented as any one of the following: a location management function (LMF), an enhanced serving mobile location center (E-SMLC), a secure user plane location (SUPL), and a SUPL location platform (SUPL LP).

[0265] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions proposed in the embodiments of the present disclosure. It can be known by those skilled in the art that, as the system architecture evolves and new business scenarios appear, the technical solutions proposed in the embodiments of the present disclosure are also applicable to similar technical problems.

[0266] The following embodiments of the present disclosure can be applied to the communication system 100 shown in FIG. 1, or part of the main bodies, but are not limited thereto. The main bodies shown in FIG. 1 are illustrative, and the communication system can include all or part of the main bodies in FIG. 1, or other main bodies other than those in FIG. 1. The number and form of each main body is arbitrary, and the connection relationship between the main bodies is illustrative. The main bodies can be connected or not connected, and the connection can be in any manner, can be direct or indirect, and can be wired or wireless.

[0267] Embodiments of the present disclosure 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), system using other communication methods, next-generation system expanded based thereon, and the like. Further, a plurality of systems can be applied in combination (for example, combination of LTE or LTE-A and 5G, and the like).

[0268] Optionally, the above-mentioned "multi-user multiplexing transmission of PUSCH (or OCC multiplexing transmission of PUSCH)" can be understood as: multiple terminals perform multiplexing transmission of PUSCH on the same time-frequency resource, for example, the PUSCHs of different terminals can correspond to different OCC sequences, when different terminals transmit PUSCHs, the OCC sequence corresponding to the PUSCH of each terminal can be used to weight the PUSCH of the terminal respectively, and each terminal can transmit the weighted PUSCH on the same time-frequency resource to the network device. When the network device receives the weighted PUSCH transmitted by each terminal on the same time-frequency resource, the PUSCH of each terminal can be determined based on the OCC sequence corresponding to the PUSCH of each terminal, so as to realize multiplexing transmission of PUSCH of multiple terminals on the same time-frequency resource.

[0269] Optionally, due to large path loss in NTN network, repetition mechanism is usually used to improve the uplink coverage of PUSCH. In some embodiments, the repetition type of PUSCH can include PUSCH repetition type A and PUSCH repetition type B. Among them, OCC multiplexing based on PUSCH repetition type B (i.e. PUSCH repetition type B like OCC multiplexing) has less impact on the protocol, and also has certain link performance improvement. Therefore, OCC multiplexing based on PUSCH repetition type B is supported to a certain extent. Optionally, when the repetition type of PUSCH is PUSCH repetition type B, the nominal repetition of PUSCH can cross the time slot, and in some embodiments, when a certain nominal repetition of PUSCH crosses the time slot, the time slot boundary will divide this nominal repetition into two actual repetitions. In some embodiments, when OCC sequence is used for multi-user multiplexing transmission of PUSCH, the OCC sequence is mapped according to the actual repetition of PUSCH. Therefore, the following problem may occur: when the time slot boundary divides a repetition into two actual repetitions with different time domain lengths, the OCC sequence is mapped based on the two actual repetitions with different time domain lengths, which will make the time domain lengths mapped by different sequence values of the OCC sequence different, resulting in the destruction of the orthogonality of OCC mapping and affecting the transmission performance of PUSCH.

[0270] Based on this, the present disclosure proposes a communication method.

[0271] FIG. 2A is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2A, the embodiment of the present disclosure relates to a communication method for the communication system 100, and the above method comprises:

[0272] Step 2101, the network device configures the terminal with a first transmission manner or a second transmission manner.

[0273] Optionally, the first transmission manner and the second transmission manner can be transmission manners of PUSCH. In some embodiments, the network device can configure the terminal with the first transmission manner or the second transmission manner when the network device determines that the PUSCH transmission of the terminal satisfies a first condition. Optionally, the first condition can include that the terminal performs multi-user multiplexing transmission on the PUSCH based on an OCC sequence, and the repetition transmission type of the PUSCH is PUSCH repetition type B. For details of “multi-user multiplexing transmission of PUSCH”, refer to the description before the embodiment of FIG. 2A.

[0274] Optionally, the first transmission manner can include that a time domain unit boundary is not used to divide one nominal repetition into two actual repetitions. In some embodiments, the time domain unit can include a slot, that is, a slot boundary is not used to divide one nominal repetition into two actual repetitions, and one actual repetition can span two adjacent slots. Optionally, for the first transmission manner, the main difference between the terminal sending the PUSCH by using the first transmission manner and the existing PUSCH repetition type B transmission manner is that the time domain unit boundary is not used to divide one nominal repetition into two actual repetitions. As for other configurations of PUSCH transmission, such as time-frequency resources of PUSCH, frequency hopping manner, OCC multiplexing manner, etc., the related configuration manners of the existing PUSCH repetition type B can be reused.

[0275] Optionally, the second sending manner described above can include that any one of the repeated transmissions of the PUSCH does not cross the time domain units, i.e., any one of the repeated transmissions of the PUSCH does not cross the time slots. In some embodiments, the second sending manner can include that the PUSCH occupies N time domain units, the PUSCH in each time domain unit is repeatedly transmitted S times, and the symbol positions occupied by the PUSCH in different time domain units are the same; wherein S and N are positive integers, and S and N are greater than or equal to 1. Optionally, FIG. 2B is a structure diagram of the PUSCH in the second sending manner according to an embodiment of the present disclosure, as shown in FIG. 2B, the PUSCH can occupy 4 time slots, the PUSCH in each time slot is repeatedly transmitted 4 times, the length of the symbol occupied by the repeated transmission of the PUSCH in one time slot can be 3 symbols, the starting symbol position of the first transmission of the PUSCH in one time slot can be the 3rd symbol in the time slot, the sequence length of the OCC sequence (or OCC-length, OCC multiplexing user number, OCC maximum multiplexing user number, etc.) can be 4, and the OCC sequence of the terminal #1 can be {1, 1, -1, -1}. Each sequence value of the OCC sequence can be mapped to one repeated transmission.

[0276] Optionally, in some embodiments, in the second sending manner, the total number of repeated transmissions of the PUSCH in one time domain unit can be divisible by L, and L is the sequence length of the OCC sequence. Optionally, the sequence length can be configured by the network device, or can be agreed by the protocol, or can be determined based on a preset value.

[0277] Optionally, in some embodiments, in the second sending manner, the total number of repeated transmissions in one time domain unit can be less than the sequence length of the OCC sequence, in which case, one OCC sequence can cover the symbols in two or more time domain units.

[0278] Optionally, in some embodiments, the method for the network device to configure the first sending manner can include that the network device sends second indication signaling to the terminal, and the second indication signaling is used to instruct the terminal to send the PUSCH in the first sending manner. Alternatively, in other embodiments, on the premise that the PUSCH transmission satisfies the first condition, if the network device does not configure the terminal to send the PUSCH in the second sending manner, the terminal defaults to send the PUSCH in the first sending manner. Wherein, the details of the first condition can be referred to the foregoing description.

[0279] Optionally, in some embodiments, the method for the network device to configure the second sending manner to the terminal can include at least one of the following:

[0280] The first kind: the network device sends the first parameter to the terminal.

[0281] Optionally, the first parameter can be related to an OCC sequence, and in some embodiments, the first parameter can include at least one of a sequence length of the OCC sequence, the OCC sequence, and a sequence value of the OCC sequence, for example.

[0282] Optionally, a first value can be agreed between the network device and the terminal in advance, and when the network device configures the terminal to send the PUSCH in the second sending manner, the network device can configure the first parameter to take the first value. Thus, after the terminal receives the first parameter, if it is determined that the first parameter takes the first value, the terminal sends the PUSCH in the second sending manner. For example, in some embodiments, if the first parameter is the sequence length of the OCC sequence, the first value can be 4, or if the first parameter is the OCC sequence, the first value can be {1, 1, -1, -1}, for example.

[0283] Secondly, the network device configures the repetition transmission type of the PUSCH to be PUSCH repetition type B.

[0284] Optionally, in some embodiments, if the network device configures the repetition transmission type of the PUSCH to be PUSCH repetition type B for the terminal, the terminal is configured to send the PUSCH in the second sending manner by default.

[0285] In some embodiments, the network device can configure the repetition transmission type of the PUSCH to be PUSCH repetition type B through dynamic authorization, such as configuring the repetition transmission type of the PUSCH to be PUSCH repetition type B through PUSCH-RepTypeIndicatorDCI0-1-16 or PUSCH-RepTypeIndicatorDCI-0-2-r16. Or, in other embodiments, the network device can configure the repetition transmission type of the PUSCH to be PUSCH repetition type B through configured authorization, such as configuring the repetition transmission type of the PUSCH to be PUSCH repetition type B through reptypeindicator-16.

[0286] It should be noted that in some embodiments, the second sending manner described above can be understood as: PUSCH repetition type A + type B, for example, the "S times of repeated transmission of PUSCH in one time domain unit" in the second sending manner can be understood as PUSCH repetition type B; the "PUSCH occupies N time domain units, and the symbol positions occupied by PUSCH in different time domain units are the same" in the second sending manner is that one time domain unit of PUSCH is repeated for N times, which can be understood as: PUSCH repetition type A. Based on this, in some embodiments, when the network device configures the repetition transmission type of PUSCH as PUSCH repetition type B in the second method described above, the terminal is configured to send PUSCH in the second sending manner by default, that is, the terminal is configured to send PUSCH in the sending manner of PUSCH repetition type A + type B by default.

[0287] Thirdly, the network device configures a first radio resource control (RRC) parameter for the terminal.

[0288] Optionally, the first RRC parameter can be used to indicate whether to send PUSCH based on the second sending manner, and the first RRC parameter can be a new RRC parameter different from an existing RRC parameter. For example, the first RRC parameter can be PUSCH-RepTypeA_TypeB. Optionally, when PUSCH-RepTypeA_TypeB is configured as {abled}, it means that the network device configures the terminal to send PUSCH in the second sending manner, and when PUSCH-RepTypeA_TypeB is configured as {enabled}, it means that the network device configures the terminal not to send PUSCH in the second sending manner.

[0289] Fourthly, the network device sends a first indication signaling to the terminal.

[0290] Optionally, the first indication signaling can be used to instruct the terminal to send PUSCH based on the second sending manner. Optionally, at least two PUSCH sending manners can be preset in a protocol, for example, the preset PUSCH sending manners can include the first sending manner, the second sending manner, and PUSCH repetition type A. Then, the network device can send the first indication signaling to the terminal to instruct the terminal to send PUSCH in the second sending manner. For example, different sending manners of PUSCH can correspond to different indication values, and the first indication signaling can carry an indication value (such as 1 or 0) corresponding to the second sending manner.

[0291] The fifth: the network device sends a first time domain resource allocation (TDRA) table or a second RRC parameter to the terminal.

[0292] Optionally, in some embodiments, the first TDRA table can include a TDRA table corresponding to PUSCH repetition type B, or can not be a TDRA table corresponding to PUSCH repetition type B, for example, can be a TDRA table corresponding to PUSCH repetition type A. Optionally, the second RRC parameter can include repK or PUSCH-AggregationFactor.

[0293] In some embodiments, when the first TDRA table includes a TDRA table corresponding to PUSCH repetition type B, if the first TDRA table contains the Numberofrepetitions field, or if the network device includes the second RRC parameter repK in the semi-static configuration for the terminal, it means that the network device configures to send the PUSCH in the second sending mode, otherwise, it means that the network device does not configure to send the PUSCH in the second sending mode; in other embodiments, when the first TDRA table is not a TDRA table corresponding to PUSCH repetition type B, if the first TDRA table contains the Numberofrepetitions field, or if the network device configures the terminal with the second RRC parameter PUSCH-AggregationFactor, it means that the network device configures to send the PUSCH in the second sending mode, otherwise, it means that the network device does not configure to send the PUSCH in the second sending mode.

[0294] It should be noted that, in some embodiments, the second method and the fifth method described above exist independently, for example, when the second method described above configures PUSCH repetition type B, the first TDRA table in the fifth method can not be a TDRA corresponding to PUSCH repetition type B, for example, it can be a TDRA table corresponding to PUSCH repetition type A, or when the second method described above configures PUSCH repetition type A, the first TDRA table in the fifth method can also be a TDRA table corresponding to PUSCH repetition type B.

[0295] The sixth method: the network device sends first downlink control information (DCI) signaling to the terminal.

[0296] Optionally, a first field of the first DCI signaling can be used to determine that the transmission mode of the PUSCH is the second transmission mode. The first field may, for example, be a TDRA field, which can be used to indicate one of the rows in a TDRA table (such as a TDRA table corresponding to PUSCH repetition type B, or a TDRA table corresponding to PUSCH repetition type A). Optionally, in some embodiments, when the row indicated by the first field contains a numberofrepetitions field and the value of the numberofrepetitions is greater than 1, it indicates that the network device configures the terminal with the second transmission mode; when the row indicated by the first field does not contain a numberofrepetitions field, or the contained numberofrepetitions has a value less than or equal to 1, it indicates that the network device does not configure the terminal with the second transmission mode.

[0297] Optionally, in some embodiments, the above six methods can be combined with each other, for example, the first method and the second method can be combined, at this time, when the network device configures the first parameter to have a first value and configures the repetition transmission type of the PUSCH to be PUSCH repetition type B, it indicates that the network device configures the terminal with the second transmission mode. Or, the above first method and the third method can be combined, at this time, when the network device configures the first parameter to have a first value and the first RRC parameter sent by the network device indicates that the PUSCH is transmitted based on the second transmission mode, it indicates that the network device configures the terminal with the second transmission mode.

[0298] Optionally, as can be known from the foregoing, the second sending manner can be understood as: PUSCH repetition type A + type B, based on which, for the first method, the third to sixth methods, if the network device configures the second sending manner, it is considered that the network device configures to send the PUSCH by using the PUSCH repetition type A + type B (i.e., the second sending manner), regardless of whether the network device configures the PUSCH repetition type B or the PUSCH repetition type A. That is, if the network device configures the second sending manner, it is considered that the network device configures to send the PUSCH by using the PUSCH repetition type A + type B (i.e., the second sending manner), regardless of whether the high-layer RRC parameter (such as: PUSCH-RepTypeIndicatorDCI0-1-16 or PUSCH-RepTypeIndicatorDCI-0-2-r16 or reptypeindicator-16) configures the PUSCH repetition type B.

[0299] Step 2102, the network device configures the time domain resource of the PUSCH for the terminal.

[0300] Optionally, when the sending manner of the PUSCH is the first sending manner, the network device can adopt the related configuration manner of the existing PUSCH repetition type B to configure the time domain resource of the PUSCH.

[0301] Optionally, when the sending manner of the PUSCH is the second sending manner, the method that the network device configures the time domain resource of the PUSCH for the terminal can include the following steps:

[0302] Step 21021: The network device configures the number of repeated transmissions of the PUSCH in one time domain unit and the symbol resource occupied by the PUSCH transmission for the terminal.

[0303] Optionally, in some embodiments, the configuration method of the number of repeated transmissions of the PUSCH in one time domain unit can include at least one of the following:

[0304] Method a: The network device configures the number of repeated transmissions of the PUSCH in one time domain unit by the sequence length of the OCC sequence.

[0305] For example, the network device can configure the terminal with a sequence length L of the OCC sequence, where the number of repeated transmissions of the PUSCH in one time domain unit can be the same as the sequence length L, or the number of repeated transmissions of the PUSCH in one time domain unit can be F times the sequence length L, F being a positive integer, or F being a positive number less than 1, such as F being 0.5, and the value of F can be agreed by a protocol and / or can be configured in advance by the network device.

[0306] Method b: the network device configures the number of repeated transmissions of the PUSCH in one time domain unit through the second TDRA table and the second DCI signaling.

[0307] Optionally, the network device can configure the terminal with the second TDRA table through RRC configuration. The second TDRA table can be used to configure at least one alternative number of repeated transmissions, and the second DCI signaling can be used to indicate any alternative number of repeated transmissions as the number of repeated transmissions of the PUSCH in one time domain unit.

[0308] For example, in some embodiments, the second TDRA table can include a TDRA table corresponding to the PUSCH repetition type B, one or more rows in the second TDRA table can respectively include an alternative number of repeated transmissions, and each row in the second TDRA table can correspond to an index value. Optionally, the second DCI signaling can indicate the index value of the row where any alternative number of repeated transmissions is located, and the terminal can determine the row corresponding to the index value indicated by the second DCI signaling from the second TDRA table, and determine the alternative number of repeated transmissions in the row as the number of repeated transmissions of the PUSCH in one time domain unit.

[0309] Method c: the network device configures the number of repeated transmissions of the PUSCH in one time domain unit through a second RRC parameter.

[0310] Optionally, the second RRC parameter can include repk, for example, and the second RRC parameter can be used to indicate the number of repeated transmissions of the PUSCH in one time domain unit.

[0311] Optionally, in some embodiments, the above-mentioned configuration method of the symbol resources occupied by the PUSCH transmission can include that the network device configures the terminal with a starting symbol position and a symbol length of the PUSCH transmission in one time domain unit, and the terminal determines the symbol resources occupied by the PUSCH transmission based on the starting symbol position and the symbol length.

[0312] Optionally, the network device can send a third TDRA table and a third DCI signaling to the terminal, wherein the third TDRA table can be used to configure at least one alternative starting symbol position and at least one alternative first length; optionally, the third DCI signaling can be used to indicate any alternative starting symbol position as the starting symbol position of the first PUSCH transmission in a time domain unit, and indicate any alternative first length as the symbol length corresponding to all PUSCH transmissions in a time domain unit; or, the third TDRA table can be used to configure at least one alternative starting symbol position and at least one alternative second length; the third DCI signaling can be used to indicate any alternative starting symbol position as the starting symbol position of the first PUSCH transmission in a time domain unit, and indicate any alternative second length as the symbol length corresponding to one PUSCH transmission in a time domain unit.

[0313] Optionally, in some embodiments, when the third DCI signaling indicates any alternative starting symbol position as the starting symbol position of the first PUSCH transmission in a time domain unit, the starting symbol position of the Zth PUSCH transmission in the same time domain unit is the ending symbol position of the (Z-1)th transmission + 1, Z≥2.

[0314] Optionally, in some embodiments, when the third DCI signaling indicates any alternative first length as the symbol length corresponding to all PUSCH transmissions in a time domain unit, the symbol length of one PUSCH transmission in a time domain unit can be: the symbol length corresponding to all PUSCH transmissions in a time domain unit ÷ the number of repeated transmissions of PUSCH in a time domain unit.

[0315] Optionally, in some embodiments, when the third DCI signaling indicates any alternative second length as the symbol length corresponding to one PUSCH transmission in a time domain unit, the symbol lengths corresponding to different PUSCH transmissions in a time domain unit are the same.

[0316] Thus, the terminal can determine the starting symbol position and the symbol length of each transmission of PUSCH in a time domain unit through the third TDRA table and the third DCI signaling, and thus can determine the symbol resources occupied by the PUSCH transmission in a time domain unit.

[0317] In some embodiments, the network device can configure the starting symbol position and the symbol length to the terminal by a start and length indicator value (SLIV), or in some other embodiments, the network device can configure the starting symbol position and the symbol length to the terminal by a start symbol, a symbol length, and / or the like. For example, in some embodiments, the network device can first configure at least one candidate SLIV to the terminal by a third TDRA table, and then the network device can indicate any one of the candidate SLIVs by a TDRA field in a third DCI signaling, and the terminal can determine the symbol resources occupied by the PUSCH transmission based on the candidate SLIV indicated by the third DCI signaling. Or, in some other embodiments, the network device can first configure at least one candidate start symbol and at least one candidate symbol length to the terminal by a third TDRA table, and then the network device can indicate any one of the candidate start symbols and any one of the candidate symbol lengths by a TDRA field in a third DCI signaling, and the terminal can determine the symbol resources occupied by the PUSCH transmission based on the candidate start symbol and the candidate symbol length indicated by the third DCI signaling. Optionally, the third TDRA table can be different from the existing TDRA table, and can be a newly defined table. Or, the third TDRA table can include a TDRA table corresponding to the PUSCH repetition type A and / or a TDRA table corresponding to the PUSCH repetition type B.

[0318] Step 21022: The network device configures the terminal with the number of time domain units occupied by the PUSCH.

[0319] Optionally, in some embodiments, the network device can configure the terminal with the number of time domain units occupied by the PUSCH by RRC configuration. For example, the network device can send a third RRC parameter to the terminal, and the third RRC parameter is used to configure the number of time domain units occupied by the PUSCH. Optionally, the third RRC parameter may, for example, include an existing RRC parameter (such as: PUSCH-AggregationFactor), and / or the third RRC parameter may, for example, include a new RRC parameter different from the existing RRC parameter.

[0320] Optionally, in some embodiments, the network device can dynamically indicate the number of time domain units occupied by the PUSCH to the terminal. Optionally, the network device can send a fourth table and a fourth DCI signaling to the terminal. Optionally, the fourth table can be multiplexed with an existing table, for example, the fourth table can include a TDRA table and / or a transmission power control (TPC) table. The fourth table can be used to configure at least one candidate value, and the fourth DCI signaling can be used to indicate any candidate value as the number of time domain units occupied by the PUSCH. For example, each candidate value in the fourth table can correspond to an index value respectively, the fourth DCI signaling can indicate the index value corresponding to any candidate value, and after receiving the fourth DCI signaling, the terminal can determine the candidate value corresponding to the index value indicated by the fourth DCI signaling as the number of time domain units occupied by the PUSCH.

[0321] Optionally, in some embodiments, a new field can be added to the fourth DCI signaling to indicate any candidate value as the number of time domain units occupied by the PUSCH, or at least part of the bits of an existing field in the fourth DCI signaling can be multiplexed to indicate any candidate value as the number of time domain units occupied by the PUSCH. Optionally, the “at least part of the bits of the existing field” can include, for example, at least one of the high several bits of the TPC field, the low several bits of the TPC field, the high several bits of the modulation and coding scheme (MCS) field, the low several bits of the MCS field, the high several bits of the TDRA field, and the low several bits of the TDRA field; or it can also be other existing fields of the fourth DCI signaling, which is not limited in the present disclosure.

[0322] It should be noted that in some embodiments, if the TDRA table is not used when configuring the number of repetitions of the PUSCH in one time domain unit, for example, if the method b is not used when configuring the number of repetitions of the PUSCH in one time domain unit, the fourth table can be a TDRA table, and the fourth table can be used to configure, in addition to the number of time domain units occupied by the PUSCH, the starting symbol position and the symbol length of the repetitions of the PUSCH in one time domain unit. Optionally, in some other embodiments, if the TDRA table is used when configuring the number of repetitions of the PUSCH in one time domain unit, for example, if the method b is used when configuring the number of repetitions of the PUSCH in one time domain unit, the fourth table can be used to configure at least one of the following: the number of repetitions of the PUSCH in one time domain unit, the number of time domain units occupied by the PUSCH, and the starting symbol position and the symbol length of the repetitions of the PUSCH in one time domain unit.

[0323] Optionally, in some embodiments, when the fourth table is a TPC table, the network device can also not send the fourth table, which can be preset by a protocol.

[0324] Optionally, in yet some embodiments, the network device can also dynamically indicate the number of time domain units occupied by the PUSCH to the terminal through a fourth RRC parameter and a fourth DCI signaling. The fourth RRC parameter can be an existing RRC parameter or a new RRC parameter, and the fourth RRC parameter can be used to configure at least one alternative value, and the fourth DCI signaling can be used to indicate any alternative value as the number of time domain units occupied by the PUSCH. For example, the fourth RRC parameter can be used to configure a list, which can include at least one alternative value, and each alternative value can correspond to an index value, and the fourth DCI signaling can indicate the index value corresponding to any alternative value, and after receiving the fourth DCI signaling, the terminal can determine the alternative value corresponding to the index value indicated by the fourth DCI signaling as the number of time domain units occupied by the PUSCH. The method of how the fourth DCI signaling indicates the index value corresponding to any alternative value can refer to the description above.

[0325] Optionally, in yet some embodiments, the network device can dynamically indicate the number of time domain units occupied by the PUSCH to the terminal through a fifth DCI signaling. Optionally, the fifth DCI signaling can be used to configure the number of time domain units occupied by the PUSCH. Optionally, a new field can be added in the fifth DCI signaling to configure the number of time domain units occupied by the PUSCH, or the existing field or part of the bits of the existing field in the fifth DCI signaling can be reused to configure the number of time domain units occupied by the PUSCH. The details of this part can refer to the description above, or the number of time domain units occupied by the PUSCH can be directly configured by a code point, for example, different code points correspond to different numbers of time domain units, and the fifth DCI signaling can indicate the code point corresponding to any number of time domain units, and after receiving the fifth DCI signaling, the terminal can determine the number of time domain units corresponding to the code point indicated by the fifth DCI signaling as the number of time domain units occupied by the PUSCH.

[0326] Step 2103, the terminal sends first information to the network device.

[0327] Optionally, the first information can be used to indicate whether the terminal supports the available slot counting mechanism.

[0328] Optionally, the available slot counting mechanism may, for example, comprise: when counting the slots, if an unavailable symbol is encountered, the terminal skips the slot in which the unavailable symbol is located and does not count the slot into the total number of repeated transmissions indicated by the network device, thereby avoiding counting the unavailable resource by the terminal and saving the counting resource of the terminal.

[0329] Optionally, in some embodiments, the terminal may, for example, send the first information through an existing user equipment capability (UE capability) field, or the terminal may, for example, send the first information through a new capability field.

[0330] Step 2104: The network device sends second information to the terminal.

[0331] Optionally, the second information may, for example, be used to enable the available slot counting mechanism. Optionally, in some embodiments, after receiving the first information, if the first information indicates that the terminal supports the available slot counting mechanism, the network device may, for example, send the above-mentioned second information to the terminal.

[0332] Step 2105: The network device configures a redundancy sequence of the PUSCH for the terminal.

[0333] Optionally, in some embodiments, in the above-mentioned second sending mode, the same redundancy version (RV) may, for example, be used between different repeated transmissions in one time domain unit, and RV cycling may, for example, be performed between different time domain units; optionally, the RV sequence may, for example, be {0, 2, 3, 1} or {0, 3, 0, 3}.

[0334] For example, assuming that the PUSCH occupies N time domain units, and the RV sequence is {0, 2, 3, 1}, the RV number of the repeated transmission in the first time domain unit is 0, the RV number of the repeated transmission in the second time domain unit is 2, the RV number of the repeated transmission in the third time domain unit is 3, and the RV number of the repeated transmission in the fourth time domain unit is 1; the RV number of the repeated transmission in the fifth time domain unit is 0, the RV number of the repeated transmission in the sixth time domain unit is 2, the RV number of the repeated transmission in the seventh time domain unit is 3, and the RV number of the repeated transmission in the eighth time domain unit is 1, and so on. Alternatively, the RV number of the repeated transmission in the first time domain unit is 0, the RV number of the repeated transmission in the second time domain unit is 0, the RV number of the repeated transmission in the third time domain unit is 2, and the RV number of the repeated transmission in the fourth time domain unit is 2; the RV number of the repeated transmission in the fifth time domain unit is 3, the RV number of the repeated transmission in the sixth time domain unit is 3, the RV number of the repeated transmission in the seventh time domain unit is 1, and the RV number of the repeated transmission in the eighth time domain unit is 1, and so on.

[0335] Optionally, in some embodiments, in the second sending mode described above, the same redundancy version can be used between different repeated transmissions within a first window, and RV cycling is performed between repeated transmissions in different first windows; optionally, the first window can include L repeated transmissions, and L is the sequence length of the OCC sequence; optionally, the RV sequence can be, for example, {0, 2, 3, 1}, {0, 3, 0, 3}, or {0, 2, 0, 2}.

[0336] For example, assuming that the PUSCH transmission is divided into H first windows, and the RV sequence is {0, 2, 3, 1}, the RV number of the repeated transmission in the first first window is 0, the RV number of the repeated transmission in the second first window is 2, the RV number of the repeated transmission in the third first window is 3, and the RV number of the repeated transmission in the fourth first window is 1; the RV number of the repeated transmission in the fifth first window is 0, the RV number of the repeated transmission in the sixth first window is 2, the RV number of the repeated transmission in the seventh first window is 3, and the RV number of the repeated transmission in the eighth first window is 1, and so on. Alternatively, the RV number of the repeated transmission in the first first window is 0, the RV number of the repeated transmission in the second first window is 0, the RV number of the repeated transmission in the third first window is 2, and the RV number of the repeated transmission in the fourth first window is 2; the RV number of the repeated transmission in the fifth first window is 3, the RV number of the repeated transmission in the sixth first window is 3, the RV number of the repeated transmission in the seventh first window is 1, and the RV number of the repeated transmission in the eighth first window is 1, and so on.

[0337] Optionally, in some embodiments, in the second transmission mode described above, the same redundancy version can be used between different repeated transmissions within a second window, and RV cycling is performed between repeated transmissions of different second windows. Optionally, the second window can include LxB repeated transmissions, B is a positive integer, B>1, and B can be configured by the network device, or B can also be agreed by the protocol. Optionally, the RV sequence can be {0, 2, 3, 1}, {0, 3, 0, 3}, or {0, 2, 0, 2}, for example.

[0338] In step 2106, the network device configures the frequency hopping related parameters of the PUSCH for the terminal.

[0339] Optionally, the network device can send a sixth DCI signaling to the terminal, and the sixth DCI signaling can be used to indicate whether to perform frequency hopping on the PUSCH. For example, if the sixth DCI signaling carries an FH flag, the sixth DCI signaling is used to indicate that frequency hopping is performed on the PUSCH, otherwise, the sixth DCI signaling is used to indicate that frequency hopping is not performed on the PUSCH.

[0340] Optionally, the sixth DCI signaling can also be used to indicate the frequency offset value between adjacent two hops. For example, at least one alternative frequency offset value can be agreed in the protocol or configured in advance by the network device, and the sixth DCI signaling can indicate any alternative frequency offset value as the frequency offset value between adjacent two hops; or, no alternative frequency offset value can be configured, and the sixth DCI signaling can directly indicate the frequency offset value between adjacent two hops. In some embodiments, the frequency offset value between adjacent two hops or any alternative frequency offset value can be directly indicated by the frequency offset carried in the frequency domain resource allocation (FDRA) field of the sixth DCI signaling, or a new indication field can be introduced in the sixth DCI signaling to carry the frequency offset to directly indicate the frequency offset value between adjacent two hops or any alternative frequency offset value.

[0341] Optionally, in some embodiments, the network device can also send a fifth RRC parameter to the terminal, which can be used to indicate that the frequency hopping manner of the PUSCH is the first frequency hopping manner. For example, the fifth RRC parameter can be frequencyhoppingOCC ENUMERATED{first frequency hopping manner}, and the first frequency hopping manner can include: different repeated transmissions in one time domain unit use the same frequency domain resource, and repeated transmissions between different time domain units use different frequency domain resources; or

[0342] different repeated transmissions in one first window use the same frequency domain resource, and repeated transmissions between different first windows use different frequency domain resources; or

[0343] different repeated transmissions in one second window use the same frequency domain resource, and repeated transmissions between different second windows use different frequency domain resources.

[0344] Optionally, in some embodiments, the network device can send the fifth RRC parameter to the terminal to configure the first frequency hopping manner when the number of repeated transmissions S of the PUSCH in one time domain unit and L satisfy S ÷ L = 2^k, k >= 1.

[0345] Step 2107: The terminal determines that the transmission manner of the PUSCH is the first transmission manner or the second transmission manner.

[0346] Optionally, the terminal can determine that the transmission manner of the PUSCH is the first transmission manner or the second transmission manner when the terminal performs multi-user multiplexing transmission on the PUSCH based on the OCC sequence, and the repeated transmission type of the PUSCH is the PUSCH repetition type B.

[0347] Optionally, the terminal can determine the transmission mode of the PUSCH as the first transmission mode or the second transmission mode based on a protocol agreement, or the terminal can determine the transmission mode of the PUSCH as the first transmission mode or the second transmission mode based on a configuration of the network device.

[0348] Details about this part can be referred to the description of step 2101.

[0349] Step 2108, the terminal determines the time domain resource of the PUSCH.

[0350] Optionally, the terminal can determine the time domain resource of the PUSCH based on a protocol agreement, or the terminal can determine the time domain resource of the PUSCH based on a configuration of the network device.

[0351] Details about this part can be referred to the description of step 2102.

[0352] Step 2109, the terminal determines whether to transmit the PUSCH based on the available slot counting mechanism.

[0353] Optionally, in some embodiments, the terminal can determine whether to transmit the PUSCH based on the available slot counting mechanism based on a configuration of the network device, or the terminal can determine whether to transmit the PUSCH based on the available slot counting mechanism based on a protocol agreement.

[0354] In some embodiments, when the network device enables the available slot counting mechanism, the terminal determines to transmit the PUSCH based on the available slot counting mechanism. In other embodiments, the terminal can always transmit the PUSCH based on the available slot counting mechanism. Details about this part can be referred to the description of steps 2103-2104.

[0355] Step 2110, the terminal determines the redundancy sequence of the PUSCH.

[0356] Optionally, the terminal can determine the redundancy sequence of the PUSCH based on a configuration of the network device, or the terminal can determine the redundancy sequence of the PUSCH based on a protocol agreement. Details about this part can be referred to the description of step 2105.

[0357] Step 2111, the terminal determines the frequency hopping related parameter of the PUSCH.

[0358] Optionally, the terminal can determine the frequency hopping related parameter of the PUSCH based on a configuration of the network device, or the terminal can determine the frequency hopping related parameter of the PUSCH based on a protocol agreement.

[0359] Details about this part can be referred to the description of step 2105.

[0360] Step 2112, the terminal sends the PUSCH to the network device.

[0361] Optionally, the terminal can send the PUSCH based on the first sending manner or the second sending manner. For example, if the network device configures the first sending manner in the step 2101, or if the terminal determines the first sending manner in the step 2107, the terminal can send the PUSCH based on the first sending manner; if the network device configures the second sending manner in the step 2101, or if the terminal determines the second sending manner in the step 2107, the terminal can send the PUSCH based on the second sending manner.

[0362] Optionally, when the terminal sends the PUSCH based on the first sending manner, the terminal can map one sequence value of the OCC sequence to one or more repeated transmissions; wherein one repeated transmission across the time domain unit boundary can be mapped by the same sequence value. In this way, it can be ensured that the time domain length of each sequence value of the OCC sequence is the time domain length occupied by one or more repeated transmissions of the PUSCH, so as to ensure that the orthogonality of the OCC sequence mapping is not destroyed, and the PUSCH transmission performance is ensured.

[0363] Optionally, when the terminal sends the PUSCH based on the second sending manner, the terminal can map one sequence value of the OCC sequence to one or more repeated transmissions; wherein, since the repeated transmission of the PUSCH in the second sending manner does not cross the time domain unit, the case that the time domain unit boundary divides one nominal repeated transmission into two actual repeated transmissions with different time domain lengths does not occur, so it can also be ensured that the time domain length of each sequence value of the OCC sequence is the time domain length occupied by one or more repeated transmissions of the PUSCH, so as to ensure that the orthogonality of the OCC sequence mapping is not destroyed, and the PUSCH transmission performance is ensured.

[0364] Optionally, in some embodiments, when the terminal sends the PUSCH using the first sending manner or the second sending manner, the terminal can also send the PUSCH based on at least one of the time domain resources of the PUSCH, the available slot count mechanism, the redundancy sequence of the PUSCH, and the frequency hopping related parameters of the PUSCH determined in the foregoing steps.

[0365] Optionally, the network device can receive the PUSCH sent by the terminal. In some embodiments, the network device can first determine a first receiving manner corresponding to the first sending manner, and determine a second receiving manner corresponding to the second sending manner, and then receive the PUSCH based on the first receiving manner or the second sending manner. Optionally, the first receiving manner can include: when receiving the PUSCH, the network device no longer receives the PUSCH according to the principle of "dividing a nominal repeated transmission into two actual repeated transmissions at a time domain unit boundary", that is, the network device receives the PUSCH according to the principle of "a repeated transmission across a time domain unit boundary is mapped by the same sequence value"; optionally, the second receiving manner can include: receiving the PUSCH according to the principle of "any repeated transmission of the PUSCH will not cross a time domain unit". For example, if the network device configures the first sending manner in the step 2101, the network device can receive the PUSCH based on the first receiving manner; if the network device configures the first sending manner in the step 2101, the network device can receive the PUSCH based on the second receiving manner.

[0366] Optionally, in some embodiments, when receiving the PUSCH, the network device can also receive the PUSCH based on at least one of a time domain resource of the PUSCH, an available slot counting mechanism, a redundancy sequence of the PUSCH, and a frequency hopping related parameter of the PUSCH.

[0367] In the above embodiments, when the terminal performs multi-user multiplexing transmission on the PUSCH based on the OCC sequence, if the repetition transmission type of the PUSCH is PUSCH repetition type B, the terminal determines the transmission mode of the PUSCH as the first transmission mode or the second transmission mode. The first transmission mode includes that the time domain unit boundary is not used to divide one nominal repeated transmission into two actual repeated transmissions, and the second transmission mode includes that any one repeated transmission of the PUSCH does not cross the time domain unit. Then, the terminal transmits the PUSCH based on the first transmission mode or the second transmission mode. Optionally, in the first transmission mode, the time domain unit boundary is not used to divide one nominal repeated transmission into two actual repeated transmissions, so the situation that the time domain unit boundary divides one nominal repeated transmission into two actual repeated transmissions with different time domain lengths does not occur. That is, even if one nominal repeated transmission crosses the time domain unit, the nominal repeated transmission is not divided into two actual repeated transmissions based on the time domain unit boundary, so that the time domain lengths between different actual repeated transmissions are the same. When the OCC sequence is mapped based on the actual repeated transmission, it can be ensured that the time domain lengths mapped by different sequence values of the OCC sequence are the same, and the orthogonality of the OCC mapping is not damaged, ensuring the transmission performance of the PUSCH. In the second transmission mode, any one repeated transmission of the PUSCH does not cross the time domain unit, so the situation that the time domain unit boundary divides one nominal repeated transmission into two actual repeated transmissions with different time domain lengths does not occur. Therefore, the orthogonality of the OCC mapping can be ensured not to be damaged, and the transmission performance of the PUSCH is ensured.

[0368] In the above embodiments, it is explained how the terminal determines the time domain resource of the PUSCH in the second transmission mode, so that the terminal can successfully transmit the PUSCH in the second transmission mode based on the time domain resource, ensuring that the orthogonality of the OCC mapping is not damaged, and ensuring the transmission performance of the PUSCH.

[0369] In the above embodiments, the terminal can also transmit the PUSCH based on the available slot counting mechanism. Therefore, when the terminal transmits the PUSCH, it mainly counts the available slots and does not count the unavailable slots, thereby ensuring the accuracy and effectiveness of the terminal slot counting and improving the transmission performance of the PUSCH. Moreover, the terminal can avoid counting the unavailable resources, thereby saving the counting resources of the terminal.

[0370] In the above embodiments, it is explained how the terminal uses the redundancy version when transmitting the PUSCH, so that the terminal can successfully transmit the PUSCH based on the redundancy version, ensuring the transmission performance of the PUSCH.

[0371] In the above embodiments, it is explained how the terminal transmits the PUSCH in frequency hopping manner, so that the terminal can successfully transmit the PUSCH in frequency hopping manner, thereby reducing the interference between PUSCHs in different time domain units and improving the transmission performance of the PUSCH.

[0372] In the above embodiments, by ensuring that the total number of repeated transmissions of the PUSCH in one time domain unit is divisible by L, it can be ensured that the number of repeated mapping rounds of the OCC sequence for the PUSCH is an integer number of rounds, thereby ensuring the orthogonality in OCC mapping and improving the transmission performance of the PUSCH.

[0373] The communication method related to the embodiments of the present disclosure can include at least one of steps 2101-2112. For example, step 2101 can be implemented as an independent embodiment, step 2102 can be implemented as an independent embodiment, step 2103 can be implemented as an independent embodiment, and step 2101+S2102 can be implemented as an independent embodiment, but not limited thereto.

[0374] In the present embodiment or example, each step can be independently, arbitrarily combined or exchanged in order, and optional modes or examples can be arbitrarily combined, without contradiction, and can be arbitrarily combined with any step of other embodiments or other examples.

[0375] FIG. 3 is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 3, the embodiments of the present disclosure relate to a communication method for a terminal, and the above method includes:

[0376] Step 3101: transmitting a PUSCH based on a first transmission mode or a second transmission mode.

[0377] Optionally, when the PUSCH is transmitted in multi-user multiplexing manner based on an OCC sequence, the repetition transmission type of the PUSCH is PUSCH repetition type B, and the transmission mode of the PUSCH is determined to be the first transmission mode or the second transmission mode; wherein the first transmission mode includes: the time domain unit boundary is not used to divide one nominal repeated transmission into two actual repeated transmissions; and the second transmission mode includes: any repeated transmission of the PUSCH does not cross a time domain unit.

[0378] Optionally, the second transmission mode includes: the PUSCH occupies N time domain units, the PUSCH in each time domain unit is transmitted S times, and the symbol positions occupied by the PUSCH in different time domain units are the same; wherein S and N are positive integers, and S and N are greater than or equal to 1.

[0379] Optionally, the method further includes at least one of the following:

[0380] determining, based on a first parameter sent by the network device, that the transmission manner of the PUSCH is the second transmission manner; the first parameter is related to the OCC sequence;

[0381] determining, based on the network device configuring a repetition transmission type of the PUSCH as a PUSCH repetition type B, that the transmission manner of the PUSCH is the second transmission manner;

[0382] determining, based on a first radio resource control (RRC) parameter sent by the network device, that the transmission manner of the PUSCH is the second transmission manner; the first RRC parameter is used to indicate whether the PUSCH is transmitted based on the second transmission manner;

[0383] determining, based on first indication signaling sent by the network device, that the transmission manner of the PUSCH is the second transmission manner; the first indication signaling is used to indicate that the PUSCH is transmitted based on the second transmission manner;

[0384] determining, based on a first time domain resource allocation (TDRA) table or a second RRC parameter sent by the network device, that the transmission manner of the PUSCH is the second transmission manner;

[0385] determining, based on a first field of first downlink control information (DCI) signaling sent by the network device, that the transmission manner of the PUSCH is the second transmission manner.

[0386] Optionally, the method further comprises:

[0387] determining, based on the transmission manner of the PUSCH being the second transmission manner, a time domain resource of the PUSCH.

[0388] Optionally, the determining the time domain resource of the PUSCH comprises at least one of:

[0389] determining a number of repetitions of the PUSCH in a time domain unit and symbol resources occupied by the PUSCH transmission;

[0390] determining a number of time domain units occupied by the PUSCH.

[0391] Optionally, the determining the number of repetitions of the PUSCH in the time domain unit comprises at least one of:

[0392] determining the number of repetitions of the PUSCH in the time domain unit based on a sequence length of the OCC sequence;

[0393] determining the number of repetitions of the PUSCH in the time domain unit based on a second TDRA table and a second DCI signaling sent by the network device; wherein the second TDRA table is used to configure at least one candidate number of repetitions, and the second DCI signaling is used to indicate any candidate number of repetitions as the number of repetitions of the PUSCH in the time domain unit;

[0394] determining the number of repetitions of the PUSCH in the time domain unit based on a second RRC parameter sent by the network device.

[0395] Optionally, the determining the symbol resources occupied by the PUSCH transmission in the time domain unit comprises:

[0396] determining the starting symbol position and the symbol length of the PUSCH transmission in the time domain unit based on a third TDRA table and a third DCI signaling sent by the network device; wherein the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate first length; the third DCI signaling is used to indicate any candidate starting symbol position as the starting symbol position of the first transmission of the PUSCH in the time domain unit, and indicate any candidate first length as the symbol length corresponding to all transmissions of the PUSCH in the time domain unit; or, the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate second length; the third DCI signaling is used to indicate any candidate starting symbol position as the starting symbol position of the first transmission of the PUSCH in the time domain unit, and indicate any candidate second length as the symbol length corresponding to one transmission of the PUSCH in the time domain unit;

[0397] determining the symbol resources occupied by the PUSCH transmission in the time domain unit based on the starting symbol position and the symbol length.

[0398] Optionally, the determining the number of time domain units occupied by the PUSCH comprises at least one of:

[0399] determining the number of time domain units occupied by the PUSCH based on a third RRC parameter sent by the network device.

[0400] determining the number of time domain units occupied by the PUSCH based on at least one of a fourth table, a fourth RRC parameter, and a fourth DCI signaling; wherein the fourth table and the fourth RRC parameter are used to configure at least one candidate value, and the fourth DCI signaling is used to indicate any candidate value as the number of time domain units occupied by the PUSCH; wherein the fourth table is configured by the network device and / or preset by a protocol.

[0401] determining a number of time domain units occupied by the PUSCH based on fifth DCI signaling sent by the network device.

[0402] Optionally, the fourth table comprises a TDRA table and / or a transmit power control (TPC) table.

[0403] Optionally, the method further comprises any one of the following:

[0404] When the PUSCH is sent, an available slot counting mechanism is enabled, and the PUSCH is sent based on the available slot counting mechanism.

[0405] When the PUSCH is sent, the PUSCH is sent based on the available slot counting mechanism.

[0406] Optionally, the method further comprises:

[0407] sending first information to a network device, the first information being used to indicate whether the terminal supports the available slot counting mechanism;

[0408] receiving second information sent by the network device, the second information being used to enable the available slot counting mechanism.

[0409] Optionally, the same redundancy version is used between different repeated transmissions in one time domain unit, and redundancy version cycling (RV cycling) is performed between different time domain units; or

[0410] the same redundancy version is used between different repeated transmissions in a first window, and RV cycling is performed between repeated transmissions in different first windows; the first window comprises L repeated transmissions, and L is a sequence length of the OCC sequence; or

[0411] the same redundancy version is used between different repeated transmissions in a second window, and RV cycling is performed between repeated transmissions in different second windows; the second window comprises LxB repeated transmissions, L is a sequence length of the OCC sequence, and B is a positive integer, B>1.

[0412] Optionally, the method further comprises:

[0413] determining whether frequency hopping is performed on the PUSCH;

[0414] performing frequency hopping on the PUSCH, and determining a first frequency hopping manner;

[0415] sending the PUSCH based on the first frequency hopping manner.

[0416] Optionally, the determining whether to hop the PUSCH comprises:

[0417] receiving sixth DCI signaling sent by the network device, the sixth DCI signaling being used to indicate whether to hop the PUSCH.

[0418] Optionally, the sixth DCI signaling is also used to indicate a frequency offset value between adjacent two hops.

[0419] Optionally, the first hopping manner comprises:

[0420] different repeated transmissions within one time domain unit use the same frequency domain resource, and repeated transmissions between different time domain units use different frequency domain resources; or

[0421] different repeated transmissions within a first window use the same frequency domain resource, and repeated transmissions between different first windows use different frequency domain resources; the first window comprises L repeated transmissions, L being a sequence length of the OCC sequence; or

[0422] different repeated transmissions within a second window use the same frequency domain resource, and repeated transmissions between different second windows use different frequency domain resources; the second window comprises L×B repeated transmissions, L being a sequence length of the OCC sequence, and B being a positive integer, B>1.

[0423] Optionally, the determining the first hopping manner comprises:

[0424] a repeated transmission number S of the PUSCH within one time domain unit satisfies S÷L=2^k, k>=1, and receiving fifth RRC parameters sent by the network device, the fifth RRC parameters being used to configure the first hopping manner as: different repeated transmissions within one time domain unit use the same frequency domain resource, and repeated transmissions between different time domain units use different frequency domain resources, or the fifth RRC parameters being used to configure the first hopping manner as: different repeated transmissions within a first window use the same frequency domain resource, and repeated transmissions between different first windows use different frequency domain resources, or the fifth RRC parameters being used to configure the first hopping manner as: different repeated transmissions within a second window use the same frequency domain resource, and repeated transmissions between different second windows use different frequency domain resources.

[0425] Optionally, a total repeated transmission number of the PUSCH within one time domain unit is divisible by L, L being a sequence length of the OCC sequence.

[0426] Optionally, the sending the PUSCH based on the first sending manner comprises:

[0427] mapping one sequence value of the OCC sequence to one or more repeated transmissions; wherein one repeated transmission across a time domain unit boundary is mapped by the same sequence value.

[0428] Details about step 3101 can refer to the above embodiment description.

[0429] In the embodiments or examples, each step can be independent, arbitrarily combined or exchanged in order, optional modes or examples can be arbitrarily combined, and can be arbitrarily combined with any step of other embodiments or other examples.

[0430] Figure 4 is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 4, the embodiment of the present disclosure relates to a communication method, for a network device, the above method comprises:

[0431] Step 4101, configuring the terminal with a first transmission mode or a second transmission mode for PUSCH.

[0432] Step 4102, determining a first receiving mode corresponding to the first transmission mode, or determining a second receiving mode corresponding to the second transmission mode.

[0433] Step 4103, receiving the PUSCH based on the first receiving mode or the second receiving mode.

[0434] Optionally, when the terminal performs multi-user multiplexing transmission on the physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, the repetition transmission type of the PUSCH is PUSCH repetition type B, and the transmission mode of the PUSCH is determined to be a first transmission mode or a second transmission mode; wherein the first transmission mode includes: the time domain unit boundary is not used to divide one nominal repeated transmission into two actual repeated transmissions; and the second transmission mode includes: any one repeated transmission of the PUSCH does not cross the time domain unit.

[0435] Optionally, the second transmission mode includes: the PUSCH occupies N time domain units, the PUSCH performs S repeated transmissions in each time domain unit, and the symbol positions occupied by the PUSCH in different time domain units are the same; wherein S and N are positive integers, and S and N are greater than or equal to 1.

[0436] Optionally, the step of configuring the terminal with a first transmission mode or a second transmission mode for PUSCH includes at least one of the following:

[0437] sending a first parameter to the terminal; the first parameter is used to configure the transmission mode of the PUSCH to be the second transmission mode, and the first parameter is related to the OCC sequence.

[0438] configuring a repetition transmission type of the PUSCH as PUSCH repetition type B;

[0439] sending a first radio resource control (RRC) parameter to the terminal, the first RRC parameter being used to indicate whether the PUSCH is transmitted based on the second transmission manner;

[0440] sending a first indication signaling to the terminal, the first indication signaling being used to indicate that the PUSCH is transmitted based on the second transmission manner;

[0441] sending a first time domain resource allocation (TDRA) table or a second RRC parameter to the terminal, the first TDRA table or the second RRC parameter being used to determine that the transmission manner of the PUSCH is the second transmission manner;

[0442] sending a first downlink control information (DCI) signaling to the terminal, a first field of the first DCI signaling being used to determine that the transmission manner of the PUSCH is the second transmission manner.

[0443] Optionally, the method further comprises at least one of the following:

[0444] sending a second TDRA table and a second DCI signaling to the terminal, wherein the second TDRA table is used to configure at least one alternative repetition transmission number, and the second DCI signaling is used to indicate any alternative repetition transmission number as the repetition transmission number of the PUSCH in one time domain unit;

[0445] sending a second RRC parameter to the terminal, the second RRC parameter being used to determine the repetition transmission number of the PUSCH in one time domain unit.

[0446] Optionally, the method further comprises:

[0447] sending, to the terminal, a third TDRA table and a third DCI signaling, wherein the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate first length; the third DCI signaling is used to indicate any candidate starting symbol position as a starting symbol position of a first transmission of the PUSCH in a time domain unit, and indicate any candidate first length as a length of symbols corresponding to all transmissions of the PUSCH in a time domain unit; or the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate second length; the third DCI signaling is used to indicate any candidate starting symbol position as a starting symbol position of a first transmission of the PUSCH in a time domain unit, and indicate any candidate second length as a length of symbols corresponding to one transmission of the PUSCH in a time domain unit.

[0448] Optionally, the method further comprises at least one of the following:

[0449] sending, to the terminal, a third RRC parameter; the third RRC parameter is used to determine a number of time domain units occupied by the PUSCH;

[0450] sending, to the terminal, at least one of a fourth table, a fourth RRC parameter, and a fourth DCI signaling; the fourth table and the fourth RRC parameter are used to configure at least one candidate value, and the fourth DCI signaling is used to indicate any candidate value as the number of time domain units occupied by the PUSCH;

[0451] sending, to the terminal, a fifth DCI signaling; the fifth DCI signaling is used to determine the number of time domain units occupied by the PUSCH.

[0452] Optionally, the fourth table comprises a TDRA table and / or a transmit power control (TPC) table.

[0453] Optionally, the method further comprises:

[0454] sending, to the terminal, second information used to enable an available slot counting mechanism.

[0455] Optionally, the method further comprises:

[0456] receiving, from the terminal, first information used to indicate whether the terminal supports the available slot counting mechanism.

[0457] Optionally, a same redundancy version is used between different repeated transmissions in a time domain unit, and redundancy version cycling (RV cycling) is performed between different time domain units; or

[0458] a same redundancy version is used between different repeated transmissions within a first window, and RV cycling is performed between repeated transmissions of different first windows; the first window includes L repeated transmissions, L being a sequence length of the OCC sequence; or

[0459] a same redundancy version is used between different repeated transmissions within a second window, and RV cycling is performed between repeated transmissions of different second windows; the second window includes L×B repeated transmissions, L being a sequence length of the OCC sequence, and B being a positive integer, B>1.

[0460] Optionally, the method further includes:

[0461] sending, to the terminal, sixth DCI signaling, the sixth DCI signaling being used to indicate whether frequency hopping is performed on the PUSCH.

[0462] Optionally, the sixth DCI signaling is further used to indicate a frequency offset value between two adjacent hops.

[0463] Optionally, the method further includes:

[0464] a number of repeated transmissions of the PUSCH within one time domain unit S and L satisfy S ÷ L = 2^k, k >= 1, L being a sequence length of the OCC sequence, and fifth RRC parameters are sent to the terminal, the fifth RRC parameters being used to configure the first frequency hopping manner as: a same frequency domain resource is used for different repeated transmissions within one time domain unit, different frequency domain resources are used for repeated transmissions between different time domain units, or the fifth RRC parameters are used to configure the first frequency hopping manner as: a same frequency domain resource is used for different repeated transmissions within a first window, different frequency domain resources are used for repeated transmissions between different first windows, or the fifth RRC parameters are used to configure the first frequency hopping manner as: a same frequency domain resource is used for different repeated transmissions within a second window, different frequency domain resources are used for repeated transmissions between different second windows.

[0465] Optionally, a total number of repeated transmissions of the PUSCH within one time domain unit is divisible by L, L being a sequence length of the OCC sequence.

[0466] Details about steps 4101-4103 can be referred to the descriptions of the above embodiments.

[0467] The communication method related to the embodiments of the present disclosure can include at least one of steps 4101-4103. For example, step 4101 can be implemented as an independent embodiment, step 4102 can be implemented as an independent embodiment, step 4103 can be implemented as an independent embodiment, step 4101+S4102 can be implemented as an independent embodiment, but not limited thereto.

[0468] In the present embodiment or example, each step can be independent, arbitrarily combined or the order exchanged, the optional mode or optional example can be arbitrarily combined, and can be arbitrarily combined with any step of other embodiments or other examples, without contradiction.

[0469] FIG. 5 is an interaction diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 5, the embodiments of the present disclosure relate to a communication method for a communication system including a terminal, a network device, the above-mentioned method including at least one of the following:

[0470] Step 5101, the network device configures the terminal with a first transmission mode or a second transmission mode for PUSCH;

[0471] Step 5102, the terminal transmits the PUSCH based on the first transmission mode or the second transmission mode.

[0472] Step 5103, the network device determines a first reception mode corresponding to the first transmission mode, or determines a second reception mode corresponding to the second transmission mode.

[0473] Step 5104, the network device receives the PUSCH based on the first reception mode or the second reception mode.

[0474] The optional implementation of steps 5101-5104 can be referred to the above-mentioned embodiment.

[0475] In some embodiments, the above-mentioned method can include the method described in the above-mentioned embodiment of the communication system side, the first device side, the network device side, etc., which will not be repeated here.

[0476] The communication method related to the embodiments of the present disclosure can include at least one of steps 5101-5104. For example, step 5101 can be implemented as an independent embodiment, step 5102 can be implemented as an independent embodiment, but not limited thereto.

[0477] In the present embodiment or example, each step can be independent, arbitrarily combined or the order exchanged, the optional mode or optional example can be arbitrarily combined, and can be arbitrarily combined with any step of other embodiments or other examples, without contradiction.

[0478] The following is an exemplary introduction to the above method.

[0479] Option 1: Modify the mechanism of splitting nominal repetition transmission resources into actual repetition transmission resources under the existing PUSCH repetition type B, to support OCC multiplexing

[0480] ● That is, under the premise of enabling PUSCH repetition type B like OCC multiplexing, when a nominal repetition encounters a slot boundary, it is no longer split into two actual repetitions. The actual transmission of a type-B repetition may span the slot boundary and cover 2 adjacent slots.

[0481] ● Otherwise, inter-symbol OCC multiplexing is still based on the existing PUSCH repetition type B mechanism

[0482] Option 2: For the repetition type B like OCC multiplexing mechanism, consider introducing a design idea that combines PUSCH repetition type A and PUSCH repetition type B. One possible example is shown in the following figure.

[0483] ● For example: assume that the number of repetitions of PUSCH repetition type A is 4, the number of OCC multiplexed users is 4, and each repetition of PUSCH repetition type B occupies 3 symbol time domain resources, with the starting symbol being symbol #3. In addition, assume that the OCC sequence value of the current user #1 is {1, 1, -1, -1}

[0484] • Optional Embodiment 1: Based on the above Figure 2B, it is conceivable that under this mechanism, the time domain resource occupied by PUSCH repetition type B based M times repetition is limited within one slot. The number of slots is determined by the number of times of PUSCH repetition type A allocation. Between any two slots, the time domain resource occupied by PUSCH is the same, which is determined by the time domain resource allocation of PUSCH repetition type B. It is conceivable that PUSCH repetition type A is to repeat all repetition type B within a slot again at the slot level (from the perspective of data processing, it is not strictly PUSCH repetition type A; from the perspective of resource allocation, the result of resource allocation on each slot is the same as follow and legacy PUSCH repetition type A).

[0485] • Optional Embodiment 2: Under the PUSCH repetition type A + type B based OCC multiplexing mechanism, the enabling / disabling of PUSCH repetition type A and PUSCH repetition type B is determined by at least one of the following ways:

[0486] • 2-1: By configuring the OCC related parameters, it is determined to use PUSCH repetition type A & B based OCC multiplexing

[0487] • 2-2: By configuring PUSCH-RepTypeIndicatorDCI0-1-16or PUSCH-RepTypeIndicatorDCI-0-2-r16(for dynamic grant), or repTypeIndicator-16(for configured grant), PUSCH repetition type B, to determine to use PUSCH repetition type A & B based OCC multiplexing (this does not mean that repetition type A cannot be used)

[0488] • 2-3: Or, by a new RRC configuration parameter, such as PUSCH-RepTypeA_TypeB{enabled}, to determine whether to use PUSCH repetition type A & B based OCC multiplexing.

[0489] • 2-4: Alternatively, the protocol predefines at least two OCC multiplexing manners, and the gNB configures / indicates a parameter to determine whether to use PUSCH type A&B based OCC multiplexing

[0490] • 2-5: Alternatively, when the gNB configures a TDRA table corresponding to PUSCH repetition type B, or when there is an RRC field repK (only for semi-static configuration), it means that PUSCH repetition type B&A based OCC multiplexing is enabled; or when the gNB configures a TDRA table (not used for PUSCH repetition type B) with a numberofrepetitions field, or when there is an RRC field PUSCH-AggregationFactor, it means that PUSCH repetition type B&A based OCC multiplexing is enabled. (It is conceivable that in this way, the configuration of the TDRA table and the configuration field of the repetition type in way 2-2 exist independently, that is, even if the repetition type A is enabled, the TDRA table corresponding to the PUSCH repetition type B can be configured)

[0491] • 2-6: When the TDRA table indicated by the TDRA field in the DCI contains a numberofrepetitions field in a row, and the numberofrepetitions field is greater than 1, it means that PUSCH repetition type B&A based OCC multiplexing is enabled. The TDRA table can be a TDRA table corresponding to PUSCH repetition type B, or it can be a TDRA table not corresponding to PUSCH repetition type B

[0492] • 2-7: The above several different ways can be used in combination; for example, 2-1 and 2-2 can be used in combination; or 2-1 and 2-3 can be used in combination, etc.

[0493] • It is envisioned that for mode 2-1 / 3 / 4 / 5 / 6, the high layer RRC parameter PUSCH-RepTypeIndicatorDCI0-1-16or PUSCH-RepTypeIndicatorDCI-0-2-r16(for dynamic grant), or repTypeIndicator-16(for configured grant) is not valid for the above multiplexing. In other words, once PUSCH repetition type A&B based OCC multiplexing is adopted, PUSCH repetition type A and PUSCH repetition type B will be enabled regardless of whether PUSCH repetition type B is enabled or not by the above field.

[0494] • Optional embodiment 3: Determine the time domain resource under PUSCH repetition type B+type A based OCC multiplexing mechanism based on at least one of the following

[0495] - 3-1: The time domain resource allocation for PUSCH repetition type B is determined by legacy way, the number of slots / repetitions for PUSCH repetition type A is determined by new defined way

[0496] o PUSCH repetition type B

[0497] o The terminal does not expect that the total number of time domain resources allocated for PUSCH repetition type B exceeds one slot (the number of symbols occupied by each repetition * the nominal number of type-B PUSCH repetitions) under legacy way; or the total number of time domain resources allocated for PUSCH repetition type B does not exceed 1 slot (under this mechanism, the nominal number of repetitions is indicated by the TDRA table corresponding to PUSCH repetition type B; or the nominal number of repetitions is configured by the RRC parameter repk)

[0498] o PUSCH repetition type A

[0499] o Slot number indication mechanism:

[0500] o RRC configuration

[0501] o Indication of repetition number or slot number by legacy RRC parameter PUSCH-AggregationFactor

[0502] o Or, new RRC parameter is added to indicate slot number

[0503] o Dynamic indication

[0504] o A new row is added in TDRA table to configure repetition number of PUSCH repetition type A; further, a row in the table is indicated by TDRA field in DCI to further determine the specific type A repetition number

[0505] o Or, a new repetition number list is configured by RRC parameter, a new field is added in DCI or at least part of bits of an existing field is multiplexed, such as high bits of TPC field, MCS field, etc., to indicate type A repetition number, and the existing field includes but is not limited to the above-mentioned field. In addition, repetition number can also be multiplexed in the existing table, such as redesigning TPC table, some rows in the table are repetition number, and repetition number is indicated by TPC field in DCI, etc.

[0506] o A new field is added in DCI or an existing field is multiplexed to directly indicate type A repetition number by codepoint

[0507] - 3-2: The number of slots occupied by PUSCH repetition type A is determined by the number of repetitions in the table of TDRA indication, or determined by the RRC semi-static parameter pusch-AggregationnFactor; the number of repetitions of PUSCH repetition type B is determined by OCC length or multiplexed user number, or the maximum multiplexed user number (the OCC length is configured or indicated by gNB, or determined by the protocol preset method or preset value), and the number of symbols occupied by each repetition in type B repetition is determined by the SLIV or start symbol, symbol length, etc. parameters carried in the TDRA list indicated by the DCI TDRA field. The TDRA table can be a newly defined table.

[0508] - Available slot counting:

[0509] When the available slot counting mechanism is enabled, the terminal uses the available slot counting mechanism to determine the slots occupied by PUSCH OCC multiplexing transmission. Optionally, the terminal indicates the capability of available slot counting through the existing UE capability field, or the terminal indicates the capability of available slot counting through a new capability field.

[0510] Alternatively, the terminal always determines the slots occupied by PUSCH OCC multiplexing based on the available slot counting mechanism. That is, when encountering an unavailable symbol, the terminal will skip the slot in which the symbol is located, and will not be counted in the total number of repetitions indicated by the gNB.

[0511] Optional embodiment 4: Under this mechanism, the redundancy version between different repetitions is determined in the following way:

[0512] - 4-1: The same redundancy version is used between different type-B repetitions in a slot; RV cycling can be performed between different slots, and the RV sequence can be {0, 2, 3, 1} or {0, 3, 0, 3}

[0513] - 4-2: Alternatively, assuming each L times type-B repetition is 1 block, L is OCC length, the same RV is used between different repetitions within each block, RV cycling can be performed between M / L blocks, the RV sequence can be {0, 2, 3, 1} or {0, 3, 0, 3} or {0, 2, 0, 2}, etc. Where M is the product of the number of type-B repetitions S and the number of type-A repetitions N (M = S * N)

[0514] - 4-3: Alternatively, the same RV is used between different repetitions within each B blocks, RV cycling can be performed between ceil(M / L / B) B blocks, the RV sequence can be {0, 2, 3, 1}, {0, 3, 0, 3} or {0, 2, 0, 2}, etc. The value of B can be determined by a protocol configuration parameter or can be determined by a protocol preset manner. When B = 1, mode 3-3 and mode 3-2 are equivalent

[0515] • Optional embodiment 5: Under this mechanism, the frequency hopping mechanism can be determined by the following modes:

[0516] - 5-1: Frequency hopping mode

[0517] o 5-1-1: The same frequency domain position is used between different repetitions within a slot; different frequency domain positions can be used between different slots (i.e., frequency hopping can be enabled between different slots)

[0518] o 5-1-2: Alternatively, assuming each L times type-B repetition is 1 block, L is OCC length, then the same frequency domain position is used between different repetitions within each block, and frequency hopping can be performed between M / L blocks;

[0519] o 5-1-3: Alternatively, the same frequency domain position is used between different repetitions within each B blocks, and frequency hopping can be performed between M / L / B B blocks. That is, an inter-L*B repetition frequency hopping mechanism is introduced. When B = 1, 5-1-2 and 5-1-3 are equivalent. The value of B can be determined by a protocol configuration parameter (which can not be a direct configuration of the value of B) or can be determined by a protocol preset manner.

[0520] - 4-2: Determination of frequency hopping mode

[0521] ○ Enable / disable frequency hopping by FH flag carried in DCI

[0522] ○ Indicate the frequency offset between two hops by the frequency offset indication carried in the FDRA field in DCI, or introduce a new frequency offset indication in DCI, to indicate the frequency offset list pre-configured by protocol or gNB

[0523] ○ Optionally, based on 5-1-1 / 2 / 3, if the number of type-B repetitions S and OCC length L in one slot satisfy the following constraint relationship: S / OCC length = 2^k, k >= 1, optionally support the above several different frequency hopping modes (5-1-1, 5-1-2, 5-1-3), gNB can optionally configure two different frequency hopping mechanisms. For example, introduce the RRC field frequencyhoppingOCC ENUMERATED{inter-B*Lrepetition, inter-slot}, B is a positive integer, which can be greater than or equal to 1.

[0524] Optional embodiment 6: Optionally, the number of type-B repetitions in one slot can be less than the OCC length; in this case, one OCC length can cover the symbols on two slots. Further, the redundancy version determination and the frequency hopping mode determination are respectively in the manner of 4-2 / 3 and 5-1-2 / 3. It is conceivable that the scheduling of gNB needs to ensure that S*N mod L = 0. In other words, the terminal does not expect that the number of repetitions S*N allocated by gNB cannot be divided by the number of multiplexed users or the OCC length L.

[0525] Optionally, the present disclosure designs a multi-user OCC multiplexing mechanism to improve system capacity and system throughput.

[0526] The embodiments of the present disclosure also propose an apparatus for implementing any of the above methods, for example, an apparatus comprising units or modules for implementing the steps performed by the terminal in any of the above methods. For another example, another apparatus is proposed, comprising units or modules for implementing the steps performed by the network device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0527] It should be understood that the division of each unit or module in the above apparatus is only a logical function division, and all or part of them can be integrated into a physical entity or physically separated in actual implementation. In addition, the units or modules in the apparatus can be implemented in the form of processor calling software: for example, the apparatus includes a processor connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of each unit or module of the above apparatus, wherein the processor is, for example, a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory in the apparatus or a memory outside the apparatus. Alternatively, the units or modules in the apparatus can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be realized by the design of hardware circuit. The above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the above units or modules are realized by the design of the logical relationship of elements in the circuit; for example, in another implementation, the above hardware circuit is a programmable logic device (PLD), and a field programmable gate array (FPGA) is taken as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of part or all of the above units or modules. All units or modules of the above apparatus can be implemented in the form of processor calling software, or all units or modules can be implemented in the form of hardware circuit, or part of the units or modules are implemented in the form of processor calling software, and the remaining part is implemented in the form of hardware circuit.

[0528] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), or the like. In another implementation, the processor can implement certain functions through a logical relationship of hardware circuits, and the logical relationship of the hardware circuits is fixed or can be reconfigured. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit. It can be understood that the processor loads instructions to implement the functions of the above part or all units or modules. In addition, the hardware circuit can also be designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), or the like.

[0529] FIG. 6A is a structural schematic diagram of a terminal according to an embodiment of the present disclosure. As shown in FIG. 6A, the terminal includes:

[0530] The processing module is configured to, when performing multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, perform transmission of the PUSCH based on a first transmission mode or a second transmission mode, where the repetition transmission type of the PUSCH is a PUSCH repetition type B, the first transmission mode includes that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions, and the second transmission mode includes that any one repetition transmission of the PUSCH does not cross a time domain unit.

[0531] Optionally, the processing module is configured to perform the steps related to “processing” performed by the terminal in any of the above methods. The terminal can further include a transceiver module configured to perform the steps related to “transmission and reception” performed by the terminal in any of the above methods.

[0532] FIG. 6B is a structural schematic diagram of a network device according to an embodiment of the present disclosure. As shown in FIG. 6B, the network device includes a processor 6001, a memory 6002, and a transceiver 6003.

[0533] The processing module is configured to, when a terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, configure a first transmission mode or a second transmission mode for the terminal for the PUSCH, where the PUSCH has a PUSCH repetition type B, the first transmission mode includes that a time domain unit boundary is not used to divide one nominal repeated transmission into two actual repeated transmissions, and the second transmission mode includes that any one repeated transmission of the PUSCH does not cross a time domain unit.

[0534] The processing module is further configured to determine a first receiving mode corresponding to the first transmission mode, or determine a second receiving mode corresponding to the second transmission mode.

[0535] The transceiver is configured to receive the PUSCH based on the first receiving mode or the second receiving mode.

[0536] Optionally, the transceiver is configured to perform steps related to "transceiving" performed by the network device in any of the above methods, and the processing module is configured to perform steps related to "processing" performed by the network device in any of the above methods.

[0537] FIG. 7A is a structural schematic diagram of a communication device 7100 according to an embodiment of the present disclosure. The communication device 7100 can be a network device (for example, an access network device, a core network device, etc.), a terminal (for example, a user equipment or the first device described above, etc.), a chip, a chip system, or a processor supporting the network device to implement any of the above methods, or a chip, a chip system, or a processor supporting the terminal to implement any of the above methods. The communication device 7100 can be used to implement the methods described in the above method embodiments, and details can be referred to the descriptions in the above method embodiments.

[0538] As shown in FIG. 7A, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a special-purpose processor, for example, a baseband processor or a central processing unit. The baseband processor can be configured to process a communication protocol and communication data, and the central processing unit can be configured to control a communication device (for example, a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a program, and process data of the program. The processor 7101 is configured to invoke instructions to enable the communication device 7100 to perform any of the above methods.

[0539] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 can also be outside the communication device 7100.

[0540] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the communication steps such as sending and receiving in the above methods are performed by the transceiver 7103, and other steps are performed by the processor 7101.

[0541] In some embodiments, the transceiver can include a receiver and a transmitter, which can be separate or integrated together. Optionally, the terms transceiver, transceiving unit, transceiver, transceiving circuit, etc. can be replaced by each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced by each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced by each other.

[0542] Optionally, the communication device 7100 further includes one or more interface circuits 7104, which are connected with the memory 7102, and can be used to receive signals from the memory 7102 or other devices, and can be used to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 can read the instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0543] The communication device 7100 described in the above embodiments can be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited to this, and the structure of the communication device 7100 can not be limited by Figure 7a. The communication device can be a standalone device or can be part of a larger device. For example, the communication device can be: (1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, which can optionally include storage components for storing data and programs; (3) an ASIC, such as a Modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0544] Figure 7B is a structural schematic diagram of a chip 7200 according to an embodiment of the present disclosure. For the case where the communication device 7100 is a chip or a chip system, the structural schematic diagram of the chip 7200 shown in Figure 7B can be referred to, but is not limited to this.

[0545] The chip 7200 comprises one or more processors 7201 configured to invoke instructions to cause the chip 7200 to perform any of the above methods.

[0546] In some embodiments, the chip 7200 further comprises one or more interface circuits 7202 connected with the memory 7203, which can be configured to receive signals from the memory 7203 or other devices, and can be configured to send signals to the memory 7203 or other devices. For example, the interface circuit 7202 can read instructions stored in the memory 7203 and send the instructions to the processor 7201. Alternatively, the terms interface circuit, interface, transceiver pin, transceiver, etc. can be replaced by each other.

[0547] In some embodiments, the chip 7200 further comprises one or more memories 7203 for storing instructions. Alternatively, all or part of the memory 7203 can be outside the chip 7200.

[0548] The disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 7100, cause the communication device 7100 to perform any of the above methods. Alternatively, the storage medium is an electronic storage medium. Alternatively, the storage medium is a computer readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices. Alternatively, the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a transitory storage medium.

[0549] The disclosure also proposes a program product which, when executed by the communication device 7100, causes the communication device 7100 to perform any of the above methods. Alternatively, the program product is a computer program product.

[0550] The disclosure also proposes a computer program which, when executed on a computer, causes the computer to perform any of the above methods.

[0551] In the embodiments described above, all or part of the system, device, and unit can be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the system, device, and unit can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer programs are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer programs can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer programs can be transferred from one website, computer, server, or data center to another website, computer, server, or data center through a wired (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example, infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium accessible by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)), etc.

[0552] Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether the functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. A skilled person can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present disclosure.

[0553] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the system, device, and unit described above can refer to the corresponding processes in the foregoing method embodiments, which will not be described here.

[0554] The above is merely a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present disclosure, which should be covered within the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: The method is performed by a terminal, and the method comprises: When a physical uplink shared channel (PUSCH) is multiplexed and transmitted based on an orthogonal cover code (OCC) sequence, a repetition type of the PUSCH is PUSCH repetition type B, and the PUSCH is transmitted based on a first transmission mode or a second transmission mode; wherein the first transmission mode comprises that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions; and the second transmission mode comprises that any one repetition transmission of the PUSCH does not cross a time domain unit.

2. The method of claim 1, wherein, The second transmission mode comprises that the PUSCH occupies N time domain units, the PUSCH performs S times of repetition transmission in each time domain unit, and a symbol position occupied by the PUSCH in different time domain units is the same; wherein S and N are positive integers, and S and N are greater than or equal to 1.

3. The method of claim 1 or 2, wherein, The method further comprises at least one of the following: A first parameter transmitted by a network device is used to determine that the transmission mode of the PUSCH is the second transmission mode; and the first parameter is related to the OCC sequence. A network device configures a repetition type of the PUSCH as PUSCH repetition type B, and determines that the transmission mode of the PUSCH is the second transmission mode. A first radio resource control (RRC) parameter transmitted by a network device is used to determine that the transmission mode of the PUSCH is the second transmission mode. A first indication signaling transmitted by a network device is used to determine that the transmission mode of the PUSCH is the second transmission mode. A first time domain resource allocation (TDRA) table or a second RRC parameter transmitted by a network device is used to determine that the transmission mode of the PUSCH is the second transmission mode. A first field of a first downlink control information (DCI) signaling transmitted by a network device is used to determine that the transmission mode of the PUSCH is the second transmission mode.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: When the transmission mode of the PUSCH is the second transmission mode, a time domain resource of the PUSCH is determined.

5. The method of claim 4, wherein, The determination of the time domain resource of the PUSCH comprises at least one of the following: ： A repetition transmission number of the PUSCH in one time domain unit and a symbol resource occupied by the PUSCH transmission are determined; A number of time domain units occupied by the PUSCH is determined.

6. The method of claim 5, wherein, The determination of the repetition transmission number of the PUSCH in one time domain unit comprises at least one of the following: A repetition transmission number of the PUSCH in one time domain unit is determined based on a sequence length of the OCC sequence; A repetition transmission number of the PUSCH in one time domain unit is determined based on a second TDRA table and a second DCI signaling transmitted by a network device; wherein the second TDRA table is used to configure at least one alternative repetition transmission number, and the second DCI signaling is used to indicate any one alternative repetition transmission number as the repetition transmission number of the PUSCH in one time domain unit; A repetition transmission number of the PUSCH in one time domain unit is determined based on a second RRC parameter transmitted by a network device.

7. The method of claim 5, wherein, The determining of the symbol resource occupied by the PUSCH transmission in one time domain unit comprises: The starting symbol position and the symbol length of the PUSCH transmission in one time domain unit are determined based on a third TDRA table and a third DCI signaling sent by the network device; the third TDRA table is used to configure at least one alternative starting symbol position and at least one alternative first length; the third DCI signaling is used to indicate any alternative starting symbol position as the starting symbol position of the first PUSCH transmission in one time domain unit, and indicate any alternative first length as the symbol length corresponding to the whole PUSCH transmission in one time domain unit; or the third TDRA table is used to configure at least one alternative starting symbol position and at least one alternative second length; the third DCI signaling is used to indicate any alternative starting symbol position as the starting symbol position of the first PUSCH transmission in one time domain unit, and indicate any alternative second length as the symbol length corresponding to the once PUSCH transmission in one time domain unit; The starting symbol position and the symbol length of the PUSCH transmission in one time domain unit are determined based on the starting symbol position and the symbol length. The determining of the number of time domain units occupied by the PUSCH comprises at least one of the following:

8. The method of any one of claims 5-7, wherein, The number of time domain units occupied by the PUSCH is determined based on a third RRC parameter sent by the network device; The number of time domain units occupied by the PUSCH is determined based on at least one of a fourth table, a fourth RRC parameter and a fourth DCI signaling; The fourth table and the fourth RRC parameter are used to configure at least one alternative value, and the fourth DCI signaling is used to indicate any alternative value as the number of time domain units occupied by the PUSCH; wherein the fourth table is configured by the network device and / or preset by the protocol; The number of time domain units occupied by the PUSCH is determined based on a fifth DCI signaling sent by the network device. The fourth table comprises a TDRA table and / or a transmission power control (TPC) table.

9. The method of claim 8, wherein, The method further comprises any of the following:

10. The method of any one of claims 1-9, wherein, When the PUSCH is sent, an available slot counting mechanism is enabled, and the PUSCH is sent based on the available slot counting mechanism; When the PUSCH is sent, the PUSCH is sent based on the available slot counting mechanism. The method further comprises at least one of the following:

11. The method of claim 10, wherein, First information is sent to the network device, and the first information is used to indicate whether the terminal supports the available slot counting mechanism; Second information sent by the network device is received, and the second information is used to enable the available slot counting mechanism. The same redundancy version is used between different repeated transmissions in one time domain unit, and redundancy version cycling (RV cycling) is performed between different time domain units; or 12. The method of any one of claims 1-11, wherein, ​ different repetitions within a first window use a same redundancy version, and repetitions between different first windows perform RV cycling; the first window includes L repetitions, L being a sequence length of the OCC sequence; or different repetitions within a second window use a same redundancy version, and repetitions between different second windows perform RV cycling; the second window includes L×B repetitions, L being a sequence length of the OCC sequence, and B being a positive integer, B>1.

13. The method of any one of claims 1-12, wherein, The method further includes: determining whether to perform frequency hopping on the PUSCH; performing frequency hopping on the PUSCH, determining a first frequency hopping manner; transmitting the PUSCH based on the first frequency hopping manner.

14. The method of claim 13, wherein, The determining whether to perform frequency hopping on the PUSCH includes: receiving sixth DCI signaling transmitted by a network device, the sixth DCI signaling being used to indicate whether to perform frequency hopping on the PUSCH.

15. The method of claim 14, wherein, The sixth DCI signaling is further used to indicate a frequency offset value between two adjacent hops.

16. The method of any one of claims 13-15, wherein, The first frequency hopping manner includes: different repetitions within one time domain unit use a same frequency domain resource, and repetitions between different time domain units use different frequency domain resources; or different repetitions within a first window use a same frequency domain resource, and repetitions between different first windows use different frequency domain resources; the first window includes L repetitions, L being a sequence length of the OCC sequence; or different repetitions within a second window use a same frequency domain resource, and repetitions between different second windows use different frequency domain resources; the second window includes L×B repetitions, L being a sequence length of the OCC sequence, and B being a positive integer, B>1.

17. The method of claim 16, wherein, The determining the first frequency hopping manner includes: receiving fifth RRC parameters transmitted by a network device, the fifth RRC parameters being used to configure the first frequency hopping manner as: different repetitions within one time domain unit use a same frequency domain resource, and repetitions between different time domain units use different frequency domain resources, or the fifth RRC parameters being used to configure the first frequency hopping manner as: different repetitions within a first window use a same frequency domain resource, and repetitions between different first windows use different frequency domain resources, or the fifth RRC parameters being used to configure the first frequency hopping manner as: different repetitions within a second window use a same frequency domain resource, and repetitions between different second windows use different frequency domain resources.

18. The method of any one of claims 1-17, wherein, A total number of repetitions of the PUSCH within one time domain unit is divisible by L, L being a sequence length of the OCC sequence.

19. The method of any one of claims 1-18, wherein, The transmitting the PUSCH based on the first transmission manner includes: mapping one sequence value of the OCC sequence to one or more repetitions; wherein one repetition across a time domain unit boundary is mapped by a same sequence value.

20. A method of communication, comprising: The method is performed by a network device, and the method includes: When a terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, a repetition transmission type of the PUSCH is a PUSCH repetition type B, and a transmission mode of the PUSCH configured to the terminal is a first transmission mode or a second transmission mode; the first transmission mode includes that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions; and the second transmission mode includes that any one repetition transmission of the PUSCH does not cross a time domain unit. A first reception mode corresponding to the first transmission mode is determined, or a second reception mode corresponding to the second transmission mode is determined. The PUSCH is received based on the first reception mode or the second reception mode.

21. The method of claim 20, wherein, The second transmission mode includes that the PUSCH occupies N time domain units, the PUSCH performs S times of repetition transmission in each time domain unit, and a symbol position occupied by the PUSCH in different time domain units is the same; S and N are positive integers, and S and N are greater than or equal to 1.

22. The method of claim 20 or 21, wherein, The second transmission mode configured to the terminal includes at least one of the following: A first parameter is sent to the terminal; the first parameter is used to configure the transmission mode of the PUSCH as the second transmission mode, and the first parameter is related to the OCC sequence; The repetition transmission type of the PUSCH is configured as the PUSCH repetition type B; A first radio resource control (RRC) parameter is sent to the terminal; the first RRC parameter is used to indicate whether the PUSCH is transmitted based on the second transmission mode; First indication signaling is sent to the terminal; the first indication signaling is used to indicate that the PUSCH is transmitted based on the second transmission mode; A first time domain resource allocation (TDRA) table or a second RRC parameter is sent to the terminal; the first TDRA table or the second RRC parameter is used to determine that the transmission mode of the PUSCH is the second transmission mode; First downlink control information (DCI) signaling is sent to the terminal; a first field of the first DCI signaling is used to determine that the transmission mode of the PUSCH is the second transmission mode. The method further includes at least one of the following:

23. The method of any one of claims 20-22, wherein, The second TDRA table is sent to the terminal, and second DCI signaling is sent to the terminal; the second TDRA table is used to configure at least one alternative repetition transmission number, and the second DCI signaling is used to indicate any one alternative repetition transmission number as a repetition transmission number of the PUSCH in one time domain unit; The second RRC parameter is sent to the terminal; the second RRC parameter is used to determine a repetition transmission number of the PUSCH in one time domain unit. The method further includes:

24. The method of any one of claims 20-23, wherein, ​ sending, to the terminal, a third TDRA table and a third DCI signaling, wherein the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate first length; the third DCI signaling is used to indicate any candidate starting symbol position as a starting symbol position of a first transmission of the PUSCH in a time domain unit, and indicate any candidate first length as a symbol length corresponding to all transmissions of the PUSCH in the time domain unit; or the third TDRA table is used to configure at least one candidate starting symbol position and at least one candidate second length; the third DCI signaling is used to indicate any candidate starting symbol position as a starting symbol position of a first transmission of the PUSCH in a time domain unit, and indicate any candidate second length as a symbol length corresponding to one transmission of the PUSCH in the time domain unit.

25. The method of any one of claims 20-24, wherein, The method further comprises at least one of the following: sending, to the terminal, a third RRC parameter; the third RRC parameter is used to determine a number of time domain units occupied by the PUSCH; sending, to the terminal, at least one of a fourth table, a fourth RRC parameter, and a fourth DCI signaling; the fourth table and the fourth RRC parameter are used to configure at least one candidate value, and the fourth DCI signaling is used to indicate any candidate value as the number of time domain units occupied by the PUSCH; sending, to the terminal, a fifth DCI signaling; the fifth DCI signaling is used to determine the number of time domain units occupied by the PUSCH.

26. The method of claim 25, wherein, The fourth table comprises a TDRA table and / or a transmission power control (TPC) table.

27. The method of any one of claims 20-26, wherein, The method further comprises: sending, to the terminal, second information; the second information is used to enable an available slot counting mechanism.

28. The method of any one of claims 20-27, wherein, The method further comprises: receiving first information sent by the terminal; the first information is used to indicate whether the terminal supports the available slot counting mechanism.

29. The method of any one of claims 20-28, wherein, The same redundancy version is used between different repeated transmissions in a time domain unit, and redundancy version cycling (RV cycling) is performed between different time domain units; or The same redundancy version is used between different repeated transmissions in a first window, and RV cycling is performed between repeated transmissions in different first windows; the first window comprises L repeated transmissions, and L is a sequence length of the OCC sequence; or The same redundancy version is used between different repeated transmissions in a second window, and RV cycling is performed between repeated transmissions in different second windows; the second window comprises L×B repeated transmissions, L is a sequence length of the OCC sequence, and B is a positive integer, B>1.

30. The method of any one of claims 20-27, wherein, The method further comprises: sending, to the terminal, a sixth DCI signaling; the sixth DCI signaling is used to indicate whether frequency hopping is performed on the PUSCH.

31. The method of claim 30, wherein, The sixth DCI signaling is further used to indicate a frequency offset value between two adjacent hops.

32. The method of any one of claims 20-31, wherein, The method further comprises: sending a fifth RRC parameter to the terminal, the fifth RRC parameter being used to configure the first frequency hopping manner as: different repeated transmissions within one time domain unit use same frequency domain resources, repeated transmissions between different time domain units use different frequency domain resources, or the fifth RRC parameter being used to configure the first frequency hopping manner as: different repeated transmissions within a first window use same frequency domain resources, repeated transmissions between different first windows use different frequency domain resources, or the fifth RRC parameter being used to configure the first frequency hopping manner as: different repeated transmissions within a second window use same frequency domain resources, repeated transmissions between different second windows use different frequency domain resources.

33. The method of any one of claims 20-32, wherein, A total number of repeated transmissions of the PUSCH within one of the time domain units is divisible by L, L being a sequence length of the OCC sequence. 34.A communication method for a communication system, the communication system comprising a terminal and a network device, the method comprising: when the terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, a repetition type of the PUSCH is PUSCH repetition type B, and the network device configures a transmission manner of the PUSCH as a first transmission manner or a second transmission manner, wherein the first transmission manner comprises that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions, and the second transmission manner comprises that any one repetition transmission of the PUSCH does not cross a time domain unit; the terminal transmits the PUSCH based on the first transmission manner or the second transmission manner; the network device determines a first reception manner corresponding to the first transmission manner or a second reception manner corresponding to the second transmission manner; the network device receives the PUSCH based on the first reception manner or the second reception manner.

35. A terminal, characterized by comprising: a processing module configured to, when a terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, a repetition type of the PUSCH is PUSCH repetition type B, and the network device configures a transmission manner of the PUSCH as a first transmission manner or a second transmission manner, transmit the PUSCH based on the first transmission manner or the second transmission manner, wherein the first transmission manner comprises that a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions, and the second transmission manner comprises that any one repetition transmission of the PUSCH does not cross a time domain unit.

36. A network device, comprising: comprising: The processing module is configured to, when a terminal performs multi-user multiplexing transmission on a physical uplink shared channel (PUSCH) based on an orthogonal cover code (OCC) sequence, and a repetition transmission type of the PUSCH is a PUSCH repetition type B, configure the terminal with a first transmission mode or a second transmission mode for transmitting the PUSCH, wherein the first transmission mode comprises: a time domain unit boundary is not used to divide one nominal repetition transmission into two actual repetition transmissions; and the second transmission mode comprises: any one repetition transmission of the PUSCH does not cross a time domain unit. The processing module is further configured to determine a first reception mode corresponding to the first transmission mode, or determine a second reception mode corresponding to the second transmission mode. The transceiver module is configured to receive the PUSCH based on the first reception mode or the second reception mode.

37. A communications device, characterized by The communication device comprises: one or more processors; a memory coupled to the processors and storing instructions which, when executed by the processors, cause the communication device to perform the method of any one of claims 1-19 or claims 20-33.

38. A communication system, characterized by The communication device comprises a terminal and a network device, wherein the terminal is configured to implement the method of any one of claims 1-19, and the network device is configured to implement the method of any one of claims 20-33.

39. A storage medium, the storage medium storing instructions, wherein, The instructions, when executed on the communication device, cause the communication device to perform the method of any one of claims 1-19 or claims 20-33.

40. A program product, characterized by The computer program, when executed on the communication device, implements the method of any one of claims 1-19 or claims 20-33.

Images