Information sending method and apparatus

Abstract

Disclosed in embodiments of the present disclosure are an information sending method and an apparatus. The method comprises: determining a first parameter, the first parameter being the number of slots occupied by transport block processing over multiple slots (TBoMS); determining a second parameter, the second parameter being the length of an orthogonal cover code (OCC) sequence; and on the basis of the first parameter and the second parameter, sending to a network device a physical uplink shared channel (PUSCH) of the TBoMS based on OCC extension, such that a terminal can realize transmission of the TBoMS based on OCC extension. Thus, the link performance of data channels can be improved while realizing multi-user multiplexing and improving the overall capacity of a system, more users can be supported to perform uplink transmission, improving the system communication efficiency, and the resource utilization rate and the spectral efficiency can be effectively improved.

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 cell radius covered by satellite is usually larger, the number of users in a cell is greater than that in the terrestrial network (TN) cell, and the transmission distance between the terminal and the satellite is longer. In order to improve the uplink system capacity while effectively ensuring the link performance of the data channel, the transport block processing over multiple slots (TBoMS) extended by orthogonal cover code (OCC) can be considered.

[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 the number of time slots occupied by the multi-slot transport block TBoMS;

[0008] Determine a second parameter, where the second parameter is the length of an orthogonal cover code OCC sequence;

[0009] Based on the first parameter and the second parameter, a physical uplink shared channel (PUSCH) of the TBoMS based on the OCC extension is sent to a network device.

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

[0011] The physical uplink shared channel PUSCH of the multi-slot transport block TBoMS extended based on the orthogonal cover code OCC sent by the receiving terminal.

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

[0013] a processing module, configured to determine a first parameter, where the first parameter is the number of time slots occupied by a multi-slot transport block TBoMS;

[0014] The processing module is further configured to determine a second parameter, where the second parameter is the length of an orthogonal cover code (OCC) sequence;

[0015] The transceiver module is configured to send a physical uplink shared channel (PUSCH) of the TBoMS based on the OCC extension to a network device based on the first parameter and the second parameter.

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

[0017] A transceiver module is configured to receive a physical uplink shared channel (PUSCH) of a multi-slot transport block (TBoMS) extended with an orthogonal cover code (OCC) sent by a terminal;

[0018] The PUSCH is sent by the terminal based on a determined first parameter and a second parameter, where the first parameter is the number of time slots occupied by the TBoMS, and the second parameter is the length of an orthogonal cover code OCC sequence.

[0019] The solution proposed in the embodiment of the present disclosure determines a first parameter, which is the number of time slots occupied by the multi-slot transmission block TBoMS, and determines a second parameter, which is the length of the orthogonal cover code OCC sequence, so that based on the first parameter and the second parameter, the physical uplink shared channel PUSCH based on the OCC-extended TBoMS is sent to the network device, so that the terminal can realize the transmission of the OCC-extended TBoMS, and can effectively improve the link performance of the data channel while realizing multi-user multiplexing and improving the overall capacity of the system, and can support more users for uplink transmission, improve the system communication efficiency, and effectively improve resource utilization and spectrum efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] 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.

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

[0022] FIG1B is a schematic diagram showing a trend of a block error rate (BLER) corresponding to different numbers of multiplexed users in an OCC extension before discrete Fourier transform according to a related art provided by an embodiment of the present disclosure as the signal-to-noise ratio (SNR) increases;

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

[0024] FIG2B is a schematic diagram of a TBoMS solution based on OCC extension provided by an embodiment of the present disclosure;

[0025] 3A-3B are flowcharts of an information sending method provided by an embodiment of the present disclosure;

[0026] 4A-4B are flowcharts of an information sending method provided by an embodiment of the present disclosure;

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

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

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

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

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

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

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

[0034] Determining a first parameter, where the first parameter is the number of time slots occupied by the multi-slot transport block TBoMS;

[0035] Determine a second parameter, where the second parameter is the length of an orthogonal cover code OCC sequence;

[0036] Based on the first parameter and the second parameter, a physical uplink shared channel (PUSCH) of the TBoMS based on the OCC extension is sent to a network device.

[0037] In the above embodiment, the terminal is enabled to realize the transmission of TBoMS based on OCC extension, which can realize multi-user multiplexing, improve the overall capacity of the system, effectively improve the link performance of the data channel, support more users for uplink transmission, improve the system communication efficiency, and effectively improve resource utilization and spectrum efficiency.

[0038] In combination with some embodiments of the first aspect, in some embodiments, the OCC extension is a pre-DFT OCC extension based on discrete Fourier transform.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the modulation symbols sent in each time slot corresponding to the TBoMS are modulation symbols that have undergone pre-DFT OCC extension.

[0040] In combination with some embodiments of the first aspect, in some embodiments, the size of the transport block TB corresponding to the TBoMS is determined based on the number of available time-frequency domain resources in a time slot corresponding to the TBoMS.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the size of the transport block TB corresponding to the TBoMS is determined based on at least one of the following information:

[0042] The number of available time-frequency domain resources in a time slot corresponding to the TBoMS;

[0043] the first parameter;

[0044] the second parameter.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, a stop bit among the multiple bits sent in the first time slot and a start bit among the multiple bits sent in the second time slot are adjacent bits among the multiple coded bits corresponding to the transport block TB;

[0046] The first time slot and the second time slot are adjacent time slots in a plurality of time slots occupied by the TBoMS, and the TB is a TB corresponding to the TBoMS.

[0047] With reference to some embodiments of the first aspect, in some embodiments, determining the first parameter includes:

[0048] The first parameter is determined based on a protocol agreement or based on first information sent by the network device.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the first parameter is determined based on the second parameter; or,

[0050] The first parameter is determined based on the first number of repeated transmissions.

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

[0052] Radio Resource Control RRC message;

[0053] Downlink control information DCI.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the first parameter is indicated by at least one of the following information fields of the DCI:

[0055] Modulation and coding strategy MCS information field;

[0056] Transmit power control TPC information field;

[0057] Time domain resource allocation TDRA information field;

[0058] Frequency hopping FH flag information field;

[0059] Frequency domain resource allocation FDRA information field;

[0060] Added new information fields.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, the first parameter is included in at least one of the following information:

[0062] Time domain resource allocation TDRA list;

[0063] Modulation and coding strategy MCS table;

[0064] Transmit power control TPC table.

[0065] With reference to some embodiments of the first aspect, in some embodiments, determining the second parameter includes:

[0066] The second parameter is determined based on a protocol agreement or based on second information sent by the network device.

[0067] In combination with some embodiments of the first aspect, in some embodiments, the second parameter is determined based on the first parameter.

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

[0069] Radio Resource Control RRC message;

[0070] Downlink control information DCI.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the second parameter is indicated by at least one of the following information fields of the DCI:

[0072] Modulation and coding strategy MCS information field;

[0073] Transmit power control TPC information field;

[0074] Time domain resource allocation TDRA information field;

[0075] Frequency hopping FH flag information field;

[0076] Frequency domain resource allocation FDRA information field;

[0077] Added new information fields.

[0078] In conjunction with some embodiments of the first aspect, in some embodiments, the second parameter is included in at least one of the following information:

[0079] Time domain resource allocation TDRA list;

[0080] Modulation and coding strategy MCS table;

[0081] Transmit power control TPC table.

[0082] In combination with some embodiments of the first aspect, in some embodiments, the orthogonal frequency division multiplexing (OFDM) symbols corresponding to the PUSCH in each time slot occupied by the TBoMS are the same.

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

[0084] Sending third information to the network device, where the third information is used to indicate that the terminal supports TBoMS based on pre-DFT OCC extension.

[0085] With reference to some embodiments of the first aspect, in some embodiments, the third information includes a first indication and a second indication;

[0086] The first indication is used to indicate that the terminal supports TBoMS-based PUSCH, and the second indication is used to indicate that the terminal supports pre-DFT-based OCC multiplexing.

[0087] With reference to some embodiments of the first aspect, in some embodiments, the third information includes a third indication;

[0088] The third indication is used to indicate that the terminal supports PUSCH of TBoMS based on pre-DFT OCC extension.

[0089] In combination with some embodiments of the first aspect, in some embodiments, the PUSCH further includes: a multi-subcarrier transmission multi-tone narrowband PUSCH.

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

