Information transmission methods, and apparatus

Abstract

Disclosed in the embodiments of the present disclosure are information transmission methods and an apparatus. A method comprises: determining a first parameter, the first parameter being used for indicating the size of orthogonal cover code (OCC) multiplexing blocks, and data symbols transmitted within the same OCC multiplexing block being different and covering the same value in an OCC sequence; determining a second parameter, the second parameter being the length of the OCC sequence, data symbols transmitted between every second-parameter number of OCC multiplexing blocks being repeated, and each OCC multiplexing block among the second-parameter number of OCC multiplexing blocks covering a different value in the OCC sequence; and, on the basis of the first parameter and the second parameter, transmitting to a network device an OCC multi-user multiplexing-based physical uplink shared channel (PUSCH), such that a terminal can implement OCC multi-user multiplexing-based transmission. The present disclosure can effectively improve the resource utilization rate and the spectrum efficiency, can implement system expansion, and can support more users to perform uplink transmission, thus ensuring the channel transmission performance while improving the system communication efficiency and the system capacity.

Description

Information sending method and device Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method and device for sending information. Background Art

[0002] Non-terrestrial Network (NTN) is an important technology introduced by the fifth generation mobile communication system (5G), which provides wireless resources through satellites (or drones) instead of ground base stations.

[0003] Due to the limited frequency band resources used for NTN, the number of users within the cell radius of satellite coverage is greater, and the transmission distance between the terminal and the satellite is longer. In order to serve more users at the same time, multi-user multiplexing based on orthogonal cover code (OCC) can be considered to achieve uplink capacity enhancement.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a method and device for sending information.

[0006] A first aspect of the present disclosure provides a method for sending information, which is performed by a terminal and includes:

[0007] Determining a first parameter, where the first parameter is used to indicate a size of an orthogonal cover code (OCC) multiplexing block;

[0008] The data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence;

[0009] Determining a second parameter, where the second parameter is a length of the OCC sequence; wherein the data symbols sent between every second parameter number of OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter number of OCC multiplexing blocks covers a different value in the OCC sequence;

[0010] Based on the first parameter and the second parameter, a physical uplink shared channel PUSCH based on the OCC multi-user multiplexing is sent to a network device.

[0011] A second aspect of the present disclosure provides an information sending method, which is performed by a network device and includes:

[0012] The physical uplink shared channel (PUSCH) based on orthogonal cover code (OCC) multi-user multiplexing sent by the receiving terminal;

[0013] The PUSCH is sent by the terminal based on the determined first parameter and second parameter, where the first parameter is used to indicate the size of the OCC multiplexing block, and the second parameter is the length of the OCC sequence, wherein the data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence; the data symbols sent between each second parameter OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter OCC multiplexing blocks covers a different value in the OCC sequence.

[0014] A third embodiment of the present disclosure provides a terminal, including:

[0015] a processing module, configured to determine a first parameter, where the first parameter is used to indicate a size of an orthogonal cover code (OCC) multiplexing block;

[0016] The data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence;

[0017] The processing module is further configured to determine a second parameter, where the second parameter is a length of the OCC sequence; wherein the data symbols sent between every second parameter number of OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter number of OCC multiplexing blocks covers a different value in the OCC sequence;

[0018] The transceiver module is configured to send a physical uplink shared channel (PUSCH) based on the OCC multi-user multiplexing to a network device based on the first parameter and the second parameter.

[0019] A fourth aspect of the present disclosure provides a network device, including:

[0020] The transceiver module is used to receive the physical uplink shared channel (PUSCH) sent by the terminal based on the orthogonal cover code (OCC) multi-user multiplexing;

[0021] The PUSCH is sent by the terminal based on the determined first parameter and second parameter, where the first parameter is used to indicate the size of the OCC multiplexing block, and the second parameter is the length of the OCC sequence, wherein the data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence; the data symbols sent between each second parameter OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter OCC multiplexing blocks covers a different value in the OCC sequence.

[0022] The solution proposed in the embodiment of the present disclosure is to determine a first parameter, which is used to indicate the size of an orthogonal cover code OCC multiplexing block; wherein the data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence; determine a second parameter, which is the length of the OCC sequence; wherein the data symbols sent between each second parameter OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter OCC multiplexing blocks covers a different value in the OCC sequence; based on the first parameter and the second parameter, send a physical uplink shared channel PUSCH based on OCC multi-user multiplexing to the network device; enable the terminal to realize transmission based on OCC multi-user multiplexing, effectively improve resource utilization and spectrum efficiency, realize system expansion, support more users for uplink transmission, improve system communication efficiency and system capacity, and at the same time ensure channel transmission performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0024] FIG1A is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0025] FIG2A is an interactive diagram of an information sending method provided by an embodiment of the present disclosure;

[0026] 2B-2I are schematic diagrams of an OCC multi-user multiplexing solution provided by an embodiment of the present disclosure;

[0027] FIG3A is a schematic diagram of a flow chart of an information sending method provided by an embodiment of the present disclosure;

[0028] FIG4A is a flow chart of an information sending method provided by an embodiment of the present disclosure;

[0029] FIG5 is a flow chart of an information sending method provided by an embodiment of the present disclosure;

[0030] FIG6A is a schematic structural diagram of a terminal provided by an embodiment of the present disclosure;

[0031] FIG6B is a schematic structural diagram of another network device provided by an embodiment of the present disclosure;

[0032] FIG7A is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0033] FIG7B is a schematic structural diagram of a chip provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] The embodiments of the present disclosure provide a method and apparatus for sending information.

[0035] In a first aspect, an embodiment of the present disclosure provides a method for sending information, the method comprising:

[0036] Determining a first parameter, where the first parameter is used to indicate a size of an orthogonal cover code (OCC) multiplexing block;

[0037] The data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence;

[0038] Determining a second parameter, where the second parameter is a length of the OCC sequence; wherein the data symbols sent between every second parameter number of OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter number of OCC multiplexing blocks covers a different value in the OCC sequence;

[0039] Based on the first parameter and the second parameter, a physical uplink shared channel PUSCH based on the OCC multi-user multiplexing is sent to a network device.

[0040] In the above embodiment, the terminal can realize transmission based on OCC multi-user multiplexing, which can effectively improve resource utilization and spectrum efficiency, realize system expansion, support more users for uplink transmission, improve system communication efficiency and system capacity, and at the same time ensure channel transmission performance.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the OOC multiplexing includes at least one of the following:

[0042] Time domain OCC multiplexing;

[0043] Frequency domain OCC multiplexing;

[0044] Time-frequency domain OCC multiplexing;

[0045] OCC multiplexing of pre-DFT before discrete Fourier transform.

