Information processing method and apparatus

Abstract

Disclosed in the embodiments of the present disclosure are an information processing method and apparatus. The method comprises: determining first information, second information and third information; and on the basis of the first information, the second information and the third information, determining an orthogonal cover code (OCC) used by a terminal, wherein the first information is used for determining the length of the OCC, the second information is used for determining a sequence of the OCC, and the third information is used for determining a generation method of the OCC. Thus, a terminal can process and send uplink information by means of an OCC, which can effectively improve the resource utilization rate and the spectrum efficiency, and can realize system capacity expansion, such that under the constraints of limited time-frequency resources and the limited transmission power of the terminal, more users can be supported in uplink transmission, thereby improving the system communication efficiency.

Description

Information processing method and device Technical Field

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

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

[0003] Due to limited frequency resources available for NTN, satellite coverage typically covers a larger cell radius, allowing for more users within a cell than in terrestrial networks. Furthermore, the transmission distance between terminals and satellites is long, necessitating uplink capacity enhancement to allow for simultaneous uplink communication with more users.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide an information processing method and apparatus.

[0006] A first embodiment of the present disclosure provides an information processing method, which is executed by a terminal and includes:

[0007] determining first information, second information, and third information;

[0008] Determining an orthogonal cover code (OCC) used by the terminal based on the first information, the second information, and the third information;

[0009] The first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

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

[0011] Sending at least one of the first information, the second information, and the third information to the terminal;

[0012] The first information, the second information, and the third information are used by the terminal to determine an orthogonal cover code OCC used by the terminal;

[0013] The first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

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

[0015] a processing module, configured to determine first information, second information, and third information;

[0016] The processing module is further configured to determine an orthogonal cover code OCC used by the terminal based on the first information, the second information, and the third information;

[0017] The first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

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

[0019] a transceiver module, configured to send at least one of the first information, the second information, and the third information to the terminal;

[0020] The first information, the second information, and the third information are used by the terminal to determine an orthogonal cover code OCC used by the terminal;

[0021] The first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

[0022] The solution proposed in the embodiment of the present disclosure determines the first information, the second information and the third information; based on the first information, the second information and the third information, determines the orthogonal cover code OCC used by the terminal; wherein the first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC; enables the terminal to process and send uplink information in an OCC manner, effectively improves resource utilization and spectrum efficiency, and realizes system expansion, so that under the premise of limited time-frequency resources and limited terminal transmission power, it can support more users for uplink transmission, thereby improving system communication efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0026] FIG2B is a schematic diagram of an indication information field design provided by an embodiment of the present disclosure;

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

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

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

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

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

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

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

[0034] The embodiments of the present disclosure provide an information processing method and apparatus.

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

[0036] Determine first information, second information and third information; based on the first information, the second information and the third information, determine the orthogonal cover code OCC used by the terminal; wherein the first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

[0037] In the above embodiment, the terminal is able to process and send uplink information in an OCC manner, which can effectively improve resource utilization and spectrum efficiency, and achieve system expansion. Therefore, under the premise of limited time-frequency resources and limited terminal transmission power, it can support more users for uplink transmission and improve system communication efficiency.

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

[0039] Determine the first information based on the provisions of the agreement; or

[0040] Receive the first information sent by the network device.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is included in at least one of the following information sent by the network device:

[0042] System information; Radio Resource Control (RRC) messages; Common Downlink Control Information (DCI); Scheduling DCI; Media Access Control Element (MAC CE).

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is included in the scheduling DCI, and the first information is included in at least one of the following information fields:

[0044] Frequency domain resource allocation FDRA information field; time domain resource allocation TDRA information field; modulation and coding strategy MCS information field; frequency hopping FH flag information field; newly added information field; antenna port field.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is included in a public DCI; the first information corresponds to the serving cell where the terminal is located; or,

[0046] The first information corresponds to the terminal group to which the terminal belongs, wherein the time-frequency domain resources used by the multiple terminals included in the terminal group are the same.

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

[0048] Determine the second information based on the provisions of the agreement; or

[0049] Receive the second information sent by the network device.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the second information is included in at least one of the following information sent by the network device:

[0051] RRC message; common DCI; scheduling DCI; MAC CE.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the second information is determined based on a provision of a protocol, and the second information is used by the terminal to determine a sequence of the OCC based on an identifier of the terminal.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the second information is included in a public DCI; the second information is used to indicate an index of the sequence of the OCC of the terminal, and the second information is at least one bit; or,

[0054] The second information is used to indicate whether the terminal adopts the OCC sequence indexed by the second information. The second information is one bit.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the second information is included in the scheduling DCI, and the second information is included in at least one of the following information fields:

[0056] Frequency domain resource allocation FDRA information field; time domain resource allocation TDRA information field; modulation and coding strategy MCS information field; frequency hopping FH flag information field; newly added information field; antenna port field.

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

[0058] Determine the third information based on a method predefined in the protocol; or

[0059] Receive the third information sent by the network device.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the third information is included in at least one of the following information sent by the network device:

[0061] RRC message; common DCI; scheduling DCI; MAC CE.

[0062] In combination with some embodiments of the first aspect, in some embodiments, the above-mentioned third information is sent by the above-mentioned network device, and the above-mentioned third information is used to indicate one of at least one candidate generation method, and the above-mentioned at least one candidate generation method is specified by the protocol.

[0063] In combination with some embodiments of the first aspect, in some embodiments, the number of OCCs generated based on the above generation method is greater than or equal to the length of the above OCC.

[0064] In combination with some embodiments of the first aspect, in some embodiments, among the multiple OCCs generated based on the above generation method, any two OCCs are orthogonal.

[0065] In combination with some embodiments of the first aspect, in some embodiments, at least two of the above-mentioned first information, the above-mentioned second information, and the above-mentioned third information are included in the same public DCI, or included in the same public MAC CE.

[0066] In combination with some embodiments of the first aspect, in some embodiments, the above-mentioned public DCI corresponds to the terminal group to which the above-mentioned terminal belongs, wherein the time-frequency domain resources used by the multiple terminals included in the above-mentioned terminal group are the same.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the OCC determined based on the common DCI or the common MAC CE satisfies at least one of the following:

[0068] The lengths of the OCCs corresponding to the above-mentioned terminals using the same time-frequency domain resources are the same; the generation methods of the OCCs corresponding to the above-mentioned terminals using the same time-frequency domain resources are the same; the sequences of the OCCs corresponding to the above-mentioned terminals using the same time-frequency domain resources are different; the sequences of the OCCs corresponding to the above-mentioned terminals using different time-frequency domain resources are the same or different.

[0069] In combination with some embodiments of the first aspect, in some embodiments, the OCC is used for at least one physical uplink control channel PUCCH and / or at least one physical uplink shared channel PUSCH corresponding to the terminal.

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

[0071] Receive fourth information sent by the network device, where the fourth information is used to indicate whether the terminal enables the OCC mechanism; the fourth information is included in at least one of the following information:

[0072] System information; RRC message; DCI.