[0091] The physical uplink shared channel PUSCH of the multi-slot transport block TBoMS extended based on the orthogonal cover code OCC sent by the receiving terminal.

[0092] In the above embodiment, the terminal is enabled to realize the transmission of TBoMS based on OCC extension, which can realize multi-user multiplexing, improve the overall capacity of the system, effectively improve the link performance of the data channel, support more users for uplink transmission, improve the system communication efficiency, and effectively improve resource utilization and spectrum efficiency.

[0093] In combination with some embodiments of the second aspect, in some embodiments, the OCC extension is a pre-DFT OCC extension based on discrete Fourier transform.

[0094] In combination with some embodiments of the second aspect, in some embodiments, the modulation symbols sent in each time slot corresponding to the TBoMS are modulation symbols that have undergone pre-DFT OCC extension.

[0095] In combination with some embodiments of the second aspect, in some embodiments, the size of the transport block TB corresponding to the TBoMS is determined based on the number of available time-frequency domain resources in a time slot corresponding to the TBoMS.

[0096] In conjunction with some embodiments of the second aspect, in some embodiments, the size of the transport block TB corresponding to the TBoMS is determined based on at least one of the following information:

[0097] The number of available time-frequency domain resources in a time slot corresponding to the TBoMS;

[0098] the first parameter;

[0099] the second parameter.

[0100] In conjunction with some embodiments of the second aspect, in some embodiments, the end bit of the multiple bits sent in the first time slot and the start bit of the multiple bits sent in the second time slot are adjacent bits in the multiple coded bits corresponding to the transport block TB;

[0101] The first time slot and the second time slot are adjacent time slots in a plurality of time slots occupied by the TBoMS, and the TB is a TB corresponding to the TBoMS.

[0102] With reference to some embodiments of the second aspect, in some embodiments, determining the first parameter includes:

[0103] The first parameter is determined based on a protocol agreement or based on first information sent by the network device.

[0104] In conjunction with some embodiments of the second aspect, in some embodiments, the first parameter is determined based on the second parameter; or,

[0105] The first parameter is determined based on the first number of repeated transmissions.

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

[0107] Radio Resource Control RRC message;

[0108] Downlink control information DCI.

[0109] In conjunction with some embodiments of the second aspect, in some embodiments, the first parameter is indicated by at least one of the following information fields of the DCI:

[0110] Modulation and coding strategy MCS information field;

[0111] Transmit power control TPC information field;

[0112] Time domain resource allocation TDRA information field;

[0113] Frequency hopping FH flag information field;

[0114] Frequency domain resource allocation FDRA information field;

[0115] Added new information fields.

[0116] In conjunction with some embodiments of the second aspect, in some embodiments, the first parameter is included in at least one of the following information:

[0117] Time domain resource allocation TDRA list;

[0118] Modulation and coding strategy MCS table;

[0119] Transmit power control TPC table.

[0120] With reference to some embodiments of the second aspect, in some embodiments, determining the second parameter includes:

[0121] The second parameter is determined based on a protocol agreement or based on second information sent by the network device.

[0122] In combination with some embodiments of the second aspect, in some embodiments, the second parameter is determined based on the first parameter.

[0123] In conjunction with some embodiments of the second aspect, in some embodiments, the second information is at least one of the following:

[0124] Radio Resource Control RRC message;

[0125] Downlink control information DCI.

[0126] In conjunction with some embodiments of the second aspect, in some embodiments, the second parameter is indicated by at least one of the following information fields of the DCI:

[0127] Modulation and coding strategy MCS information field;

[0128] Transmit power control TPC information field;

[0129] Time domain resource allocation TDRA information field;

[0130] Frequency hopping FH flag information field;

[0131] Frequency domain resource allocation FDRA information field;

[0132] Added new information fields.

[0133] In conjunction with some embodiments of the second aspect, in some embodiments, the second parameter is included in at least one of the following information:

[0134] Time domain resource allocation TDRA list;

[0135] Modulation and coding strategy MCS table;

[0136] Transmit power control TPC table.

[0137] In combination with some embodiments of the second aspect, in some embodiments, the orthogonal frequency division multiplexing OFDM symbols corresponding to the PUSCH in each time slot occupied by the TBoMS are the same.

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

[0139] receiving third information sent by the terminal, where the third information is used to indicate that the terminal supports TBoMS based on pre-DFT OCC extension.

[0140] With reference to some embodiments of the second aspect, in some embodiments, the third information includes a first indication and a second indication;

[0141] The first indication is used to indicate that the terminal supports TBoMS-based PUSCH, and the second indication is used to indicate that the terminal supports pre-DFT-based OCC multiplexing.

[0142] With reference to some embodiments of the second aspect, in some embodiments, the third information includes a third indication;

[0143] The third indication is used to indicate that the terminal supports PUSCH of TBoMS based on pre-DFT OCC extension.

[0144] In combination with some embodiments of the second aspect, in some embodiments, the PUSCH further includes: a multi-subcarrier transmission multi-tone narrowband PUSCH.

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

[0146] The terminal determines a first parameter, where the first parameter is the number of time slots occupied by the multi-slot transport block TBoMS;

[0147] The terminal determines a second parameter, where the second parameter is the length of an orthogonal cover code OCC sequence;

[0148] The terminal sends a physical uplink shared channel PUSCH of the TBoMS based on the OCC extension to a network device based on the first parameter and the second parameter.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] 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.

[0153] 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.

[0154] 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.

[0155] 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.

[0156] 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.

[0157] In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system 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.

[0158] 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.

[0159] 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.

[0160] 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.

[0161] 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.

[0162] 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.

[0163] 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.

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

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

[0166] 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.

[0167] 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.

[0168] 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.

[0169] 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.

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

[0171] 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.

[0172] 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.

[0173] 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.

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

[0175] 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.

[0176] 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.

[0177] 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.

[0178] 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.

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

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

[0181] 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.

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

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

[0184] In some embodiments, the 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 radio access network 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.

[0185] 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.

[0186] In some embodiments, the network device 101 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.

[0187] In some embodiments, the terminal 102 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a Narrow Band-Internet of Things (NB-IoT) device, a satellite communication 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.

[0188] 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.

[0189] 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.

[0190] 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, Narrowband-IoT (NB-IoT) systems, Vehicle-to-Everything (V2X) systems, 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).

[0191] 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.

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

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

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

[0195] 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.

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

[0197] Currently, common OCC multiplexing schemes include: pre-DFT based OCC spreading, symbol-level OCC spreading, repetition-based OCC multiplexing, etc.

[0198] However, the above schemes each have their own shortcomings: for pre-DFT based OCC spreading, when the code rate is high or the number of multiplexed users is large, the actual transmission code rate may be relatively large. For example, as shown in Figure 1B, when the number of multiplexed users is 1, the code rate is greater than 1, which cannot guarantee the transmission of information bits. The OCC multiplexing scheme should not be limited to scheduling scenarios with very low code rates. In addition, in order to effectively achieve system expansion, a certain number of multiplexed users should also be guaranteed; for symbol-level OCC spreading, compared with pre-DFT based OCC spreading, it is more affected by channel time-varying properties. Theoretically, the link performance under this scheme may be worse than that of pre-DFT based OCC spreading; for repetition-based OCC multiplexing, this scheme will also be affected by channel time-varying properties. In particular, when the satellite moves at a high speed, the link performance will also be affected by channel time-varying properties.

[0199] In summary, an effective solution needs to be considered to improve the uplink system capacity while effectively ensuring the link performance of the data channel.

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

[0201] 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:

[0202] Step S2101: Terminal 102 sends third information.

[0203] In some embodiments, the network device 101 receives third information sent by the terminal 102 .

[0204] In some embodiments, the third information is used to indicate the capability of the terminal 102 .

[0205] In some embodiments, the third information is used to indicate that the terminal 102 supports pre-DFT-based OCC multiplexing.

[0206] In some embodiments, the name of the third information is not limited, and it can be, for example, "terminal capability", "whether to support pre-DFT-based OCC multiplexing", etc.

[0207] In some embodiments, the third information may be included in the signaling of the terminal capability (UE capability).

[0208] In some embodiments, the third information may be included in a newly added field in the signaling of the terminal capability.

[0209] In some embodiments, the third information may be included in radio resource control (RRC) signaling.