[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the OOC multiplexing is time-domain OCC multiplexing, and the PUSCH is repeatedly transmitted, the OCC multiplexing is based on repeated PUSCH or time slot multiplexing, and determining the first parameter includes:

[0047] Determine the first parameter based on the agreement of the protocol; or,

[0048] determining the first parameter based on the number of repeated transmissions of the PUSCH, the second parameter, and the third parameter; or

[0049] determining the first parameter based on the indication information sent by the network device; or,

[0050] The first parameter is determined to be a first multiple of 4, where the first multiple is a positive integer.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the PUSCH repetition transmission is type A PUSCH repetition transmission, or the PUSCH repetition transmission is type B PUSCH repetition transmission.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the redundancy version RV corresponding to each PUSCH in the repeatedly transmitted PUSCH is the same; or,

[0053] For at least one cyclic redundancy version RV corresponding to the PUSCH included in the same OCC multiplexing block, the RVs and the cyclic order of the RVs included in each second parameter of OCC multiplexing blocks are the same; or,

[0054] The redundancy versions RV corresponding to the second parameter PUSCHs in the repeatedly transmitted PUSCH are the same.

[0055] In combination with some embodiments of the first aspect, in some embodiments, the PUSCH repetition is type A PUSCH repetition, and the unit of the first parameter is the time domain resource occupied by a repeated transmission of the PUSCH, or the unit of the first parameter is a time slot.

[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the PUSCH repeated transmission is type B PUSCH repeated transmission, and the unit of the first parameter is the time domain resource occupied by the PUSCH repeatedly transmitted once;

[0057] The repeatedly transmitted PUSCH is a nominally repeatedly transmitted PUSCH, or the repeatedly transmitted PUSCH is an actually repeatedly transmitted PUSCH.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the PUSCH repeated transmission is a type A PUSCH repeated transmission;

[0059] The terminal resource allocation method is based on an available time slot counting mechanism, wherein the terminal expects that the available time slots corresponding to other terminals in the same user group are located at the same position in the time domain, wherein the multiple terminals in the same user group use the same time-frequency domain resources; or

[0060] The terminal does not expect to configure repeated PUSCH or time slot based OCC multiplexing and available time slot counting mechanism at the same time.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the PUSCH repeated transmission is a type B PUSCH repeated transmission;

[0062] The terminal expects that the symbol position of the time domain resources corresponding to other terminals in the same user group is the same, wherein the time and frequency domain resources used by multiple terminals included in the same user group are the same.

[0063] In combination with some embodiments of the first aspect, in some embodiments, the terminal expects that the starting time domain position corresponding to the PUSCH repeatedly sent by other terminals in the same user group is the same.

[0064] In combination with some embodiments of the first aspect, in some embodiments, the terminal expects the number of PUSCH repetition transmissions to be the same as the number of PUSCH repetition transmissions of other terminals in the same user group; or,

[0065] The terminal expects that the ratio of the number of PUSCH repetition transmissions to the second parameter is the same as the ratio of the number of PUSCH repetition transmissions to the second parameter of other terminals in the same user group, where each terminal has a corresponding second parameter.

[0066] With reference to some embodiments of the first aspect, in some embodiments, the OOC multiplexing is time-domain OCC multiplexing, the OCC multiplexing is symbol-based multiplexing, and determining the first parameter includes:

[0067] Determine the first parameter based on the agreement of the protocol; or,

[0068] determining the first parameter based on the number of available symbols, the second parameter, and a third parameter; or

[0069] The first parameter is determined based on the indication information sent by the network device.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the PUSCH is a PUSCH transmitted based on a single time slot; or,

[0071] The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following:

[0072] Type A PUSCH is repeatedly transmitted;

[0073] Type B PUSCH is repeatedly transmitted;

[0074] PUSCH based on multi-slot transport blocks TBoMS;

[0075] Type A PUSCH repetition transmission based on multi-slot transport blocks TBoMS.

[0076] With reference to some embodiments of the first aspect, in some embodiments, the PUSCH is a type B PUSCH that is repeatedly transmitted;

[0077] The terminal expects that each time a PUSCH is actually sent, the position of the time domain resources corresponding to each PUSCH actually sent by other terminals in the same user group is the same, wherein the time and frequency domain resources used by multiple terminals included in the same user group are the same.

[0078] With reference to some embodiments of the first aspect, in some embodiments, the PUSCH is a type B PUSCH that is repeatedly transmitted;

[0079] The terminal expects that the starting time domain symbol of the PUSCH repeated transmission is the same as the starting time domain symbol corresponding to other terminals in the same user group, and the terminal expects that the symbol length is the same as that of the other terminals in the same user group.

[0080] In conjunction with some embodiments of the first aspect, in some embodiments, the PUSCH is a PUSCH transmitted based on multiple time slots;

[0081] The OCC multiplexing is performed based on symbols in each time slot; or

[0082] The OCC multiplexing is based on the symbols in the time domain resources occupied by each TBoMS transmission; or,

[0083] The OCC multiplexing is performed based on symbols in the time domain resources occupied by each repetition.

[0084] In combination with some embodiments of the first aspect, in some embodiments, the unit of the first parameter is a time domain symbol.

[0085] In combination with some embodiments of the first aspect, in some embodiments, the terminal expects that the starting symbol position corresponding to the PUSCH sent by other terminals in the same user group in a time slot is the same.

[0086] In conjunction with some embodiments of the first aspect, in some embodiments, the number of available symbols of the terminal is the same as the number of available symbols of other terminals in the same user group; or,

[0087] The ratio of the number of available symbols of the terminal to the second parameter is the same as the ratio of the number of available symbols of other terminals in the same user group to the second parameter, wherein each terminal has a corresponding second parameter.

[0088] With reference to some embodiments of the first aspect, in some embodiments, the OOC multiplexing is frequency-domain OCC multiplexing, and determining the first parameter includes:

[0089] Determine the first parameter based on the agreement of the protocol; or,

[0090] Determine the first parameter based on a sub-physical resource block sub PRB and the second parameter; or,

[0091] Determine the first parameter based on the number of resource blocks (RBs) allocated to the terminal, the second parameter, and a third parameter; or

[0092] The first parameter is determined based on the indication information sent by the network device.

[0093] In combination with some embodiments of the first aspect, in some embodiments, the unit of the first parameter is a resource unit RE, or the unit of the first parameter is a resource block RB.

[0094] With reference to some embodiments of the first aspect, in some embodiments, the OOC multiplexing is time-frequency domain OCC multiplexing, and determining the first parameter includes:

[0095] Determine the first parameter based on the agreement of the protocol; or,

[0096] Determine the first parameter based on a sub-physical resource block sub PRB and the second parameter; or,

[0097] Determine the first parameter based on the number of resource blocks (RBs) allocated to the terminal, the number of available symbols, the second parameter, and the third parameter; or

[0098] The first parameter is determined based on the indication information sent by the network device.

[0099] In combination with some embodiments of the first aspect, in some embodiments, the PUSCH is a PUSCH transmitted based on a single time slot; or,

[0100] The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following:

[0101] Type A PUSCH is repeatedly transmitted;

[0102] Type B PUSCH is repeatedly transmitted;

[0103] PUSCH based on multi-slot transport blocks TBoMS;

[0104] Repeated transmission of multi-slot transport blocks TBoMS.

[0105] With reference to some embodiments of the first aspect, in some embodiments, the OOC multiplexing is pre-DFT OCC multiplexing, and determining the first parameter includes:

[0106] The first parameter is determined based on at least one of the following parameters:

[0107] The number of resource blocks (RBs) allocated to the terminal;

[0108] The number of users multiplexed by the OCC;

[0109] The number of resource units RE in a resource block RB.

[0110] In combination with some embodiments of the first aspect, in some embodiments, the PUSCH is a PUSCH transmitted based on a single time slot; or,

[0111] The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following:

[0112] Type A PUSCH is repeatedly transmitted;

[0113] Type B PUSCH is repeatedly transmitted;

[0114] PUSCH based on multi-slot transport blocks TBoMS;

[0115] Repeated transmission of multi-slot transport blocks TBoMS.

[0116] In combination with some embodiments of the first aspect, in some embodiments, the OCC expansion is performed before discrete Fourier transform DFT.

[0117] With reference to some embodiments of the first aspect, in some embodiments, the PUSCH sent by the terminal and the PUSCH sent by other terminals in the same user group use different subcarriers.

[0118] In conjunction with some embodiments of the first aspect, in some embodiments, the PUSCH is a PUSCH based on a multi-slot transport block TBoMS, and the method further includes:

[0119] Based on the resources of a time slot, a transport block TB carried by the PUSCH is determined.

[0120] In combination with some embodiments of the first aspect, in some embodiments, the PUSCH further includes: a multi-tone NPUSCH that transmits multiple subcarriers.

[0121] In a second aspect, an embodiment of the present disclosure provides a method for sending information, the method comprising:

[0122] The physical uplink shared channel (PUSCH) based on orthogonal cover code (OCC) multi-user multiplexing sent by the receiving terminal;

[0123] The PUSCH is sent by the terminal based on the determined first parameter and second parameter, where the first parameter is used to indicate the size of the OCC multiplexing block, and the second parameter is the length of the OCC sequence, wherein the data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence; the data symbols sent between each second parameter OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter OCC multiplexing blocks covers a different value in the OCC sequence.

[0124] In the above embodiment, the terminal can realize transmission based on OCC multi-user multiplexing, which can effectively improve resource utilization and spectrum efficiency, realize system expansion, support more users for uplink transmission, improve system communication efficiency and system capacity, and at the same time ensure channel transmission performance.

[0125] In conjunction with some embodiments of the second aspect, in some embodiments, the OOC multiplexing includes at least one of the following:

[0126] Time domain OCC multiplexing;

[0127] Frequency domain OCC multiplexing;

[0128] Time-frequency domain OCC multiplexing;

[0129] OCC multiplexing of pre-DFT before discrete Fourier transform.

[0130] In conjunction with some embodiments of the second aspect, in some embodiments, the OOC multiplexing is time domain OCC multiplexing, and the PUSCH is repeatedly transmitted, and the OCC multiplexing is based on repeated PUSCH or time slot multiplexing;

[0131] The first parameter is determined based on the agreement of the protocol; or,

[0132] The first parameter is determined based on the number of times the PUSCH is repeatedly transmitted, the second parameter, and a third parameter; or,

[0133] The first parameter is determined based on indication information sent by the network device; or,

[0134] The first parameter is a first multiple of 4, wherein the first multiple is a positive integer.

[0135] In combination with some embodiments of the second aspect, in some embodiments, the PUSCH repetition transmission is type A PUSCH repetition transmission, or the PUSCH repetition transmission is type B PUSCH repetition transmission.

[0136] In conjunction with some embodiments of the second aspect, in some embodiments, the redundancy version RV corresponding to each PUSCH in the repeatedly transmitted PUSCH is the same; or,

[0137] For at least one cyclic redundancy version RV corresponding to the PUSCH included in the same OCC multiplexing block, the RVs and the cyclic order of the RVs included in each second parameter of OCC multiplexing blocks are the same; or,

[0138] The redundancy versions RV corresponding to the second parameter PUSCHs in the repeatedly transmitted PUSCH are the same.

[0139] In combination with some embodiments of the second aspect, in some embodiments, the PUSCH repetition is type A PUSCH repetition, and the unit of the first parameter is the time domain resource occupied by a repeated transmission of the PUSCH, or the unit of the first parameter is a time slot.

[0140] In conjunction with some embodiments of the second aspect, in some embodiments, the PUSCH repeated transmission is type B PUSCH repeated transmission, and the unit of the first parameter is the time domain resource occupied by the PUSCH repeatedly transmitted once;

[0141] The repeatedly transmitted PUSCH is a nominally repeatedly transmitted PUSCH, or the repeatedly transmitted PUSCH is an actually repeatedly transmitted PUSCH.

[0142] In conjunction with some embodiments of the second aspect, in some embodiments, the PUSCH repeated transmission is a PUSCH repeated transmission of type A;

[0143] The resource allocation mode of the terminal is based on an available time slot counting mechanism, and the terminal expects that the available time slots corresponding to other terminals in the same user group are located at the same position in the time domain, wherein the multiple terminals included in the same user group use the same time-frequency domain resources; or

[0144] The terminal does not expect to configure repeated PUSCH or time slot based OCC multiplexing and available time slot counting mechanism at the same time.

[0145] In conjunction with some embodiments of the second aspect, in some embodiments, the PUSCH repeated transmission is a type B PUSCH repeated transmission;

[0146] The terminal expects that the symbol position of the time domain resources corresponding to other terminals in the same user group is the same, wherein the time and frequency domain resources used by multiple terminals included in the same user group are the same.

[0147] In combination with some embodiments of the second aspect, in some embodiments, the terminal expects that the starting time domain position corresponding to the PUSCH repeatedly sent by other terminals in the same user group is the same.

[0148] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal expects the number of PUSCH repetition transmissions to be the same as the number of PUSCH repetition transmissions of other terminals in the same user group; or,

[0149] The terminal expects that the ratio of the number of PUSCH repetition transmissions to the second parameter is the same as the ratio of the number of PUSCH repetition transmissions to the second parameter of other terminals in the same user group, where each terminal has a corresponding second parameter.

[0150] With reference to some embodiments of the second aspect, in some embodiments, the OOC multiplexing is time-domain OCC multiplexing, and the OCC multiplexing is multiplexed based on symbols;

[0151] The first parameter is determined based on the agreement of the protocol; or,

[0152] The first parameter is determined based on the number of available symbols, the second parameter and the third parameter; or,

[0153] The first parameter is determined based on indication information sent by the network device.

[0154] In conjunction with some embodiments of the second aspect, in some embodiments, the PUSCH is a PUSCH transmitted based on a single time slot; or,

[0155] The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following:

[0156] Type A PUSCH is repeatedly transmitted;

[0157] Type B PUSCH is repeatedly transmitted;

[0158] PUSCH based on multi-slot transport blocks TBoMS;

[0159] Type A PUSCH repetition transmission based on multi-slot transport blocks TBoMS.

[0160] With reference to some embodiments of the second aspect, in some embodiments, the PUSCH is a type B PUSCH that is repeatedly transmitted;

[0161] The terminal expects that each time a PUSCH is actually sent, the position of the time domain resources corresponding to each PUSCH actually sent by other terminals in the same user group is the same, wherein the time and frequency domain resources used by multiple terminals included in the same user group are the same.

[0162] With reference to some embodiments of the second aspect, in some embodiments, the PUSCH is a type B PUSCH that is repeatedly transmitted;

[0163] The terminal expects that the starting time domain symbol of the PUSCH repeated transmission is the same as the starting time domain symbol corresponding to other terminals in the same user group, and the terminal expects that the symbol length is the same as that of the other terminals in the same user group.

[0164] In conjunction with some embodiments of the second aspect, in some embodiments, the PUSCH is a PUSCH transmitted based on multiple time slots;

[0165] The OCC multiplexing is performed based on symbols in each time slot; or

[0166] The OCC multiplexing is based on the symbols in the time domain resources occupied by each TBoMS transmission; or,

[0167] The OCC multiplexing is performed based on symbols in the time domain resources occupied by each repetition.

[0168] In combination with some embodiments of the second aspect, in some embodiments, the unit of the first parameter is symbol.

[0169] In combination with some embodiments of the second aspect, in some embodiments, the terminal expects that the starting symbol position corresponding to the PUSCH sent by other terminals in the same user group in a time slot is the same.

[0170] In conjunction with some embodiments of the second aspect, in some embodiments, the number of available symbols of the terminal is the same as the number of available symbols of other terminals in the same user group; or,

[0171] The ratio of the number of available symbols of the terminal to the second parameter is the same as the ratio of the number of available symbols of other terminals in the same user group to the second parameter, wherein each terminal has a corresponding second parameter.

[0172] With reference to some embodiments of the second aspect, in some embodiments, the OOC multiplexing is frequency domain OCC multiplexing;

[0173] The first parameter is determined based on the agreement of the protocol; or,

[0174] The first parameter is determined based on a sub-physical resource block sub PRB and the second parameter; or

[0175] The first parameter is determined based on the number of resource blocks (RBs) allocated to the terminal, the second parameter, and a third parameter; or

[0176] The first parameter is determined based on indication information sent by the network device.

[0177] In combination with some embodiments of the second aspect, in some embodiments, the unit of the first parameter is a resource unit RE, or the unit of the first parameter is a resource block RB.

[0178] With reference to some embodiments of the second aspect, in some embodiments, the OOC multiplexing is time-frequency domain OCC multiplexing;

[0179] The first parameter is determined based on the agreement of the protocol; or,

[0180] The first parameter is determined based on a sub-physical resource block sub PRB and the second parameter; or,

[0181] The first parameter is determined based on the number of resource blocks (RBs) allocated to the terminal, the number of available symbols, the second parameter, and the third parameter; or,

[0182] The first parameter is determined based on indication information sent by the network device.

[0183] In conjunction with some embodiments of the second aspect, in some embodiments, the PUSCH is a PUSCH transmitted based on a single time slot; or,

[0184] The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following:

[0185] Type A PUSCH is repeatedly transmitted;

[0186] Type B PUSCH is repeatedly transmitted;

[0187] PUSCH based on multi-slot transport blocks TBoMS;

[0188] Repeated transmission of multi-slot transport blocks TBoMS.

[0189] With reference to some embodiments of the second aspect, in some embodiments, the OOC multiplexing is pre-DFT OCC multiplexing;

[0190] The first parameter is determined based on at least one of the following parameters:

[0191] The number of resource blocks (RBs) allocated to the terminal;

[0192] The number of users multiplexed by the OCC;

[0193] The number of resource units RE in a resource block RB.

[0194] In conjunction with some embodiments of the second aspect, in some embodiments, the PUSCH is a PUSCH transmitted based on a single time slot; or,

[0195] The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following:

[0196] Type A PUSCH is repeatedly transmitted;

[0197] Type B PUSCH is repeatedly transmitted;

[0198] PUSCH based on multi-slot transport blocks TBoMS;

[0199] Repeated transmission of multi-slot transport blocks TBoMS.

[0200] In combination with some embodiments of the second aspect, in some embodiments, the OCC expansion is performed before discrete Fourier transform DFT.

[0201] With reference to some embodiments of the second aspect, in some embodiments, the PUSCH sent by the terminal and the PUSCH sent by other terminals in the same user group use different subcarriers.

[0202] In combination with some embodiments of the second aspect, in some embodiments, the PUSCH is a PUSCH based on a multi-slot transport block TBoMS, and the transport block TB carried by the PUSCH is determined based on resources of one time slot.

[0203] In combination with some embodiments of the second aspect, in some embodiments, the PUSCH further includes: a multi-tone NPUSCH that transmits multiple subcarriers.

[0204] In a third aspect, an embodiment of the present disclosure provides a method for sending information, the method comprising:

[0205] The terminal determines a first parameter, where the first parameter is used to indicate a size of an orthogonal cover code (OCC) multiplexing block;

[0206] The data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence;

[0207] The terminal determines a second parameter, where the second parameter is a length of the OCC sequence; wherein the data symbols sent between every second parameter number of OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter number of OCC multiplexing blocks covers a different value in the OCC sequence;

[0208] The terminal sends a physical uplink shared channel PUSCH based on the OCC multi-user multiplexing to a network device based on the first parameter and the second parameter.

[0209] In a fourth aspect, an embodiment of the present disclosure proposes a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0210] In a fifth aspect, an embodiment of the present disclosure proposes a network device, which includes a transceiver module and a processing module; wherein the network device is used to execute the second aspect and the optional implementation method of the second aspect.

[0211] In a sixth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; wherein the terminal is used to execute the first aspect and the optional implementation method of the first aspect.

[0212] In a seventh aspect, an embodiment of the present disclosure proposes a network device, comprising: one or more processors; wherein the network device is used to execute the second aspect and the optional implementation method of the second aspect.

[0213] In the eighth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a terminal and a network device; wherein the terminal is configured to execute the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to execute the method described in the second aspect and the optional implementation of the second aspect.

[0214] In the ninth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0215] In a tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0216] In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect and the optional implementation of the first aspect, the second aspect and the optional implementation of the second aspect.