[0073] In combination with some embodiments of the first aspect, in some embodiments, at least one of the above-mentioned first information, the above-mentioned second information and the above-mentioned third information is further used to indicate whether the above-mentioned terminal enables the OCC mechanism.

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

[0075] Determine to enable the OCC mechanism and parse the information field in the scheduling DCI based on the new definition; or,

[0076] Determine that the OCC mechanism is not enabled, and parse the information field in the scheduling DCI based on the traditional definition; wherein the information field in the scheduling DCI includes at least one of the following:

[0077] Frequency domain resource allocation FDRA information field; time domain resource allocation TDRA information field; modulation and coding strategy MCS information field; frequency hopping FH flag information field; antenna port field.

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

[0079] Send fifth information to the network device, where the fifth information is used to indicate that the terminal has the capability of supporting code division multiplexing.

[0080] In a second aspect, an embodiment of the present disclosure provides an information processing method, the method comprising:

[0081] Sending at least one of the first information, the second information, and the third information to the terminal; the first information, the second information, and the third information are used by the terminal to determine the orthogonal cover code OCC used by the terminal; wherein the first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

[0082] In the above embodiment, the terminal is able to process and send uplink information in an OCC manner, which can effectively improve resource utilization and spectrum efficiency, and achieve system expansion. Therefore, under the premise of limited time-frequency resources and limited terminal transmission power, it can support more users for uplink transmission and improve system communication efficiency.

[0083] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is included in at least one of the following information sent by the network device:

[0084] System information; Radio Resource Control (RRC) messages; Common Downlink Control Information (DCI); Scheduling DCI; Media Access Control Element (MAC CE).

[0085] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is included in the scheduling DCI, and the first information is included in at least one of the following information fields:

[0086] Frequency domain resource allocation FDRA information field; time domain resource allocation TDRA information field; modulation and coding strategy MCS information field; frequency hopping FH flag information field; newly added information field; antenna port field.

[0087] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is included in a public DCI; the first information corresponds to the serving cell where the terminal is located; or,

[0088] The first information corresponds to the terminal group to which the terminal belongs, wherein the time-frequency domain resources used by the multiple terminals included in the terminal group are the same.

[0089] In conjunction with some embodiments of the second aspect, in some embodiments, the second information is included in at least one of the following information sent by the network device:

[0090] RRC message; common DCI; scheduling DCI; MAC CE.

[0091] In conjunction with some embodiments of the second aspect, in some embodiments, the second information is included in a public DCI; the second information is used to indicate an index of the sequence of the OCC of the terminal, and the second information is at least one bit; or,

[0092] The second information is used to indicate whether the terminal adopts the OCC sequence indexed by the second information. The second information is one bit.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, the second information is included in the scheduling DCI, and the second information is included in at least one of the following information fields:

[0094] Frequency domain resource allocation FDRA information field; time domain resource allocation TDRA information field; modulation and coding strategy MCS information field; frequency hopping FH flag information field; newly added information field; antenna port field.

[0095] In conjunction with some embodiments of the second aspect, in some embodiments, the third information is included in at least one of the following information sent by the network device:

[0096] RRC message; common DCI; scheduling DCI; MAC CE.

[0097] In combination with some embodiments of the second aspect, in some embodiments, the third information is used to indicate one of at least one candidate generation method, and the at least one candidate generation method is specified by the protocol.

[0098] In combination with some embodiments of the second aspect, in some embodiments, the number of OCCs generated by the terminal based on the generation method is greater than or equal to the length of the OCC.

[0099] In combination with some embodiments of the second aspect, in some embodiments, among the multiple OCCs generated by the terminal based on the generation method, any two OCCs are orthogonal.

[0100] In combination with some embodiments of the second aspect, in some embodiments, at least two of the above-mentioned first information, the above-mentioned second information, and the above-mentioned third information are included in the same public DCI, or included in the same public MAC CE.

[0101] In combination with some embodiments of the second aspect, in some embodiments, the above-mentioned public DCI corresponds to the terminal group to which the above-mentioned terminal is located, wherein the time-frequency domain resources used by the multiple terminals included in the above-mentioned terminal group are the same.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the OCC determined based on the common DCI or the common MAC CE satisfies at least one of the following:

[0103] The lengths of the OCCs corresponding to the above-mentioned terminals using the same time-frequency domain resources are the same; the generation methods of the OCCs corresponding to the above-mentioned terminals using the same time-frequency domain resources are the same; the sequences of the OCCs corresponding to the above-mentioned terminals using the same time-frequency domain resources are different; the sequences of the OCCs corresponding to the above-mentioned terminals using different time-frequency domain resources are the same or different.

[0104] In combination with some embodiments of the second aspect, in some embodiments, the above-mentioned OCC is used for at least one physical uplink control channel PUCCH and / or at least one physical uplink shared channel PUSCH corresponding to the above-mentioned terminal.

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

[0106] Sending fourth information to the terminal, where the fourth information is used to indicate whether the terminal enables the OCC mechanism; the fourth information is included in at least one of the following information:

[0107] System information; RRC message; DCI.

[0108] In combination with some embodiments of the second aspect, in some embodiments, at least one of the second information and the third information is further used to indicate whether the terminal enables the OCC mechanism.

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

[0110] Receive fifth information sent by the terminal, where the fifth information is used to indicate that the terminal has a capability of supporting code division multiplexing.

[0111] In a third aspect, an embodiment of the present disclosure provides an information processing method, which includes:

[0112] The terminal determines the first information, the second information and the third information; the terminal determines the orthogonal cover code OCC used by the terminal based on the first information, the second information and the third information; wherein the first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

[0113] In the above embodiment, the terminal is able to process and send uplink information in an OCC manner, which can effectively improve resource utilization and spectrum efficiency, and achieve system expansion. Therefore, under the premise of limited time-frequency resources and limited terminal transmission power, it can support more users for uplink transmission and improve system communication efficiency.

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

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

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

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

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

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

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

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

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

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

[0124] In some embodiments, the terms information processing method and communication method are interchangeable, information processing device and communication device are interchangeable, and information processing system and communication system are interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0140] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal", Narrow Band-Internet of Things (NB-IoT) device, "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.

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

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

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

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

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

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

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

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

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

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

[0151] In some embodiments, the terminal 102 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a Narrow Band-Internet of Things (NB-IoT) device, a satellite communication device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and at least one of a reduced capability (RedCap) terminal, but is not limited thereto.

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

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

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

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

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

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

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

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

[0160] Therefore, considering user multiplexing based on orthogonal cover codes (OCC), the terminal may perform symbol or resource spreading.

[0161] In summary, for the transmission of the Physical Uplink Shared Channel (PUSCH) using OCC multi-user multiplexing, it is necessary to consider how to design the terminal to achieve system expansion, etc.

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

[0163] FIG2A is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to an information processing method, which includes:

[0164] Step S2101: Terminal 102 sends the fifth information.

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

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

[0167] In some embodiments, the fifth information is used to indicate that the terminal 102 has the capability of supporting code division multiplexing.

[0168] In some embodiments, the name of the fifth information is not limited, and it can be, for example, "terminal capability", "whether code division multiplexing is supported", "whether OCC mechanism is supported", etc.

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

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

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

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

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

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

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

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

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