[0210] In some embodiments, the third information may be included in terminal assistance information (UE assistance information).

[0211] In some embodiments, for scheduling using different types of downlink control information (DCI), the same or different fields may be used to send the third information.

[0212] Optionally, different types of DCI may include: fallback DCI; non-fallback DCI; and compact DCI.

[0213] Optionally, the non-fallback DCI is, for example, DCI format 0-1, DCI format 0-3, etc.

[0214] Optionally, the fallback DCI is, for example, DCI format 0-0.

[0215] Optionally, the compact DCI is, for example, DCI format 0-2.

[0216] It should be noted that fallback DCI has a smaller payload than non-fallback DCI, supports or includes limited information fields, reduces signaling overhead, and can somewhat mitigate transmission uncertainty. Non-fallback DCI, on the other hand, supports more information fields and allows for more flexible DCI configuration based on system characteristics. Compact DCI is a compact DCI format, potentially smaller than DCI formats 0-1 and 1-1, used to schedule data transmission for Ultra-Reliable Low-Latency Communications (URLLC).

[0217] In some embodiments, the third information may be sent using the same or different fields for different channels.

[0218] Optionally, the different channels may include: a physical uplink control channel (Physical Uplink Control Channel, PUCCH); and a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH).

[0219] In some embodiments, the third information may be sent using the same or different fields for different types of DCI and different channels.

[0220] In some embodiments, the third information includes a first indication and a second indication;

[0221] The first indication is used to indicate that the terminal 102 supports TBoMS-based PUSCH, and the second indication is used to indicate that the terminal 102 supports pre-DFT-based OCC multiplexing.

[0222] It should be noted that if the terminal 102 only sends the first indication and does not send the second indication, or if the terminal 102 only sends the second indication and does not send the first indication, it indicates that the terminal 102 does not support the PUSCH of the TBoMS based on the pre-DFT OCC extension. Only when the terminal 102 sends the first indication and the second indication at the same time, it indicates that the terminal 102 supports the PUSCH of the TBoMS based on the pre-DFT OCC extension.

[0223] In some embodiments, the third information includes a third indication;

[0224] The third indication is used to indicate that the terminal supports the PUSCH of TBoMS based on pre-DFT OCC extension.

[0225] As an example, the terminal 102 reports the pre-DFT based OCC spreading with TBoMS capability based on RRC signaling. For example, the capability reporting can be performed based on the UE capability. Specifically, there are the following two capability reporting methods:

[0226] Method 1: TBoMS and pre-DFT based OCC spreading each provide separate capability indications. Optionally, TBoMS can provide terminal capability indications based on R17 signaling.

[0227] Method 2: Joint capability indication of pre-DFT based OCC spreading with TBoMS. That is, a capability reporting field is used for indication. If the capability field is reported, it indicates that the terminal supports the transmission of pre-DFT based OCC spreading with TBoMS. Otherwise, if the terminal does not report the capability field, it indicates that the terminal does not support the transmission of pre-DFT based OCC spreading with TBoMS.

[0228] In step S2102 , the terminal 102 determines a first parameter.

[0229] In some embodiments, the first parameter is the number of time slots occupied by the TBoMS.