[0217] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in accordance with the first aspect and its optional implementation, the second aspect and its optional implementation.

[0218] It is understandable that the above-mentioned terminals, access network devices, core network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0219] The present disclosure provides an information transmission method and apparatus. In some embodiments, the terms "information transmission method" and "information processing method" and "communication method" are interchangeable; the terms "information transmission apparatus" and "information processing apparatus" and "communication apparatus" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0220] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0221] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0222] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0223] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "above", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0224] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0225] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0226] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0227] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0228] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0229] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

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

[0231] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0232] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0233] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0234] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0235] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0236] In some embodiments, "terminal" or "terminal device" may be referred to as "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, etc.

[0237] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0238] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0239] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

[0241] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0242] FIG1A is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0243] As shown in FIG. 1A , a communication system 100 includes a network device 101 and a terminal 102 .

[0244] In some embodiments, the access network device 101 is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include nodes such as satellites or drones in an information sending network, evolved NodeB (eNB) in a 5G communication system, next generation evolved NodeB (ng-eNB), next generation NodeB (gNB), next generation RAN node (NG-RAN node), node B (NB), home node B (HNB), home evolved nodeB (HeNB), wireless backhaul equipment, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open base station (Open RAN), cloud base station (Cloud RAN), base station in other communication systems, and at least one of access nodes in a Wi-Fi system, but is not limited thereto.

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

[0246] In some embodiments, the network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0247] In some embodiments, the terminal 102 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, 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 at least one of a reduced capability (RedCap) terminal, but is not limited thereto.

[0248] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0249] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0250] The embodiments of the present disclosure may be applied to non-terrestrial networks (NTN), 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.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX ( 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0251] In some embodiments, a non-terrestrial network (NTN) is an important technology introduced by the fifth-generation mobile communication system (5G). It provides wireless resources through satellites (or UAS platforms, where UAS is an unmanned aircraft system) rather than ground base stations, as shown in Figure 1A. The link between the satellite and the terminal is called a service link.

[0252] In NTN, uplink capacity enhancement is considered to serve more users simultaneously for the following reasons:

[0253] 1. The frequency band resources used for NTN are limited;

[0254] 2. Satellite coverage has a larger cell radius, and the number of users in a cell is greater than that of terrestrial networks;

[0255] 3. The transmission distance between the terminal and the satellite is relatively long. Under the premise of limited terminal transmission power, in order to improve cell coverage and transmission performance, the NTN network often needs to perform more blind retransmissions, which will greatly waste spectrum resources and reduce spectrum efficiency.

[0256] Therefore, multi-user multiplexing based on orthogonal cover codes (OCC) is considered to achieve uplink capacity enhancement.

[0257] In summary, for the scenario of OCC multi-user multiplexing, it is necessary to consider how to design the OCC multiplexing solution.

[0258] The information sending method and device provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0259] FIG2A is an interactive diagram of a method for sending information according to an embodiment of the present disclosure. As shown in FIG2A , the embodiment of the present disclosure relates to a method for sending information, and the method includes:

[0260] In step S2101, the terminal 102 determines a first parameter.

[0261] In some embodiments, the first parameter is used to indicate the size of the OCC multiplexing block.

[0262] The data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence.

