Information sending methods and apparatuses

Abstract

Disclosed in the embodiments of the present disclosure are information sending methods and apparatuses. A method comprises: receiving first information sent by a network device; determining a demodulation reference signal (DMRS) of a terminal on the basis of the first information; and sending the DMRS to the network device on a physical uplink shared channel (PUSCH) based on orthogonal cover code (OCC) multi-user multiplexing, wherein the DMRS of the terminal is orthogonal to DMRSs corresponding to other terminals in the same OCC multiplexing user group, and time-frequency domain resources of PUSCHs corresponding to the terminals in the same user group are the same. Therefore, DMRS sequences between different users performing OCC multi-user multiplexing are mutually orthogonal, so as to ensure that a receiving end can effectively execute DMRS channel estimation of different multiplexing users, thereby effectively improving the communication efficiency of a system and also improving the spectrum and resource utilization.

Description

Information sending method and device Technical Field

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

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

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

[0004] Summary of the Invention

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

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

[0007] receiving first information sent by a network device;

[0008] Determine a demodulation reference signal DMRS of the terminal based on the first information;

[0009] Sending the DMRS to the network device on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing;

[0010] The DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

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

[0012] Sending first information to a terminal, where the first information is used to determine a demodulation reference signal (DMRS) of the terminal;

[0013] Receiving the DMRS sent by the terminal on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing;

[0014] The DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

[0015] A third aspect of the present disclosure provides a method for sending information, the method comprising:

[0016] The network device sends first information to the terminal;

[0017] The terminal determines, based on the first information, a demodulation reference signal (DMRS) of the terminal;

[0018] The terminal sends the DMRS to the network device on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing;

[0019] The DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

[0020] A fourth embodiment of the present disclosure provides a terminal, including:

[0021] a transceiver module, configured to receive first information sent by a network device;

[0022] A processing module, configured to determine a demodulation reference signal (DMRS) of the terminal based on the first information;

[0023] The transceiver module is further configured to send the DMRS to the network device on a physical uplink shared channel (PUSCH) based on orthogonal cover code (OCC) multi-user multiplexing;

[0024] The DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

[0025] A fifth embodiment of the present disclosure provides a network device, including:

[0026] a transceiver module, configured to receive first information sent by a network device;

[0027] A processing module, configured to determine a demodulation reference signal (DMRS) of the terminal based on the first information;

[0028] The transceiver module is further configured to send the DMRS to the network device on a physical uplink shared channel (PUSCH) based on orthogonal cover code (OCC) multi-user multiplexing;

[0029] The DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

[0030] The solution proposed in the embodiment of the present disclosure is as follows: first information sent by a network device is received; based on the first information, a demodulation reference signal DMRS of a terminal is determined; the DMRS is sent to the network device on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing; the DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same; the DMRS sequences between different users performing OCC multi-user multiplexing are made orthogonal to each other, so as to ensure that the receiving end can effectively perform DMRS channel estimation of different multiplexed users, thereby effectively improving the communication efficiency of the system and improving spectrum and resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0034] FIG2B is a schematic diagram of an OCC multi-user multiplexing resource mapping method provided by an embodiment of the present disclosure;

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

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

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

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

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

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

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

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

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

[0044] receiving first information sent by a network device;

[0045] Determine a demodulation reference signal DMRS of the terminal based on the first information;

[0046] Sending the DMRS to the network device on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing;

[0047] The DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

[0048] In the above embodiment, the DMRS sequences of different users are made orthogonal to each other, so as to ensure that the receiving end can effectively perform DMRS channel estimation for different multiplexed users.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the DMRS is generated based on at least one of the following sequences:

[0050] Type 1 low peak-to-average power ratio low-PAPR sequence;

[0051] Type 2 low-PAPR sequence.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the first information is used to indicate a first index in a preset first table, and the DMRS is determined based on a DMRS port corresponding to the first index.

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

[0054] determining second information, where the second information is used to indicate a length of the OCC sequence, or the second information is used to indicate a number of users multiplexed by the OCC;

[0055] Based on the second information, the preset first table is determined.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the first information is used to indicate the cyclic shift of the DMRS, or the first information is used to indicate a first parameter, and the first parameter is used to generate the DMRS.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the OCC multiplexing is pre-DFT OCC multiplexing before discrete Fourier transform, and the method further includes:

[0058] Determine a frequency domain position corresponding to the DMRS of the terminal based on at least one of the following information:

[0059] The number of users multiplexed by the above OCC;

[0060] The length of the above OCC sequence;

[0061] The index of the above OCC sequence.

[0062] In combination with some embodiments of the first aspect, in some embodiments, the DMRS is generated based on a type 1 low peak-to-average power ratio low-PAPR sequence, and the DMRS is determined based on a DMRS port and a cyclic shift sequence.

[0063] In combination with some embodiments of the first aspect, in some embodiments, the first information is used to indicate the first parameter and the DMRS port.

[0064] In combination with some embodiments of the first aspect, in some embodiments, the first information is the first index in the preset first table, and the DMRS is determined based on the DMRS port corresponding to the first index and the first parameter.

[0065] In combination with some embodiments of the first aspect, in some embodiments, the downlink control information DCI for scheduling the above-mentioned PUSCH includes at least one of the following: fallback DCI; non-fallback DCI.

[0066] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is used to indicate an index of the OCC sequence, and the index of the OCC sequence is used to determine at least one of the following information:

[0067] DMRS port corresponding to the above terminal;

[0068] The length of the above DMRS;

[0069] Cyclic shift of the above DMRS;

[0070] The first parameter is used to generate the DMRS.

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