[0230] As an example, as shown in FIG2B , in this example, PUSCH transmission occupies 8 time slots (Slot#0-Slot#7), one TBoMS occupies 4 time slots (Slot#0-Slot#3 or Slot#4-Slot#7), and two TBoMS repeated transmissions (1 st repetition and 2 nd repetition). In addition, pre-DFT based OCC spreading is performed for each time slot transmission. That is, before performing DFT, the modulation symbol spreading and the number of modulation symbol spreading are first determined. This number is related to the length of the OOC sequence (OCC length). For example, if the OCC length is 4, 3 symbol spreadings are performed, which means that each modulation symbol will be repeatedly spread 3 times, resulting in a total of 4 spread symbols (the original symbol plus 3 spreads). Therefore, a modulation symbol is repeated 4 times in total, corresponding to the OCC length.

[0231] Optionally, spreading can be performed on a symbol block basis, with each block containing N symbols. The value of N is determined by protocol agreement or by a combination of protocol agreement and parameters indicated by the gNB, and N is greater than or equal to 1. In this spreading scheme, data symbols are processed not as individual symbols but as symbol blocks. Each symbol block contains a certain number of symbols. Since spreading is performed across the entire symbol block, the same spreading effect can be applied to multiple symbols simultaneously.

[0232] Furthermore, OCC sequence covering can be performed, that is, each value in the OCC sequence is multiplied by the corresponding Modulation symbol, or by each Modulation symbol in each block. In this process, different Modulation symbols in the same block can be covered with the same OCC sequence value.

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

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

[0235] 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.

[0236] In some embodiments, the name of the first parameter is not limited, and it can be, for example, "number of time slots", "number of time slots occupied by TBoMS", etc.

[0237] In some embodiments, the size of a transport block (TB) corresponding to a TBoMS is determined based on the number of available time-frequency domain resources within a time slot corresponding to the TBoMS. That is, in the present disclosure, for pre-DFT OCC spreading with TBoMS, the size of a TB corresponding to the TBoMS is determined based on the total number of available resources within a time slot corresponding to the TBoMS.

[0238] It should be noted that a time slot corresponding to TBoMS refers to any one of the time slots corresponding to TBoMS. For example, for the PUSCH transmission shown in Figure 2B above, the size of the TB corresponding to TBoMS can be determined based on the number of available time-frequency domain resources in any time slot from Slot#0 to Slot#7. Alternatively, the size of the TB corresponding to TBoMS can be determined based on the first time slot used for TBoMS PUSCH transmission. For example, the size of the TB corresponding to TBoMS can be determined based on the number of available time-frequency domain resources in slot#0.

[0239] It should be noted that the available time-frequency domain resources in a time slot refer to the time-frequency domain resources allocated by the network device 101 for data transmission, and do not include the time-frequency domain resources occupied by reference signals and the like.

[0240] In some embodiments, the size of the TB corresponding to the TBoMS is determined based on at least one of the following information:

[0241] The number of available time-frequency domain resources in a time slot corresponding to the TBoMS;

[0242] The first parameter mentioned above;

[0243] The second parameter mentioned above.

[0244] As an example, the size of the TB corresponding to TBoMS = number of REs * number of OSs * Q * v * code rate / OCC length * number of slots per TBoMS, where the number of REs represents the number of available frequency domain resources in a time slot corresponding to TBoMS, the number of OSs represents the number of available time domain resources in a time slot corresponding to TBoMS, Q represents the modulation order, v represents the number of transmission layers, code rate represents the code rate, OCC length represents the length of the OCC sequence, and number of slots per TBoMS represents the number of time slots occupied by TBoMS.

[0245] In some embodiments, the end bit of the plurality of bits sent in the first time slot and the start bit of the plurality of bits sent in the second time slot are adjacent bits in the plurality of coded bits corresponding to the TB;

[0246] The first time slot and the second time slot are adjacent time slots in a plurality of time slots occupied by the TBoMS, and the TB is a TB corresponding to the TBoMS.

[0247] It should be noted that the multiple time slots occupied by the TBoMS are more than two, and the first time slot and the second time slot are any two adjacent time slots in the multiple time slots.

[0248] For example, for the PUSCH transmission shown in Figure 2B above, the eight time slots correspond to the same transport block, and each time slot transmits different bits of the transport block. The 1st to 100th bits may be sent in Slot#0, the 101st to 200th bits may be sent in Slot#1, the 201st to 300th bits may be sent in Slot#2, and so on. At this time, the end bit of the multiple bits sent in the previous time slot and the start bit of the multiple bits sent in the next time slot in adjacent time slots are adjacent bits in the multiple coded bits corresponding to the TB, that is, the 100th bit sent in Slot#0 is adjacent to the 101st bit sent in Slot#1, and the 200th bit sent in Slot#1 is adjacent to the 201st bit sent in Slot#2.

[0249] In the present disclosure, for TBoMS based pre-DFT OCC spreading, when performing rate-matching, back-to-back coded bit values ​​are taken between two adjacent time slots within the TBoMS time duration. That is, the start bit of the next time slot is the end bit of the previous time slot + 1.

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

[0251] As a possible implementation manner, the first parameter is determined based on the second parameter.

[0252] As an example, the first parameter can be the same as the second parameter, for example, the number of slots occupied by TBoMS is the OCC length, or equal to the total number of users multiplexed by OCC, or it can be the ratio between the second parameter and a specific value, for example, the number of slots occupied by TBoMS = the total number of users multiplexed by OCC / N, where N is configured / indicated by the base station, or determined by protocol agreement.

[0253] As a possible implementation manner, the first parameter is determined based on the first number of repeated transmissions.

[0254] Optionally, the first number of repeated transmissions may be indicated by the network device 101. It should be noted that the first number of repeated transmissions indicated by the network device 101 is the number of repeated transmissions of the TB transmitted based on a single time slot, that is, the total number of time slots occupied after a TB is repeatedly transmitted multiple times. For example, if the time slot occupied by the TBoMS is n, and the total number of time slots occupied after the TB is repeatedly transmitted M times is n*M, then the first number of repeated transmissions is n*M.

[0255] As an example, the number of slots occupied by the TBoMS is implicitly determined by the number of repetitions indicated by the gNB. For example, the number of slots occupied by the TBoMS = number of repetitions / M, where M is configured / indicated by the base station or determined by protocol agreement, such as M = 2, 4, etc. Alternatively, M is determined by the OCC length, with different OCC lengths corresponding to different M. A larger OCC length corresponds to a smaller M. In this case, the number of slots occupied by the TBoMS = number of repetitions / M, meaning that the number of repetitions for the TB based on multi-slot transmission is M, and repetition represents the total number of slots occupied by the TB corresponding to the TBoMS when it is transmitted M times.

[0256] Optionally, the first parameter is determined based on the first information sent by the network device 101.

[0257] As a possible implementation manner, the first information is at least one of the following: RRC message; DCI.

[0258] Optionally, the above RRC message may be, for example, RRC reconfiguration RRCReconfiguration, synchronous reconfiguration ReconfiguartionWithSync, RRC release with suspend configuration RRCRelease with SuspendConfig, etc.

[0259] Optionally, the above-mentioned DCI may be a common DCI or a scheduling DCI; wherein the scheduling DCI includes: fallback DCI, non-fallback DCI, and compact DCI.

[0260] In some embodiments, the network device 101 may indicate the first parameter via an RRC message or a DCI.

[0261] Optionally, the first information is an RRC message or DCI, and the first information directly indicates the above-mentioned first parameter.

[0262] In some embodiments, the network device 101 may configure and indicate the first parameter by combining RRC messages and DCI.

[0263] Optionally, a set of first parameters may be configured through RCC signaling, where the first information is DCI, and the first information is used to indicate an index in the set.

[0264] As a possible implementation manner, the first parameter is indicated by at least one of the following information fields of the DCI:

[0265] Modulation and Coding Scheme (MCS) information field;

[0266] Transmission Power Control (TPC) information field;

[0267] Time Domain Resource Assignment (TDRA) information domain;

[0268] Frequency Hopping (FH) flag information field;

[0269] Frequency Domain Resource Allocation (FDRA) information field;

[0270] Added new information fields.

[0271] As a possible implementation manner, the first parameter is included in at least one of the following information:

[0272] Time Domain Resource Assignment (TDRA) list;

[0273] Modulation and Coding Scheme (MCS) table;

[0274] Transmission Power Control (TPC) table.

[0275] The above TDRA table, MCS table and TPC table are configured by the gNB or agreed upon in the protocol.

[0276] It can be understood that the newly added information field refers to the information field newly added in the scheduling DCI.

[0277] In some embodiments, the newly added information field is in non-fallback DCI or compact DCI.

[0278] In some embodiments, only the fallback DCI may reuse the existing information field to indicate the above-mentioned first parameter, or all three types of DCI may reuse the existing information field to indicate the above-mentioned first parameter, or the fallback DCI and non-fallback DCI / compact DCI may reuse the existing information field to indicate the above-mentioned first parameter.

[0279] Optionally, the first parameter is indicated by an MCS information field. For example, m bits in the MCS information field may be used to indicate the first parameter, where m is a positive integer. The m bits may be the m bits starting from the most significant bit in the information field, or the m bits starting from the least significant bit in the information field, and so on.

[0280] Optionally, the first parameter is indicated by a TPC information field, for example, at least one bit in the TPC information field may be used to indicate the first parameter, or some rows or columns in a TPC table may be reused.

[0281] Optionally, the first parameter is indicated by a TDRA information field, for example, by adding a field indicating the first parameter to a TDRA list. In this case, the first parameter is included in the TDRA list rather than in the TDRA information field. The TDRA information field of the DCI is used to indicate the index of one of the rows of the TDRA list (comprising multiple rows), and the first parameter is determined based on this method.

[0282] In addition, the first parameter may also be included in an MCS table or a TPC table, similar to the indication of the TDRA information field.

[0283] That is to say, at least part of the bits in the MCS information field, TPC information field, or TDRA information field can be used to directly indicate the above-mentioned first parameter, or the above-mentioned first parameter can be placed in the above-mentioned MCS list, TPC list, or TDRA list, and the table index can be indicated through the corresponding information field in the DCI.

[0284] It should be noted that the TDRAlist, MCS table and TPC table may be preset in the protocol. Therefore, if the above-mentioned first parameter is placed in these two tables, it is necessary to obtain a modified protocol preset table again, wherein the protocol preset table can be manually modified.

[0285] Optionally, the first parameter is indicated by an FH flag information field, for example, the FH flag field may be multiplexed.

[0286] Optionally, the first parameter is indicated by the FDRA information field, for example, some bits in the FDRA information field may be used to indicate the first parameter, or the first parameter is jointly encoded with frequency domain resource allocation.

[0287] In some embodiments, when the network device 101 indicates the above-mentioned first parameter by reusing the existing information field, the terminal 102 parses the above-mentioned information field based on the above-mentioned new definition when determining to enable pre-DFT OCC spreading with TBoMS, thereby determining the above-mentioned first parameter indicated by the above-mentioned information field.

[0288] In some embodiments, when the network device 101 indicates the first parameter by reusing an existing information field, the terminal 102 parses the information field based on the legacy definition when determining that pre-DFT OCC spreading with TBoMS is not enabled.

[0289] Optionally, the network device 101 may enable / disable pre-DFT OCC spreading with TBoMS by explicitly configuring enable / disable RRC parameters, and the terminal 102 determines whether to enable / disable pre-DFT OCC spreading with TBoMS based on the RRC parameters.

[0290] Alternatively, the enabling / disabling of pre-DFT OCC spreading with TBoMS is implicitly determined by configuring pre-DFT OCC spreading with TBoMS related parameters through RRC.

[0291] Whether the newly added domain exists in non-fallback DCI and / or compactDCI is determined by explicitly configuring the enable / disable RRC parameters. If enabled, it exists in non-fallback DCI and / or compactDCI; if disabled, it does not exist in non-fallback DCI and / or compactDCI. Alternatively, whether the newly added domain exists in non-fallback DCI and / or compactDCI can be implicitly determined by determining whether the pre-DFT OCC spreading with TBoMS related RRC parameters are configured.

[0292] In summary, in this disclosure, the number of slots occupied by the TBoMS can be determined by protocol agreement or indicated by the gNB. Specifically, there are two methods:

[0293] Method 1: The number of slots occupied by the TBoMS is determined by the protocol. For example, the number of slots occupied by the TBoMS is equal to the OCC length, or equal to the total number of users multiplexed by the OCC; or the number of slots occupied by the TBoMS = the total number of users multiplexed by the OCC / N, where N is configured / indicated by the base station or determined by the protocol. Alternatively, the number of slots occupied by the TBoMS is implicitly determined by the number of repetitions indicated by the gNB, for example, the number of slots occupied by the TBoMS = the number of repetitions / M, where M is configured / indicated by the base station or determined by the protocol, such as M = 2, 4, etc. Alternatively, M is determined by the OCC length, with different OCC lengths corresponding to different M, and a larger OCC length corresponds to a smaller M.

[0294] Method 2: The number of slots occupied by the TBoMS can also be configured and / or indicated by the gNB through semi-static signaling or dynamic signaling.

[0295] Regarding the DCI indication method, specifically, at least one of the following methods may be used for indication: (Several fields in the following methods may be used for joint indication)

[0296] Multiplex the higher bits of MCS;

[0297] Reuse at least one bit of the TPC, or reuse some rows in the TPC table;

[0298] Reuse the TDRA field, where the number of slots occupied by the TBoMS is configured in at least one row of the TDRA list through RRC configuration. Different rows can have different values ​​(that is, the number of slots occupied by the TBoMS is added as a new column in the TDRA table);

[0299] Multiplex the FH flag field;

[0300] Some bits of the FDRA domain, or the number of slots occupied by the TBoMS, are jointly coded with the frequency domain resource allocation.

[0301] It should be noted that in the above method, only if the gNB explicitly or implicitly enables pre-DFT OCC spreading with TBoMS, can the terminal interpret the field based on the new definition. Otherwise, the above field is still interpreted based on the original meaning. The enabling method can be: determining whether to enable or disable based on whether the gNB is configured with pre-DFT based OCC multiplexing related parameters, such as whether the gNB is configured with OCC length, or determining whether to enable or disable through the explicit signaling configuration of the gNB, for example, through 1 bit indication.

[0302] In each embodiment of the present disclosure, the PUSCH uses the same OFDM (Orthogonal Frequency Division Multiplexing) symbol in each time slot occupied by the TBoMS. That is, in the present disclosure, for pre-DFT-based OCC spreading with TBoMS, each time slot uses the same OFDM symbol resource allocation for PUSCH transmission, for example, OFDM symbols #0-#12.

[0303] In various embodiments of the present disclosure, the PUSCH also includes multi-tone NPUSCH. That is, in the present disclosure, pre-DFT based OCC spreading with TBoMS is applicable to transmission of at least one of the following channels: PUSCH, NPUSCH format 1 with multi-tone.

[0304] In step S2103, the terminal 102 determines a second parameter.

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

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

[0307] In some embodiments, the terminal 102 determines the second parameter based on the agreement of the protocol.

[0308] As a possible implementation, the second parameter is determined based on the first parameter. For example, the second parameter may be the same as the first parameter, or the second parameter may be a ratio between the first parameter and a specific value.

[0309] As an example, the length of the OCC sequence, or the number of multiplexed users, can be determined by the protocol agreement and the number of slots occupied by a TBoMS PSUCH transmission. For example, the protocol agrees that OCC length = the number of slots occupied by TBoMS / Q, where Q can be agreed upon by the protocol, such as Q=1, or Q=1 / 2, etc.

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

[0311] As a possible implementation manner, the second information is at least one of the following: RRC message; DCI.

[0312] Optionally, the above RRC message may be, for example, RRC reconfiguration RRCReconfiguration, synchronous reconfiguration ReconfiguartionWithSync, RRC release with suspend configuration RRCRelease with SuspendConfig, etc.

[0313] Optionally, the above-mentioned DCI may be a common DCI or a scheduling DCI; wherein the scheduling DCI includes: fallback DCI, non-fallback DCI, and compact DCI.

[0314] In some embodiments, the network device 101 may indicate the second parameter via an RRC message or DCI.

[0315] Optionally, the first information is an RRC message or DCI, and the second information directly indicates the above-mentioned second parameter.

[0316] In some embodiments, the network device 101 may configure and indicate the second parameter by combining RRC messages and DCI.

[0317] Optionally, a set of second parameters may be configured through RCC signaling, where the second information is DCI, and the second information is used to indicate an index in the set.

[0318] As a possible implementation manner, the second parameter is indicated by at least one of the following information fields of the DCI:

[0319] Modulation and Coding Scheme (MCS) information field;

[0320] Transmission Power Control (TPC) information field;

[0321] Time Domain Resource Assignment (TDRA) information domain;

[0322] Frequency Hopping (FH) flag information field;

[0323] Frequency Domain Resource Allocation (FDRA) information field;

[0324] Added new information fields.

[0325] As a possible implementation manner, the second parameter is included in at least one of the following information:

[0326] Time Domain Resource Assignment (TDRA) list;

[0327] Modulation and Coding Scheme (MCS) table;

[0328] Transmission Power Control (TPC) table.

[0329] The above TDRA table, MCS table and TPC table are configured by the gNB or agreed upon in the protocol.

[0330] It can be understood that the newly added information field refers to the information field newly added in the scheduling DCI.

[0331] In some embodiments, the newly added information field is in non-fallback DCI or compact DCI.

[0332] In some embodiments, only the fallback DCI may reuse the existing information field to indicate the above-mentioned second parameter, or all three types of DCI may reuse the existing information field to indicate the above-mentioned second parameter, or the fallback DCI and non-fallback DCI / compact DCI may reuse the existing information field to indicate the above-mentioned second parameter.

[0333] Optionally, the second parameter is indicated by an MCS information field. For example, m bits in the MCS information field may be used to indicate the second parameter, where m is a positive integer. The m bits may be the m bits starting from the most significant bit in the information field, or the m bits starting from the least significant bit in the information field, and so on.

[0334] Optionally, the second parameter is indicated by a TPC information field, for example, at least one bit in the TPC information field may be used to indicate the second parameter, or some rows or columns in a TPC table may be reused.

[0335] Optionally, the second parameter is indicated by a TDRA information field, for example, a field indicating the second parameter may be added to the TDRA list. In this case, the second parameter is included in the TDRA list rather than in the TDRA information field. The TDRA information field of the DCI is used to indicate the index of one of the rows of the TDRA list (containing multiple rows), and the second parameter is determined based on this method.

[0336] In addition, the second parameter may also be included in an MCS table or a TPC table, similar to the indication of the TDRA information field.

[0337] That is to say, the second parameter may be directly indicated using at least part of the bits in the MCS information field, the TPC information field, or the TDRA information field, or the second parameter may be placed in the MCS list, the TPC list, or the TDRA list, and the table index may be indicated through the corresponding information field in the DCI.

[0338] It should be noted that the TDRAlist, MCS table and TPC table may be preset in the protocol. Therefore, if the second parameter is placed in these two tables, it is necessary to obtain a modified protocol preset table again, wherein the protocol preset table can be manually modified.

[0339] Optionally, the second parameter is indicated by an FH flag information field, for example, the FH flag field may be multiplexed.

[0340] Optionally, the second parameter is indicated by the FDRA information field, for example, some bits in the FDRA information field may be used to indicate the second parameter, or the second parameter is jointly encoded with the frequency domain resource allocation.

[0341] In some embodiments, when the network device 101 indicates the above-mentioned second parameter by reusing the existing information field, the terminal 102 parses the above-mentioned information field based on the above-mentioned new definition when determining to enable pre-DFT OCC spreading with TBoMS, thereby determining the above-mentioned second parameter indicated by the above-mentioned information field.

[0342] In some embodiments, when the network device 101 indicates the second parameter by reusing an existing information field, the terminal 102 parses the information field based on the legacy definition when determining that pre-DFT OCC spreading with TBoMS is not enabled.

[0343] Optionally, the network device 101 may enable / disable pre-DFT OCC spreading with TBoMS by explicitly configuring enable / disable RRC parameters, and the terminal 102 determines whether to enable / disable pre-DFT OCC spreading with TBoMS based on the RRC parameters.

[0344] Alternatively, the enabling / disabling of pre-DFT OCC spreading with TBoMS is implicitly determined by configuring pre-DFT OCC spreading with TBoMS related parameters through RRC.

[0345] Whether the newly added domain exists in non-fallback DCI and / or compact DCI is determined by explicitly configuring the enable / disable RRC parameters. If enabled, it exists in non-fallback DCI and / or compact DCI; if disabled, it does not exist in non-fallback DCI and / or compact DCI. Alternatively, the presence of the newly added domain in non-fallback DCI and / or compact DCI can be implicitly determined by determining whether the pre-DFT OCC spreading with TBoMS related RRC parameters are configured.

[0346] In summary, in the present disclosure, based on the OCC multiplexing method, the total number of users multiplexed on a block of time-frequency domain resources can be determined based on the following method:

[0347] Determined based on semi-static configuration or dynamic indication from the base station. For semi-static configuration, for example, the OCC length is determined based on RRC signaling. Dynamic indication of the OCC length is similar to method 2 for determining the number of slots occupied by the TBoMS in step S2102A. For example, the OCC length can be indicated by the TDRA field and configured as a column in the TDRA table via RRC signaling. Different rows can have different parameter values. The gNB further indicates the OCC length by indicating a row in the table based on the TDRA field in dynamic signaling.

[0348] The OCC length, or the total number of multiplexed users, can be determined by a protocol-specified method and the number of slots occupied by a TBoMS PSUCH transmission. For example, the protocol specifies OCC length = number of slots occupied by the TBoMS / Q, where Q can be specified by the protocol, such as Q = 1 or Q = 1 / 2. In this manner, the number of slots occupied by the TBoMS can be determined in two ways based on the number of slots occupied by the TBoMS in step S2102A.

[0349] In step S2104, the terminal 102 sends a PUSCH of the TBoMS based on the OCC extension.

[0350] In some embodiments, the network device 101 receives the PUSCH of the TBoMS based on the OCC extension.

[0351] In some embodiments, the terminal 102 sends the above-mentioned PUSCH of the TBoMS based on the OCC extension to the network device 101 based on the first parameter and the second parameter.

[0352] In some embodiments, the OCC extension is a pre-DFT OCC extension based on discrete Fourier transform.

[0353] As shown in the aforementioned embodiments, the modulation symbols sent in each time slot corresponding to the TBoMS are all modulation symbols that have been subjected to pre-DFT OCC spreading.

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

[0355] 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.

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

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

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

[0359] 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.

[0360] 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.

[0361] 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.

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

[0363] 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.

[0364] 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.

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

[0366] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain 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, a certain A, any A, or first A, etc., but not limited to this.

[0367] 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.

[0368] The information transmission method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2104. For example, step S2101 may be implemented as an independent embodiment, steps S2102+S2103 may be implemented as independent embodiments, steps S2102+S2103+S2104 may be implemented as independent embodiments, and so on, but the present disclosure is not limited thereto.

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

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

[0371] 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:

[0372] Step S3101: Send third information to the network device 101.

[0373] 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.

[0374] Step S3102, determine the first parameter.

[0375] 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.

[0376] Step S3103: determine the second parameter.

[0377] The optional implementation of step S3103 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.

[0378] Step S3104 : Send the PUSCH of the TBoMS based on the OCC extension to the network device 101 .

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

[0380] The information transmission method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3104. For example, step S3101 may be implemented as an independent embodiment, steps S3102+S3103 may be implemented as independent embodiments, steps S3102+S3103+S3104 may be implemented as independent embodiments, steps S3101+S3102+S3103+S3104 may be implemented as independent embodiments, and so on, but the present disclosure is not limited thereto.

[0381] In some embodiments, step S3101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

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

[0384] Step S3201, determine the first parameter.

[0385] The optional implementation of step S3201 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.

[0386] Step S3202, determine the second parameter.

[0387] The optional implementation of step S3202 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.

[0388] Step S3203 : Send the PUSCH of the TBoMS based on the OCC extension to the network device 101 .

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

[0390] The information transmission method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3203. For example, step S3201 may be implemented as an independent embodiment, step S3202 may be implemented as an independent embodiment, steps S3201+S3202 may be implemented as independent embodiments, steps S3201+S3202+S3203 may be implemented as independent embodiments, etc., but the present disclosure is not limited thereto.

[0391] In some embodiments, step S3201 and step S3202 may be executed in an interchanged order or simultaneously.

[0392] 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:

[0393] Step S4101: receiving the third information sent by terminal 102.

[0394] The optional implementation of step S4101 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.

[0395] Step S4102 : receiving a PUSCH of a TBoMS based on OCC extension sent by the terminal 102 .

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

[0397] Optionally, the PUSCH of the OCC-extended TBoMS is determined by the terminal 102 based on the first parameter and the second parameter. For an optional implementation of determining the first parameter, see the optional implementation of step S2102 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , and will not be described in detail here. For an optional implementation of determining the second parameter, see the optional implementation of step S2103 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , and will not be described in detail here.

[0398] The information sending method involved in the embodiments of the present disclosure may include at least one of steps S4101 and S4102. For example, step S4101 may be implemented as an independent embodiment, step S4102 may be implemented as an independent embodiment, steps S4101+S4102 may be implemented as independent embodiments, etc., but the present disclosure is not limited thereto.

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

[0400] Step S4201 : receiving a PUSCH of a TBoMS based on OCC extension sent by the terminal 102 .

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

[0402] Optionally, the PUSCH of the OCC-extended TBoMS is determined by the terminal 102 based on the first parameter and the second parameter. For an optional implementation of determining the first parameter, see the optional implementation of step S2102 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , and will not be described in detail here. For an optional implementation of determining the second parameter, see the optional implementation of step S2103 of FIG. 2A and other related parts of the embodiment involved in FIG. 2A , and will not be described in detail here.

[0403] 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:

[0404] Step S5101: Terminal 102 determines a first parameter, where the first parameter is the number of time slots occupied by TBoMS.

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

[0406] Step S5103 : The terminal 102 sends a PUSCH of the TBoMS based on the OCC extension to the network device 101 based on the first parameter and the second parameter.

[0407] The optional implementation methods of steps S5101-S5103 can refer to the steps in any embodiment or any multiple embodiments in the above-mentioned Figures 2A, 3A-3B, and 4A-4B, and other related parts of the embodiments involved in Figures 2A, 3A-3B, and 4A-4B.

[0408] 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.

[0409] 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.

[0410] 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.

[0411] 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.

[0412] 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.

[0413] Figure 6A is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure. As shown in Figure 6A, a terminal 6100 may include at least one of a transceiver module 6101 and a processing module 6102. In some embodiments, the processing module is configured to determine a first parameter, which is the number of time slots occupied by a multi-slot transport block (TBoMS); the processing module is further configured to determine a second parameter, which is the length of an orthogonal cover code (OCC) sequence; and the transceiver module is configured to transmit, based on the first and second parameters, a physical uplink shared channel (PUSCH) for the TBoMS extended with the OCC to the network device.

[0414] In some embodiments of the present disclosure, the above-mentioned OCC extension is a pre-DFT OCC extension based on discrete Fourier transform.

[0415] In some embodiments of the present disclosure, the modulation symbols sent in each time slot corresponding to the TBoMS are all modulation symbols that have been subjected to pre-DFT OCC spreading.

[0416] In some embodiments of the present disclosure, the size of the transport block TB corresponding to the TBoMS is determined based on the number of available time-frequency domain resources in a time slot corresponding to the TBoMS.

[0417] In some embodiments of the present disclosure, the size of the transport block TB corresponding to the TBoMS is determined based on at least one of the following information:

[0418] The number of available time-frequency domain resources in a time slot corresponding to the above TBoMS;

[0419] The first parameter mentioned above;

[0420] The second parameter mentioned above.

[0421] In some embodiments of the present disclosure, the end bit of the plurality of bits sent in the first time slot and the start bit of the plurality of bits sent in the second time slot are adjacent bits in the plurality of coded bits corresponding to the transport block TB;

[0422] The first time slot and the second time slot are adjacent time slots among the multiple time slots occupied by the TBoMS, and the TB is a TB corresponding to the TBoMS.

[0423] In some embodiments of the present disclosure, determining the first parameter includes:

[0424] The first parameter is determined based on the agreement of the protocol or based on the first information sent by the network device.

[0425] In some embodiments of the present disclosure, the first parameter is determined based on the second parameter; or,

[0426] The first parameter is determined based on the first number of repeated transmissions.

[0427] In some embodiments of the present disclosure, the first information is at least one of the following:

[0428] Radio Resource Control RRC message;

[0429] Downlink control information DCI.

[0430] In some embodiments of the present disclosure, the first parameter is indicated by at least one of the following information fields of the DCI:

[0431] Modulation and coding strategy MCS information field;

[0432] Transmit power control TPC information field;

[0433] Time domain resource allocation TDRA information field;

[0434] Frequency hopping FH flag information field;

[0435] Frequency domain resource allocation FDRA information field;

[0436] Added new information fields.

[0437] In some embodiments of the present disclosure, the first parameter is included in at least one of the following information:

[0438] Time domain resource allocation TDRA list;

[0439] Modulation and coding strategy MCS table;

[0440] Transmit power control TPC table.

[0441] In some embodiments of the present disclosure, determining the second parameter includes:

[0442] The second parameter is determined based on the agreement of the protocol or based on the second information sent by the network device.

[0443] In some embodiments of the present disclosure, the second parameter is determined based on the first parameter.

[0444] In some embodiments of the present disclosure, the second information is at least one of the following:

[0445] Radio Resource Control RRC message;

[0446] Downlink control information DCI.

[0447] In some embodiments of the present disclosure, the second parameter is indicated by at least one of the following information fields of the DCI:

[0448] Modulation and coding strategy MCS information field;

[0449] Transmit power control TPC information field;

[0450] Time domain resource allocation TDRA information field;

[0451] Frequency hopping FH flag information field;

[0452] Frequency domain resource allocation FDRA information field;

[0453] Added new information fields.

[0454] In some embodiments of the present disclosure, the second parameter is included in at least one of the following information:

[0455] Time domain resource allocation TDRA list;

[0456] Modulation and coding strategy MCS table;

[0457] Transmit power control TPC table.

[0458] In some embodiments of the present disclosure, the orthogonal frequency division multiplexing (OFDM) symbols corresponding to the PUSCH in each time slot occupied by the TBoMS are the same.

[0459] In some embodiments of the present disclosure, the transceiver module is further configured to:

[0460] Sending third information to the network device, where the third information is used to indicate that the terminal supports TBoMS based on pre-DFT OCC extension.

[0461] In some embodiments of the present disclosure, the third information includes a first indication and a second indication;

[0462] The first indication is used to indicate that the terminal supports TBoMS-based PUSCH, and the second indication is used to indicate that the terminal supports pre-DFT-based OCC multiplexing.

[0463] In some embodiments of the present disclosure, the third information includes a third indication;

[0464] The third indication is used to indicate that the terminal supports the PUSCH of TBoMS based on pre-DFT OCC extension.

[0465] In some embodiments of the present disclosure, the above-mentioned PUSCH further includes: a narrowband PUSCH with multi-tone transmission using multiple subcarriers.

[0466] 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 2104, but not limited to this) performed by the terminal in any of the above methods, which will not be repeated here.

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