[0263] As an example, as shown in FIG2B , the length of the OCC sequence used in this example is 4 (OCC length = 4), the OCC sequence is (1, -1, 1, -1), and there are four OCC multiplexing blocks (Block#1-Block#4). Among them, multiplexing block Block#1 includes data symbols d(0)-d(5), that is, the data symbols sent in the same OCC multiplexing block are different, and the data symbols in the entire multiplexing block Block#1 cover the first value "1" in the OCC sequence. The data symbols included in each of the subsequently sent multiplexing blocks Block#2-Block#4 are repetitions of Block#1, that is, the data symbols sent between each OCC multiplexing block of the length of the OCC sequence (4 in this example) are repeated, but each of the four OCC multiplexing blocks covers a different value in the OCC sequence. Block #2 covers the second value "-1" in the OCC sequence, Block #3 covers the third value "1" in the OCC sequence, and Block #4 covers the fourth value "-1" in the OCC sequence.

[0264] It should be noted that the data symbols included in the multiplexing block refer to the modulated data symbols sent within the multiplexing block. The data symbols are mapped to resources for transmission. The mapped resources occupy an orthogonal frequency division multiplexing (OFDM) symbol (OFDM symbol, OS) in the time domain and a resource element (RE) in the frequency domain.

[0265] In various embodiments of the present disclosure, the length of the OCC sequence is a second parameter determined by the terminal 102 .

[0266] Optionally, the second parameter may also be the number of users multiplexed by the OCC.

[0267] It should be noted that in each embodiment of the present disclosure, the length of the OCC sequence is equal to the number of users multiplexed by the OCC.

[0268] In some embodiments, the name of the first parameter is not limited, and may be, for example, "block size", "OCC multiplexing block", "multiplexing block size", etc.

[0269] In some embodiments, the OCC multi-user multiplexing mode adopted by the terminal 102 includes at least one of the following:

[0270] Time domain OCC multiplexing; frequency domain OCC multiplexing; time-frequency domain OCC multiplexing; pre-DFT (before discrete Fourier transform DFT) OCC multiplexing.

[0271] Optionally, when the terminal 102 performs time-domain OCC multiplexing, it may be performed based on a time-domain symbol granularity or a time slot granularity.

[0272] In some embodiments, the Physical Uplink Shared Channel (PUSCH) sent by the terminal 102 has repetition enabled, and the OCC multiplexing may also be performed based on the granularity of one repetition.

[0273] In some embodiments, the terminal 102 performs time-domain OCC multiplexing and enables PUSCH repetition. The OCC multiplexing is based on repeated PUSCH or time slot multiplexing.

[0274] In some embodiments, the repetition transmission of the PUSCH may be based on type A repetition transmission (repetition type A) or based on type B repetition transmission (repetition type B).

[0275] Optionally, the first parameter is determined based on a protocol agreement.

[0276] As a possible approach, the value of the first parameter is 1.

[0277] As an example, as shown in Figure 2C , assume that the number of users using OCC multiplexing is two (UE#1 and UE#2), the length of the OCC sequence is 2, the number of repetitions for UE#1 is 8, and the number of repetitions for UE#2 is 4. The PUSCH is based on type A repetition transmission (repetition type A), the scheduling type of the PUSCH is configured grant (CG) PUSCH type 1 (CG PUSCH type 1), the OCC sequence used by UE#1 is (1,1), and the OCC sequence used by UE#2 is (1,-1). The value of the first parameter is 1 (block size = 1), which means that each OCC multiplexing block includes one repetition. The first and second OCC multiplexing blocks of UE#1 transmit redundancy version (RV) RV#0. The first multiplexing block covers the first value "1" in the OCC sequence, and the second multiplexing block covers the second value "1" in the OCC sequence. UE#1's third and fourth OCC multiplexing blocks transmit RV#2. The third multiplexing block covers the first value "1" in the OCC sequence, and the fourth multiplexing block covers the second value "1" in the OCC sequence. UE#1's fifth and sixth OCC multiplexing blocks transmit RV#3. The fifth multiplexing block covers the first value "1" in the OCC sequence, and the sixth multiplexing block covers the second value "1" in the OCC sequence. UE#1's seventh and eighth OCC multiplexing blocks transmit RV#1. The seventh multiplexing block covers the first value "1" in the OCC sequence, and the eighth multiplexing block covers the second value "1" in the OCC sequence. UE#2's OCC sequence is orthogonal to that of UE#1. UE#2's first and second OCC multiplexing blocks transmit RV#0. The first multiplexing block covers the first value "1" in the OCC sequence, and the second multiplexing block covers the second value "-1" in the OCC sequence. The third and fourth OCC multiplexing blocks of UE#2 send RV#3. The third multiplexing block covers the first value "1" in the OCC sequence, and the fourth multiplexing block covers the second value "-1" in the OCC sequence.

[0278] Optionally, the first parameter is determined based on the number of PUSCH repetitions of the terminal 102, the second parameter and the third parameter.

[0279] As a possible manner, the first parameter = the number of repetitions / the second parameter / the third parameter.

[0280] As a possible approach, the value of the third parameter may be 1.

[0281] As a possible approach, the third parameter may be agreed upon by a protocol, or configured or indicated by the network device 101 .

[0282] As an example, as shown in Figure 2D , assume that the number of users using OCC multiplexing is two (UE#1 and UE#2), the OCC sequence length is 2, and the repetition count for both UE#1 and UE#2 is 8. The PUSCH is repetition type A-based, the PUSCH scheduling type is CG PUSCH type 1, the OCC sequence used by UE#1 is (1,1), and the OCC sequence used by UE#2 is (1,-1). The value of the third parameter is 1, which determines the value of the first parameter to be: 8 / 2 / 1 = 4. This means that each OCC multiplexing block includes four repetitions. UE#1's first OCC multiplexing block transmits {RV#0, RV#2, RV#3, RV#1}, and the second OCC multiplexing block also transmits {RV#0, RV#2, RV#3, RV#1}. The first multiplexing block covers the first value "1" in the OCC sequence, and the second multiplexing block covers the second value "1" in the OCC sequence. The first OCC multiplexing block sent by UE#2 is {RV#0, RV#3, RV#0, RV#3}, and the second OCC multiplexing block sent is also {RV#0, RV#3, RV#0, RV#3}. The first multiplexing block covers the first value "1" in the OCC sequence, and the second multiplexing block covers the second value "-1" in the OCC sequence.

[0283] Optionally, the terminal 102 determines the first parameter based on indication information sent by the network device 101. The indication information directly indicates the first parameter.

[0284] As a possible approach, the terminal 102 adopts a continuous time slot counting mechanism to determine the duration of the OCC multiplexing block in a back-to-back manner starting from the starting time domain position of the repetition; or, the terminal 102 adopts an available time slot counting mechanism to determine the time domain resources occupied by the OCC multiplexing block according to the number of repetitions.

[0285] In some embodiments, the first parameter is determined to be a first multiple of 4, and the first multiple is a positive integer.

[0286] As an example, when the ratio of the number of repetitions to the number of multiplexed users is 4*M (where M is a positive integer), the first parameter (block size) is determined to be 4*N, that is, a multiplexing block includes 4*N repetitions, where N is a positive integer and M is divisible by N, for example, N=1, N=M, etc., where positive integer multiples of 4 are used to ensure that the block size is greater than the length of the RV sequence (sequence length), such as {#0,#2,#3,#1}, {#0,#3,#0,#3}, etc., so that the RV version can be changed within an OCC multiplexing block, but the RV on the corresponding repetition or slot remains consistent between the spreading OCC sequence length (second parameter) OCC multiplexing blocks. In this way, different CG PUSCH users are allowed to use different RV cycling sequences.

[0287] In some embodiments, for repetition-based or time slot-based OCC multiplexing, RV cycling may be canceled, and each repeated transmission uses the same RV, such as {0, 0, 0, 0}.

[0288] In some embodiments, for OCC multiplexing based on repetition or time slot, the redundancy version RV can be circulated within an OCC multiplexing block, but the RV on the repetition or time slot at the corresponding position remains consistent between OCC multiplexing blocks of the OCC sequence length, as shown in Figure 2D above.

[0289] In some embodiments, the PUSCH repetition transmission is type A PUSCH repetition transmission, the unit of the first parameter is the time domain resource occupied by one repeated transmission of the PUSCH, or the unit of the first parameter is a time slot.

[0290] In some embodiments, the above-mentioned PUSCH repetition is type B PUSCH repetition, and the unit of the above-mentioned first parameter is the time domain resource occupied by a repeated transmission of the PUSCH; wherein, the repeated transmission of the PUSCH is a nominal repeated transmission of the PUSCH (nominal repetition), or, the repeated transmission of the PUSCH is an actual repeated transmission of the PUSCH (actual repetition).

[0291] In some embodiments, for repeated transmission of PUSCH of type A, if the terminal 102 adopts an available time slot counting mechanism to perform repeated transmission of PUSCH, the terminal 102 does not expect that the position of the available time slot determined by other terminals in the same multiplexing user group is different in the time domain, that is, the terminal 102 expects that the position of the available time slot determined by other terminals in the same multiplexing user group is the same in the time domain; or, the terminal does not expect the available time slot counting mechanism to be enabled simultaneously with repetition-based or time slot-based OCC multiplexing.

[0292] In some embodiments, for repeated transmission of the PUSCH of type B, the terminal 102 expects to have the same time domain resource allocation (the time domain position of the symbols is the same) as other terminals in the same multiplexing user group.

[0293] In some embodiments, the terminal 102 expects the starting time domain position of the repetition to be the same as that of other terminals in the same multiplexing user group.

[0294] In some embodiments, the terminal 102 expects that the starting time domain position for OCC coverage will be the same as that of other terminals in the same multiplexing user group.

[0295] In some embodiments, the available slot counting mechanism of the terminal 102 is enabled, and the unit of the first parameter is slot, where the first parameter = the slots occupied by all repeatedly transmitted PUSCHs / the second parameter / the third parameter.

[0296] In some embodiments, for the terminal 102 to determine the first parameter based on the number of repetitions, the terminal 102 expects to have the same number of repetitions as other terminals in the same multiplexing user group; or, the terminal 102 expects the ratio of the number of repetitions corresponding to other terminals in the same multiplexing user group to the third parameter to be the same.

[0297] In some embodiments, in a manner where terminal 102 expects the ratio of the number of repetitions corresponding to other terminals in the same multiplexed user group to be the same as the third parameter, a certain constraint relationship exists between the number of repetitions and the second parameter (number of multiplexed users): the number of repetitions must be divisible by the second parameter. Alternatively, this constraint relationship may not be satisfied. When this constraint relationship is not satisfied, the resources occupied by the remaining number of repetitions, that is, mod(repetition number, second parameter), are no longer subject to OCC multiplexing. Of course, other design ideas are not excluded, such as aligning the end positions of the time domain resources of the multiplexed repetitions at the end, and excluding the resources occupied by the remaining number of repetitions at the beginning from OCC multiplexing.

[0298] In some embodiments, the length of the OCC sequence (also called the OCC code length) may be the same as the number of repetitions, and the number of multiplexed users may be less than the length of the OCC sequence. In this case, repetition is required not to perform RV cycling (which is applicable to channels with relatively slow time domain changes).

[0299] In some embodiments, the length of the OCC sequence can also be determined based on the number of repetitions. For example, the number of repetitions needs to be guaranteed to be an integer multiple of the length of the OCC sequence, and the length of the OCC sequence is greater than or equal to the number of OCC multiplexed users. In this case, the terminal needs to know the length of the OCC sequence and information related to the OCC sequence index.

[0300] In some embodiments, the terminal 102 may consider at least one of the following methods for performing repetition-based or slot-based time-domain OCC multiplexing:

[0301] Modulation -> Discrete Fourier Transform (DFT) -> Precoding -> Mapping to virtual resource blocks (VRB) -> Mapping to physical resources -> Time domain-OCC covering to physical resources;

[0302] Modulation -> DFT -> Time domain OCC overlay on DFT symbols -> Precoding -> Mapping to virtual resource blocks -> Mapping to physical resources;

[0303] Modulation -> DFT -> precoding -> time domain OCC overlay on DFT symbols (processing on a per-port basis) -> mapping to virtual resource blocks -> mapping to physical resources.

[0304] In some embodiments, for repetition-based OCC multiplexing, partial frequency domain overlapping may be allowed, that is, the locations of resource blocks (RBs) of different terminals in the same user group may not be exactly the same (but from the perspective of DMRS sequence generation, in order to ensure that the DMRS sequences of different terminals in the same user group remain the same, or the DMRS sequences of different terminals in the same user group remain orthogonal, the same frequency domain resource allocation is required. This limitation also applies to frequency domain OCC multiplexing, time-frequency domain OCC multiplexing and pre-DFT OCC multiplexing).

[0305] In some embodiments, for repetition type A, the time domain positions of symbols in a time slot of different terminals in the same user group may be different (but the DMRS symbol positions need to be aligned), as shown in FIG2C .

[0306] In some embodiments, OCC multiplexing may be allowed based on partial time slots or partial repetitions.

[0307] Optionally, when OCC multiplexing is allowed based on partial time slots or partial repetition, the terminal does not need to perform symbol spreading when processing.

[0308] In some embodiments, the terminal 102 performs time-domain OCC multiplexing, where the OCC multiplexing is performed based on symbols.

[0309] Optionally, the first parameter is determined based on a protocol agreement.

[0310] As a possible approach, the value of the first parameter is 1.

[0311] As an example, as shown in Figure 2E, it is assumed that the number of users multiplexed by OCC is 2, the length of the OCC sequence is 2, the PUSCH is based on type B mapping (PUSCH mapping type B), the number of symbols (symbol length) is 14, the shaded area is the DMRS symbol, and the OCC sequence used is (1, -1). The value of the first parameter is 1 (block size = 1), that is, each OCC multiplexing block includes one time domain symbol in the time domain. a(i) in the figure represents the data symbol after DFT. The first multiplexing block covers the first value "1" in the OCC sequence and is used to transmit data symbols a(0) to a(b) (i.e., a(0) to a(b) in the figure); the second multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit data symbols a(0) to a(b) (i.e., -a(0) to -a(b) in the figure). The third multiplexing block covers the first value "1" in the OCC sequence and is used to transmit data symbols a(c) to a(n) (i.e., the a(c) column in the figure, not listed one by one in the figure); the fourth multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit data symbols a(c) to a(n) (i.e., the -a(c) column in the figure, not listed one by one in the figure).

[0312] As can be seen, the data symbols transmitted between OCC multiplexing blocks of each OCC sequence length (2 in this example) are repeated, but each OCC multiplexing block in the two OCC multiplexing blocks covers a different value in the OCC sequence. In other words, the data symbols transmitted by the first multiplexing block and the second multiplexing block are the same, but cover different values ​​in the OCC sequence; and the data symbols transmitted by the first multiplexing block and the third multiplexing block are different.

[0313] Optionally, the first parameter is determined based on the number of available symbols of the terminal 102, the second parameter and the third parameter.

[0314] As a possible manner, the first parameter = the number of available symbols / the second parameter / the third parameter.

[0315] As a possible approach, the value of the third parameter may be 1.

[0316] As a possible approach, the third parameter may be agreed upon by a protocol, or configured or indicated by the network device 101 .

[0317] As an example, as shown in Figure 2F, assuming that the number of users multiplexed by OCC is 2, the length of the OCC sequence is 2, the PUSCH is based on type B mapping (PUSCH mapping type B), the shaded area is the reference signal RS symbol, and the OCC sequence used is (1,-1). The value of the third parameter is 1, the number of allocated time domain symbols is 14 (allocated symbol length = 14), but two of the time domain symbols are used to transmit RS, so the number of available symbols is 14-2 = 12, and the first parameter value is determined as: (14-2) / 2 / 1 = 6. In other words, each OCC multiplexing block includes 6 time domain symbols in the time domain. a(i) in the figure represents the data symbol after DFT. The first multiplexing block covers the first value "1" in the OCC sequence and is used to transmit data symbols a(0) to a(...) (i.e., the 6 columns starting with a(0) in the figure, which are not listed one by one in the figure); the second multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit data symbols a(0) to a(b) (i.e., the 6 columns starting with -a(0) in the figure, which are not listed one by one in the figure). The third multiplexing block covers the first value "1" in the OCC sequence and is used to transmit data symbols a(c) to a(n) (i.e., the a(c) column in the figure, which are not listed one by one in the figure); the fourth multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit data symbols a(c) to a(n) (i.e., the -a(c) column in the figure, which are not listed one by one in the figure).

[0318] Optionally, the terminal 102 determines the first parameter based on indication information sent by the network device 101. The indication information directly indicates the first parameter.

[0319] As a possible approach, the terminal 102 determines the time domain resources (block duration) occupied by the OCC multiplexing block in a back-to-back manner starting from a starting time domain symbol in a time slot.

[0320] In some embodiments, the PUSCH that performs OCC multiplexing based on symbols is a PUSCH transmitted based on a single time slot; or, the PUSCH is a PUSCH transmitted based on multiple time slots.

[0321] The PUSCH transmitted based on multiple time slots includes at least one of the following:

[0322] Type A PUSCH is repeatedly transmitted;

[0323] Type B PUSCH is repeatedly transmitted;

[0324] Transport Block Processing over multi-Slots PUSCH (TBoMS)

[0325] Type A PUSCH repetition transmission based on multi-slot transport blocks TBoMS.

[0326] In some embodiments, the PUSCH is a repeated transmission of Type B PUSCH, and terminal 102 expects that each actual PUSCH transmission will have the same time-domain resource location as each actual PUSCH transmission by other terminals in the same user group, where multiple terminals in the same user group use the same time-frequency resources. (For example, the i-th actual PUSCH transmission of user x and user y has the same time-domain location, where i = 1…N for user x and i = 1…M for user y, where M and N may be different).

[0327] In some embodiments, the PUSCH is a repeated transmission of type B PUSCH, and the terminal 102 expects that the starting time domain symbol of the repeated transmission of the PUSCH is the same as the starting time domain symbol corresponding to other terminals in the same user group, and the terminal 102 expects the symbol length to be the same as that corresponding to other terminals in the same user group.

[0328] In some embodiments, the PUSCH is a PUSCH transmitted based on multiple time slots, and the above-mentioned OCC multiplexing is multiplexed based on the symbols in each time slot; or, the above-mentioned OCC multiplexing is multiplexed based on the symbols in the time domain resources occupied by each TBoMS transmission; or, the above-mentioned OCC multiplexing is multiplexed based on the symbols in the time domain resources occupied by each repetition.

[0329] In some embodiments, the unit of the first parameter is a time domain symbol.

[0330] In some embodiments, the terminal 102 expects that the starting symbol position corresponding to the PUSCH transmitted in a time slot by other terminals in the same user group is the same.

[0331] In some embodiments, for a method of determining the first parameter based on the number of available symbols, terminal 102 expects its number of available symbols to be the same as that of other terminals in the same user group; or, terminal 102 expects the ratio of its number of available symbols to the second parameter to be the same as that of other terminals in the same user group, where each terminal has a corresponding second parameter (i.e., the second parameter is UE-specific). The second parameter can be determined by the terminal based on the number of available symbols, or configured or indicated by network device 101.

[0332] In some embodiments, when terminal 102 expects the ratio of the number of available symbols to the second parameter to be the same for different terminals in the same user group, the number of available symbols and the second parameter must satisfy the following constraint: the number of available symbols is divisible by the second parameter. Alternatively, this remainder relationship may not be satisfied. When this constraint is not satisfied, the remaining symbols, that is, the resources occupied by mod(number of available symbols, second parameter), are no longer reused by OCC. Of course, other design ideas are not excluded, such as aligning the tails of reused symbol resources and excluding symbols remaining at the head from OCC reuse.

[0333] It should be noted that the number of available symbols in the above embodiments refers to the number of symbols excluding those for sending DMRS.

[0334] In some embodiments, the process of the terminal 102 performing symbol-based time-domain OCC multiplexing may consider at least one of the following methods:

[0335] Modulation -> DFT -> OCC symbol extension / time domain OCC overlay on DFT symbols -> precoding -> mapping to virtual resource blocks -> mapping to physical resources;

[0336] Modulation -> DFT -> precoding -> OCC symbol extension / time domain OCC overlay on DFT symbols (processing on a per-port basis) -> mapping to virtual resource blocks -> mapping to physical resources.

[0337] In some embodiments, the granularity of time-domain OCC multiplexing and the method for determining the first parameter may be determined by a protocol. For example, the protocol stipulates that when PUSCH repetition is enabled, the repetition-based OCC multiplexing method is used by default; the protocol stipulates that for PUSCH transmitted in a single time slot, the symbol-based OCC multiplexing method described above is used by default.

[0338] In some embodiments, the method for determining the first parameter may be a plurality of determination methods agreed upon by the protocol, and the network device 101 may indicate one of the determination methods.

[0339] Optionally, if the network device 101 is not configured or indicates relevant parameters of the first parameter determination method, it is determined that OCC is disabled (i.e., OCC multiplexing is not performed); or, if the network device 101 is not configured or indicates relevant parameters of the first parameter determination method, the default first parameter is determined based on a method agreed upon in the protocol.

[0340] Optionally, for OCC multiplexing based on symbols, repetitions, or slots, the first parameter may be indicated using the same field. For example, the protocol specifies a value set {sym2, sym4, sym8, slot 1, slot 2, ...}, and the network device 101 further indicates one of the values ​​of the enumerated type as the value of the first parameter.

[0341] In some embodiments, the OCC sequence may be generated by at least one of the following methods: a Walsh sequence, a Hadamard sequence, a PN sequence, a gold sequence, a cyclic shift sequence, a Zadoff–Chu sequence, a DFT-based OCC code, etc.

[0342] As an example, generating an OCC sequence based on a cyclically shifted sequence can be: sequence#0 = [s(0), s(1), s(2), ... s(k)], where k = 0, ..., M-1, s(k) = exp(j*2pi*k / M), and M is the code length. Furthermore, for the kth value of sequence#i, s(k) = s((k+i)modM). That is, first determine one sequence (sequence length M), and the remaining M-1 sequences can be obtained based on cyclic shifts of this sequence, thereby constructing an orthogonal sequence.

[0343] As an example, a possible OCC sequence is as follows:

[0344] The length of the OCC sequence is 2, and the two OCC sequences can be W2 = [1 1]; [1 -1];

[0345] The length of the OCC sequence is 4, and the four OCC sequences can be W4=[1 1 1 1];[1 -1 1 -1];[1 1 -1 -1];[1 -1 -1 1];

[0346] The length of the OCC sequence is 8, and the 8 OCC sequences can be W8 = [1 1 1 1 1 1 1 1]; [1 -1 1 -1 1 -1 1 -1]; [1 1 -1 -1 1 1 -1 -1]; [1 -1 -1 1 1 -1 -1 1]; [1 1 1 1 -1 -1 -1 -1]; [1 -1 1 -1 -1 -1 1 -1]; [1 1 -1 -1 -1 -1 -1 1 1]; [1 -1 -1 -1 -1 1 1 -1].

[0347] In some embodiments, the terminal 102 does not expect its data symbols to be multiplexed with DMRS symbols of other terminals in the same user group on the same resource element (RE).

[0348] In some embodiments, the scheduling type of the PUSCH in the above embodiments may be a configured grant PUSCH (CG PUSCH) or a dynamic grant (DG) PUSCH (DG PUSCH), where CG PUSCH includes type 1 and type 2.

[0349] In some embodiments, the terminal 102 performs frequency domain OCC multiplexing.

[0350] Optionally, the first parameter is determined based on a protocol agreement.

[0351] As a possible manner, the value of the first parameter is 1, and the unit is resource unit RE.

[0352] As an example, as shown in Figure 2G, it is assumed that the number of users of OCC multiplexing is 2, the length of the OCC sequence is 2, the shaded part is the DMRS symbol, and the OCC sequence used is (1,-1). The value of the first parameter is 1 (block size = 1), that is, each OCC multiplexing block includes one RE in the frequency domain. a(i) in the figure represents the data symbol after DFT. The first multiplexing block covers the first value "1" in the OCC sequence and is used to transmit the data symbol a(0) (i.e., a(0) in the figure); the second multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit the data symbol a(0) (i.e., -a(0) in the figure). The third multiplexing block covers the first value "1" in the OCC sequence and is used to transmit the data symbol a(1) (i.e., a(1) in the figure); the fourth multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit the data symbol a(1) (i.e., -a(1) in the figure). The fifth multiplexing block covers the first value "1" in the OCC sequence and is used to transmit the data symbol a(2) (i.e., a(2) in the figure); the sixth multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit the data symbol a(2) (i.e., -a(2) in the figure)... and so on. The remaining multiplexing blocks will not be repeated here.

[0353] Similarly, data symbols transmitted between OCC multiplexing blocks are repeated for each OCC sequence length (2 in this example), but each OCC multiplexing block in the two OCC multiplexing blocks covers a different value in the OCC sequence. In other words, the data symbols transmitted by the first multiplexing block and the second multiplexing block are the same, but cover different values ​​in the OCC sequence; and the data symbols transmitted by the first multiplexing block and the third multiplexing block are different.

[0354] Optionally, the first parameter is determined based on a sub-physical resource block (PRB) and a second parameter.

[0355] As a possible approach, the first parameter = 12 / the second parameter.

[0356] Optionally, in this mode, the second parameter (number of OCC multiplexed users) needs to be divisible by 12. For example, the number of OCC multiplexed users is {2, 4, 6, 12}, etc. Based on this mode, if only OCC multiplexing of data symbols is considered, different terminals in the same user group are not required to have the same frequency domain resource allocation.

[0357] As an example, as shown in Figure 2H, it can be assumed that the number of users of OCC multiplexing is 2, the length of the OCC sequence is 2, the shaded part is the reference signal RS symbol, and the OCC sequence used is (1,-1). The value of the first parameter is determined to be: 12 / 2=6, that is, each OCC multiplexing block includes 6 REs in the frequency domain. a(i) in the figure represents the data symbol after DFT. The first multiplexing block covers the first value "1" in the OCC sequence and is used to transmit data symbols a(0) to a(5) (i.e., a(0) to a(5) in the figure); the second multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit data symbols a(0) to a(5) (i.e., -a(0) to -a(5) in the figure). The third multiplexing block covers the first value "1" in the OCC sequence and is used to transmit data symbols a(6) to a(b) (i.e., a(6) to a(b) in the figure); the fourth multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit data symbols a(6) to a(b) (i.e., -a(6) to -a(b) in the figure). The fifth multiplexing block covers the first value "1" in the OCC sequence and is used to transmit data symbols a(c) to a(h) (i.e., a(c) to a(h) in the figure); the sixth multiplexing block covers the second value "-1" in the OCC sequence and is used to transmit data symbols a(c) to a(h) (i.e., -a(c) to -a(h) in the figure)... and so on. The remaining multiplexing blocks are not repeated here.

[0358] Optionally, the first parameter is determined based on the number of resource blocks RB allocated to the terminal 102, the second parameter and the third parameter.

[0359] As a possible manner, the first parameter = the number of available RBs / the second parameter / the third parameter.

[0360] As a possible approach, the value of the third parameter may be 1.

[0361] As a possible approach, the third parameter may be agreed upon by a protocol, or configured or indicated by the network device 101 .

[0362] Optionally, in the case where the first parameter is determined based on the number of allocated RBs, the network device 101 is required to allocate the same RBs (same length, same starting position, for example, second parameter = 1) to different terminals in the same multiplexing user group when performing resource allocation. Alternatively, the ratio of the number of allocated RBs to the second parameter is required to be the same, where different terminals may have different {RB, second parameter} values.

[0363] Optionally, when the length of the OCC sequence is m, it corresponds to m multiplexing blocks (transmitting the same data symbol, covering different values ​​in the OCC sequence); accordingly, for the case where the first parameter is determined based on the number of allocated RBs, the start and end positions of each m multiplexing blocks of different terminals in the same user group are required to be consistent (the time domain OCC multiplexing scheme also has similar requirements).

[0364] Optionally, the terminal 102 determines the first parameter based on indication information sent by the network device 101. The indication information directly indicates the first parameter.

[0365] Optionally, the unit of the first parameter may be at least one of the following: RE, RB. Alternatively, a value set may be agreed upon in the protocol, including both RE-level and RB-level values, such as {2REs, 3REs, 4REs, 6REs, 1RB, 2RBs, 3RBs, ..., etc.}, and the network device 101 may configure or indicate one of the values ​​in the set through higher layer signaling or physical layer signaling.

[0366] Optionally, when the length of the OCC sequence is m, it corresponds to m multiplexing blocks (transmitting the same data symbol, covering different values ​​in the OCC sequence); accordingly, this method requires that the start and end positions of each m multiplexing blocks of different terminals in the same multiplexing user group remain consistent (the time domain OCC multiplexing scheme also has similar requirements).

[0367] In some embodiments, the PUSCH based on frequency domain OCC multiplexing is a PUSCH transmitted based on a single time slot; or, the PUSCH is a PUSCH transmitted based on multiple time slots.

[0368] The PUSCH transmitted based on multiple time slots includes at least one of the following:

[0369] Type A PUSCH is repeatedly transmitted;

[0370] Type B PUSCH is repeatedly transmitted;

[0371] Transport Block Processing over multi-Slots PUSCH (TBoMS)

[0372] Type A PUSCH repetition transmission based on multi-slot transport blocks TBoMS.

[0373] In some embodiments, the process of frequency-domain OCC multiplexing performed by the terminal 102 may consider at least one of the following methods:

[0374] Modulation -> DFT -> OCC symbol extension / frequency domain OCC overlay on DFT symbols -> precoding -> mapping to virtual resource blocks -> mapping to physical resources;

[0375] Modulation -> DFT -> precoding -> OCC symbol extension / frequency domain OCC overlay on DFT symbols (processing on a per-port basis) -> mapping to virtual resource blocks -> mapping to physical resources.

[0376] In some embodiments, the granularity of frequency-domain OCC multiplexing and the method for determining the first parameter may be one of the methods agreed upon by the protocol. For example, when the terminal 102 is allocated one RB, the method for determining the first parameter based on the protocol agreement (e.g., first parameter = 1 RE) is used by default; or, in any case, the method for determining the first parameter based on the protocol agreement (e.g., first parameter = 1 RE) is used.

[0377] In some embodiments, the method for determining the first parameter may be a plurality of determination methods agreed upon by the protocol, and the network device 101 may indicate one of the determination methods.

[0378] Optionally, if the network device 101 is not configured or indicates relevant parameters of the first parameter determination method, it is determined that OCC is disabled (i.e., OCC multiplexing is not performed); or, if the network device 101 is not configured or indicates relevant parameters of the first parameter determination method, the default first parameter is determined based on a method agreed upon in the protocol.

[0379] In some embodiments, the terminal 102 does not expect its data symbols to be multiplexed with DMRS symbols of other terminals in the same user group on the same resource element (RE).

[0380] In some embodiments, the scheduling type of the PUSCH in the above embodiments may be a configured grant PUSCH (CG PUSCH) or a dynamic grant (DG) PUSCH (DG PUSCH), where CG PUSCH includes type 1 and type 2.

[0381] In some embodiments, the design of the OCC sequence is the same as that of the time-domain OCC multiplexing.

[0382] In some embodiments, the terminal 102 performs time-frequency domain OCC multiplexing.

[0383] It can be understood that the manner in which the terminal 102 performs time-frequency domain OCC multiplexing is similar to the aforementioned time-domain OCC multiplexing and frequency-domain OCC multiplexing.

[0384] Optionally, the first parameter is determined based on the agreement of the protocol.

[0385] Optionally, the terminal 102 determines the first parameter based on the sub-physical resource block subPRB, the number of available symbols, and the second parameter.

[0386] Optionally, the terminal 102 determines the first parameter based on the number of allocated resource blocks RBs, the number of available symbols, the second parameter and the third parameter.

[0387] Optionally, the terminal 102 determines the first parameter based on indication information sent by the network device 101. The indication information directly indicates the first parameter.

[0388] In some embodiments, the PUSCH based on time-frequency domain OCC multiplexing is a PUSCH transmitted based on a single time slot; or, the PUSCH is a PUSCH transmitted based on multiple time slots.

[0389] The PUSCH transmitted based on multiple time slots includes at least one of the following:

[0390] Type A PUSCH is repeatedly transmitted;

[0391] Type B PUSCH is repeatedly transmitted;

[0392] Transport Block Processing over multi-Slots PUSCH (TBoMS)

[0393] Type A PUSCH repetition transmission based on multi-slot transport blocks TBoMS.

[0394] In some embodiments, terminal 102 performs pre-DFT OCC multiplexing.

[0395] In some embodiments, the process of performing pre-DFT OCC multiplexing by the terminal 102 may consider the following example method:

[0396] Modulation -> OCC symbol extension -> DFT -> precoding -> mapping to virtual resource blocks -> mapping to physical resources.

[0397] In some embodiments, pre-DFT OCC multiplexing can only be performed when transforming precoding of the terminal 102 is enabled.

[0398] In some embodiments, the data symbols transmitted within the same OCC multiplexing block are different, and the data symbols in the entire multiplexing block cover the same value in the OCC sequence. The data symbols included in each of the subsequently transmitted multiplexing blocks (the number of which is the number of multiplexed users minus 1, i.e., the second parameter -1) are repetitions of the first OCC multiplexing block. That is, the data symbols transmitted between every second parameter OCC multiplexing blocks are repetitive, but each OCC multiplexing block in the second parameter OCC multiplexing blocks covers a different value in the OCC sequence.

[0399] Optionally, the terminal 102 may determine the first parameter based on the number of allocated RBs and the second parameter.

[0400] As a possible manner: first parameter = number of allocated RBs * 12 / second parameter.

[0401] In some embodiments, the terminal 102 does not expect its data symbols to be multiplexed with DMRS symbols of other terminals in the same user group on the same resource element (RE).

[0402] In some embodiments, for a solution based on pre-DFT OCC multiplexing, different terminals multiplexed on the same RB are required to use different OCC sequence indices for PUSCH transmission; or, the terminal does not expect other terminals multiplexed on the same RB to use the same OCC sequence.

[0403] In some embodiments, for a solution based on pre-DFT OCC multiplexing, the same length of OCC sequences for different terminals can achieve maximum frequency domain resource utilization; or, the terminal does not expect to use a different OCC sequence length from other terminals multiplexed on the same RB.

[0404] In some embodiments, the scheduling type of the PUSCH based on pre-DFTOCC multiplexing can be a configured grant PUSCH (CG PUSCH) or a dynamic grant (DG) PUSCH (DG PUSCH), where CG PUSCH includes type 1 and type 2.

[0405] In some embodiments, the PUSCH based on pre-DFTOCC multiplexing is a PUSCH transmitted based on a single time slot; or, the PUSCH is a PUSCH transmitted based on multiple time slots.

[0406] The PUSCH transmitted based on multiple time slots includes at least one of the following:

[0407] Type A PUSCH is repeatedly transmitted;

[0408] Type B PUSCH is repeatedly transmitted;

[0409] Transport Block Processing over multi-Slots PUSCH (TBoMS)

[0410] Type A PUSCH repetition transmission based on multi-slot transport blocks TBoMS.

[0411] In some embodiments, for the PUSCH based on multi-slot transmission of pre-DFT CC multiplexing, it is not required to allocate the same time domain slot length to different terminals.

[0412] In some embodiments, for a PUSCH multiplexed based on multi-slot transmission using pre-DFT OCC, pre-DFT OCC is processed individually based on each time slot.

[0413] In some embodiments, the PUSCH is a PUSCH based on a multi-slot transport block TBoMS, and the terminal 102 can determine the transport block TB carried by the PUSCH based on resources of one time slot.

[0414] In some embodiments, for the pre-DFTOCC multiplexing scheme, the PUSCH sent by the terminal 102 uses different subcarriers from the PUSCH sent by other terminals in the same user group, as shown in FIG2I .

[0415] As an example, a possible OCC sequence for pre-DFT OCC multiplexing may be shown in Tables 1 to 4 below:

[0416] OCC sequence (number of multiplexed users is 2):

[0417] OCC sequence (number of multiplexed users is 4): (reference: R1-1719395, HW (moderator) for PUCCH format 4)

[0418] OCC sequence (number of multiplexed users is 6):

[0419] OCC sequence (number of multiplexed users is 12):

[0420] In various embodiments of the present disclosure, the PUSCH also includes a multi-subcarrier transmission (multi-tone) NPUSCH.

[0421] In step S2102 , the terminal 102 determines a second parameter.

[0422] In some embodiments, the second parameter is the length of the OCC sequence.

[0423] In some embodiments, the second parameter is the number of multiplexed users (ie, the number of terminals included in the same user group).

[0424] In some embodiments, the terminal 102 determines the second parameter based on information sent by the network device 101 .

[0425] In some embodiments, the terminal 102 determines the second parameter based on downlink control information (DCI) or radio resource control (RRC) or medium access control (MAC) control element (CE) sent by the network device 101.

[0426] In step S2103 , the terminal 102 sends a PUSCH based on OCC multi-user multiplexing.

[0427] In some embodiments, the network device 101 receives the above-mentioned PUSCH based on OCC multi-user multiplexing.

[0428] In some embodiments, the terminal 102 sends the above-mentioned PUSCH based on OCC multi-user multiplexing to the network device 101 based on the first parameter and the second parameter.

[0429] As shown in the above embodiments, the OCC multiplexing can be time-domain OCC multiplexing, or frequency-domain OCC multiplexing, or time-frequency domain OCC multiplexing, or pre-DFT OCC multiplexing, etc.

[0430] In some embodiments, the terminal 102 can transmit a PUSCH based on OCC multi-user multiplexing. The PUSCH includes the above-mentioned DMRS and data symbols to be transmitted.

[0431] In some embodiments, the PUSCH is based on Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM).

[0432] In some embodiments, terms such as "eNB", "gNB", "base station", "NG-RAN node", etc. can be used interchangeably.

[0433] In some embodiments, the terms "bearer", "Protocol Data Unit (PDU) session", "Evolved Radio Access Bearer (E-RAB)", "EPS bearer", "QoS flow" and the like may be used interchangeably.

[0434] In some embodiments, terms such as "Next Generation Application Proposal (NGAP)" and "S1 Application Proposal (S1AP)" may be used interchangeably.

[0435] In some embodiments, the terms "Xn Application Proposal (XnAP)" and "X2 Application Proposal (X2AP)" may be used interchangeably.

[0436] In some embodiments, terms such as "carrier", "band", and "frequency" can be used interchangeably.

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

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

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

[0440] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0441] In some embodiments, terms such as "resource block (RB)", "physical resource block (PRB)", "sub-carrier group (SCG)", "resource element group (REG)", "PRB pair", "RB pair", "resource element (RE)", and "sub-carrier" can be used interchangeably.

[0442] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0443] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0444] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.