[0072] Non-fallback downlink control information DCI;

[0073] Fallback downlink control information DCI;

[0074] Radio Resource Control (RRC);

[0075] Media Access Control Element MAC CE.

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

[0077] Based on the DMRS port and a preset second table, determine a time-frequency domain resource position corresponding to the DMRS, and / or determine an index of an OCC sequence corresponding to the DMRS;

[0078] Based on the index of the OCC sequence, the DMRS covers the value in the OCC sequence and is mapped to the corresponding time-frequency domain resource position.

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

[0080] Sending first information to a terminal, where the first information is used to determine a demodulation reference signal (DMRS) of the terminal;

[0081] Receiving the DMRS sent by the terminal on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing;

[0082] The DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

[0083] In the above embodiment, the DMRS sequences of different users are made orthogonal to each other, so as to ensure that the receiving end can effectively perform DMRS channel estimation for different multiplexed users.

[0084] In conjunction with some embodiments of the second aspect, in some embodiments, the DMRS is generated based on at least one of the following sequences:

[0085] Type 1 low peak-to-average power ratio low-PAPR sequence;

[0086] Type 2 low-PAPR sequence.

[0087] In combination with some embodiments of the second aspect, in some embodiments, the first information is used to indicate a first index in a preset first table, and the DMRS is determined based on a DMRS port corresponding to the first index.

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

[0089] determining second information, where the second information is used to indicate a length of the OCC sequence, or the second information is used to indicate a number of users multiplexed by the OCC;

[0090] Based on the second information, the preset first table is determined.

[0091] In combination with some embodiments of the second aspect, in some embodiments, the first information is used to indicate the cyclic shift of the DMRS, or the first information is used to indicate a first parameter, and the first parameter is used to generate the DMRS.

[0092] In conjunction with some embodiments of the second aspect, in some embodiments, the OCC multiplexing is pre-DFT OCC multiplexing before discrete Fourier transform; and the frequency domain position corresponding to the DMRS of the terminal is determined based on at least one of the following information:

[0093] The number of users multiplexed by the above OCC;

[0094] The length of the above OCC sequence;

[0095] The index of the above OCC sequence.

[0096] In combination with some embodiments of the second aspect, in some embodiments, the above-mentioned DMRS is generated based on a type 1 low peak-to-average power ratio low-PAPR sequence, and the above-mentioned DMRS is determined based on a DMRS port and a cyclic shift sequence.

[0097] In combination with some embodiments of the second aspect, in some embodiments, the first information is used to indicate the first parameter and the DMRS port.

[0098] In combination with some embodiments of the second aspect, in some embodiments, the first information is a first index in a preset first table, and the DMRS is determined based on the DMRS port corresponding to the first index and the first parameter.

[0099] In combination with some embodiments of the second aspect, in some embodiments, the downlink control information DCI for scheduling the above-mentioned PUSCH includes at least one of the following: fallback DCI; non-fallback DCI.

[0100] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is used to indicate an index of the OCC sequence, and the index of the OCC sequence is used to determine at least one of the following information:

[0101] DMRS port corresponding to the above terminal;

[0102] The length of the above DMRS;

[0103] Cyclic shift of the above DMRS;

[0104] The first parameter is used to generate the DMRS.

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

[0106] Non-fallback downlink control information DCI;

[0107] Fallback downlink control information DCI;

[0108] Radio Resource Control (RRC);

[0109] Media Access Control Element MAC CE.

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

[0111] The network device sends first information to the terminal;

[0112] The terminal determines, based on the first information, a demodulation reference signal (DMRS) of the terminal;

[0113] The terminal sends a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing to the network device based on the DMRS;

[0114] The DMRSs corresponding to the above-mentioned terminal and other terminals in the same OCC multiplexing user group are orthogonal, and the terminals included in the above-mentioned same user group use the same time-frequency domain resources.

[0115] In the above embodiment, the DMRS sequences of different users are made orthogonal to each other, so as to ensure that the receiving end can effectively perform DMRS channel estimation for different multiplexed users.

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

[0117] 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 core network device is used to execute the second aspect and the optional implementation method of the second aspect.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0154] 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), a satellite communication device, a Capability Reduced (RedCap) device, a car with communication function, a smart car, a tablet computer (Pad), 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.

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

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

[0157] The embodiments of the present disclosure may be applied to non-terrestrial networks (NTN), long term evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX ( 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0158] In some embodiments, the 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, unmanned aircraft systems) rather than ground base stations, as shown in Figure 1A. The link between the satellite and the terminal is called a service link, and the link between the satellite and the core network equipment is called a feeder link.

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

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

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

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

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

[0164] In summary, in OCC multi-user multiplexing scenarios, one issue that needs to be considered is how to ensure that the demodulation reference signals (DMRS) corresponding to different users are mutually orthogonal, so that the receiver can perform DMRS channel estimation for different multiplexed users. Therefore, the DMRS based on OCC multi-user multiplexing needs to be redesigned.

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

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

[0167] Step S2101: The network device 101 sends first information.

[0168] In some embodiments, the terminal 102 receives the first information.

[0169] In some embodiments, the first information is used by the terminal 102 to determine the corresponding DMRS.

[0170] In some embodiments, the first information is used to indicate a first index in a preset first table, and the terminal 102 can determine the DMRS based on a DMRS port corresponding to the first index.

[0171] Optionally, the preset first table may be specified in a protocol.

[0172] In some embodiments, the preset first table is determined by the terminal 102 based on second information, wherein the second information is used to indicate the length of the OCC sequence, or the second information is used to indicate the number of users multiplexed by the OCC.