[0178] 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 somewhat mitigate transmission uncertainty. Non-fallback DCI, on the other hand, supports more information fields and allows for more flexible DCI configuration based on system characteristics. Compact DCI is a compact DCI format, potentially smaller than DCI formats 0-1 and 1-1, used to schedule data transmission for Ultra-Reliable Low-Latency Communications (URLLC).

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

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

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

[0182] In some embodiments, the fifth information is further used to indicate one or more OCC generation formulas supported by the terminal 102 .

[0183] Optionally, the protocol may specify multiple different OCC generation formulas. Terminal 102 may report one or more supported OCC generation formulas based on UE capabilities, RRC message reporting, or UE assistance information reporting. Network device 102 may configure or indicate one of the corresponding OCC generation formulas based on the terminal capabilities.

[0184] In some embodiments, the terminal 101 that sends the fifth information is in a connected state or an inactive state.

[0185] Step S2102: The network device 101 sends fourth information.

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

[0187] In some embodiments, the fourth information is used to indicate whether the terminal 102 enables the OCC mechanism.

[0188] In some embodiments, the fourth information is used to instruct the terminal 102 to enable the OCC mechanism, or to instruct the terminal 102 to disable the OCC mechanism.

[0189] In some embodiments, the fourth information is included in at least one of the following information: system information (SI); RRC message; DCI.

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

[0191] In some embodiments, the above-mentioned DCI may be a common DCI or a scheduling DCI; wherein the scheduling DCI includes: fallback DCI, non-fallback DCI, and compact DCI.

[0192] In some embodiments, the name of the fourth information is not limited, and may be, for example, "OCC mechanism enable", "OCC mechanism disable", etc.

[0193] In some embodiments, the network device 101 may not send the fourth information, and may not instruct the terminal 102 to enable or disable the OCC mechanism through the fourth information.

[0194] In some embodiments, the network device 101 does not send the fourth information, and the OCC mechanism is disabled by default. That is, if the terminal 102 does not receive the fourth information, it is considered that the OCC mechanism is disabled.

[0195] In some embodiments, after determining that the terminal 102 has the capability to support code division multiplexing, the network device 101 instructs the terminal 102 to enable the OCC mechanism.

[0196] Step S2103: Terminal 102 determines the first information.

[0197] In some embodiments, the first information is used by the terminal 102 to determine the length of the OCC (also referred to as the OCC code length).

[0198] In some embodiments, the name of the first information is not limited, and may be, for example, "code length indication", "code length configuration", "length indication", "length configuration", "OCC length indication", etc.

[0199] In some embodiments, the first information may be a fixed code length predefined by a protocol.

[0200] In some embodiments, the network device 101 sends the first information.

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

[0202] In some embodiments, the first information may indicate the length of the OCC using a bitmap or codepoint. Alternatively, the protocol may have a fixed set of candidate OCC lengths, and the first information may indicate an index in the set, thereby indicating the length of the OCC. For example, if the candidate OCC length set is {2, 4, 8}, the first information may be an index value of the set, such as "00", indicating that the OCC length is 2.

[0203] In some embodiments, the first information may be included in at least one of the following information: system information SI; RRC message; common DCI; scheduling DCI; medium access control (MAC) control element (CE).

[0204] Optionally, the system information SI may include: system information block 1 (System Information Block 1, SIB1), other system information (other system information, OSI), etc.

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

[0206] Optionally, the scheduling DCI may include: fallback DCI, non-fallback DCI, and compact DCI.

[0207] In some embodiments, the network device 101 may configure or indicate the OCC length through system information or RRC messages.

[0208] Optionally, a set of OCC lengths may be predefined in the protocol, and the first information (included in the SI or RRC message) is used to indicate an index in the set.

[0209] Optionally, a set of OCC lengths may be configured through system information or RRC signaling, and the first information (included in the SI or RRC message) is used to indicate an index in the set.

[0210] In some embodiments, the network device 101 may configure and indicate the OCC length by combining RRC messages and DCI.

[0211] Optionally, a set of OCC lengths may be configured through RCC signaling, and the first information (included in the DCI) is used to indicate an index in the set.

[0212] In some embodiments, the network device 101 may configure and indicate the OCC length by combining system information and DCI.

[0213] Optionally, a set of OCC lengths may be configured through system information, and the first information (included in the DCI) is used to indicate an index in the set.

[0214] In some embodiments, a set of OCC lengths may be predefined in the protocol, and the first information (included in the DCI) is used to indicate an index in the set.

[0215] In some embodiments, the first information may directly indicate the length of the OCC by means of a codepoint.

[0216] In some embodiments, the first information may be included in at least one of the following information fields of the scheduling DCI:

[0217] Frequency Domain Resource Assignment (FDRA) information field;

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

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

[0220] Frequency hopping (FH) flag information field;

[0221] Added new information fields;

[0222] Antenna port field.

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

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

[0225] In some embodiments, only the fallback DCI may reuse the existing information field to indicate the OCC length, or all three types of DCI may reuse the existing information field to indicate the OCC length, or the fallback DCI and non-fallback DCI / compact DCI may reuse the existing information field to indicate the OCC length.

[0226] Optionally, the first information is included in the FDRA information field. For example, some bits in the FDRA information field may be used to indicate the length of the OCC, or the length of the OCC may be jointly encoded with the frequency domain resource allocation.

[0227] Optionally, the first information is included in the TDRA information field, for example, a field indicating the OCC length may be added to the TDRA list.

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

[0229] In some embodiments, when the information field of the multiplexed antenna port is used to indicate the length of the OCC, the following example method may be used for indication:

[0230] For example, there is a mapping relationship between the length of the OCC and the demodulation reference signal (DMRS) port / DMRS sequence indicated by the antenna port. The terminal 102 can determine the corresponding OCC length based on the DMRS port or DMRS sequence indicated by the antenna port.

[0231] In some embodiments, the first information is further used to indicate whether the terminal 102 enables the OCC mechanism (that is, to indicate whether the terminal 102 enables the OCC mechanism, or to indicate whether the terminal 102 disables the OCC mechanism).

[0232] In some embodiments, if the network device 101 indicates the OCC length by reusing an existing information field, the terminal 102, upon determining that the OCC mechanism is enabled, parses the information field based on the new definition to determine the first information included in the information field, and further determines the length of the OCC. If the network device 101 indicates the OCC length by reusing an existing information field, the first information cannot be used to instruct the terminal 102 to enable or disable the OCC mechanism.

[0233] In some embodiments, when the network device 101 indicates the OCC length by reusing an existing information field, the terminal 102 parses the information field based on a legacy definition when determining that the OCC mechanism is not enabled.

[0234] Optionally, the network device 101 may enable / disable the OCC mechanism by explicitly configuring RRC parameters, and the terminal 102 determines whether to enable / disable the OCC mechanism based on the RRC parameters.

[0235] In some embodiments, when the first information is included in the public DCI, all terminals in the cell may use the same OCC code length, that is, the first information may correspond to the serving cell where the terminal 102 is located.

[0236] Optionally, the public DCI may be a cell-specific public DCI.