[0468] Figure 6B is a schematic diagram of the structure of another network device proposed in an embodiment of the present disclosure. As shown in Figure 6B, 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) of a multi-slot transport block (TBoMS) extended with an orthogonal cover code (OCC) sent by a terminal; the PUSCH is sent by the terminal based on a first parameter and a second parameter determined, where the first parameter is the number of time slots occupied by the TBoMS, and the second parameter is the length of the OCC sequence.

[0469] In some embodiments of the present disclosure, the above-mentioned OCC extension is a pre-DFT OCC extension based on discrete Fourier transform.

[0470] In some embodiments of the present disclosure, the modulation symbols sent in each time slot corresponding to the TBoMS are all modulation symbols that have been subjected to pre-DFT OCC spreading.

[0471] In some embodiments of the present disclosure, the size of the transport block TB corresponding to the TBoMS is determined based on the number of available time-frequency domain resources in a time slot corresponding to the TBoMS.

[0472] In some embodiments of the present disclosure, the size of the transport block TB corresponding to the TBoMS is determined based on at least one of the following information:

[0473] The number of available time-frequency domain resources in a time slot corresponding to the above TBoMS;

[0474] The first parameter mentioned above;

[0475] The second parameter mentioned above.

[0476] In some embodiments of the present disclosure, the end bit of the plurality of bits sent in the first time slot and the start bit of the plurality of bits sent in the second time slot are adjacent bits in the plurality of coded bits corresponding to the transport block TB;