[0173] Optionally, the second information is specified by a protocol or sent by the network device 101 .

[0174] In some embodiments, the name of the second information is not limited, and may be, for example, "OCC sequence information", "OCC multiplexing information", "OCC multiplexing configuration", "OCC sequence index", "downlink control information", etc.

[0175] In some embodiments, the first information is used to indicate a cyclic shift for generating a DMRS sequence, or is used to indicate a phase for generating a DMRS sequence.

[0176] Optionally, the cyclic shift of the DMRS includes an initial cyclic shift.

[0177] In some embodiments, the first information is used to indicate a first parameter, and the first parameter is used to generate the DMRS.

[0178] In some embodiments, the first information is used to indicate an index of an OCC sequence, and the terminal 102 determines at least one of the following information based on the index of the OCC sequence (that is, implicitly indicated by the index of the OCC sequence):

[0179] DMRS port corresponding to terminal 102;

[0180] DMRS length;

[0181] Cyclic shift of DMRS;

[0182] The first parameter is used to generate the DMRS.

[0183] In some embodiments, the name of the first information is not limited, and may be, for example, "downlink control information", "media access control control unit", "radio resource control", "DMRS indication", "DMRS index", etc.

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

[0185] Non-fallback downlink control information (DCI);

[0186] Fallback downlink control information DCI;

[0187] Radio Resources Control (RRC);

[0188] Medium Access Control (MAC) Control Element (CE).

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

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

[0191] It should be noted that fallback DCI has a smaller payload than non-fallback DCI, supports or includes limited information fields, has lower signaling overhead, and can avoid transmission uncertainty to a certain extent; while non-fallback DCI can support more information fields, can be configured accordingly based on system characteristics, and is more flexible.

[0192] In some embodiments, the first information is fallback DCI, and the first information can be used to configure or indicate an OCC sequence index to implicitly determine a DMRS port, the number of DMRS time domain symbols, etc., or to implicitly determine a DMRS cyclic shift, etc. The OCC sequence index and parameters such as the DMRS port have a certain correlation.

[0193] Furthermore, the index of the OCC sequence may also be determined through DCI or RRC, MAC CE, etc.

[0194] In some embodiments, the first information is configuration or indication of a UE-specific DMRS port through RRC / MAC CE signaling, or cyclic shift of a UE-specific DMRS, etc.

[0195] In some embodiments, there is a correspondence between the first information and the terminal 102, and the first information is used to indicate a DMRS port or a cyclic shift of the DMRS.

[0196] In particular, in some embodiments, when the first information is DCI (which may be fallback DCI or non-fallback DCI), and the first information is used to indicate a DMRS port or a cyclic shift of a DMRS, multiplexing of at least one of the following fields may be considered:

[0197] Some bits of the Frequency Domain Resource Assignment (FDRA) information field;

[0198] Time Domain Resource Assignment (TDRA) information field, for example, a new column can be added to the TDRA list for the OCC sequence index / DMRS port / cyclic shift, etc.

[0199] Modulation and Coding Scheme (MCS), for example, the high-order bits of the MCS may be used to indicate the OCC sequence index / DMRS port / cyclic shift, etc., or to constitute at least part of the bits used to indicate the above information;

[0200] At least part of the bits of the Transmit Power Control (TPC) field, or information such as the OCC sequence index / DMRS port / cyclic shift is multiplexed into a TPC table.

[0201] It should be noted that the reason for considering multiplexing the TPC field or TPC table is that the path loss of the terminal in the NTN link is too large, so the terminal transmits PUSCH at full power to a large extent, and the closed-loop power control part is invalid.

[0202] In some embodiments, it should be further explained that when OCC multiplexing is enabled, the PUSCH scheduled by DCI format 0-0 is no longer restricted to using only one fixed DMRS port and single-symbol DMRS.

[0203] Alternatively, OCC multiplexing of DFT-S-OFDM PUSCH is only applicable to scheduling of non-fallback DCI.

[0204] In some embodiments, at least one of the following processing methods is considered for the original DMRS port indicator bit in the non-fallback DCI:

[0205] When OCC multiplexing is enabled, the DMRS port field is no longer used in the non-fallback DCI;

[0206] The DMRS port field points to the reserved rows in the table;

[0207] A two-level indication method is adopted: the use priority of the indication information in the non-fallback DCI is higher than the use priority of the indication information in the MAC CE / RRC.

[0208] Optionally, when the PUSCH of DFT-s-OFDM adopts OCC multiplexing and the number of multiplexed users is greater than 8, for non-fallback DCI, the number of bits of the antenna port indicator bit needs to be extended.

[0209] In step S2102 , the terminal 102 determines a demodulation reference signal (DMRS) of the terminal.

[0210] In some embodiments, the terminal 102 determines the DMRS of the terminal based on the first information.

[0211] In some embodiments, the DMRS corresponding to the terminal 102 is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, where the multiple terminals included in the same user group use the same time-frequency domain resources.

[0212] In some embodiments, the DMRS of the terminal 102 is generated based on at least one of the following sequences:

[0213] Type 1 low Peak to Average Power Ratio (PAPR) sequence;

[0214] Type 2 low-PAPR sequence.

[0215] In some embodiments, the first information is used to indicate a first index in a preset first table, and terminal 102 can determine the DMRS based on the DMRS port corresponding to the first index. That is, terminal 102 can ensure orthogonality between DMRSs of different terminals by configuring / indicating different DMRS ports.

[0216] Optionally, the preset first table may be specified in a protocol.

[0217] As an example, orthogonal DMRS ports and their corresponding parameter configurations may be shown in Table 1 below, which may be a second table preset in the embodiment of the present disclosure: Wherein, CDM group is a Code Division Multiplexing (CDM) group.