[0237] In some embodiments, when the first information is included in the public DCI, different terminal groups (UE groups) may use different OCC code lengths. The same UE group may use the same OCC sequence generation method and OCC code length, while different UE groups may use the same or different public DCI. In other words, the first information may correspond to the terminal group to which the terminal 102 belongs. Multiple terminals in a terminal group may use the same time-frequency domain resources to transmit uplink information.

[0238] Optionally, if the same public DCI is used, the corresponding bit positions to be read need to be configured to the terminals of each UE group through RRC (a group of UEs share the same number of bit positions). If different public DCI signaling is used, it can be distinguished by at least one of the following methods: different public DCIs correspond to different search spaces (SS), or different public DCIs correspond to different control resource sets (CORESET) configurations; different terminal groups correspond to different radio network temporary identifiers (RNTIs), which are configured by the network device 101.

[0239] In some embodiments, the first information may also be included in semi-static signaling or dynamic signaling. A code length set is fixed in the protocol, and the network device 101 indicates an index of the set through the semi-static signaling or dynamic signaling.

[0240] In some embodiments, the network device 101 may configure a code length set, and for each uplink transmission, the network device 101 may further indicate an index of the set through dynamic signaling.

[0241] In step S2104, the terminal 102 determines the second information.

[0242] In some embodiments, the second information is used by the terminal 102 to determine the sequence of the OCC.

[0243] In some embodiments, the name of the second information is not limited, and may be, for example, "sequence indication", "sequence rule", "sequence number", "sequence index", "OCC sequence indication", etc.

[0244] In some embodiments, the second information may be an OCC sequence index determination rule predefined in a protocol.

[0245] Optionally, in a possible embodiment, the OCC sequence index determination rule is: determining the OCC sequence based on an identifier of the terminal.

[0246] Optionally, the terminal identifier includes: a Cell-Radio Network Temporary Identifier (C-RNTI); a Temporary Mobile Subscriber Identity (TMSI); and the like.

[0247] For example, the terminal 102 may determine the OCC sequence of the terminal 102 based on the terminal ID (such as C-RNTI / TMSI, etc.) and a rule predefined by the protocol.

[0248] In some embodiments, the network device 101 sends the second information.

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

[0250] In some embodiments, the second information may be included in at least one of the following information: system information SI; RRC message; common DCI; scheduling DCI; medium access control element MAC CE.

[0251] Optionally, the system information SI may include: SIB1, other system information OSI, etc.

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

[0253] Optionally, the scheduling DCI may include: fallback DCI, non-fallback DCI, and compact DCI.

[0254] In some embodiments, the second information may indicate the OCC sequence in the form of a bitmap or codepoint.

[0255] In some embodiments, the network device 101 may configure or indicate the OCC sequence through system information or RRC messages.

[0256] In some embodiments, the second information may directly indicate the OCC sequence by means of a code point.

[0257] In some embodiments, the second information may be included in at least one of the following information fields of the scheduling DCI:

[0258] Frequency domain resource allocation FDRA information field;

[0259] Time domain resource allocation TDRA information field;

[0260] Modulation and coding strategy MCS information field;

[0261] Frequency hopping FH flag information field;

[0262] Added new information fields;

[0263] Antenna port field.

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

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

[0266] In some embodiments, only the fallback DCI may reuse the existing information field to indicate the OCC sequence, or all three types of DCI may reuse the existing information field to indicate the OCC sequence, or the fallback DCI and non-fallback DCI / compact DCI may reuse the existing information field to indicate the OCC sequence.

[0267] Optionally, the second information is included in the FDRA information field. For example, some bits in the FDRA information field may be used to indicate the OCC sequence, or the OCC sequence and frequency domain resource allocation may be jointly encoded.

[0268] Optionally, the second information is included in the TDRA information field, for example, a field indicating the OCC sequence may be added to the TDRA list.

[0269] Optionally, the second information is included in an MCS information field. For example, the OCC sequence may be indicated by using m bits in the MCS information field, where m is a positive integer. The m bits may be the m bits starting from the most significant bit in the information field, or the m bits starting from the least significant bit in the information field, and so on.

[0270] In some embodiments, when the information field of the multiplexed antenna port is used to indicate the OCC sequence, the following example method may be used for indication:

[0271] For example, there is a one-to-one mapping relationship between the OCC sequence index and the demodulation reference signal (DMRS) port / DMRS sequence indicated by the antenna port. The terminal 102 can determine the corresponding OCC sequence index based on the DMRS port or DMRS sequence indicated by the antenna port.

[0272] In some embodiments, the second information is further used to indicate whether the terminal 102 enables the OCC mechanism (that is, to indicate whether the terminal 102 enables the OCC mechanism, or to indicate whether the terminal 102 disables the OCC mechanism).

[0273] In some embodiments, when the network device 101 indicates the OCC sequence by reusing an existing information field, the terminal 102, upon determining that the OCC mechanism is enabled, parses the information field based on the new definition to determine the second information included in the information field, and further determines the OCC sequence. When the network device 101 indicates the OCC sequence by reusing an existing information field, the second information cannot be used to instruct the terminal 102 to enable or disable the OCC mechanism.

[0274] In some embodiments, when the network device 101 indicates the OCC sequence by reusing an existing information field, the terminal 102 parses the information field based on a legacy definition when determining that the OCC mechanism is not enabled.

[0275] Optionally, the network device 101 may enable / disable the OCC mechanism by explicitly configuring RRC parameters, and the terminal 102 determines whether to enable / disable the OCC mechanism based on the RRC parameters.

[0276] In some embodiments, for the case where the first information is included in the public DCI, the RRC message may configure a bit position corresponding to the terminal 102 in the public DCI (which may be several bits (such as the mth to nth bits), used to indicate an index of an OCC sequence set), and the terminal 102 determines the OCC sequence index of the terminal 102 by parsing the bits of the above specific bit position in the DCI.

[0277] Optionally, when the corresponding bits are all "0" or all "1", it indicates that the OCC index indication is not performed and the terminal 102 does not perform OCC multiplexing. In this case, taking a 4-bit indication as an example, if all 0s are used for disabling, "0001" corresponds to the first sequence in the OCC sequence set (for example, sequence s0).

[0278] In some embodiments, for the case where the first information is included in the public DCI, it may also be that the RRC message configures a bit position corresponding to the terminal 102 in the public DCI (one bit for each terminal), and the terminal 102 determines the OCC sequence index of the terminal 102 by parsing the bits at the above specific bit position in the DCI.

[0279] Optionally, whether the terminal 102 enables the OCC mechanism and the OCC sequence corresponding to the terminal 102 may be indicated in a bitmap manner.

[0280] Optionally, the maximum number of generated OCC sequences may be the same as the bit length in the DCI, and there may be a one-to-one correspondence between the OCC sequence index and the bit position. If the corresponding bit in the DCI is 0, it indicates that the corresponding terminal does not use the corresponding sequence index. If the corresponding bit in the DCI is 1, it indicates that the corresponding OCC index is used.