[0477] The first time slot and the second time slot are adjacent time slots among the multiple time slots occupied by the TBoMS, and the TB is a TB corresponding to the TBoMS.

[0478] In some embodiments of the present disclosure, determining the first parameter includes:

[0479] The first parameter is determined based on the agreement of the protocol or based on the first information sent by the network device.

[0480] In some embodiments of the present disclosure, the first parameter is determined based on the second parameter; or,

[0481] The first parameter is determined based on the first number of repeated transmissions.

[0482] In some embodiments of the present disclosure, the first information is at least one of the following:

[0483] Radio Resource Control RRC message;

[0484] Downlink control information DCI.

[0485] In some embodiments of the present disclosure, the first parameter is indicated by at least one of the following information fields of the DCI:

[0486] Modulation and coding strategy MCS information field;

[0487] Transmit power control TPC information field;

[0488] Time domain resource allocation TDRA information field;

[0489] Frequency hopping FH flag information field;

[0490] Frequency domain resource allocation FDRA information field;

[0491] Added new information fields.

[0492] In some embodiments of the present disclosure, the first parameter is included in at least one of the following information:

[0493] Time domain resource allocation TDRA list;

[0494] Modulation and coding strategy MCS table;

[0495] Transmit power control TPC table.

[0496] In some embodiments of the present disclosure, determining the second parameter includes:

[0497] The second parameter is determined based on the agreement of the protocol or based on the second information sent by the network device.

[0498] In some embodiments of the present disclosure, the second parameter is determined based on the first parameter.

[0499] In some embodiments of the present disclosure, the second information is at least one of the following:

[0500] Radio Resource Control RRC message;

[0501] Downlink control information DCI.

[0502] In some embodiments of the present disclosure, the second parameter is indicated by at least one of the following information fields of the DCI:

[0503] Modulation and coding strategy MCS information field;

[0504] Transmit power control TPC information field;

[0505] Time domain resource allocation TDRA information field;

[0506] Frequency hopping FH flag information field;

[0507] Frequency domain resource allocation FDRA information field;

[0508] Added new information fields.

[0509] In some embodiments of the present disclosure, the second parameter is included in at least one of the following information:

[0510] Time domain resource allocation TDRA list;

[0511] Modulation and coding strategy MCS table;

[0512] Transmit power control TPC table.

[0513] In some embodiments of the present disclosure, the orthogonal frequency division multiplexing (OFDM) symbols corresponding to the PUSCH in each time slot occupied by the TBoMS are the same.

[0514] In some embodiments of the present disclosure, the transceiver module is further configured to:

[0515] Receive third information sent by the terminal, where the third information is used to indicate that the terminal supports TBoMS based on pre-DFT OCC extension.

[0516] In some embodiments of the present disclosure, the third information includes a first indication and a second indication;

[0517] The first indication is used to indicate that the terminal supports TBoMS-based PUSCH, and the second indication is used to indicate that the terminal supports pre-DFT-based OCC multiplexing.

[0518] In some embodiments of the present disclosure, the third information includes a third indication;

[0519] The third indication is used to indicate that the terminal supports the PUSCH of TBoMS based on pre-DFT OCC extension.

[0520] In some embodiments of the present disclosure, the above-mentioned PUSCH further includes: a narrowband PUSCH with multi-tone transmission using multiple subcarriers.

[0521] 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 2104, but not limited to this) performed by the network device in any of the above methods, which will not be repeated here.

[0522] 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.

[0523] 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.

[0524] 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.

[0525] 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.

[0526] 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.

[0527] 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.

[0528] 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.

[0529] 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.

[0530] 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.

[0531] 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.

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

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

[0534] 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.

[0535] 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).

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

[0537] 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.

[0538] 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.

[0539] 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.

[0540] 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.

[0541] 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)).

[0542] 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.

[0543] 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.

[0544] 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 the number of time slots occupied by the multi-slot transport block TBoMS; Determine a second parameter, where the second parameter is the length of an orthogonal cover code OCC sequence; Based on the first parameter and the second parameter, a physical uplink shared channel (PUSCH) of the TBoMS based on the OCC extension is sent to a network device.

2. The method according to claim 1, characterized in that The OCC extension is based on pre-DFT OCC extension before discrete Fourier transform.

3. The method according to claim 2, characterized in that The modulation symbols sent in each time slot corresponding to the TBoMS are all modulation symbols that have been subjected to pre-DFT OCC spreading.

4. The method according to any one of claims 1 to 3, characterized in that The size of the transport block TB corresponding to the TBoMS is determined based on the number of available time-frequency domain resources in a time slot corresponding to the TBoMS.

5. The method according to any one of claims 1 to 3, characterized in that The size of the transport block TB corresponding to the TBoMS is determined based on at least one of the following information: The number of available time-frequency domain resources in a time slot corresponding to the TBoMS; the first parameter; the second parameter.