[0218] The terminal 102 can determine the DMRS port and the number of DMRS symbols based on the first information and the first table; determine the frequency domain resources of the DMRS and the OCC code sequence covered by the DMRS based on the number of DMRS symbols, the DMRS port and the second table.

[0219] Table 1 Parameters of PUSCH DMRS configuration type 1

[0220] That is, Table 1 is applicable to a PUSCH whose waveform is DFT-s-OFDM for OCC multiplexing.

[0221] In some embodiments, the preset first table may be as shown in Table 2 to Table 4 below.

[0222] Table 2 Antenna Ports

[0223] Among them, optionally, the conditions for using Table 2 are: transmit precoding (transform precoder) is enabled (enabled), the DMRS configuration type is type 1 (dmrs-Type=1), the maximum length of the DMRS symbol is 2 (maxLength=2), OCC is enabled or the number of multiplexed users exceeds 8, excluding the information elements DMRS uplink transmit precoding dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured and pi / 2-BPSK modulation is used.

[0224] Table 3 Antenna Ports

[0225] Among them, optionally, the conditions for using Table 3 are: transmit precoding (transform precoder) is enabled (enabled), the DMRS configuration type is type 1 (dmrs-Type=1), the maximum length of the DMRS symbol is 2 (maxLength=2), OCC is configured and the OCC sequence length is greater than 8, excluding the case where the high-level parameters DMRS uplink transmit precoding dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and pi / 2-BPSK modulation is used.

[0226] Table 4 Antenna Ports

[0227] Among them, optionally, the conditions for using Table 4 are: transmit precoding (transform precoder) is enabled (enabled), the DMRS configuration type is type 1 (dmrs-Type=1), the maximum length of the DMRS symbol is 1 (maxLength=1), and OCC is configured (or OCC is configured and the OCC sequence length is greater than 4), excluding the case where the information elements dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured and pi / 2-BPSK modulation is used.

[0228] In the above embodiments, the number of bits occupied by the first information may increase based on the increase in the number of DMRS ports configured in the protocol.

[0229] Optionally, the first information may be, for example, DCI format 1-1, DCI format 1-2, etc.

[0230] In some embodiments, the preset first table is determined by the terminal 102 based on second information (for example, based on the OCC being configured and having a length greater than 8, the preset first table is determined to be Table 3). The second information is used to indicate the length of the OCC sequence, or the second information is used to indicate the number of users multiplexed by the OCC. In other words, the terminal 102 can select a first table to use from multiple tables specified in the protocol (for example, Tables 2-4, etc.) based on the length of the OCC sequence or the number of users multiplexed by the OCC.

[0231] Optionally, the second information is specified by a protocol or sent by the network device 101 .

[0232] Optionally, the above embodiment of determining DMRS (based on the design of DMRS ports) and multi-user multiple-input multiple-output MU-MIMO cannot be enabled at the same time.

[0233] Optionally, the terminal 102 is configured or indicated with OCC-related parameters (eg, the length of an OCC sequence or an index of an OCC sequence), which can implicitly indicate that the terminal 102 supports PUSCH OCC multiplexing based on the design of a DMRS port.

[0234] In some embodiments, the first information is a non-fallback DCI, and the terminal 102 can indirectly determine the OCC sequence index based on the indication of the antenna port. For example, there is a mapping relationship between the DMRS port and the OCC sequence index, or there is a mapping relationship between the OCC sequence index and the antenna port value.

[0235] In some embodiments, the first information is used to indicate an index of an OCC sequence, and the index of the OCC sequence is used to determine at least one of the following information:

[0236] DMRS port corresponding to terminal 102;

[0237] The number of DMRS time domain symbols;

[0238] Cyclic shift of DMRS;

[0239] The first parameter (n scid ), the first parameter is used to generate the DMRS.

[0240] As an example, the antenna port value is directly mapped to the index of the i-th OCC sequence for performing OCC on the data symbol.

[0241] As another example, a new column may be added to the antenna port table (eg, Table 2-4) to determine the index of the OCC sequence of the terminal.