[0281] As an example, as shown in Table 1 below, the first row represents the 12 bits in the public DCI, and the second row represents the sequence corresponding to each bit (where s0 represents the sequence with index 0, and so on). There is a one-to-one correspondence between the sequence index and the bit position. The terminal corresponding to the bit with a value of "0" does not use the corresponding sequence (s0, s1, s4, s7, s8, s9, s10, s11), and the terminal corresponding to the bit with a value of "1" uses the corresponding sequence (s2, s3, s5, s6). If the bit position corresponding to terminal 102 is the third bit, terminal 102 uses the OCC sequence s2 with an index of 2. If the bit position corresponding to terminal 102 is the fifth bit, terminal 102 does not use the OCC sequence s4 with an index of 4, and does not perform OCC multiplexing.

[0282] Table 1 Example of OCC sequence indication method

[0283] Optionally, for the terminal group, the maximum number of generated OCC sequences may be less than or equal to the bit length in the DCI. That is, the number of users in the terminal group may be less than or equal to the number of users monitoring the public DCI, and the number of bits with a value of "1" in the DCI may be equal to the number of generated OCC sequences (it should be noted that this needs to be ensured by the scheduling of the network device 101). Furthermore, the correspondence between the bits in the DCI and the OCC sequence index is shown in Table 2 below. The first row represents the 12 bits in the public DCI, and the second row represents the four OCC sequences (s0 represents a sequence with an index of 0).

[0284] Table 2 Example of OCC sequence indication method

[0285] In some embodiments, for the second information to be included in the public DCI, considering that the payload size of the DCI may be too long, the public DCI can also be grouped, for example, a group of users uses a specific public DCI, OCC code length and OCC sequence generation formula.

[0286] Optionally, the public DCI can be grouped in the following manner: different public DCIs correspond to different search spaces SS, or different public DCIs correspond to different control resource set CORESET configurations (the terminal 102 does not expect different terminal groups to use the same search space or CORESET); different terminal groups correspond to different radio network temporary identifiers (Radio Network Temporary Indentifier, RNTI), which is configured by the network device 101.

[0287] Optionally, for the method of including the second information in the public DCI, another point that needs to be considered is that the network device 101 needs to configure the total length of the DCI payload size to the terminal 102 through an RRC message.

[0288] In some embodiments, the second information may be included in a MAC CE, which may be a common MAC CE or a terminal-specific (UE-specific) MAC CE. The MAC CE may be a new MAC CE or a reused legacy MAC CE. For a common MAC CE, the specific indication method is similar to that of the common DCI described above, and may be indicated by one or more bit positions in the MAC CE, which will not be described in detail here.

[0289] In some embodiments, multiple terminals may share the same OCC sequence (the same OCC sequence index is configured for the multiple terminals through RRC messages), and further determine which terminal uses the OCC sequence for OCC multiplexing by scheduling the OCC enable / disable indicator bit in the DCI.

[0290] In step S2105 , the terminal 102 determines the third information.

[0291] In some embodiments, the third information is used by the terminal 102 to determine the method for generating the OCC.

[0292] In some embodiments, the name of the third information is not limited, and may be, for example, "generation method indication", "generation rule", "OCC generation method", etc.

[0293] In some embodiments, the third information may be an OCC sequence generation formula predefined by a protocol.

[0294] In some embodiments, the network device 101 sends third information.

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

[0296] In some embodiments, the third information may be included in at least one of the following information: system information SI; RRC message; common DCI; scheduling DCI; medium access control element MAC CE.

[0297] Optionally, the system information SI may include: SIB1, other system information OSI, etc.

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

[0299] Optionally, the scheduling DCI may include: fallback DCI, non-fallback DCI, and compact DCI.

[0300] In some embodiments, the third information may be in the form of a bitmap or codepoint to indicate the OCC generation method.

[0301] In some embodiments, the third information is used to indicate one of at least one candidate generation method, where the at least one candidate generation method is pre-specified by a protocol.

[0302] In some embodiments, the third information may be included in at least one of the following information fields of the scheduling DCI:

[0303] Frequency domain resource allocation FDRA information field;

[0304] Time domain resource allocation TDRA information field;

[0305] Modulation and coding strategy MCS information field;

[0306] Frequency hopping FH flag information field;

[0307] Added new information fields;

[0308] Antenna port field.

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

[0310] In some embodiments, the third information is further used to indicate whether the terminal 102 enables the OCC mechanism (that is, to indicate whether the terminal 102 enables the OCC mechanism, or to indicate whether the terminal 102 disables the OCC mechanism).

[0311] In some embodiments, when network device 101 indicates the OCC generation method by reusing an existing information field, terminal 102, upon determining that the OCC mechanism is enabled, parses the information field based on the new definition to determine the third information included in the information field, and further determines the OCC generation method. When network device 101 indicates the OCC generation method by reusing an existing information field, the first information cannot be used to instruct terminal 102 to enable or disable the OCC mechanism.

[0312] In some embodiments, when the network device 101 indicates the OCC generation method by reusing an existing information field, the terminal 102 parses the information field based on a legacy definition when determining that the OCC mechanism is not enabled.

[0313] In some embodiments, the number of OCCs generated based on the generation method indicated by the third information is greater than or equal to the length of the OCC.

[0314] In some embodiments, any two OCCs among the multiple OCCs generated based on the generation method indicated by the third information are orthogonal.

[0315] In some embodiments, the autocorrelation of each OCC generated based on the generation method indicated by the third information is very strong.

[0316] In some embodiments, the sum of the cross-correlations of the multiple OCCs generated based on the generation method indicated by the third information is small, or the sum of the cross-correlations of the squares of the multiple OCCs satisfies certain mathematical constraints; or the sum of the cross-correlations between the multiple OCCs satisfies certain mathematical constraints.

[0317] In step S2106, the terminal 102 determines the orthogonal cover code OCC to be used.

[0318] In some embodiments, the terminal 102 can determine the OCC to be used based on the first information, the second information, and the third information.

[0319] In some embodiments, the terminal 102 can generate an OCC specific to the terminal based on the first information, the second information, and the third information, and can use the OCC to encode uplink information before sending it.

[0320] In some embodiments, the generated OCC is used for at least one physical uplink control channel PUCCH and / or at least one physical uplink shared channel PUSCH of the terminal 102 .

[0321] In some embodiments, multiple PUCCHs of terminal 102 share the same first information, or share the same second information, or share the same third information; or share the same first information and second information, or share the same first information and third information, or share the same second information and third information; or the first information, the second information and the third information are all the same.

[0322] In some embodiments, multiple PUSCHs of terminal 102 share the same first information, or share the same second information, or share the same third information; or share the same first information and second information, or share the same first information and third information, or share the same second information and third information; or the first information, the second information and the third information are all the same.

[0323] In some embodiments, at least one of the first information, the second information, and the third information corresponding to the multiple PUCCHs of the terminal 102 is separately indicated or specified.

[0324] In some embodiments, at least one of the first information, the second information, and the third information corresponding to the multiple PUSCHs of the terminal 102 is separately indicated or specified.