[0445] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0446] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2103. For example, step 2101 may be implemented as an independent embodiment, steps 2101+2102 may be implemented as independent embodiments, steps 2101+2103 may be implemented as independent embodiments, steps 2101+2102+2103 may be implemented as independent embodiments, and so on, but the present invention is not limited thereto.

[0447] In some embodiments, step S2101 and step S2102 may be executed in an interchanged order or simultaneously.

[0448] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A .

[0449] FIG3A is a flow chart of a method for sending information according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a method for sending information, which is executed by terminal 102 and includes:

[0450] Step S3101, determine the first parameter.

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

[0452] Step S3102, determine the second parameter.

[0453] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0454] Step S3103: Send PUSCH based on OCC multi-user multiplexing.

[0455] The optional implementation of step S3104 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0456] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3103. For example, step 3101 may be implemented as an independent embodiment, steps 3101+3102 may be implemented as independent embodiments, steps 3101+3103 may be implemented as independent embodiments, steps 3101+3102+3103 may be implemented as independent embodiments, and so on, but the present invention is not limited thereto.

[0457] In some embodiments, step S3101 and step S3102 may be executed in an interchanged order or simultaneously.

[0458] FIG4A is a flow chart of a method for sending information according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a method for sending information, which is executed by a network device 101 and includes:

[0459] Step S4101: Receive PUSCH based on OCC multi-user multiplexing.

[0460] The optional implementation of step S4101 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0461] Optionally, the OCC multi-user multiplexing-based PUSCH is determined by the terminal 102 based on the first parameter and the second parameter. For optional implementations of determining the first parameter, see the optional implementation of step S2101 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , and are not described in detail here. For optional implementations of determining the second parameter, see the optional implementation of step S2102 in FIG. 2A and other related parts of the embodiment involved in FIG. 2A , and are not described in detail here.

[0462] FIG5 is a flow chart of a method for sending information according to an embodiment of the present disclosure. As shown in FIG5 , the method according to the embodiment of the present disclosure is used in a communication system 100, and the method includes:

[0463] In step S5101, the terminal 102 determines a first parameter, where the first parameter is used to indicate the size of an OCC multiplexing block.

[0464] In step S5102, the terminal 102 determines a second parameter, which is the length of the OCC sequence.

[0465] In step S5103 , the terminal 102 sends a PUSCH based on OCC multi-user multiplexing to the network device 101 based on the first parameter and the second parameter.

[0466] Optional implementations of steps S5101-S5103 may refer to the steps in any one or more of the embodiments in FIG. 2A, FIG. 3A, and FIG. 4A, and other related parts of the embodiments involved in FIG. 2A, FIG. 3A, and FIG. 4A.