[0242] In some embodiments, for the case where the above-mentioned DMRS is generated based on a type 2 low-PAPR sequence, as a possible embodiment, the following mapping relationship can be considered: {DMRS port#0, nscid#0} corresponds to OCC index#0, {DMRS port#0, nscid#1} corresponds to OCC index#1, {DMRS port#1, nscid#0} corresponds to OCC index#2, {DMRS port#1, nscid#1} corresponds to OCC index#3, and so on.

[0243] As an example, the above-mentioned preset first table may be shown in Table 5 to Table 7 below.

[0244] Table 5 Antenna Ports

[0245] Among them, optionally, the conditions for using Table 5 are: the DMRS configuration type is type 1 (dmrs-Type=1), the maximum length of the DMRS symbol is 2 (maxLength=2), the high-level parameters DMRS uplink transmission precoding dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, and pi / 2-BPSK modulation is used, and OCC is configured (or the length of OCC is configured).

[0246] Table 6 Antenna Ports

[0247] Among them, optionally, the conditions for using Table 6 are: transmit precoding (transform precoder) is enabled (enabled), the DMRS configuration type is type 1 (dmrs-Type=1), the maximum length of the DMRS symbol is 2 (maxLength=2), the high-level parameters DMRS uplink transmit precoding dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, and pi / 2-BPSK modulation is used, and the OCC length is greater than 8.

[0248] Table 7 Antenna Ports

[0249] Among them, optionally, the conditions for using Table 7 are: transmit precoding (transform precoder) is enabled (enabled), the DMRS configuration type is type 1 (dmrs-Type=1), the maximum length of the DMRS symbol is 1 (maxLength=1), in addition to the high-level parameters DMRS uplink transmit precoding dmrs-UplinkTransformPrecoding and tp-pi2BPSK are both configured, and pi / 2-BPSK modulation is used, OCC is configured (or OCC is configured and the length is greater than 4).

[0250] In some embodiments, the first information is used to indicate a cyclic shift of the DMRS, or the first information is used to indicate a first parameter used to generate the DMRS sequence. That is, the terminal 102 ensures orthogonality between different DMRSs through different cyclic shifts of the DMRSs.

[0251] Optionally, the first parameter is used for a DMRS generated based on a type 2 low-PAPR sequence.

[0252] In some embodiments, the first information is used to indicate an index of an OCC sequence, and the cyclic shift of the DMRS is determined based on the index of the OCC sequence.

[0253] In some embodiments, an existing field in the first information may be reused, or a new field may be added to the first information to indicate the OCC sequence index. Reusing an existing field may, for example, indicate the cyclic shift of the DMRS using fields such as TPC, FDRA, and antenna port.

[0254] Optionally, the cyclic shift includes an initial cyclic shift.

[0255] As an example, the first information implicitly determines the cyclic shift by indicating the index of the OCC sequence. It can be considered to preset a table as shown in Table 8 below in the protocol:

[0256] Table 8 OCC sequence index and cyclic shift

[0257] The cyclic shift index m0 is related to the number of users multiplexed by the OCC.

[0258] In some embodiments, it is determined that the number of users multiplexed by the OCC is less than or equal to 4, and the DMRS of the terminal 102 is determined based on the cyclic shift of the DMRS.

[0259] Optionally, the terminal 102 uses different DMRS cyclic shifts to ensure orthogonality between different DMRSs, which has certain requirements for frequency domain resource allocation, such as the number of resource blocks (RBs) that the terminal 102 expects to be allocated being greater than 1 or greater than 6.

[0260] In some embodiments, the DMRS is generated based on a type 1 low-PAPR sequence, and the DMRS may be determined based on a DMRS port and a cyclic shift sequence. That is, by combining the above two approaches, orthogonality between DMRSs of different terminals is ensured.

[0261] As an example, for example, based on a combination of a maximum of 8 DMRS ports in R16 (lagacy) and 2 sequence cyclic shifts (m0 or m_cs uses different values), a total of 16 orthogonal DMRSs can be generated.

[0262] Optionally, for the generation method of the DMRS, a joint indication or an independent indication method may be used to determine the DMRS.

[0263] Optionally, the DMRS may be determined by a joint indication, for example, OCC index 0-7 is used to indicate that the cyclic shift index is 0 and the DMRS ports are 0-7; OCC index 8-15 is used to indicate that the cyclic shift index is 6 and the DMRS ports are 0-7.

[0264] Or, optionally, the DMRS port is still determined based on a traditional method, and the cyclic shift index is indicated in the first information by adding a new field or reusing an existing field. The first information may be DCI, RRC, and the like.

[0265] In some embodiments, the DMRS is generated based on a type 2 low-PAPR sequence, the first information is used to indicate a first parameter and a first index in a preset first table, and the DMRS is generated based on a DMRS port corresponding to the first index and the first parameter (n scid That is, by combining the above two methods, the orthogonality between the DMRSs of different terminals is guaranteed.

[0266] Optionally, when orthogonality between DMRSs of different terminals is ensured by combining the above two approaches, the terminal 102 does not expect to be allocated different PUSCH resources from other terminals in the same user group.

[0267] In some embodiments, the OCC multiplexing of the terminal 102 is OCC multiplexing before discrete Fourier transform (pre-DFT OCC), and the terminal 102 can determine the frequency domain position corresponding to the DMRS of the terminal based on at least one of the following information:

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

[0269] The length of the OCC sequence;

[0270] The index of the OCC sequence.

[0271] In some embodiments, the DMRS frequency domain position is consistent with the frequency domain position of the data symbols occupied by the corresponding terminal after DFT, and the resource mapping is as shown in Figure 2B: Assuming that there are 4 users multiplexed (UE#0-UE#3), PUSCH mapping type B is adopted, and the PUSCH length is = 4 OFDM symbols (OS). In other words, the DMRS frequency domain position is directly determined based on the number of OCC multiplexed users (or the length of the OCC sequence) and the OCC sequence index.

[0272] It can be understood that 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.

[0273] In step S2103, the terminal 102 determines the time-frequency domain resource location corresponding to the DMRS.

[0274] In some embodiments, the terminal 102 can determine the time-frequency domain resource position corresponding to the DMRS based on the DMRS port and a preset second table.

[0275] As an example, the preset second table may be as shown in Table 1 in the previous step.

[0276] In step S2104, the terminal 102 determines the OCC sequence corresponding to the DMRS.

[0277] In some embodiments, the terminal 102 can determine the OCC sequence corresponding to the DMRS based on the number of DMRS symbols and a preset second table.

[0278] As an example, the preset second table may be as shown in Table 1 in the previous step.

[0279] How the terminal 102 determines the index of the OCC sequence may be as shown in the embodiment of the previous steps, and will not be repeated here.

[0280] In step S2105 , the terminal 102 sends the DMRS on the PUSCH based on OCC multi-user multiplexing.

[0281] In some embodiments, the terminal 102 can map the DMRS covering the value in the OCC sequence to the corresponding time-frequency domain resource position based on the index of the OCC sequence.

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

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

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

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

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

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

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

[0289] 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", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

[0302] Step S3101, receiving first information.

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

[0304] Step S3102: Determine the demodulation reference signal DMRS of the terminal.

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

[0306] Step S3103: Determine the time-frequency domain resource location corresponding to the DMRS.

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

[0308] Step S3104: determine the index of the OCC sequence corresponding to the DMRS.

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

[0310] Step S3105: Send the DMRS on the PUSCH based on OCC multi-user multiplexing.

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

[0312] The communication method according to the embodiments of the present disclosure may include at least one of steps S3101 to S3105. For example, step 3101 may be implemented as an independent embodiment, steps 3101+3102 may be implemented as an independent embodiment, steps 3101+3102+3103 may be implemented as an independent embodiment, steps 3101+3102+3104 may be implemented as an independent embodiment, steps 3101+3102+3105 may be implemented as an independent embodiment, steps 3101+3102+3103+3104 may be implemented as an independent embodiment, steps 3101+3102+3103+3104 may be implemented as an independent embodiment, and steps 3101+3102+3103+3104+3105 may be implemented as an independent embodiment, etc., but the present invention is not limited thereto.

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

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

[0315] Step S3201, receiving first information.

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

[0317] Step S3202: Determine the demodulation reference signal DMRS of the terminal.

[0318] Optional implementations of step S3202 can be found in step S2102 of FIG. 2A , optional implementations of step S3102 of FIG. 3A , and other related parts of the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0319] Step S3203: Determine the index of the OCC sequence corresponding to the DMRS.

[0320] Optional implementations of step S3203 can be found in step S2104 of FIG. 2A , optional implementations of step S3104 of FIG. 3A , and other related parts of the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0321] Step S3204: Send the DMRS on the PUSCH based on OCC multi-user multiplexing.

[0322] Optional implementations of step S3204 can be found in step S2105 of FIG. 2A , optional implementations of step S3105 of FIG. 3A , and other related parts of the embodiments involved in FIG. 2A and FIG. 3A , which will not be described in detail here.

[0323] The communication method according to the embodiments of the present disclosure may include at least one of steps S3201 to S3204. For example, step 3202 may be implemented as an independent embodiment, steps 3201+3202 may be implemented as an independent embodiment, step 3203 may be implemented as an independent embodiment, steps 3202+3203 may be implemented as an independent embodiment, steps 3201+3202+3203+3204 may be implemented as independent embodiments, etc., but the present invention is not limited thereto.

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

[0325] Step S3301, receiving first information.

[0326] The optional implementation of step S3301 can refer to the optional implementation of step S2101 in Figure 2A, step S3101 in Figure 3A, step S3201 in Figure 3B, and other related parts in the embodiments involved in Figures 2A, 3A, and 3B, which will not be repeated here.

[0327] Step S3302: Determine the demodulation reference signal DMRS of the terminal.

[0328] The optional implementation of step S3302 can be found in the optional implementation of step S2102 in Figure 2A, step S3102 in Figure 3A, step S3202 in Figure 3B, and other related parts in the embodiments involved in Figures 2A, 3A, and 3B, which will not be repeated here.

[0329] Step S3303: Send the DMRS on the PUSCH based on OCC multi-user multiplexing.

[0330] The optional implementation of step S3303 can refer to the optional implementation of step S2105 in Figure 2A, step S3105 in Figure 3A, step S3204 in Figure 3B, and other related parts in the embodiments involved in Figures 2A, 3A, and 3B, which will not be repeated here.

[0331] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3303. For example, step 3302 may be implemented as an independent embodiment, step 3303 may be implemented as an independent embodiment, steps 3301+3302 may be implemented as an independent embodiment, steps 3302+3303 may be implemented as an independent embodiment, steps 3301+3302+3303 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

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

[0333] Step S4101, sending the first information.

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

[0335] Optionally, the first information is used by the terminal 102 to determine the DMRS of the terminal. Optional implementations thereof can be found in the optional implementations of step S2102 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0336] Step S4102: Receive DMRS sent on the PUSCH based on OCC multi-user multiplexing.

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