[0325] Optionally, in some embodiments, for the above-mentioned first information, second information and third information, at least two of the three may be included in the same public DCI; or at least two of the three may be included in the same public MAC CE.

[0326] Optionally, the public DCI corresponds to the terminal group to which the terminal 102 belongs.

[0327] Optionally, for an OCC determined based on the public DCI or public MAC CE, at least one of the following conditions must be met:

[0328] The OCC lengths corresponding to terminals using the same time-frequency domain resources are the same;

[0329] The OCC generation method for terminals using the same time-frequency domain resources is the same;

[0330] The OCC sequences corresponding to terminals using the same time-frequency domain resources are different;

[0331] The OCC sequences corresponding to terminals using different time-frequency domain resources are the same or different.

[0332] As an example, the first information, the second information, and the third information are all included in the same public DCI. A possible public DCI design scheme is shown in FIG2B (assuming that the protocol presets four OCC generation formulas, the code length set is {2, 4, 6, 8}, and the set index indication method is used to indicate the OCC code length). It should be noted that FIG2B is only provided as an example. The order of the various fields in the DCI, etc., can be flexibly adjusted based on the implementation and are not limited here.

[0333] In this manner, the OCC code length set may be configured by the network device 101 or specified by the protocol. Based on the OCC code length set, the terminal 102 determines the number of bits corresponding to the first information in the DCI, and the network device 101 configures the starting position for parsing the DCI for each terminal. The number of generation formulas may be specified by the protocol. The number of bits occupied by the second information may be a fixed value preset by the protocol, with the same length for each terminal group; or it may be determined by the terminal 102 based on certain parameters, such as the terminal 102 determining the number of bits occupied by the second information based on the OCC code length, the OCC generation formula, and at least one of the preset rules / tables of the protocol; in addition, it may be configured by the network device 101, and different terminal groups may correspond to different bit lengths.

[0334] As another example, the first information and the second information may be included in the same public DCI. Similar to the above example, the public DCI does not include the third information, and the OCC code length set may be configured by the network device 101 or the protocol specification. The terminal 102 determines the number of bits corresponding to the first information in the DCI based on the OCC code length set, and the network device 101 configures the starting position for parsing the DCI for each terminal. The number of bits occupied by the second information may be a fixed value preset by the protocol, with the same length for each terminal group; or it may be determined by the terminal 102 based on certain parameters, such as the terminal 102 determines the number of bits occupied by the second information based on the OCC code length, the OCC generation formula, and at least one of the preset rules / tables of the protocol; in addition, it may be configured by the network device 101, and different terminal groups may correspond to different bit lengths.

[0335] As another example, the first information and the third information may be included in the same public DCI. Similar to the above example, the public DCI does not include the second information. The OCC code length set may be configured by network device 101 or specified by the protocol. Terminal 102 determines the number of bits corresponding to the first information in the DCI based on the OCC code length set. Network device 101 also configures the starting position for parsing the DCI for each terminal. The number of generation formulas may be specified by the protocol.

[0336] As another example, the second information and the third information may be included in the same public DCI. Similar to the above example, the public DCI does not include the first information. At the same time, the network device 101 configures the starting position for parsing the DCI for each terminal. The number of generation formulas may be specified by the protocol. The number of bits occupied by the second information may be a fixed value preset by the protocol, with the same length for each terminal group; or it may be determined by the terminal 102 based on certain parameters, such as the terminal 102 determining the number of bits occupied by the second information based on the OCC code length, the OCC generation formula, and at least one of the protocol preset rules / tables; in addition, it may be configured by the network device 101, and different terminal groups may correspond to different bit lengths.

[0337] In some embodiments, terminals in the same terminal group monitor the same public DCI.

[0338] In some embodiments, terminals in different terminal groups can monitor the same or different common DCIs (that is, OCC-related indication information of different terminal groups (for example, at least one of the first to fourth information) can be in the same DCI or in different DCIs).

[0339] Optionally, a method for performing common DCI grouping may include at least one of the following:

[0340] Different terminal groups correspond to different search spaces SS, or different terminal groups correspond to different control resource set CORESET configurations (the terminal 102 does not expect different terminal groups to use the same search space or CORESET);

[0341] Different terminal groups correspond to different radio network temporary identifiers RNTI, which are configured by the network device 101;

[0342] Different terminal groups correspond to different demodulation reference signal (DMRS) patterns, or correspond to different common search spaces (CSS), or correspond to different group common SSs.

[0343] In some embodiments, if different terminal groups correspond to different DCIs, the network device 101 does not need to configure each terminal to parse the starting bit position of the DCI.

[0344] In some embodiments, all terminals monitor the same DCI, which contains only one OCC code length, OCC formula, and OCC sequence index indication field, or n OCC code lengths, OCC formulas, and OCC sequence index indication fields, where n is less than the number of terminals, such as 2. Terminals multiplexed on the same time-frequency domain resources use the same code length, OCC code generation formula, and different code sequence indexes. Two terminals multiplexed on different time-frequency domain resources may share the same OCC code sequence.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0359] The communication method according to the embodiments of the present disclosure may include at least one of steps S2101 to S2106. For example, steps 2101+2102 may be implemented as an independent embodiment, steps 2103+2104+2105 may be implemented as an independent embodiment, steps 2103+2104+2105+2106 may be implemented as an independent embodiment, steps 2101+2102+2103+2104+2105 may be implemented as an independent embodiment, steps 2101+2102+2103+2104+2105+2106 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

[0360] In some embodiments, step S2101 and step S2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

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

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

[0364] Step S3101: Send the fifth information to the network device 101.

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

[0366] Step S3102: Receive the fourth information sent by the network device 101.

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

[0368] Step S3103: determine the first information.

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

[0370] Step S3104, determine the second information.

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

[0372] Step S3105, determine the third information.

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

[0374] Step S3106: determine the orthogonal cover code OCC.

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

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

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

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

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

[0380] Step S3201: Send the fifth information to the network device 101.

[0381] 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 embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0382] Step S3202, determine the first information.

[0383] The optional implementation of step S3202 can refer to step S2103 in Figure 2A, the optional implementation of step S3103 in Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

[0384] Step S3203, determine the second information.

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

[0386] Step S3204, determine the third information.

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

[0388] Step S3205: determine the orthogonal cover code OCC.

[0389] The optional implementation of step S3205 can refer to step S2106 in Figure 2A, the optional implementation of step S3106 in Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

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

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

[0392] In some embodiments, step S3202, step S3203, and step S3204 may be executed in an interchangeable order or simultaneously.

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

[0394] Step S3301, determine the first information.

[0395] The optional implementation of step S3301 can refer to the optional implementation of step S2103 in Figure 2A, step S3103 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.

[0396] Step S3302, determine the second information.

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

[0398] Step S3303, determine the third information.

[0399] The optional implementation of step S3303 can be found in 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.

[0400] Step S3304: determine the orthogonal cover code OCC.

[0401] The optional implementation of step S3304 can be found in the optional implementation of step S2106 in Figure 2A, step S3106 in Figure 3A, step S3205 in Figure 3B, and other related parts in the embodiments involved in Figures 2A, 3A, and 3B, which will not be repeated here.