6. The method according to any one of claims 1 to 5, characterized in that An end bit among the multiple bits sent in the first time slot and a start bit among the multiple bits sent in the second time slot are adjacent bits among the multiple coded bits corresponding to the transport block TB; The first time slot and the second time slot are adjacent time slots in a plurality of time slots occupied by the TBoMS, and the TB is a TB corresponding to the TBoMS.

7. The method according to any one of claims 1 to 6, characterized in that Determining the first parameter includes: The first parameter is determined based on a protocol agreement or based on first information sent by the network device.

8. The method according to claim 7, characterized in that The first parameter is determined based on the second parameter; or, The first parameter is determined based on the first number of repeated transmissions.

9. The method according to claim 7, characterized in that The first information is at least one of the following: Radio Resource Control RRC message; Downlink control information DCI.

10. The method according to claim 9, characterized in that The first parameter is indicated by at least one of the following information fields of the DCI: Modulation and coding strategy MCS information field; Transmit power control TPC information field; Time domain resource allocation TDRA information field; Frequency hopping FH flag information field; Frequency domain resource allocation FDRA information field; Added new information fields.

11. The method according to claim 7 or 9, characterized in that The first parameter is included in at least one of the following information: Time domain resource allocation TDRA list; Modulation and coding strategy MCS table; Transmit power control TPC table.

12. The method according to any one of claims 1 to 11, characterized in that Determining the second parameter includes: The second parameter is determined based on a protocol agreement or based on second information sent by the network device.

13. The method according to claim 12, characterized in that The second parameter is determined based on the first parameter.

14. The method according to claim 13, characterized in that The second information is at least one of the following: Radio Resource Control RRC message; Downlink control information DCI.

15. The method according to claim 14, characterized in that The second parameter is indicated by at least one of the following information fields of the DCI: Modulation and coding strategy MCS information field; Transmit power control TPC information field; Time domain resource allocation TDRA information field; Frequency hopping FH flag information field; Frequency domain resource allocation FDRA information field; Added new information fields.

16. The method according to claim 12 or 14, characterized in that The second parameter is included in at least one of the following information: Time domain resource allocation TDRA list; Modulation and coding strategy MCS table; Transmit power control TPC table.

17. The method according to any one of claims 1 to 16, characterized in that The orthogonal frequency division multiplexing (OFDM) symbols corresponding to the PUSCH in each time slot occupied by the TBoMS are the same.

18. The method according to any one of claims 1 to 17, characterized in that The method further comprises: Sending third information to the network device, where the third information is used to indicate that the terminal supports TBoMS based on pre-DFT OCC extension.

19. The method according to claim 18, characterized in that The third information includes a first indication and a second indication; The first indication is used to indicate that the terminal supports TBoMS-based PUSCH, and the second indication is used to indicate that the terminal supports pre-DFT-based OCC multiplexing.

20. The method according to claim 18, wherein The third information includes a third indication; The third indication is used to indicate that the terminal supports the PUSCH of TBoMS based on pre-DFT OCC extension.

21. The method according to any one of claims 1 to 20, characterized in that The PUSCH also includes: a narrowband PUSCH that transmits multi-tone signals using multiple subcarriers.

22. A method for sending information, characterized in that: The method is performed by a network device, and includes: The physical uplink shared channel PUSCH of the multi-slot transport block TBoMS extended based on the orthogonal cover code OCC sent by the receiving terminal.

23. The method according to claim 22, characterized in that The OCC extension is based on pre-DFT OCC extension before discrete Fourier transform.

24. The method according to claim 23, wherein The modulation symbols sent in each time slot corresponding to the TBoMS are all modulation symbols that have been subjected to pre-DFT OCC spreading.

25. The method according to any one of claims 22 to 24, characterized in that The size of the transport block TB corresponding to the TBoMS is determined based on the number of available time-frequency domain resources in a time slot corresponding to the TBoMS.

26. The method according to any one of claims 22 to 24, characterized in that The size of the transport block TB corresponding to the TBoMS is determined based on at least one of the following information: The number of available time-frequency domain resources in a time slot corresponding to the TBoMS; the first parameter; the second parameter.

27. The method according to any one of claims 22 to 26, characterized in that: An end bit among the multiple bits sent in the first time slot and a start bit among the multiple bits sent in the second time slot are adjacent bits among the multiple coded bits corresponding to the transport block TB; The first time slot and the second time slot are adjacent time slots in a plurality of time slots occupied by the TBoMS, and the TB is a TB corresponding to the TBoMS.

28. The method according to any one of claims 22 to 27, characterized in that Determining the first parameter includes: The first parameter is determined based on a protocol agreement or based on first information sent by the network device.

29. The method according to claim 28, characterized in that The first parameter is determined based on the second parameter; or, The first parameter is determined based on the first number of repeated transmissions.

30. The method according to claim 28, wherein The first information is at least one of the following: Radio Resource Control RRC message; Downlink control information DCI.

31. The method according to claim 30, characterized in that The first parameter is indicated by at least one of the following information fields of the DCI: Modulation and coding strategy MCS information field; Transmit power control TPC information field; Time domain resource allocation TDRA information field; Frequency hopping FH flag information field; Frequency domain resource allocation FDRA information field; Added new information fields.

32. The method according to claim 28 or 30, characterized in that The first parameter is included in at least one of the following information: Time domain resource allocation TDRA list; Modulation and coding strategy MCS table; Transmit power control TPC table.

33. The method according to any one of claims 22 to 32, characterized in that Determining the second parameter includes: The second parameter is determined based on a protocol agreement or based on second information sent by the network device.

34. The method according to claim 33, wherein The second parameter is determined based on the first parameter.

35. The method according to claim 34, wherein The second information is at least one of the following: Radio Resource Control RRC message; Downlink control information DCI.

36. The method according to claim 35, characterized in that The second parameter is indicated by at least one of the following information fields of the DCI: Modulation and coding strategy MCS information field; Transmit power control TPC information field; Time domain resource allocation TDRA information field; Frequency hopping FH flag information field; Frequency domain resource allocation FDRA information field; Added new information fields.

37. The method according to claim 33 or 35, characterized in that The second parameter is included in at least one of the following information: Time domain resource allocation TDRA list; Modulation and coding strategy MCS table; Transmit power control TPC table.

38. The method according to any one of claims 22 to 37, characterized in that The orthogonal frequency division multiplexing (OFDM) symbols corresponding to the PUSCH in each time slot occupied by the TBoMS are the same.

39. The method according to any one of claims 22 to 38, characterized in that The method further comprises: receiving third information sent by the terminal, where the third information is used to indicate that the terminal supports TBoMS based on pre-DFT OCC extension.

40. The method according to claim 39, wherein The third information includes a first indication and a second indication; The first indication is used to indicate that the terminal supports TBoMS-based PUSCH, and the second indication is used to indicate that the terminal supports pre-DFT-based OCC multiplexing.

41. The method according to claim 39, wherein The third information includes a third indication; The third indication is used to indicate that the terminal supports the PUSCH of TBoMS based on pre-DFT OCC extension.

42. The method according to any one of claims 22 to 41, wherein: The PUSCH also includes: a narrowband PUSCH that transmits multi-tone signals using multiple subcarriers.

43. A terminal, characterized in that: The terminal includes: a processing module, configured to determine a first parameter, where the first parameter is the number of time slots occupied by a multi-slot transport block TBoMS; The processing module is further configured to determine a second parameter, where the second parameter is the length of an orthogonal cover code (OCC) sequence; The transceiver module is configured to send a physical uplink shared channel (PUSCH) of the TBoMS based on the OCC extension to a network device based on the first parameter and the second parameter.

44. A network device, characterized in that The network equipment includes: The transceiver module is used to receive the physical uplink coherence of the multi-slot transmission block TBoMS based on the orthogonal cover code OCC extension sent by the terminal. Shared channel PUSCH; The PUSCH is sent by the terminal based on a determined first parameter and a second parameter, where the first parameter is the number of time slots occupied by the TBoMS, and the second parameter is the length of an orthogonal cover code OCC sequence.

45. 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 21.

46. ​​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 22-42.

47. 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 21, and the network device is configured to implement the information processing method according to any one of claims 22 to 42.

48. 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 22 to 42.

Images