[0338] Optionally, the PUSCH includes a DMRS and data symbols. The DMRS is mapped to a corresponding time-frequency domain resource position after the terminal 102 covers the value in the OCC sequence. For optional implementations, see the optional implementations of steps S2103 and S2104 in FIG. 2A , and other related parts of the embodiment involved in FIG. 2A , which will not be repeated here.

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

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

[0341] Step S5101: The network device 101 sends first information to the terminal 102.

[0342] Step S5102: Terminal 102 determines the DMRS of terminal 102 based on the first information.

[0343] In step S5103, the terminal 102 sends the DMRS on the PUSCH based on OCC multi-user multiplexing.

[0344] Optionally, the DMRSs corresponding to the terminal 102 and other terminals in the same OCC multiplexing user group are orthogonal, and the terminals included in the same user group use the same time-frequency domain resources.

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

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

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

[0348] The following is an exemplary introduction to the above methods in the above embodiments.

[0349] In some embodiments, the DMRS orthogonality may include at least one of the following:

[0350] Method 1: Orthogonalization of DMRS ports (introducing a new orthogonal DMRS port table; or, whether DFT-S-OFDM can support DMRS configuration type 2).

[0351] Method 2: DMRS uses different cyclic shifts to maintain orthogonality.

[0352] Optionally, this approach can be well applied to a situation where the number of multiplexed users is relatively small, for example, the number of multiplexed users is less than or equal to 4.

[0353] Optionally, in this manner, there are certain requirements for frequency domain resource allocation, for example, the terminal expects the number of RBs to be allocated to be greater than 1, or greater than 6, etc.