[0402] The communication method according to the embodiments of the present disclosure may include at least one of steps S3301 to S3304. For example, steps 3301, 3302, and 3303 may be implemented as independent embodiments, steps 3301, 3302, 3303, and 3304 may be implemented as independent embodiments, and step 3304 may be implemented as an independent embodiment, etc., but the present disclosure is not limited thereto.

[0403] In some embodiments, step S3301, step S3302, and step S3303 may be executed in an interchanged order or simultaneously.

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

[0405] Step S4101, receiving the fifth information sent by terminal 102.

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

[0407] Step S4102: Send fourth information to terminal 102.

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

[0409] Step S4103: Send first information to terminal 102.

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

[0411] Step S4104: Send the second information to the terminal 102.

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

[0413] Step S4105: Send third information to terminal 102.

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

[0415] Optionally, the first information, the second information, and the third information are used by the terminal 102 to determine its specific orthogonal cover code OCC. For optional implementations, see the optional implementation of step S2106 in FIG2A and other related parts of the embodiment involved in FIG2A , which will not be described in detail here.

[0416] The communication method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4105. For example, steps 4101+4102 may be implemented as an independent embodiment, steps 4103+4104+4105 may be implemented as an independent embodiment, steps 4103+4104+4105 may be implemented as an independent embodiment, steps 4101+4102+4103+4104+4105 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto.

[0417] In some embodiments, step S4101 and step S4102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0418] In some embodiments, step S4102, step S4103, step S4104, and step S4105 may be executed in an interchanged order or simultaneously.

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

[0420] Step S4201: Send first information to terminal 102.

[0421] Optional implementations of step S4201 can be found in step S2103 of FIG. 2A , optional implementations of step S4103 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2A and FIG. 4A , which will not be described in detail here.

[0422] Step S4202: Send second information to terminal 102.

[0423] The optional implementation of step S4202 can refer to the optional implementation of step S2104 in Figure 2A, step S4104 in Figure 4A, and other related parts in the embodiments involved in Figures 2A and 4A, which will not be repeated here.

[0424] Step S4203: Send third information to terminal 102.

[0425] The optional implementation of step S4203 can refer to the optional implementation of step S2105 in Figure 2A, step S4105 in Figure 4A, and other related parts in the embodiments involved in Figures 2A and 4A, which will not be repeated here.

[0426] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4201 to S4203.

[0427] In some embodiments, step S4201, step S4202, and step S4203 may be executed in an interchangeable order or simultaneously.

[0428] FIG5 is a flow chart of an information processing method 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:

[0429] In step S5101, the terminal 102 determines first information, where the first information is used to determine the length of the OCC.

[0430] In step S5102, the terminal 102 determines second information, where the second information is used to determine a sequence of the OCC.

[0431] In step S5103, the terminal 102 determines third information, where the third information is used to determine a method for generating the OCC.

[0432] In step S5104, the terminal 102 determines the OCC of the terminal based on the first information, the second information and the third information.

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

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

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

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

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

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

[0439] Figure 6A is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure. As shown in Figure 6A, a terminal 6100 may include at least one of a transceiver module 6101 and a processing module 6102. In some embodiments, the processing module is configured to determine first information, second information, and third information; the processing module is further configured to determine an orthogonal cover code (OCC) to be used by the terminal based on the first information, the second information, and the third information; wherein the first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the method for generating the OCC.

[0440] Optionally, the above-mentioned transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, which will not be repeated here.

[0441] Optionally, the processing module is used to execute at least one of the other steps performed by the terminal in any of the above methods, which will not be described in detail here.

[0442] Figure 6B is a schematic diagram of the structure of another network device proposed in an embodiment of the present disclosure. As shown in Figure 6B, network device 6200 may include: at least one of a transceiver module 6201 and a processing module 6202. In some embodiments, the transceiver module is configured to send at least one of first information, second information, and third information to a terminal; the first information, second information, and third information are used by the terminal to determine the orthogonal cover code (OCC) used by the terminal; the first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

[0443] Optionally, the above-mentioned transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the network device in any of the above methods, which will not be repeated here.

[0444] 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 described in detail here.

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

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

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

[0448] As shown in FIG7A , a communication device 7100 includes one or more processors 7101. Processor 7101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit (CPU). The baseband processor may be used to process communication protocols and communication data, while the CPU 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 CU, etc.), execute programs, and process program data. The communication device 7100 is configured to perform any of the above methods.

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

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

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

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

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

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

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

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

[0457] 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, and the processor 7201 performs at least one of the other steps.

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

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

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

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

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

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

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

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

[0466] 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. An information processing method, characterized in that: The method is executed by a terminal, and includes: determining first information, second information, and third information; Determining an orthogonal cover code OCC used by the terminal based on the first information, the second information, and the third information; The first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

2. The method according to claim 1, characterized in that The method further comprises: Determine the first information based on the provisions of the protocol; or Receive the first information sent by the network device.

3. The method according to claim 2, characterized in that The first information is included in at least one of the following information sent by the network device: System information; Radio Resource Control RRC message; Common downlink control information DCI; Scheduling DCI; Media Access Control Element MAC CE.

4. The method according to claim 3, characterized in that The first information is included in the scheduling DCI, and the first information is included in at least one of the following information fields: Frequency domain resource allocation FDRA information field; Time domain resource allocation TDRA information field; Modulation and coding strategy MCS information field; Frequency hopping FH flag information field; Added new information fields; Antenna port field.

5. The method according to claim 3, characterized in that The first information is included in a public DCI; The first information corresponds to the serving cell where the terminal is located; or, The first information corresponds to a terminal group to which the terminal belongs, wherein the multiple terminals included in the terminal group use the same time-frequency domain resources.

6. The method according to claim 1, characterized in that The method further comprises: Determine the second information based on the provisions of the protocol; or Receive the second information sent by the network device.

7. The method according to claim 6, characterized in that The second information is included in at least one of the following information sent by the network device: RRC message; Public DCI; Scheduling DCI; MAC CE.

8. The method according to claim 6, characterized in that The second information is determined based on a provision of a protocol, and the second information is used by the terminal to determine the sequence of the OCC based on an identifier of the terminal.

9. The method according to claim 7, characterized in that The second information is included in the public DCI; The second information is used to indicate the index of the OCC sequence of the terminal, and the second information is at least one bit; or, The second information is used to indicate whether the terminal adopts the OCC sequence indexed by the second information, and the second information is one bit.

10. The method according to claim 7, characterized in that The second information is included in the scheduling DCI, and the second information is included in at least one of the following information fields: Frequency domain resource allocation FDRA information field; Time domain resource allocation TDRA information field; Modulation and coding strategy MCS information field; Frequency hopping FH flag information field; Added new information fields; Antenna port field.

11. The method according to claim 1, wherein The method further comprises: Determine the third information based on a method predefined in the protocol; or, Receive the third information sent by the network device.

12. The method according to claim 11, characterized in that The third information is included in at least one of the following information sent by the network device: RRC message; Public DCI; Scheduling DCI; MAC CE.