[0467] In some embodiments, the above method may include the above method of embodiments of the communication system side, terminal side, network device side, etc., which will not be repeated here.

[0468] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0469] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0470] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0471] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. 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 a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0472] FIG6A is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure. As shown in FIG6A , a terminal 6100 may include: a transceiver module 6101, a processing module 6102, etc. In some embodiments, the processing module is used to determine a first parameter, which is used to indicate the size of an orthogonal cover code (OCC) multiplexing block; wherein the data symbols sent within the same OCC multiplexing block are different and cover the same value in the OCC sequence; the processing module is further used to determine a second parameter, which is the length of the OCC sequence; wherein the data symbols sent between each second parameter number of OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter number of OCC multiplexing blocks covers a different value in the OCC sequence; the transceiver module is used to send a physical uplink shared channel (PUSCH) based on the OCC multi-user multiplexing to the network device based on the first parameter and the second parameter.

[0473] Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (such as step 2103, but not limited to this) performed by the terminal in any of the above methods, which will not be repeated here.

[0474] Optionally, the processing module is used to execute at least one of the other steps (such as step 2101 and step 2102, but not limited thereto) executed by the terminal in any of the above methods, which will not be repeated here.

[0475] FIG6B is a schematic diagram of the structure of another network device proposed in an embodiment of the present disclosure. As shown in FIG6B , the network device 6200 may include: at least one of a transceiver module 6201 and a processing module 6202. In some embodiments, the transceiver module is configured to receive a physical uplink shared channel (PUSCH) based on orthogonal cover code (OCC) multi-user multiplexing sent by a terminal; the PUSCH is sent by the terminal based on a determined first parameter and a second parameter, the first parameter being used to indicate the size of the OCC multiplexing block, and the second parameter being the length of the OCC sequence, wherein the data symbols sent within the same OCC multiplexing block are different and cover the same value in the OCC sequence; the data symbols sent between every second parameter number of OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter number of OCC multiplexing blocks covers a different value in the OCC sequence.

[0476] Optionally, the above-mentioned transceiver module is used to execute at least one of the communication steps such as sending and / or receiving (such as step 2103, but not limited to this) performed by the network device in any of the above methods, which will not be repeated here.

[0477] Optionally, the processing module is used to execute at least one of the other steps performed by the network device in any of the above methods, which will not be repeated here.

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

[0479] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0480] Figure 7A is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0481] As shown in FIG7A , the communication device 7100 includes one or more processors 7101. The processor 7101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control a communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 7100 is used to perform any of the above methods.

[0482] 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 may be located outside the communication device 7100.

[0483] 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 transceiver 7103 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 7101 performs at least one of the other steps.

[0484] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0485] In some embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuit 7104 is connected to the memory 7102. The interface circuit 7104 may be configured to receive signals from the memory 7102 or other devices, and may be configured to send signals to the memory 7102 or other devices. For example, the interface circuit 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.

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

[0487] 7B is a schematic diagram of the structure of a chip 7200 according to an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 7200 shown in FIG7B , but the present disclosure is not limited thereto.

[0488] The chip 7200 includes one or more processors 7201 , and the chip 7200 is configured to execute any of the above methods.

[0489] In some embodiments, the chip 7200 further includes one or more interface circuits 7202. Optionally, the interface circuit 7202 is connected to the memory 7203. The interface circuit 7202 can be used to receive signals from the memory 7203 or other devices, and can be used 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.

[0490] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 2101, step 2105, but not limited to these), and the processor 7201 performs at least one of the other steps (for example, step 2102, step 2103, step 2104, but not limited to these).

[0491] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0492] In some embodiments, the chip 7200 further includes one or more memories 7203 for storing instructions. Alternatively, all or part of the memories 7203 may be located outside the chip 7200.

[0493] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0494] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

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

[0496] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is 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 device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

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

[0498] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0499] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A method for sending information, characterized in that: The method is executed by a terminal, and includes: Determining a first parameter, where the first parameter is used to indicate a size of an orthogonal cover code (OCC) multiplexing block; The data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence; Determining a second parameter, where the second parameter is a length of the OCC sequence; wherein the data symbols sent between every second parameter of the OCC multiplexing blocks are repeated, and different OCC multiplexing blocks cover different values ​​in the OCC sequence; Based on the first parameter and the second parameter, a physical uplink shared channel PUSCH based on the OCC multi-user multiplexing is sent to a network device.

2. The method according to claim 1, characterized in that The OOC multiplexing includes at least one of the following: Time domain OCC multiplexing; Frequency domain OCC multiplexing; Time-frequency domain OCC multiplexing; OCC multiplexing of pre-DFT before discrete Fourier transform.

3. The method according to claim 2, characterized in that The OOC multiplexing is time-domain OCC multiplexing, and the PUSCH is repeatedly transmitted. The OCC multiplexing is multiplexed based on repeated PUSCHs or time slots. Determining the first parameter includes: Determine the first parameter based on the agreement of the protocol; or, determining the first parameter based on the number of repeated transmissions of the PUSCH, the second parameter, and the third parameter; or determining the first parameter based on the indication information sent by the network device; or, Determine that the value of the first parameter is n times 4, where n is a positive integer.

4. The method according to claim 3, characterized in that The PUSCH repetition transmission is type A PUSCH repetition transmission, or the PUSCH repetition transmission is type B PUSCH repetition transmission.

5. The method according to claim 3 or 4, characterized in that The redundancy version RV corresponding to each PUSCH in the repeatedly transmitted PUSCH is the same; or, For at least one cyclic redundancy version RV corresponding to the PUSCH included in the same OCC multiplexing block, the RVs and the cyclic order of the RVs included in each second parameter of OCC multiplexing blocks are the same; or, The redundancy version RV corresponding to each second parameter number of PUSCHs in the repeatedly transmitted PUSCHs is the same.

6. The method according to any one of claims 3 to 5, characterized in that: The PUSCH repetition transmission is type A PUSCH repetition transmission, and the unit of the first parameter is the time domain resource occupied by the PUSCH repetition transmission once, or the unit of the first parameter is the time slot.

7. The method according to any one of claims 3 to 5, characterized in that: The PUSCH repetition transmission is type B PUSCH repetition transmission, and the unit of the first parameter is the time domain resource occupied by one repeated transmission of the PUSCH; The repeatedly transmitted PUSCH is a nominally repeatedly transmitted PUSCH, or the repeatedly transmitted PUSCH is an actually repeatedly transmitted PUSCH.

8. The method according to any one of claims 3 to 7, characterized in that: The PUSCH repeated transmission is a PUSCH repeated transmission of type A; Determining a resource allocation mode based on an available time slot counting mechanism, wherein the terminal expects that the available time slots corresponding to other terminals in the same user group are located in the same time domain, wherein the multiple terminals included in the same user group use the same time-frequency domain resources; or The terminal does not expect to configure repeated PUSCH or time slot based OCC multiplexing and available time slot counting mechanism at the same time.

9. The method according to any one of claims 3 to 7, characterized in that: The PUSCH repetition transmission is a PUSCH repetition transmission of type B; The terminal expects that the symbol position of the time domain resources corresponding to other terminals in the same user group is the same, wherein the time and frequency domain resources used by multiple terminals included in the same user group are the same.

10. The method according to any one of claims 3 to 9, characterized in that: The terminal expects that the starting time domain position corresponding to the PUSCH repeatedly sent by other terminals in the same user group is the same.

11. The method according to any one of claims 3 to 9, characterized in that: The terminal expects the number of PUSCH repetition transmissions to be the same as the number of PUSCH repetition transmissions of other terminals in the same user group; or The terminal expects that the ratio of the number of PUSCH repetition transmissions to the second parameter is the same as the ratio of the number of PUSCH repetition transmissions to the second parameter of other terminals in the same user group, where each terminal has a corresponding second parameter.

12. The method according to claim 2, characterized in that The OOC multiplexing is time-domain OCC multiplexing, and the OCC multiplexing is multiplexed based on symbols. Determining the first parameter includes: Determine the first parameter based on the agreement of the protocol; or, determining the first parameter based on the number of available symbols, the second parameter, and a third parameter; or The first parameter is determined based on the indication information sent by the network device.

13. The method according to claim 12, characterized in that The PUSCH is a PUSCH transmitted based on a single time slot; or, The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following: Type A PUSCH is repeatedly transmitted; Type B PUSCH is repeatedly transmitted; PUSCH based on multi-slot transport blocks TBoMS; Type A PUSCH repetition transmission based on multi-slot transport blocks TBoMS.

14. The method according to claim 12 or 13, characterized in that The PUSCH repetition transmission is a PUSCH repetition transmission of type B; The terminal expects that each time a PUSCH is actually sent, the position of the time domain resources corresponding to each PUSCH actually sent by other terminals in the same user group is the same, wherein the time and frequency domain resources used by multiple terminals in the same user group are the same.

15. The method according to any one of claims 12 to 14, characterized in that: The PUSCH repetition transmission is a PUSCH repetition transmission of type B; The terminal expects that the starting time domain symbol of the repeated PUSCH transmission is the same as the starting time domain symbol corresponding to other terminals in the same user group, and the terminal expects that the symbol length is the same as that of the other terminals in the same user group.

16. The method according to any one of claims 12 to 15, characterized in that: The PUSCH is a PUSCH transmitted based on multiple time slots; The OCC multiplexing is performed based on symbols in each time slot; or The OCC multiplexing is based on the symbols in the time domain resources occupied by each TBoMS transmission; or, The OCC multiplexing is performed based on symbols in the time domain resources occupied by each repetition.

17. The method according to any one of claims 12 to 16, characterized in that: The unit of the first parameter is symbol.

18. The method according to any one of claims 12 to 17, characterized in that: The terminal expects that the starting symbol position corresponding to the PUSCH sent by other terminals in the same user group in a time slot is the same.

19. The method according to any one of claims 12 to 18, characterized in that: The number of available symbols for the terminal is the same as the number of available symbols for other terminals in the same user group; or The ratio of the number of available symbols of the terminal to the second parameter is the same as the ratio of the number of available symbols of other terminals in the same user group to the second parameter, wherein each terminal has a corresponding second parameter.

20. The method according to claim 2, characterized in that The OOC multiplexing is frequency-domain OCC multiplexing, and determining the first parameter includes: Determine the first parameter based on the agreement of the protocol; or, determining the first parameter based on a sub-physical resource block subPRB and the second parameter; or, Determine the first parameter based on the number of resource blocks (RBs) allocated to the terminal, the second parameter, and a third parameter; or The first parameter is determined based on the indication information sent by the network device.

21. The method according to claim 19 or 20, characterized in that The unit of the first parameter is a resource unit RE, or the unit of the first parameter is a resource block RB.

22. The method according to claim 2, characterized in that The OOC multiplexing is time-frequency domain OCC multiplexing, and determining the first parameter includes: Determine the first parameter based on the agreement of the protocol; or, determining the first parameter based on a sub-physical resource block subPRB and the second parameter; or, Determine the first parameter based on the number of resource blocks (RBs) allocated to the terminal, the number of available symbols, the second parameter, and the third parameter; or The first parameter is determined based on the indication information sent by the network device.

23. The method according to any one of claims 20 to 22, characterized in that The PUSCH is a PUSCH transmitted based on a single time slot; or, The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following: Type A PUSCH is repeatedly transmitted; Type B PUSCH is repeatedly transmitted; PUSCH based on multi-slot transport blocks TBoMS; Repeated transmission of multi-slot transport blocks TBoMS.