[0354] Optionally, the first and second methods may also be combined. In this case, the terminal does not expect different terminals to be allocated different PUSCH frequency domain resources.

[0355] Method 3: The frequency domain positions of RS symbols of different UEs and the subcarrier positions of data symbols after DFT of different UEs are aligned. That is, the DMRSs of different UEs are orthogonalized in a frequency division multiplexing (FDM) manner.

[0356] In some embodiments, scheduling may be performed based on non-fallback DCI or fallback DCI.

[0357] In some embodiments, for non-fallback DCI, such as the design of DCI format 0-1 / 2 / 3, antenna port indication is reused. However, for DFT-S-OFDM, in order to support multiplexing of more than 8 UEs, the number of ports of DMRS configuration type 1 should also be enhanced.

[0358] Optionally, a DMRS port configuration table with an increased number of ports may be designed for DFT-S-OFDM (different from the above-mentioned orthogonal DMRS port table, this table is a table indicated by DCI configuration).

[0359] Correspondingly, as the number of ports increases, the number of DCI indication bits also increases.

[0360] Optionally, one of the activation conditions of the above-mentioned newly added table is: determining whether to use the new table or reuse the existing table based on the length of the OCC sequence or the total number of multiplexed users (for example, if the OCC length or the number of multiplexed users is <= 8, reuse the existing table; otherwise use the new table); the OCC length or the total number of multiplexed users can be configured or indicated by the gNB.

[0361] Optionally, the OCC sequence index and antenna port index values ​​can be bound. For example, the indicated antenna port index (i) directly corresponds to the i-th OCC sequence index for the data symbol undergoing OCC. Alternatively, a new column is added to the antenna port table to determine the OCC sequence index of the terminal.

[0362] In some embodiments, for fallback DCI, determine whether OCC multiplexing is supported. If OCC is supported, how to design the DMRS orthogonal port or orthogonal initial cyclic shift indication:

[0363] Method 1: Use a method similar to non-fallback DCI to directly indicate the port table index, specifically through RRC or MAC CE signaling.

[0364] Method 2: directly configure at least one of the following parameters through RRC or MAC CE signaling: UE-specific OCC port; DMRS length; nscid (the DMRS is a DMRS generated based on Low-PAPR sequence type 2), etc.

[0365] Method 3: The OCC sequence index indicates the DMRS port table index or DMRS port used by the terminal, or indicates the initial cyclic shift of the DMRS sequence, or indicates the NSCI. Corresponding signaling design: The OCC sequence index can be indicated by existing bits in the RRC / MAC CE / DCI.

[0366] Furthermore, the above-mentioned DMRS orthogonal indication method can also be reused for non-fallback DCI. The original indication bit in the non-fallback DCI can be directly removed or indicated to a reserved bit; alternatively, a two-level indication method can be adopted (for example, the indication usage priority in the DCI is higher than the usage priority of the MAC CE / RRC). Alternatively, for non-fallback DCI, the terminal can indirectly determine the OCC sequence index through the indication of the antenna port, for example, there is a one-to-one mapping relationship between different DMRS ports and the OCC sequence index.

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

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

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

[0370] FIG6A is a schematic diagram of the structure of the network device proposed in an embodiment of the present disclosure. As shown in FIG6A , the terminal 6100 may include: at least one of a transceiver module 6101 and a processing module 6102. In some embodiments, the transceiver module is used to receive first information sent by the network device; the processing module is used to determine the demodulation reference signal DMRS of the terminal based on the first information; the transceiver module is also used to send the DMRS to the network device on the physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing; the DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

[0371] 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 2101 and step 2105, but not limited to these) executed by the terminal in any of the above methods, which will not be repeated here.

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

[0373] FIG6B is a schematic diagram of the structure of another network device proposed in an embodiment of the present disclosure. As shown in FIG6B , the network device 6200 may include: at least one of a transceiver module 6201 and a processing module 6202. In some embodiments, the transceiver module is used to send first information to a terminal, and the first information is used to determine a demodulation reference signal (DMRS) of the terminal; the transceiver module is also used to receive the DMRS sent by the terminal on a physical uplink shared channel (PUSCH) based on orthogonal cover code (OCC) multi-user multiplexing; wherein the DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0397] 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: receiving first information sent by a network device; Determining a demodulation reference signal (DMRS) of the terminal based on the first information; Sending the DMRS to the network device on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing; The DMRS of the terminal is orthogonal to the DMRSs corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCHs corresponding to the terminals in the same user group are the same.

2. The method according to claim 1, characterized in that The DMRS is generated based on at least one of the following sequences: Type 1 low peak-to-average power ratio low-PAPR sequence; Type 2 low-PAPR sequence.

3. The method according to claim 2, characterized in that The first information is used to indicate a first index in a preset first table, and the DMRS is determined based on a DMRS port corresponding to the first index.

4. The method according to claim 3, characterized in that The method further comprises: determining second information, where the second information is used to indicate a length of the OCC sequence, or the second information is used to indicate a number of users multiplexed by the OCC; Based on the second information, the preset first table is determined.

5. The method according to claim 2, characterized in that The first information is used to indicate a cyclic shift of the DMRS, or the first information is used to indicate a first parameter, and the first parameter is used to generate the DMRS.

6. The method according to claim 2, characterized in that The OCC multiplexing is pre-DFT OCC multiplexing before discrete Fourier transform, and the method further includes: Determine a frequency domain position corresponding to the DMRS of the terminal based on at least one of the following information: The number of users multiplexed by the OCC; The length of the OCC sequence; The index of the OCC sequence.