13. The method according to claim 12, characterized in that The third information is sent by the network device, and is used to indicate one of at least one candidate generation method, where the at least one candidate generation method is specified by a protocol.

14. The method according to claim 11, characterized in that The number of OCCs generated based on the generation method is greater than or equal to the length of the OCC.

15. The method according to claim 11, characterized in that Among the multiple OCCs generated based on the generation method, any two OCCs are orthogonal to each other.

16. The method according to any one of claims 1 to 15, characterized in that At least two of the first information, the second information, and the third information are included in the same common DCI, or included in the same common MAC CE.

17. The method according to claim 16, characterized in that The public DCI corresponds to the terminal group to which the terminal belongs, wherein the multiple terminals included in the terminal group use the same time-frequency domain resources.

18. The method according to claim 16, characterized in that The OCC determined based on the public DCI or the public MAC CE satisfies at least one of the following: The OCCs corresponding to the terminals using the same time-frequency domain resources have the same length; The OCC corresponding to the terminals using the same time-frequency domain resources is generated in the same manner; The OCC sequences corresponding to the terminals using the same time-frequency domain resources are different; The OCC sequences corresponding to the terminals using different time-frequency domain resources are the same or different.

19. The method according to any one of claims 1 to 18, characterized in that The OCC is used for at least one physical uplink control channel PUCCH and / or at least one physical uplink shared channel PUSCH corresponding to the terminal.

20. The method according to any one of claims 1 to 19, characterized in that The method further comprises: receiving fourth information sent by a network device, where the fourth information is used to indicate whether the terminal enables an OCC mechanism; The fourth information is included in at least one of the following information: System information; RRC message; DCI.

21. The method according to claim 20, characterized in that At least one of the first information, the second information and the third information is further used to indicate whether the terminal enables the OCC mechanism.

22. The method according to claim 21, characterized in that The method further comprises: Determine to enable the OCC mechanism and parse the information field in the scheduling DCI based on the new definition; or, Determine that the OCC mechanism is not enabled and parse the information field in the scheduling DCI based on the traditional definition; The information field in the scheduling DCI includes at least one of the following: Frequency domain resource allocation FDRA information field; Time domain resource allocation TDRA information field; Modulation and coding strategy MCS information field; Frequency hopping FH flag information field; Antenna port field.

23. The method according to any one of claims 20 to 22, characterized in that The method further comprises: Fifth information is sent to the network device, where the fifth information is used to indicate that the terminal has a capability of supporting code division multiplexing.

24. An information processing method, characterized in that: The method is performed by a network device, and includes: Sending at least one of the first information, the second information, and the third information to the terminal; The first information, the second information, and the third information are used by the terminal to determine an orthogonal cover code OCC used by the terminal; The first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

25. The method according to claim 24, characterized in that The first information is included in at least one of the following information sent by the network device: System information; Radio Resource Control RRC message; Common downlink control information DCI; Scheduling DCI; Media Access Control Element MAC CE.

26. The method according to claim 25, characterized in that The first information is included in the scheduling DCI, and the first information is included in at least one of the following information fields: Frequency domain resource allocation FDRA information field; Time domain resource allocation TDRA information field; Modulation and coding strategy MCS information field; Frequency hopping FH flag information field; Added new information fields; Antenna port field.

27. The method according to claim 25, characterized in that The first information is included in a public DCI; The first information corresponds to the serving cell where the terminal is located; or, The first information corresponds to a terminal group to which the terminal belongs, wherein the multiple terminals included in the terminal group use the same time-frequency domain resources.

28. The method according to claim 24, characterized in that The second information is included in at least one of the following information sent by the network device: RRC message; Public DCI; Scheduling DCI; MAC CE.

29. The method according to claim 28, characterized in that The second information is included in the public DCI; The second information is used to indicate the index of the OCC sequence of the terminal, and the second information is at least one bit; or, The second information is used to indicate whether the terminal adopts the OCC sequence indexed by the second information, and the second information is one bit.

30. The method according to claim 28, wherein The second information is included in the scheduling DCI, and the second information is included in at least one of the following information fields: Frequency domain resource allocation FDRA information field; Time domain resource allocation TDRA information field; Modulation and coding strategy MCS information field; Frequency hopping FH flag information field; Added new information fields; Antenna port field.

31. The method according to claim 24, wherein The third information is included in at least one of the following information sent by the network device: RRC message; Public DCI; Scheduling DCI; MAC CE.

32. The method according to claim 31, characterized in that The third information is used to indicate one of at least one candidate generation method, where the at least one candidate generation method is specified by the protocol.

33. The method according to claim 31, wherein The number of OCCs generated by the terminal based on the generation method is greater than or equal to the length of the OCC.

34. The method according to claim 31, wherein Among the multiple OCCs generated by the terminal based on the generation method, any two OCCs are orthogonal.

35. The method according to any one of claims 24 to 34, characterized in that At least two of the first information, the second information, and the third information are included in the same common DCI, or included in the same common MAC CE.

36. The method according to claim 35, characterized in that The public DCI corresponds to the terminal group to which the terminal belongs, wherein the multiple terminals included in the terminal group use the same time-frequency domain resources.

37. The method according to claim 35, characterized in that The OCC determined based on the public DCI or the public MAC CE satisfies at least one of the following: The OCCs corresponding to the terminals using the same time-frequency domain resources have the same length; The OCC corresponding to the terminals using the same time-frequency domain resources is generated in the same manner; The OCC sequences corresponding to the terminals using the same time-frequency domain resources are different; The OCC sequences corresponding to the terminals using different time-frequency domain resources are the same or different.

38. The method according to any one of claims 24 to 37, characterized in that The OCC is used for at least one physical uplink control channel PUCCH and / or at least one physical uplink shared channel PUSCH corresponding to the terminal.

39. The method according to any one of claims 24 to 38, wherein: The method further comprises: Sending fourth information to the terminal, where the fourth information is used to indicate whether the terminal enables an OCC mechanism; The fourth information is included in at least one of the following information: System information; RRC message; DCI.

40. The method according to claim 39, wherein At least one of the first information, the second information and the third information is further used to indicate whether the terminal enables the OCC mechanism.

41. The method according to claim 39 or 40, characterized in that The method further comprises: Fifth information sent by the terminal is received, where the fifth information is used to indicate that the terminal has a capability of supporting code division multiplexing.

42. A terminal, characterized in that: The terminal includes: a processing module, configured to determine first information, second information, and third information; The processing module is further configured to determine an orthogonal cover code OCC used by the terminal based on the first information, the second information, and the third information; The first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

43. A network device, characterized in that The network equipment includes: a transceiver module, configured to send at least one of the first information, the second information, and the third information to the terminal; The first information, the second information, and the third information are used by the terminal to determine an orthogonal cover code OCC used by the terminal; The first information is used to determine the length of the OCC, the second information is used to determine the sequence of the OCC, and the third information is used to determine the generation method of the OCC.

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

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

46. ​​A communication system, characterized in that The invention comprises a terminal and a network device, wherein the terminal is configured to implement the information processing method according to any one of claims 1 to 23, and the network device is configured to implement the information processing method according to any one of claims 24 to 41.

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

Images