24. The method according to claim 2, characterized in that The OOC multiplexing is pre-DFTOCC multiplexing, and determining the first parameter includes: The first parameter is determined based on at least one of the following parameters: The number of resource blocks (RBs) allocated to the terminal; The number of users multiplexed by the OCC; The number of resource units RE in a resource block RB.

25. The method according to claim 24, characterized in that The PUSCH is a PUSCH transmitted based on a single time slot; or, The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following: Type A PUSCH is repeatedly transmitted; Type B PUSCH is repeatedly transmitted; PUSCH based on multi-slot transport blocks TBoMS; Repeated transmission of multi-slot transport blocks TBoMS.

26. The method according to claim 24 or 25, characterized in that The OCC expansion is performed before discrete Fourier transform DFT.

27. The method according to any one of claims 24 to 26, characterized in that The PUSCH sent by the terminal and the PUSCH sent by other terminals in the same user group use different subcarriers.

28. The method according to any one of claims 24 to 27, characterized in that The PUSCH is a PUSCH based on a multi-slot transport block TBoMS, and the method further includes: Based on the resources of a time slot, a transport block TB carried by the PUSCH is determined.

29. The method according to any one of 1 to 28, characterized in that The PUSCH also includes: a multi-tone NPUSCH that transmits multiple subcarriers.

30. A method for sending information, characterized in that: The method is performed by a network device, and includes: The physical uplink shared channel (PUSCH) based on orthogonal cover code (OCC) multi-user multiplexing sent by the receiving terminal; The PUSCH is sent by the terminal based on the determined first parameter and second parameter, where the first parameter is used to indicate the size of the OCC multiplexing block, and the second parameter is the length of the OCC sequence, wherein the data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence; the data symbols sent between each second parameter OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter OCC multiplexing blocks covers a different value in the OCC sequence.

31. The method according to claim 30, wherein The OOC multiplexing includes at least one of the following: Time domain OCC multiplexing; Frequency domain OCC multiplexing; Time-frequency domain OCC multiplexing; OCC multiplexing of pre-DFT before discrete Fourier transform.

32. The method according to claim 31, characterized in that The OOC multiplexing is time-domain OCC multiplexing, and the PUSCH is repeatedly transmitted. The OCC multiplexing is multiplexed based on repeated PUSCH or time slot; The first parameter is determined based on the agreement of the protocol; or, The first parameter is determined based on the number of times the PUSCH is repeatedly transmitted, the second parameter, and a third parameter; or, The first parameter is determined based on indication information sent by the network device; or, The value of the first parameter is n times 4, where n is a positive integer.

33. The method according to claim 32, characterized in that The PUSCH repetition transmission is type A PUSCH repetition transmission, or the PUSCH repetition transmission is type B PUSCH repetition transmission.

34. The method according to claim 32 or 33, characterized in that The redundancy version RV corresponding to each PUSCH in the repeatedly transmitted PUSCH is the same; or, For at least one cyclic redundancy version RV corresponding to the PUSCH included in the same OCC multiplexing block, the RVs and the cyclic order of the RVs included in each second parameter of OCC multiplexing blocks are the same; or, The redundancy versions RV corresponding to the second parameter PUSCHs in the repeatedly transmitted PUSCH are the same.

35. The method according to any one of claims 32 to 34, characterized in that The PUSCH repetition transmission is type A PUSCH repetition transmission, and the unit of the first parameter is the time domain resource occupied by the PUSCH repetition transmission once, or the unit of the first parameter is the time slot.

36. The method according to any one of claims 32 to 34, characterized in that The PUSCH repetition transmission is type B PUSCH repetition transmission, and the unit of the first parameter is the time domain resource occupied by one repeated transmission of the PUSCH; The repeatedly transmitted PUSCH is a nominally repeatedly transmitted PUSCH, or the repeatedly transmitted PUSCH is an actually repeatedly transmitted PUSCH.

37. The method according to any one of claims 32 to 36, wherein: The PUSCH repeated transmission is a PUSCH repeated transmission of type A; The resource allocation mode of the terminal is based on an available time slot counting mechanism, and the terminal expects that the available time slots corresponding to other terminals in the same user group are located at the same position in the time domain, wherein the multiple terminals included in the same user group use the same time-frequency domain resources; or The terminal does not expect to configure repeated PUSCH or time slot based OCC multiplexing and available time slot counting mechanism at the same time.

38. The method according to any one of claims 32 to 36, characterized in that The PUSCH repetition transmission is a PUSCH repetition transmission of type B; The terminal expects that the symbol position of the time domain resources corresponding to other terminals in the same user group is the same, wherein the time and frequency domain resources used by multiple terminals included in the same user group are the same.

39. The method according to any one of claims 32 to 38, wherein: The terminal expects that the starting time domain position corresponding to the PUSCH repeatedly sent by other terminals in the same user group is the same.

40. The method according to any one of claims 32 to 38, characterized in that The terminal expects the number of PUSCH repetition transmissions to be the same as the number of PUSCH repetition transmissions of other terminals in the same user group; or The terminal expects that the ratio of the number of PUSCH repetition transmissions to the second parameter is the same as the ratio of the number of PUSCH repetition transmissions to the second parameter of other terminals in the same user group, where each terminal has a corresponding second parameter.

41. The method according to claim 31, wherein The OOC multiplexing is time-domain OCC multiplexing, and the OCC multiplexing is multiplexed based on symbols; The first parameter is determined based on the agreement of the protocol; or, The first parameter is determined based on the number of available symbols, the second parameter and the third parameter; or, The first parameter is determined based on indication information sent by the network device.

42. The method according to claim 41, wherein The PUSCH is a PUSCH transmitted based on a single time slot; or, The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following: Type A PUSCH is repeatedly transmitted; Type B PUSCH is repeatedly transmitted; PUSCH based on multi-slot transport blocks TBoMS; Type A PUSCH repetition transmission based on multi-slot transport blocks TBoMS.

43. The method according to claim 41 or 42, characterized in that The PUSCH is a type B PUSCH that is repeatedly transmitted; The terminal expects that each time a PUSCH is actually sent, the position of the time domain resources corresponding to each PUSCH actually sent by other terminals in the same user group is the same, wherein the time and frequency domain resources used by multiple terminals in the same user group are the same.

44. The method according to any one of claims 41 to 43, wherein: The PUSCH is a type B PUSCH that is repeatedly transmitted; The terminal expects that the starting time domain symbol of the repeated PUSCH transmission is the same as the starting time domain symbol corresponding to other terminals in the same user group, and the terminal expects that the symbol length is the same as that of the other terminals in the same user group.

45. The method according to any one of claims 41 to 44, characterized in that The PUSCH is a PUSCH transmitted based on multiple time slots; The OCC multiplexing is performed based on symbols in each time slot; or The OCC multiplexing is based on the symbols in the time domain resources occupied by each TBoMS transmission; or, The OCC multiplexing is performed based on symbols in the time domain resources occupied by each repetition.

46. ​​The method according to any one of claims 41 to 45, characterized in that The unit of the first parameter is symbol.

47. The method according to any one of claims 41 to 46, characterized in that The terminal expects that the starting symbol position corresponding to the PUSCH sent by other terminals in the same user group in a time slot is the same.

48. The method according to any one of claims 41 to 47, characterized in that The number of available symbols for the terminal is the same as the number of available symbols for other terminals in the same user group; or The ratio of the number of available symbols of the terminal to the second parameter is the same as the ratio of the number of available symbols of other terminals in the same user group to the second parameter, wherein each terminal has a corresponding second parameter.

49. The method according to claim 31, wherein The OOC multiplexing is frequency domain OCC multiplexing; The first parameter is determined based on the agreement of the protocol; or, The first parameter is determined based on a sub-physical resource block sub PRB and the second parameter; or The first parameter is determined based on the number of resource blocks (RBs) allocated to the terminal, the second parameter, and a third parameter; or The first parameter is determined based on indication information sent by the network device.

50. The method according to claim 48 or 49, characterized in that The unit of the first parameter is a resource unit RE, or the unit of the first parameter is a resource block RB.

51. The method according to claim 31, wherein The OOC multiplexing is time-frequency domain OCC multiplexing; The first parameter is determined based on the agreement of the protocol; or, The first parameter is determined based on a sub-physical resource block sub PRB and the second parameter; or, The first parameter is determined based on the number of resource blocks (RBs) allocated to the terminal, the number of available symbols, the second parameter, and the third parameter; or, The first parameter is determined based on indication information sent by the network device.

52. The method according to any one of claims 49 to 51, wherein: The PUSCH is a PUSCH transmitted based on a single time slot; or, The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following: Type A PUSCH is repeatedly transmitted; Type B PUSCH is repeatedly transmitted; PUSCH based on multi-slot transport blocks TBoMS; Repeated transmission of multi-slot transport blocks TBoMS.

53. The method according to claim 31, wherein The OOC multiplexing is pre-DFT OCC multiplexing; The first parameter is determined based on at least one of the following parameters: The number of resource blocks (RBs) allocated to the terminal; The number of users multiplexed by the OCC; The number of resource units RE in a resource block RB.

54. The method according to claim 53, wherein The PUSCH is a PUSCH transmitted based on a single time slot; or, The PUSCH is a PUSCH transmitted based on multiple time slots; wherein the PUSCH transmitted based on multiple time slots includes at least one of the following: Type A PUSCH is repeatedly transmitted; Type B PUSCH is repeatedly transmitted; PUSCH based on multi-slot transport blocks TBoMS; Repeated transmission of multi-slot transport blocks TBoMS.

55. The method according to claim 53 or 54, characterized in that The OCC expansion is performed before discrete Fourier transform DFT.

56. The method according to any one of claims 53 to 55, characterized in that The PUSCH sent by the terminal and the PUSCH sent by other terminals in the same user group use different subcarriers.

57. The method according to any one of claims 53 to 56, characterized in that The PUSCH is a PUSCH based on a multi-slot transport block TBoMS, and the transport block TB carried by the PUSCH is determined based on resources of one time slot.

58. The method according to any one of 29-57, characterized in that The PUSCH also includes: a multi-tone NPUSCH that transmits multiple subcarriers.

59. A terminal, characterized in that: The terminal includes: a processing module, configured to determine a first parameter, where the first parameter is used to indicate a size of an orthogonal cover code (OCC) multiplexing block; The data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence; The processing module is further configured to determine a second parameter, where the second parameter is a length of the OCC sequence; wherein the data symbols sent between every second parameter number of OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter number of OCC multiplexing blocks covers a different value in the OCC sequence; The transceiver module is configured to send a physical uplink shared channel (PUSCH) based on the OCC multi-user multiplexing to a network device based on the first parameter and the second parameter.

60. A network device, characterized in that The network equipment includes: The transceiver module is used to receive the physical uplink shared channel (PUSCH) sent by the terminal based on the orthogonal cover code (OCC) multi-user multiplexing; The PUSCH is sent by the terminal based on the determined first parameter and second parameter, where the first parameter is used to indicate the size of the OCC multiplexing block, and the second parameter is the length of the OCC sequence, wherein the data symbols sent in the same OCC multiplexing block are different and cover the same value in the OCC sequence; the data symbols sent between each second parameter OCC multiplexing blocks are repeated, and each OCC multiplexing block in the second parameter OCC multiplexing blocks covers a different value in the OCC sequence.

61. A terminal, characterized in that: The terminal includes: one or more processors; The terminal is used to execute the information processing method according to any one of claims 1 to 29.

62. A network device, characterized in that The network equipment includes: one or more processors; Wherein, the network device is used to execute the information processing method according to any one of claims 30-58.

63. A communication system, characterized in that The invention comprises a terminal and a network device, wherein the terminal is configured to implement the information processing method according to any one of claims 1 to 29, and the network device is configured to implement the information processing method according to any one of claims 30 to 58.

64. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the information processing method according to any one of claims 1 to 29 or 30 to 58.

Images