7. The method according to claim 2, characterized in that The DMRS is generated based on a type 1 low peak-to-average power ratio low-PAPR sequence, and the DMRS is determined based on a DMRS port and a cyclic shift sequence.

8. The method according to claim 2, characterized in that The first information is used to indicate a first parameter and a DMRS port.

9. The method according to claim 8, characterized in that The first information is a first index in the preset first table, and the DMRS is determined based on a DMRS port corresponding to the first index and the first parameter.

10. The method according to any one of claims 2 to 9, characterized in that: The downlink control information DCI for scheduling the PUSCH includes at least one of the following: Fallback DCI; Non-fallback DCI.

11. The method according to claim 10, characterized in that The first information is used to indicate an index of the OCC sequence, and the index of the OCC sequence is used to determine at least one of the following information: The DMRS port corresponding to the terminal; The number of time domain symbols of the DMRS; a cyclic shift of the DMRS; A first parameter, where the first parameter is used to generate the DMRS.

12. The method according to any one of claims 1 to 11, characterized in that The first information is at least one of the following: Non-fallback downlink control information DCI; Fallback downlink control information DCI; Radio Resource Control (RRC); Media Access Control Element MAC CE.

13. The method according to any one of claims 1 to 12, characterized in that The method further comprises: Determine, based on the DMRS port and a preset second table, a frequency domain resource position corresponding to the DMRS, and / or determine an index of an OCC sequence corresponding to the DMRS; Based on the index of the OCC sequence, the DMRS covers the value in the OCC sequence and is mapped to the corresponding frequency domain resource position.

14. A method for sending information, characterized in that: The method is performed by a network device, and includes: Sending first information to a terminal, where the first information is used to determine a demodulation reference signal (DMRS) of the terminal; Receiving the DMRS sent by the terminal on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing; The DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

15. The method according to claim 14, characterized in that The DMRS is generated based on at least one of the following sequences: Type 1 low peak-to-average power ratio low-PAPR sequence; Type 2 low-PAPR sequence.

16. The method according to claim 15, characterized in that The first information is used to indicate a first index in a preset first table, and the DMRS is determined based on a DMRS port corresponding to the first index.

17. The method according to claim 16, characterized in that The method further comprises: determining second information, where the second information is used to indicate a length of the OCC sequence, or the second information is used to indicate a number of users multiplexed by the OCC; Based on the second information, the preset first table is determined.

18. The method according to claim 15, characterized in that The first information is used to indicate a cyclic shift of the DMRS, or the first information is used to indicate a first parameter, and the first parameter is used to generate the DMRS.

19. The method according to claim 15, characterized in that The OCC multiplexing is pre-DFT OCC multiplexing before discrete Fourier transform; the frequency domain position corresponding to the DMRS of the terminal is determined based on at least one of the following information: The number of users multiplexed by the OCC; The length of the OCC sequence; The index of the OCC sequence.

20. The method according to claim 15, wherein The DMRS is generated based on a type 1 low peak-to-average power ratio low-PAPR sequence, and the DMRS is determined based on a DMRS port and a cyclic shift sequence.

21. The method according to claim 15, wherein The first information is used to indicate a first parameter and a DMRS port.

22. The method according to claim 21, characterized in that The first information is a first index in the preset first table, and the DMRS is determined based on a DMRS port corresponding to the first index and the first parameter.

23. The method according to any one of claims 15 to 22, characterized in that The downlink control information DCI for scheduling the PUSCH includes at least one of the following: Fallback DCI; Non-fallback DCI.

24. The method according to claim 23, wherein The first information is used to indicate an index of the OCC sequence, and the index of the OCC sequence is used to determine at least one of the following information: The DMRS port corresponding to the terminal; The number of time domain symbols of the DMRS; a cyclic shift of the DMRS; A first parameter, where the first parameter is used to generate the DMRS.

25. The method according to any one of claims 14 to 24, characterized in that The first information is at least one of the following: Non-fallback downlink control information DCI; Fallback downlink control information DCI; Radio Resource Control (RRC); Media Access Control Element MAC CE.

26. A method for sending information, characterized in that: The method comprises: The network device sends first information to the terminal; Determining, by the terminal, a demodulation reference signal (DMRS) of the terminal based on the first information; The terminal sends the DMRS to the network device on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing; The DMRS of the terminal is orthogonal to the DMRSs corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCHs corresponding to the terminals in the same user group are the same.

27. A terminal, characterized in that: The terminal includes: a transceiver module, configured to receive first information sent by a network device; a processing module, configured to determine a demodulation reference signal (DMRS) of the terminal based on the first information; The transceiver module is further configured to send the DMRS to the network device on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing; The DMRS of the terminal is orthogonal to the DMRSs corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCHs corresponding to the terminals in the same user group are the same.

28. A network device, characterized in that: The network equipment includes: a transceiver module, configured to send first information to a terminal, where the first information is used to determine a demodulation reference signal (DMRS) of the terminal; The transceiver module is further configured to receive the DMRS sent by the terminal on a physical uplink shared channel PUSCH based on orthogonal cover code OCC multi-user multiplexing; The DMRS of the terminal is orthogonal to the DMRS corresponding to other terminals in the same OCC multiplexing user group, and the time-frequency domain resources of the PUSCH corresponding to the terminals in the same user group are the same.

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

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

31. A communication system, characterized in that: The invention comprises a terminal and a network device, wherein the terminal is configured to implement the information sending method according to any one of claims 1 to 13, and the network device is configured to implement the information sending method according to any one of claims 14 to 25.

32. 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 sending method according to any one of claims 1 to 13 or 14 to 25.

Images