Method and apparatus in a node for wireless communication

Abstract

A method and apparatus in a node for wireless communication are provided. The method comprises the following steps: receiving first information; wherein the first information is used for indicating a first orthogonal cover code (OCC) codeword of the first node; the first node belongs to a first OCC group, and nodes in the same OCC group use the same RV value.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and more specifically, to a method and apparatus in a node for wireless communication. Background Art

[0002] With the development and popularization of communication systems (such as the 5th generation (5G) system), the demand for enhancing the uplink capacity of communication systems is increasing day by day. By using the orthogonal cover code (OCC) technology, resource multiplexing on multiple terminal devices can be achieved, thereby achieving a better uplink capacity enhancement effect.

[0003] In communication, the redundancy version (RV) is mainly used to provide redundant information for data transmission to enhance the transmission reliability of data in an unreliable channel. The existing solutions have not clarified the problem of how a terminal obtains the RV value and the OCC codeword. Summary of the Invention

[0004] Embodiments of this application provide a method and apparatus in a node for wireless communication. The following introduces various aspects related to this application.

[0005] In a first aspect, a method in a first node for wireless communication is provided, including: receiving first information; wherein, the first information is used to indicate a first OCC codeword of the first node; the first node belongs to a first OCC group, and nodes in the same OCC group use the same RV value.

[0006] In a second aspect, a method in a second node for wireless communication is provided, including: sending first information; wherein, the first information is used to indicate a first OCC codeword of a first node; the first node belongs to a first OCC group, and nodes in the same OCC group use the same RV value.

[0007] In a third aspect, a method in a first node for wireless communication is provided, including:

[0008] A first transceiver module, configured to receive first information; wherein, the first information is used to indicate a first code OCC codeword of the first node; the first node belongs to a first OCC group, and nodes in the same OCC group use the same RV value.

[0009] In a fourth aspect, a method in a second node for wireless communication is provided, including:

[0010] The first transceiver module is used to send the first information; wherein, the first information is used to indicate the first OCC codeword of the first node; the first node belongs to the first OCC group, and nodes in the same OCC group use the same RV value.

[0011] In a fifth aspect, a first node used for wireless communication is provided, including a transceiver, a memory, and a processor. The memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals, so that the first node executes the method described in the first aspect.

[0012] In a sixth aspect, a second node used for wireless communication is provided, including a transceiver, a memory, and a processor. The memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals, so that the second node executes the method described in the second aspect.

[0013] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned first node and / or second node. In another possible design, the system may further include other devices that interact with the first node or the second node in the solution provided by the embodiment of the present application.

[0014] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a computer to execute some or all of the steps in the methods of the above aspects.

[0015] In a ninth aspect, an embodiment of the present application provides a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to enable a computer to execute some or all of the steps in the methods of the above aspects. In some implementations, the computer program product may be a software installation package.

[0016] In a tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0017] In the embodiment of the present application, the first node determines the required OCC codeword based on the first information from the second node. The first node determines the RV value from the first information or the RV cyclic sequence. The first node performs uplink transmission based on the OCC codeword and the RV. This embodiment realizes the problem of the first node obtaining the RV value and the OCC codeword without changing the size of the DCI. Description of the Drawings

[0018] Figure 1 It is a schematic diagram of the system architecture of a wireless communication system to which the embodiments of the present application can be applied.

[0019] Figure 2 It is a schematic diagram of the network architecture to which the embodiments of the present application can be applied.

[0020] Figure 3A and Figure 3B It is a schematic diagram of the wireless protocol stack structure to which the embodiments of the present application can be applied.

[0021] Figure 4 It is a schematic diagram of the RV values in the same OCC group to which the embodiments of the present application can be applied.

[0022] Figure 5 It is a schematic diagram of the RV cycle across OCC groups to which the embodiments of the present application can be applied.

[0023] Figure 6 A wireless communication method provided by the embodiments of the present application.

[0024] Figure 7 It is a schematic diagram of the wireless communication method of Solution 1 provided by the embodiments of the present application.

[0025] Figure 8 It is a schematic diagram of the bits of the RV field in the DCI for scheduling PUSCH.

[0026] Figure 9 is Figure 7 A schematic diagram of the process of a possible implementation manner of the method shown.

[0027] Figure 10 is Figure 9 An interaction example of the implementation manner shown.

[0028] Figure 11 It is a schematic diagram of the wireless communication method of Solution 2 provided by the embodiments of the present application.

[0029] Figure 12 is Figure 11 A schematic diagram of the process of a possible implementation manner of the method shown.

[0030] Figure 13 is Figure 12 An interaction example of the implementation manner shown.

[0031] Figure 14 It is a schematic diagram of the wireless communication method of Solution 3 provided by the embodiments of the present application.

[0032] Figure 15 is Figure 14 A schematic diagram of the process of a possible implementation manner of the method shown.

[0033] Figure 16 This is a schematic structural diagram of a first node for wireless communication provided by an embodiment of the present application.

[0034] Figure 17 This is a schematic structural diagram of a second node for wireless communication provided by an embodiment of the present application.

[0035] Figure 18 This is a schematic structural diagram of a communication device provided by an embodiment of the present application.

[0036] Figure 19 This is a schematic diagram of the hardware module of the communication device provided by an embodiment of the present application. Detailed implementation manners

[0037] Communication system architecture

[0038] The wireless communication system of the embodiment of the present application may include a network device and a terminal device. The network device may be a device that communicates with the terminal device. The network device may provide communication coverage for a specific geographical area and may communicate with the terminal devices located within the coverage area.

[0039] Figure 1 Exemplarily, a wireless communication system 100 is shown to include a network device 110 and a plurality of terminal devices. For example, the terminal devices 120a to 120j in the figure. Optionally, the wireless communication system 100 may include a plurality of network devices and the coverage range of each network device may include other numbers of terminal devices. The embodiment of the present application does not limit this.

[0040] Optionally, the wireless communication system may further include other network entities such as a network controller and a mobility management entity. The embodiment of the present application does not limit this.

[0041] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth-generation (5G) system or the new radio (NR) system, the long-term evolution (LTE) system, the LTE frequency division duplex (FDD) system, the LTE time division duplex (TDD) system, the advanced long-term evolution (LTE-A) system, the enhanced 5G (5G advanced) system, the low-power communication system, etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth-generation (6G) mobile communication system, or the satellite communication system, and so on.

[0042] In the communication technologies before the NR system, for a terminal device, the working mode of the terminal device can support multiple communication technologies simultaneously, and each communication technology corresponds to a multiple access method. However, with the evolution of technology, in the NR system and the communication technologies after the NR system, a single communication system can support multiple multiple access methods.

[0043] It should be understood that the multiple access method, also known as the multiple access mode or multiple access technology, refers to a technology for efficiently sharing a wireless resource (such as time / frequency / space / carrier) when multiple users access a network (such as a cell in a mobile communication or a wireless local area network). That is, when multiple users share a wireless resource, it is divided according to time, frequency, space, coding, subcarriers, etc., so that different users use (or access) the divided resource for communication in different division methods. Occupying different divided resources is like having different addresses, and the same wireless resource can have multiple addresses, so it is called multiple access. The multiple access methods are roughly divided into two categories: orthogonal multiple access (OMA), that is, there is no interference between users; non-orthogonal multiple access (NOMA), and the signals of each user may interfere with other users.

[0044] The multiple access methods involved in this application include, but are not limited to, the following: Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Space Division Multiple Access (SDMA), Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA), Non-Orthogonal Multiple Access (NOMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-Carrier Frequency Division Multiple Access (SC-FDMA), and other multiple access methods.

[0045] The following description describes a New Radio (NR) system for example purposes and uses NR terms in most of the following descriptions. However, these technologies can also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems. A wireless communication system includes a terminal device and a network-side device.

[0046] It should be understood that the 6G system will adopt a more flexible and efficient multiple access method. For example, Non-Orthogonal Multiple Access (NOMA) technology transmits data of multiple users simultaneously in the same frequency band and uses the differences between users to optimize resource allocation and interference management; technologies such as sparse codebooks and multi-dimensional modulation can be used to improve spectral efficiency and transmission performance. Multiple access methods based on Interleaved Division Multiple Access, multiple access methods based on multi-user shared access, resource-expanded multiple access, and Unsourced Multiple Access (UMA), etc.

[0047] The terms "system" and "network" in the embodiments of this application are often used interchangeably. The described technologies can be used not only for the systems and radio technologies mentioned above, but also for other systems and radio technologies.

[0048] It should be understood that all or part of the functions of the communication devices in this application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform).

[0049] Figure 2 FIG. is a schematic diagram of a network architecture 200 of an embodiment of the present application. The network architecture 200 illustrates the network architecture of a 5G NR / LTE / LTE-A system, and the 5G NR / LTE / LTE-A network architecture may also be referred to as the network architecture of a 5G system (5GS) / evolved packet system (EPS). The network architecture 200 includes at least one of a network device 110, a terminal device 120, a 5G core network (5GC) / evolved packet core (EPC) 210, a home subscriber server (HSS) / unified data management (UDM) 220, and an Internet service 230. Figure 2 The network device and the terminal device in are exemplified by RAN and UE respectively.

[0050] As Figure 2As shown, the network device 110 provides termination of the user plane protocol and the control plane protocol towards the terminal device 120. The network device 110 is connected to the 5GC / EPC 210 through the S1 / NG interface. The 5GC / EPC 210 includes a mobility management entity (MME) / authentication management field (AMF) / session management function (SMF) 211, other MME / AMF / SMFs 214, a serving gateway (S-GW) / user plane function (UPF) 212, and a packet data network gateway (P-GW) / UPF 213. The MME / AMF / SMF 211 is a control node that processes the signaling between the terminal device 120 and the 5GC / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user Internet protocol (IP) packets are transmitted through the S-GW / UPF 212, and the S-GW / UPF 212 itself is connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF 213 is connected to the Internet service 230. The Internet service 230 includes the operator-corresponding Internet protocol services, which may specifically include the Internet, intranet, IP multimedia subsystem (IMS), and packet-switched streaming services. It can be seen that the network architecture 200 provides packet-switched services. However, those skilled in the art will easily understand that the various concepts presented throughout this application can be extended to networks that provide circuit-switched services or other cellular networks.

[0051] Figure 3A and Figure 3B respectively show the schematic diagrams of the wireless protocol stack structures of an embodiment of the present application. Figure 3A and Figure 3B Taking the 5G wireless protocol stack as an example for introduction. The 5G wireless protocol stack is divided into two planes: the user plane (UP) protocol stack and the control plane (CP) protocol stack. The user plane protocol stack is the protocol cluster used for user data transmission, and the control plane protocol stack is the protocol cluster used for the control signaling transmission of the 5G system. The specific names of the layers of each protocol stack are as follows:

[0052] Such as Figure 3AAs shown in the figure, the user plane protocol stack from top to bottom includes: Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer.

[0053] As Figure 3B shown in the figure, the control plane protocol stack from top to bottom includes: Non-Access Stratum (NAS); Radio Resource Control (RRC) layer, PDCP layer, RLC layer, MAC layer, and PHY layer.

[0054] It should be understood that different layers in the above protocol stack have different functions, and the communication function between the terminal device and the network device is jointly realized through inter-layer interaction. With the development of artificial intelligence technology, the artificial intelligence-assisted computing function has penetrated into the processing implementation methods of the above protocol stack. For example, the scheduling algorithm of the MAC layer and the encoding and decoding algorithm of the PHY layer can apply artificial intelligence algorithms to improve the performance of communication algorithms.

[0055] As an example, Figure 3A and Figure 3B the wireless protocol architecture in is applicable to the first node in this application.

[0056] As an example, Figure 3A and Figure 3B the wireless protocol architecture in is applicable to the second node in this application.

[0057] It should be understood that some function implementations in the wireless protocol architecture can also be implemented in one or more devices. For example, the functions of different layers in the control plane protocol stack can be combined and implemented by multiple nodes on the network side.

[0058] It should be understood that the explanations of the terms in the embodiments of this application can refer to the specification protocols of the 3rd Generation Partnership Project (3GPP) series TS36, TS37, and TS38, but can also refer to the specification protocols of the Institute of Electrical and Electronics Engineers (IEEE).

[0059] For ease of understanding, some relevant technical knowledge related to the embodiments of the present application will be introduced first. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application. The embodiments of the present application include at least some of the following contents.

[0060] NTN system

[0061] NTN generally provides communication services to ground terminal devices by means of satellite communication.

[0062] For terrestrial network communication, in scenarios such as the ocean, mountains, and deserts, it is impossible to set up network devices for terrestrial communication. Or, considering the costs of network device setup and operation, terrestrial communication usually does not cover areas with sparse population. Compared with terrestrial network communication, NTN has many advantages. First, for the NTN communication network, it is not restricted by geography. In theory, satellites can orbit the Earth, so every corner of the Earth can be covered by satellite communication. Moreover, the area that non-terrestrial network devices can cover is much larger than that of terrestrial network devices. That is, NTN cells can cover a larger range.

[0063] With the development and popularization of NTN technology, more and more terminal devices will be connected to NTN. Therefore, the uplink data volume will continue to increase, and the requirements for the continuity and stability of NTN services will also continue to increase. As a result, the demand for enhanced uplink capacity in NTN is increasing day by day.

[0064] Orthogonal cover code (OCC)

[0065] The OCC technology is generally used in wireless communication systems. This technology spreads and encodes the transmitted signal by generating a set of orthogonal code sequences, which can further improve the spectral efficiency and anti-interference ability of the system.

[0066] The OCC technology can be applied in communication systems to enhance the uplink capacity of the communication system. For example, in the NTN system, the OCC technology has been applied to the transmission of PUCCH. By performing OCC multiplexing on the antenna ports of different terminal devices within the same CDM group, the uplink capacity of NTN is effectively enhanced. This proves the feasibility of the OCC multiplexing technology in enhancing the uplink capacity of the NTN system.

[0067] Redundancy version (RV)

[0068] In communication, the RV value refers to multiple versions obtained by encoding or otherwise processing the same data differently during data transmission to improve the reliability and error correction ability of data transmission. It is mainly used to provide redundant information for data transmission to enhance the transmission reliability of data in an unreliable channel. For example, in modern mobile communication standards, channel coding technologies such as Turbo codes or low-density parity-check (LDPC) codes are used to cope with the complex and changing wireless channel environment. The RV value is based on different coding versions generated by these coding technologies, and the redundant information contained therein is different. In actual use, the RV value is usually combined with the retransmission technology. When retransmitting, the encoded data with different RV values is sent, and different redundant information is combined to improve the decoding success rate and enhance the reliability of data transmission. In retransmission, common cyclic sequences of RV values are {0, 2}, {0, 3}, {0, 2, 3, 1}, etc.

[0069] RV cycle across OCC groups

[0070] In NTN, the RV cycle of OCC uses the same RV value within the same OCC group. An example of the RV value setting within the same OCC group is as Figure 4 shown. At this time, the OCC length used is 4, the OCC scheme is cross-slot OCC, and the OCC sequence is the Walsh sequence. Assuming that the RV used by UE1 and UE3 in the current OCC group is 0, while the RV used by UE2 is 2, then from Figure 4 it can be seen that within this OCC group (i.e., OCC group1), the same RV value is used for all time slots of a single UE.

[0071] Regarding the RV cycle across OCC groups (group), if considering RV cycling across OCC groups and the cyclic sequence of RV is {0, 2, 3, 1}, and other OCC-related parameters are the same as those Figure 4 shown, then the example of the RV cycle across OCC groups is as Figure 5 shown. It can be seen that when each UE switches to the next OCC group (group), its RV value will be switched and cycled according to the cyclic sequence of the RV.

[0072] DCI for PUSCH transmission

[0073] According to the protocol content, the downlink control information (DCI) for scheduling the physical uplink shared channel (PUSCH) includes four types, namely DCI0_0, DCI0_1, DCI0_2, and DCI0_3. According to the introduction of their respective fields in the protocol, the existing fields of all the above DCIs do not have a field indicating the OCC codeword. At the same time, in the dynamic grant physical uplink shared channel (DG-PUSCH) of NTN, if capacity enhancement is to be achieved by using OCC multiplexing, it is necessary to use DCI to dynamically schedule the OCC codeword used by the UE.

[0074] To be able to indicate the OCC codeword in DCI, a possible technical solution is to perform joint coding based on the original fields of DCI0_1. For example, the most common one is the joint coding scheme of the antenna ports field, OCC length, and OCC codeword index. This scheme defaults that the number of bits of the antenna ports field in DCI0_1 is 4.

[0075] Assume that the number of bits of the frequency domain resource assignment field is 4 and the number of bits of the uplink / supplementary uplink indicator (UL / SUL Indicator) field is 1. Then for DCI0_0, roughly estimated, the number of bits required for one scheduling is about 21 bits; for DCI0_1, when the number of bits of the antenna ports field is 4, the minimum number of bits required for one scheduling is about 32 bits, and the RRC configuration process of DCI0_1 is more complex than that of DCI0_0.

[0076] In summary, under the same other conditions, using DCI0_1 for scheduling will require higher downlink resource overhead than DCI0_0. At the same time, the bits of the antenna ports field in DCI0_1 are mainly used to achieve the spatial multiplexing capacity gain of multi-user multiple-input multiple-output (MU-MIMO), while only a single transmit / receive antenna (i.e., 1Tx / Rx) is used in the uplink of NTN. Therefore, it is also necessary to indicate the OCC codeword based on DCI0_0. In addition, in order to better improve the applicability, the OCC codeword indication scheme should also be applicable to other DCIs as much as possible, such as performing joint coding based on the common fields of the above DCIs and the OCC codeword.

[0077] MAC Link and difference between CE configuration and RRC configuration

[0078] In a mobile communication system, the Medium Access Control - Control Element (MAC CE) configuration and the Radio Resource Control (RRC) configuration cooperate with each other to jointly complete the allocation and management of radio resources. The RRC is mainly responsible for the radio resource configuration of the upper layer, including cell selection / reselection parameters, security configuration, etc., providing a basic framework for the operation of the MAC layer. The MAC CE configuration, on the other hand, operates on some dynamic and immediate resource controls at the MAC layer. It can perform more flexible fine - tuning of resources according to the basic rules of the RRC configuration and the actual situation of the current channel and services.

[0079] This application focuses on elaborating on how a UE obtains RV values and OCC codewords, and performs uplink transmission based on the RV values and OCC codewords.

[0080] Considering that there is no indication field for the OCC codeword in the DCI used for dynamic scheduling of the PUSCH, in order to be able to indicate the OCC codeword using the DCI without changing the DCI size, it is necessary to multiplex or jointly encode the original fields in the DCI. Based on this, an embodiment of this application provides a wireless communication method to solve the above - mentioned problem. Figure 6 This is a schematic flowchart of the method.

[0081] Figure 6 It can be executed by a first node. Exemplarily, the first node can be a UE in an OCC group, and the second node can be an NTN network device. In other words, this application can be applied in an NTN communication system.

[0082] Figure 6 The method shown can include S610.

[0083] S610, the first node receives first information. Among them, the first information can be used to indicate the first OCC codeword of the first node.

[0084] Optionally, the first OCC codeword can be applied to the transmission of the PUSCH, thereby improving the capacity / throughput of the PUSCH. In some embodiments, the first information can include the index of the first OCC codeword.

[0085] In some embodiments, the first information can separately indicate the first OCC codeword.

[0086] In some embodiments, the first information can also be used to indicate the RV value. Exemplarily, the first information is the index information of the joint encoding of the first OCC codeword and the RV value.

[0087] In some embodiments, the first information is carried in all or part of the RV fields in the downlink scheduling information DCI.

[0088] In some embodiments, the first node may also receive second information, where the second information is used to indicate the joint coding table corresponding to the first node.

[0089] Exemplarily, the second information may include an index value corresponding to the first joint coding table. The first node determines the first joint coding table corresponding to the index by querying in a pre-configured set of joint coding tables.

[0090] In some embodiments, the first node may combine the first information and the second information to determine the first OCC codeword and the RV value. The transmission time of the second information may be before the transmission time of the first information, after the transmission time of the first information, or they may be transmitted simultaneously.

[0091] In some embodiments, each joint coding table in the set of joint coding tables includes an OCC codeword. Optionally, the joint coding table may further include at least one of the following: RV value, OCC codeword length, and index corresponding to each OCC codeword.

[0092] In some embodiments, the set of joint coding tables may be specified by a standard, or pre-set, or configured by a network device. The joint coding table may meet the requirements: specified by a standard, or pre-set, or configured by a network device. For example, an NTN network device may send configuration information to the first node, and this configuration information may be used to indicate the set of joint coding tables. Then, the second node sends an index value through RRC or MAC CE, and this index value indicates the first joint coding table that the first node needs to use. The first joint coding table may also implicitly include OCC length information, so that the second node does not need to additionally indicate the OCC length to the first node.

[0093] Generally, before sending the first information, the second node first performs OCC configuration on the first node, that is, sends the second information. The first node may obtain the index value from the OCC configuration and then determine the first joint coding table corresponding to the index value from the set of joint coding tables.

[0094] In some embodiments, the first node may also receive third information, where the third information is used to indicate the RV cyclic sequence.

[0095] In some embodiments, the RV cyclic sequence may satisfy: specified by standards, or preset, or configured by a network device. Exemplarily, {0} indicates no RV cycling, and all repeated RVs are 0; {0 2} indicates that the cyclic sequence of RV cycling in OCC group units is 020202...; {0 3} indicates that the cyclic sequence of RV cycling in OCC group units is 030303...; {0 2 3 1} indicates that the cyclic sequence of RV cycling in OCC group units is 0231023102....

[0096] In some embodiments, the third information may be the RV cyclic sequence notified by the second node to the first node through RRC or MAC CE. The first node determines the first OCC codeword from the first joint coding table corresponding to the first node according to the first information; then the first node determines the current RV value from the RV cyclic sequence according to the third information.

[0097] In some embodiments, the first node may belong to the first OCC group. The first OCC group may further include other nodes. In other words, the first OCC group may include multiple terminal devices.

[0098] In some embodiments, the first node may further receive fourth information, where the fourth information is used to indicate the OCC codeword length used by the first node. Exemplarily, the gNB notifies the UE of the required OCC length, for example, the OCC length is 4.

[0099] In some embodiments, the OCC codeword length may be determined based on the requirements of the first node. For example, when a user watches a 4K video, the base station allocates a 4-symbol OCC codeword to ensure stable high-rate transmission through anti-interference optimization; for an automated device (URLLC UE) that needs to report sensor data in real time, the base station allocates a 2-symbol OCC code to ensure that the data is transmitted within 1 ms, and at the same time supports fast scheduling through a short code length. It can be seen that a short OCC codeword length supports high-density and low-latency services, and a long OCC codeword length enhances edge coverage and anti-interference capabilities. By dynamically adjusting the OCC codeword length based on UE requirements, the 5G network can achieve an optimal balance of capacity, latency, and reliability in different scenarios. The OCC codeword length may be implicitly indicated in the joint coding table, or may be the fourth information received indicating the OCC codeword length used by the first node. Based on the OCC codeword length, the first node determines whether to use the RV value and the first OCC codeword for uplink transmission. Or rather, whether the UE uses OCC can be determined by judging whether it receives a signaling indicating the OCC length, or can also be indicated by a separately designed signaling to indicate whether the UE uses OCC. When the UE does not use OCC, it will still interpret the subsequent DCI field indicating the scheduling of PUSCH according to the original standard, and will no longer interpret the RV field in the DCI as an OCC codeword.

[0100] It should be noted that the present application does not limit the message type carrying the first information. For example, the first information may be carried by a DCI or an RRC message. For another example, the first information is carried in all or part of the RV fields in the DCI.

[0101] The present application does not limit the message type carrying the second information. For example, the second information may be carried by an RRC message.

[0102] In summary, the present application proposes various RV and OCC codeword acquisition schemes, which may include:

[0103] (1) Scheme 1: The second node jointly encodes and indicates the RV field of the DCI with the OCC codeword, and the first node determines the OCC codeword and the RV value according to the joint coding indication.

[0104] (2) Scheme 2: The second node modifies all or part of the RV fields to indicate the OCC codeword. In addition, the second node configures an RV cyclic sequence for the first node, and the first node determines the current RV value by inference.

[0105] (3) Scheme 3: The second node modifies all or part of the RV fields to indicate the OCC codeword, and the second node directly indicates the RV value currently used by the first node.

[0106] The above different solutions can enable the first node to obtain the RV value and the OCC codeword without changing the DCI size, and the scenarios applicable to this application also include the RV cycle scenario across OCC groups.

[0107] The above method embodiments will be described separately below.

[0108] Figure 7 It is a schematic flowchart of a wireless communication method provided by an embodiment of this application to illustrate the above Solution 1.

[0109] Figure 7 The method shown may include S710 to S740.

[0110] S710, the first node receives the first information. Among them, the first information can be used to indicate the first OCC codeword and RV value of the first node.

[0111] S720, the first node receives the second information. Among them, the second information corresponds to the first joint coding table. For example, the second information includes the index value of the first joint coding table.

[0112] S730, the first node performs uplink transmission of PUSCH based on the first OCC codeword and RV value.

[0113] S740, the second node receives the PUSCH from the first node and performs decoding processing.

[0114] In a possible embodiment, the first information may include the index in the first joint coding table of the first node. The first node determines the first OCC codeword and RV value corresponding to the index by querying the index in the first joint coding table.

[0115] In some embodiments, the first node obtains a set of joint coding tables. Exemplarily, this set of joint coding tables includes Joint Coding Table 1 to Joint Coding Table 13 (see below), and the index values (Com_Code_Idx) corresponding to each joint coding table. For example, before the NTN network device sends the first information, it first configures OCC for UE 1, and UE1 can obtain the index configuration table of the set of joint coding tables from the OCC configuration (such as Table 0 below).

[0116] In some embodiments, the second information received by the first node includes the index (Com_Code_Idx) of the first joint coding table of the first node, and the first information received by the first node includes the index (RV_OCCcw_Idx) of the first OCC and RV in the first joint coding table.

[0117] In some embodiments, the first information may be carried by a DCI or an RRC message. Optionally, the DCI may be any one of DCI0_0 to DCI0_3. The second node sends a DCI to the first node based on the PDCCH to dynamically schedule the PUSCH. The first node indexes, in the first joint coding table according to the first information in the DCI, the RV value of the data that the first node should transmit and the OCC codeword required for spreading.

[0118] In some embodiments, the first information may be carried by an RRC message. For example, the configuration of the OCC code is embedded in the PUCCH-Config. Another example is that when the UE makes an initial access, it obtains the PUCCH resource configuration of the initial BWP (bandwidth part) through the MIB and SIB1, including the default OCC code length, or the gNB issues a dedicated PUCCH resource configuration for the UE through the RRCReconfiguration message, including the default OCC code length.

[0119] In some embodiments, the first node may also receive third information, which is used to indicate that the first node uses the first OCC codeword or does not use the first OCC codeword. For example, if the NTN network device indicates to UE1 to use the first OCC codeword through the RRC or MAC CE, then UE1 uses the joint coding table set to interpret the first information and the second information, so as to determine the first OCC codeword and the RV value. Another example is that if the NTN network device indicates to UE1 not to use the first OCC codeword or the joint coding table through the RRC, then UE1 still interprets the subsequent DCI field (such as RV_OCCcw_Idx) that indicates the scheduling of the PUSCH according to the original standard, that is, does not use the first OCC codeword.

[0120] In some embodiments, the first node may determine whether to use the first OCC codeword based on whether it is configured with a joint coding table. For example, if UE1 receives the configuration information of the joint coding table including the RV and the OCC codeword, it uses the set of joint coding tables to interpret the first information and the second information, so as to determine the first OCC codeword and the RV value. When UE1 does not receive the configuration information of the joint coding table including the RV and the OCC codeword, or UE1 receives the configuration information but then receives other information indicating "deactivation", it will still interpret the subsequent DCI field (such as RV_OCCcw_Idx) indicating the scheduling of PUSCH according to the original standard, and will not use the joint coding interpretation method to interpret the DCI. For another example, UE1 and UE2 perform OCC multiplexing, where UE1 receives the configuration information of the joint coding table of the RV value and the OCC codeword from the gNB, while UE2 does not receive it. Therefore, UE1 will use the interpretation method of the joint coding of the RV and the OCC codeword when processing the PDCCH sent by the gNB subsequently (for scheduling the PUSCH uplink transmission of UE1); while UE2 will still interpret it according to the original standard when processing the PDCCH sent by the gNB subsequently (for scheduling the PUSCH uplink transmission of UE2), and will not use the interpretation method of the joint coding of the RV and the OCC codeword.

[0121] In some embodiments, the second node may use DCI0_0 for PUSCH dynamic scheduling, perform joint coding of the RV field (such as redundancy version) in it with the OCC codeword, and then indicate the joint coding through the first information. For DCI0_0, the bit diagram of its RV field is as Figure 8 shown in (a) of, and the size of its RV field is fixed at 2 bits. Among them, the solid line indicates that the bit size of the RV field is fixed.

[0122] In some embodiments, the second node may use DCI0_1 for PUSCH dynamic scheduling and perform joint coding of the RV field in it with the OCC codeword. For DCI0_1, the bit diagram of its RV field is as Figure 8 shown in (b) of, where the size of the RV field is optional and needs to be pre-configured or specified by the protocol, and its range is 2 to 8 bits. Among them, the dashed line indicates that the bit size of the RV field is not fixed.

[0123] In some embodiments, the second node may use DCI0_1 to perform PUSCH dynamic scheduling for UE1 using OCC. For example, the OCC codeword length is 2 bits, and the gNB configures the positions of these 2 bits, so that the indexes of 8 bits are as Figure 8As shown in (b) therein, they are 1 to 8 from left to right. For example, if the 2 bits configured by the gNB are the 1st bit and the 3rd bit, then the subsequent gNB will jointly indicate the RV and OCC codewords based on these 2 bits, thereby generating and sending the first information for indicating the RV and OCC codewords.

[0124] In some embodiments, DCI0_2 or 0_3 can be used for PUSCH dynamic scheduling, and the RV field therein is jointly encoded with the RV and OCC codewords. For DCI0_2 and 0_3, the bit schematic diagram of their RV fields is as Figure 8 shown in (c) therein. The size of its RV field is also optional and needs to be pre-configured or specified by the protocol, and its range is 0 to 2 bits. For example, the gNB uses DCI0_2 to perform PUSCH dynamic scheduling for UE1 using OCC. Assuming that the bit length for joint encoding is 1 bit, the gNB configures the position of this 1 bit, and the indexes of the 2 bits are as Figure 8 shown in (c) therein, which are 1 and 2 from left to right. For example, if the 1 bit configured by the gNB is the 2nd bit, then the subsequent gNB will jointly indicate the RV and OCC codewords based on this.

[0125] In some embodiments, the first node can perform uplink transmission of PUSCH based on the RV and OCC codewords found from the corresponding joint coding table.

[0126] In some embodiments, the second node performs OCC de-configuration after completing the uplink transmission. Doing so means that the first node no longer uses OCC to transmit PUSCH, and at the same time no longer interprets DCI in the manner described in this solution.

[0127] In some embodiments, the scheduling method can be initial transmission scheduling (New Data Indicator flipped) or retransmission scheduling (New Data Indicator not flipped). Whether it is initial transmission or retransmission, the first node needs to interpret DCI according to this embodiment after OCC configuration, otherwise it will still use the interpretation method in the original standard. In addition, if the first node has performed OCC configuration during initial transmission and has not performed OCC de-configuration before retransmission, it can be defaulted to still perform retransmission according to the OCC method, and at this time, DCI can be interpreted according to this embodiment.

[0128] Further below, in combination with Figure 9 the specific example shown, Figure 7 the method flow shown is specifically described.

[0129] Figure 9 The method shown can include S910 to S960.

[0130] For S910, UE1, UE2, UE3, and UE4 perform OCC multiplexing, and the gNB configures OCC for these four UEs. Meanwhile, each UE obtains its corresponding joint coding table.

[0131] Exemplarily, assume that the joint coding bits are 2 bits, and the positions of these 2 bits in the DCI have also been configured by the gNB or specified by the protocol. Table 0 in the following text is an example of the index configuration table of the joint coding table of RV and OCC codewords, and Tables 1 to 13 in the following text are examples of joint coding tables 1 to 13.

[0132] In addition, each joint coding table has a corresponding OCC length. For example, the OCC lengths corresponding to joint coding tables 1 to 9 are 4, while the OCC lengths corresponding to joint coding tables 10 to 13 are 2. Therefore, after the gNB configures joint coding tables 1 to 13 for the UE, the UE can uniquely find the corresponding RV value and OCC codeword from the joint coding table according to the "RV_OCCcw_Idx" field in the DCI of the subsequent PDCCH (used to schedule the PUSCH uplink transmission of this UE) from the gNB, and can also know the OCC length (which can be obtained from the length of the OCC codeword).

[0133] Exemplarily, the gNB may configure the joint coding tables required to be used by UEs UE1 to UE4 through RRC and / or MAC CE respectively based on the index configuration table of the joint coding table. For UE1, the gNB will configure the joint coding table index for UE1 through RRC. For example, if the configuration information is "Com_Code_Idx = 0001", then UE1 looks up the index "Com_Code_Idx = 0001" in Table 0 and obtains the corresponding joint coding table 1 (as shown in Table 1); for UE2, the gNB will configure the joint coding table index for UE through MAC CE. For example, the MAC CE is placed at the beginning of the MAC protocol data unit (PDU), and the configuration information it contains is "Com_Code_Idx = 0010", and then it is transmitted to UE2 via PDCCH. UE2 will parse the parameters of the extracted MAC CE according to the format and protocol of the MAC CE to obtain the configuration information "010" contained therein, and based on Table 0, index to the joint coding table 2 (as shown in Table 2). In the same way, for UE3, the gNB will configure the joint coding table index for UE3 through RRC. For example, the configuration information is "Com_Code_Idx = 0011", then UE3 looks up the index "Com_Code_Idx = 0011" in Table 0 and obtains the corresponding joint coding table 3 (as shown in Table 3). For UE4, the gNB will configure the joint coding table index for UE4 through RRC. For example, the configuration information is "Com_Code_Idx = 0100", then UE4 looks up the index "Com_Code_Idx = 0100" in Table 0 and obtains the corresponding joint coding table 4 (as shown in Table 4).

[0134] In a possible embodiment, if it is necessary to modify the current joint coding tables 1 to 13, the second node may perform RRC reconfiguration or MAC CE reconfiguration, so that the first node obtains the updated joint coding table of the RV and OCC codewords.

[0135] S920, the gNB sends DCI to the UE based on the PDCCH to dynamically schedule the PUSCH.

[0136] S930, each UE indexes the RV value of the data that the UE should transmit and the OCC codeword required for spreading in the corresponding joint coding table according to the "RV_OCCcw_Idx" field in the DCI.

[0137] Assume that the gNB uses DCI0_0 for UEs UE1 to UE4, as Figure 10As shown, in Scenario 1, the "RV_OCCcw_Idx" fields of the DCI indicated by the gNB are 00, 01, 10, and 11 respectively. Therefore, each UE can find the RV for transmitting data and the OCC codeword required for spreading in the jointly coded table configured previously. For example, the RV value of UE1 is 0, and the OCC codeword is [1 1 1 1]; the RV value of UE2 is 0, and the OCC codeword is [1 -1 1 -1]; the RV value of UE3 is 0, and the OCC codeword is [1 1 -1 -1]; the RV value of UE4 is 0, and the OCC codeword is [1 -1 -1 1]. In Scenario 2, the "RV_OCCcw_Idx" fields of the DCI indicated by the gNB are 01, 10, 11, and 00 respectively. Therefore, each UE can find the RV for transmitting data and the OCC codeword required for spreading in the jointly coded table configured previously. For example, the RV value of UE1 is 2, and the OCC codeword is [1 -1 1 -1]; the RV value of UE2 is 2, and the OCC codeword is [1 1 -1 -1]; the RV value of UE3 is 2, and the OCC codeword is [1 -1 -1 1]; the RV value of UE4 is 2, and the OCC codeword is [1 1 1 1]. In Scenario 3, the "RV_OCCcw_Idx" fields of the DCI indicated by the gNB are 10, 11, 00, and 01 respectively. Therefore, each UE can find the RV for transmitting data and the OCC codeword required for spreading in the jointly coded table configured previously. For example, the RV value of UE1 is 3, and the OCC codeword is [1 1 -1 -1]; the RV value of UE2 is 3, and the OCC codeword is [1 -1 -1 1]; the RV value of UE3 is 3, and the OCC codeword is [1 1 1 1]; the RV value of UE4 is 3, and the OCC codeword is [1 -1 1 -1].

[0138] S940, each UE performs uplink transmission of the PUSCH based on the corresponding RV and OCC codeword.

[0139] In this embodiment, it is assumed that there is 1 OCC group in 1 PUSCH, that is, for each of the four UEs, 1 PUSCH will contain 4 repeated time slots, the data transmitted by these time slots is the same (and the RV values are also the same), and each time slot will be assigned one codeword (1 or -1) from the OCC codeword with a length of 4, and multiplying the codeword completes the OCC spreading operation.

[0140] S950, the gNB receives and decodes the PUSCH sent by each UE.

[0141] For S960, when the PUSCH scheduling based on OCC ends, the gNB deconfigures OCC for each UE based on RRC. Each UE will no longer use OCC to transmit PUSCH, and at the same time, each UE will no longer interpret DCI in the manner described in this implementation scheme.

[0142] Table 0 (Index Configuration Table of Joint Coding Table)

[0143]

[0144]

[0145] Table 1 (Joint Coding Table 1 of RV and OCC Codewords)

[0146]

[0147] Table 2 (Joint Coding Table 2 of RV and OCC Codewords)

[0148]

[0149] Table 3 (Joint Coding Table 3 of RV and OCC Codewords)

[0150]

[0151] Table 4 (Joint Coding Table 4 of RV and OCC Codewords)

[0152]

[0153] Table 5 (Joint Coding Table 5 of RV and OCC Codewords)

[0154]

[0155] Table 6 (Joint Coding Table 6 of RV and OCC Codewords)

[0156]

[0157] Table 7 (Joint Coding Table 7 of RV and OCC Codewords)

[0158]

[0159] Table 8 (Joint Coding Table 8 of RV and OCC Codewords)

[0160]

[0161] Table 9 (Joint Coding Table 9 of RV and OCC Codewords)

[0162]

[0163]

[0164] Table 10 (Joint Coding Table 10 of RV and OCC Codewords)

[0165]

[0166] Table 11 (Joint Coding Table 11 of RV and OCC Codewords)

[0167]

[0168] Table 12 (Joint Coding Table 12 of RV and OCC Codewords)

[0169]

[0170] Table 13 (Joint Coding Table 13 of RV and OCC Codewords)

[0171]

[0172]

[0173] Figure 11 It is a schematic flowchart of another wireless communication method provided by an embodiment of the present application to illustrate the above-mentioned Solution 2.

[0174] Figure 11 The method shown may include S1110 to S1140.

[0175] S1110, the second node configures the OCC for the first node, and the first node obtains the required OCC length and RV cyclic sequence.

[0176] In a possible embodiment, whether the UE uses the OCC can be determined by determining whether an indication signaling of the OCC length is received, or a separate signaling can also be designed to indicate whether the UE uses the OCC. When the UE does not use the OCC, it will still interpret the subsequent DCI field indicating the scheduling of the PUSCH according to the original standard, and will no longer interpret the RV field in the DCI as an OCC codeword.

[0177] In a possible embodiment, the gNB notifies the UE of an RV cyclic sequence through RRC or MAC CE. The RV cyclic sequence can be one of the RV cyclic sequences shown in Table 14 below, where {0} indicates no RV cycling and all repeated RV values are 0; {0 2} indicates a cyclic sequence with RV cycling in OCC groups as 020202...; {0 3} indicates a cyclic sequence with RV cycling in OCC groups as 030303...; {0 2 3 1} indicates a cyclic sequence with RV cycling in OCC groups as 0231023102.... At the same time, the gNB also informs the UE of the OCC length required to be used, and the OCC length can be one of the options shown in Table 15.

[0178] Exemplarily, the OCC codeword indication tables for each length are specified by the protocol. For example, as shown in Tables 16 and 17, the OCC codewords with lengths of 4 and 2 require 2 bits and 1 bit for indication respectively. Therefore, when the UE obtains the OCC length, it can directly infer the OCC codeword indication table it should use. For example, if the gNB informs UE1 that the required OCC length is 2, then UE1 can infer by itself that it should use Table 17 to obtain the OCC codeword during the subsequent PUSCH scheduling process.

[0179] S1120, the second node sends DCI to the first node based on the PDCCH to dynamically schedule the PUSCH.

[0180] S1130, the first node retrieves the OCC codeword it should use in the OCC codeword indication table according to the "OCC_code_word_Idx" field in the DCI (i.e., the Redundancy version field in the original standard), and the first node infers the RV value required to be used based on the configured RV cyclic sequence.

[0181] An example of the UE obtaining the OCC codeword and RV for the first transmission is as follows. Assume that after step S1110, the RV cyclic sequence obtained by UE1 is {0 2 3 1} and the OCC length is 4. Then UE1 will interpret the OCC_code_word_Idx field in the DCI according to Table 16. The gNB sends the DCI to UE1 for dynamic scheduling of the PUSCH. Assume that DCI0_0 is used, and the OCC_code_word_Idx field in it is 10. Then UE1 can find the indicated OCC codeword as [1 1 -1 -1] in Table 16 accordingly. At the same time, this DCI is for the first transmission scheduling. Assume that its New Data Indicator is 1, and the RV it obtains is the first RV value of the RV cyclic sequence, that is, 0.

[0182] The following example illustrates how a UE obtains the OCC codeword and RV for retransmission. Based on the previous example, the gNB sends DCI to UE1 again for PUSCH transmission scheduling. This DCI is the second transmission scheduling. Assuming its New Data Indicator field is still 1, this indicates that this field has not flipped, indicating a retransmission schedule. UE1 now needs to obtain the RV value by shifting the RV value used in the previous transmission one position in the RV cyclic sequence. In this case, it should select the second RV value in the RV cyclic sequence, which is 2. Assuming the OCC_code_word_Idx field in this DCI is 00, UE1 can find the indicated OCC codeword in Table 17 as [11 1 1].

[0183] S1140: The first node performs uplink transmission of the PUSCH based on the corresponding OCC codeword and RV value.

[0184] S1150: The second node receives and decodes the PUSCH sent by the first node.

[0185] The following example illustrates the situation where the gNB sends DCI to the UE but does not receive a PUSCH. When the gNB sends DCI scheduling signaling to the UE but does not receive a PUSCH, this patented solution can default to handling the situation as if DCI signaling was lost. This is because when DCI signaling is lost, the UE cannot receive any instructions from the gNB, so the UE will not transmit a PUSCH, and the gNB will not receive any PUSCH-related signals, including pilot signals, namely the Demodulation Reference Signal (DMRS). DMRS signals are easier to detect during PUSCH transmission than data signals, so the probability of missing a PUSCH is very low, approximately 0.1%. Therefore, in this embodiment, when the gNB does not detect any PUSCH-related signals, it can be assumed that the UE did not transmit a PUSCH. In this case, the gNB can default to handling the RV value and decoding of the next PUSCH as if DCI signaling was lost. This embodiment is highly effective in scenarios with a fault tolerance greater than 0.1%.

[0186] S1160: The second node deconfigures the OCC for the first node based on the RRC or MAC CE.

[0187] It should be understood that OCC deconfiguration means that the first node no longer uses the OCC to transmit the PUSCH, and no longer interprets the DCI in the manner described in this embodiment.

[0188] The following further combines Figure 12 The specific example shown is Figure 11 The method flow shown is described in detail.

[0189] Figure 12 The method shown may include S1210 to S1310. In this embodiment, it is assumed that the OCC codeword changes on average once every 24 ms, the RV changes on average once every 6 ms, and the RV cyclic sequence does not change under normal circumstances.

[0190] S1210, UE1, UE2, UE3, and UE4 perform OCC multiplexing. First, the gNB configures OCC for these 4 UEs. At the same time, each UE needs to obtain the OCC length and RV cyclic sequence it uses.

[0191] In this embodiment, it is determined whether the UE uses OCC by determining whether an indication signaling of the OCC length is received. It is assumed that the gNB configures these 4 UEs through RRC, uses the cross-slot OCC scheme, and it is assumed that the OCC length and RV cyclic sequence have been configured for all 4 UEs by the gNB. Therefore, each UE interprets the RV field as an OCC codeword in the subsequent DCI indication process to interpret the DCI. For example, UE1 to UE4 all receive an OCC length of 4, and the RV cyclic sequence is {0 2 3 1}.

[0192] S1220, the gNB sends the first DCI to UE1 to UE4 based on the PDCCH to dynamically schedule the PUSCH.

[0193] S1230, UE1 to UE4 retrieve the OCC codeword they should use from the OCC codeword indication table according to the "OCC_code_word_Idx" field (i.e., the Redundancy version field in the original standard) in the first DCI, and UE1 to UE4 infer the RV value to be used based on the configured RV cyclic sequence.

[0194] This scheduling is an initial transmission scheduling, and the New Data Indicator in the first DCI sent by the gNB to UE1 to UE4 = 1. The RV used is the first value of the RV cyclic sequence. UE1 to UE4 retrieve the OCC codeword required for spreading of this UE1 to UE4 from the OCC codeword indication table according to the OCC_code_word_Idx field in the DCI. Since it is an initial transmission scheduling, the RV used by UE1 to UE4 in this transmission is the first value of the RV cyclic sequence. In this embodiment, that is, the RV used by each UE in this transmission is 0. As Figure 13As shown, assuming DCI0_0 is used, for UE1 to UE4, the OCC_code_word_Idx fields indicated by the gNB are 00, 01, 10, and 11 respectively. Therefore, each UE can retrieve its respective OCC codeword. The OCC codeword of UE1 is [1 1 1 1]; the OCC codeword of UE2 is [1 -1 1 -1]; the OCC codeword of UE3 is [1 1 -1 -1]; the OCC codeword of UE4 is [1 -1 -1 1].

[0195] S1240, UE1 to UE4 perform uplink transmission of PUSCH based on the corresponding RV values and OCC codewords.

[0196] In this embodiment, it is assumed that there is 1 OCC group in 1 PUSCH, that is, for each UE, 1 PUSCH will contain 4 repeated time slots, and the data transmitted in these time slots is the same (and the RV is also the same). Each time slot will be assigned one codeword (1 or -1) from the OCC codeword with a length of 4, and multiplying the codeword completes the OCC spreading operation.

[0197] S1250, the gNB receives and decodes the PUSCH sent by UE1 to UE4.

[0198] S1260, the gNB sends a second DCI to UE1 to UE4 based on the PDCCH to dynamically schedule the PUSCH.

[0199] This scheduling is the first retransmission scheduling, and the RV used is the second value of the RV cyclic sequence. UE1 to UE4 retrieve the OCC codewords required for spreading of this UE1 to UE4 in the OCC codeword indication table according to the OCC_code_word_Idx field in the second DCI.

[0200] During this scheduling process, the New Data Indicator in the second DCI sent by the gNB to UE1 to UE4 = 1, which is not flipped compared to the previous first DCI scheduling, indicating that this scheduling is a retransmission scheduling. Assuming DCI0_0 is used, for UE1 to UE4, the OCC_code_word_Idx fields indicated by the gNB are 00, 01, 10, and 11 respectively. Therefore, each UE can retrieve its respective OCC codeword. The OCC codeword of UE1 is [1 1 1 1]; the OCC codeword of UE2 is [1 -1 1 -1]; the OCC codeword of UE3 is [1 1 -1 -1]; the OCC codeword of UE4 is [1 -1 -1 1]. Since this is the first retransmission scheduling, the RV used by UE1 to UE4 in this transmission is the second value of the RV cyclic sequence, that is, in this embodiment, the RV used by each UE in this transmission is 2.

[0201] S1270, UE1 to UE4 retrieve the OCC codewords they should use in the OCC codeword indication table according to the "OCC_code_word_Idx" field in the second DCI (i.e., the Redundancy version field in the original standard), and UE1 to UE4 infer the required RV values based on the configured RV cyclic sequence.

[0202] S1280, UE1 to UE4 perform uplink transmission of PUSCH based on the corresponding RV values and OCC codewords.

[0203] S1290, gNB receives and decodes the PUSCH sent by UE1 to UE4.

[0204] S1300, gNB continues to send DCI to UE1 to UE4 for subsequent initial transmission or retransmission scheduling of PUSCH.

[0205] For example, gNB continues to send the third DCI to UE1 to UE4 for subsequent initial transmission scheduling of PUSCH, and the New Data Indicator in the third DCI sent by gNB to UE1 to UE4 = 0, which does not flip compared to the previous second DCI scheduling, meaning this scheduling is an initial transmission scheduling. The RV used is the first value of the RV cyclic sequence. UE1 to UE4 retrieve the OCC codewords required for spreading of this UE1 to UE4 in the OCC codeword indication table according to the "OCC_code_word_Idx" field in the third DCI. Since it is an initial transmission scheduling, the RV used by UE1 to UE4 in this transmission is the first value of the RV cyclic sequence. In this embodiment, the RV used by each UE in this transmission is 0.

[0206] S1310, the scheduling of PUSCH based on OCC ends. gNB deconfigures OCC for UE1 to UE4 based on RRC. Each UE will no longer use OCC to transmit PUSCH, and at the same time will no longer interpret DCI in the manner described in this solution.

[0207] Table 14 (RV cyclic sequence table)

[0208]

[0209]

[0210] Table 1 (OCC length indication table)

[0211] OCC length 2 4

[0212] Table 16 (OCC codeword indication table with OCC length of 4)

[0213]

[0214] Table 17 (OCC codeword indication table with OCC length of 2)

[0215]

[0216] Figure 14 It is a schematic flowchart of another wireless communication method provided by an embodiment of the present application to illustrate the above-mentioned solution three.

[0217] Figure 14 The method shown may include S1410 to S1460. The difference between this embodiment and the above-mentioned embodiment lies in S1420, where the second node indicates the RV value of the first node through DCI.

[0218] S1410, the second node configures OCC for the first node, and the first node obtains the required OCC length to be used.

[0219] Exemplarily, the gNB informs the UE of the required OCC length through RRC or MAC CE, and the OCC length can be one of the options shown in Table 15.

[0220] S1420, the second node sends DCI to the first node based on the PDCCH to dynamically schedule the PUSCH.

[0221] S1430, the first node retrieves the OCC codeword it should use from the OCC codeword indication table according to the "RV_OCC_cw_Idx" field in the DCI, and directly determines the RV value according to the "RV_OCC_cw_Idx" field in the DCI.

[0222] Among them, RV_OCC_cw_Idx is the redundancy version (RV) field in the original standard. In this embodiment, a part of the RV field is modified to indicate the OCC codeword, and another part of the RV field is used to indicate the RV value. For example, DCI0_1 can be used for PUSCH dynamic scheduling, and the RV field part therein is modified to indicate the OCC codeword, and a part of this field will be used to indicate the RV and another part to indicate the OCC codeword. For DCI0_1, the bit schematic diagram of its RV field is as shown in Figure 8 (b) shown, the size of its RV field is optional and needs to be pre-configured by the gNB or specified by the protocol, and its range is 2 to 8 bits.

[0223] It can be seen that in this embodiment, the first node can directly obtain the RV value through this field without self-inference or looking up a table.

[0224] S1440, the first node performs uplink transmission of the PUSCH based on the corresponding OCC codeword and RV value.

[0225] S1450, the second node receives and decodes the PUSCH sent by the first node.

[0226] S1460, the second node deconfigures the OCC for the first node based on RRC or MAC CE.

[0227] Exemplarily, assume that after step S1410, the OCC length obtained by the UE is 2, and the bit lengths preconfigured by the gNB for the OCC codeword and RV indication are both 1 bit. These 2 bits are combined into the RV_OCC_cw_Idx field in the DCI. Assume that the UE performs RV cycling according to the sequence {0 2}, then the UE can interpret the RV_OCC_cw_Idx field in the DCI according to Table 18. The gNB sends the DCI to the UE for dynamic scheduling of the PUSCH. Assume that the RV_OCC_cw_Idx field in the DCI is 10, then the UE can find the indicated OCC codeword as [1 -1] in Table 18 according to this, and determine the RV value as 0 according to the DCI.

[0228] Further described below in conjunction with Figure 15 the specific example shown, Figure 14 the method flow shown is specifically described.

[0229] Figure 15 The method shown may include S1510 to S1570.

[0230] S1510, UE1 and UE2 perform OCC multiplexing, the gNB configures the OCC for these 2 UEs, and at the same time each UE needs to obtain the OCC length it uses.

[0231] In this embodiment, it is determined whether the UE uses OCC by determining whether an indication signaling of the OCC length is received. Assume that the gNB configures these 2 UEs through RRC, uses the cross-slot OCC scheme, and assume that both 2 UEs have been configured with the OCC length by the gNB. Therefore, each UE will interpret the DCI in the subsequent DCI indication process in the way that all or part of the RV fields are interpreted as OCC codewords. For example, both UE1 and UE2 receive an OCC length of 2.

[0232] S1520, the gNB sends DCI to UE1 and UE2 based on the PDCCH to dynamically schedule the PUSCH.

[0233] S1530, UE1 and UE2 determine the RV value of the data that the UE1 and UE2 should transmit according to the RV_OCC_cw_Idx field in the DCI, and determine the OCC codeword required for spreading of the UE1 and UE2 according to the RV_OCC_cw_Idx field in the DCI.

[0234] In this embodiment, for UE1 and UE2, the RV_OCC_cw_Idx fields indicated by the gNB are 00 and 10 respectively. Therefore, each UE can retrieve its respective OCC codeword in Table 18. The OCC codeword of UE1 is [1 1], and the RV is 0; the OCC codeword of UE2 is [1 -1], and the RV value is determined to be 0 according to the RV_OCC_cw_Idx field in the DCI.

[0235] S1540, UE1 and UE2 perform uplink transmission of the PUSCH based on the corresponding RV value and OCC codeword.

[0236] In this embodiment, it is assumed that there is 1 OCC group in 1 PUSCH, that is, for each UE, 1 PUSCH will contain 2 repeated time slots, and the data transmitted by these time slots is the same (and the RV is also the same). Each time slot will be assigned one codeword (1 or -1) from the OCC codeword with a length of 2, and multiplying with the OCC codeword completes the OCC spreading operation.

[0237] S1550, the gNB receives and decodes the PUSCH sent by UE1 and UE2.

[0238] Optionally, S1560, the gNB continues to send DCI to UE1 and UE2 for subsequent initial transmission or retransmission scheduling of the PUSCH.

[0239] S1570, the gNB deconfigures the OCC for the UE based on the RRC or MAC CE.

[0240] Table 18 (OCC codeword indication table)

[0241]

[0242] The present application solves the problem of the UE obtaining the RV value and the OCC codeword in the case of using OCC for DG-PUSCH through any of the above embodiments, and has the following gains:

[0243] (1) The present application does not need to modify the size of the DCI, nor does it modify other fields except for the RV, thus greatly avoiding the modification of the DCI format in the original standard.

[0244] (2) The solution of this application can be applied to the DCI for scheduling PUSCH, that is, DCI0_0 to DCI0_3, because the RV field is a field that all DCI for scheduling PUSCH have.

[0245] (3) The indication process of the joint coding table in the first solution of this application can indicate the OCC length at the same time, so as to avoid or simplify the additional OCC length indication process. And the three solutions of this application can all indicate whether the UE uses OCC during the configuration process before scheduling, so as to avoid the additional indication process of whether to use OCC.

[0246] As described above in conjunction with Figures 1 to 15 , the method embodiments of this application have been described in detail. Next, in conjunction with Figures 16 to 19 , the device embodiments of this application will be described in detail. It should be understood that the descriptions of the method embodiments correspond to those of the device embodiments. Therefore, for the parts not described in detail, reference can be made to the previous method embodiments.

[0247] Figure 16 A first node for wireless communication provided by an embodiment of this application. The first node can be any kind of terminal device. As Figure 16 shown, the first node 1000 includes a first transceiver module 1610 and a first processing module 1620.

[0248] In some embodiments, the first transceiver module 1610 can be used to receive first information; wherein, the first information is used to indicate the first orthogonal cover code (OCC) codeword of the first node; the first node belongs to a first OCC group, and nodes in the same OCC group use the same redundancy version (RV) value

[0249] In some embodiments, the first information is carried in all or part of the RV field in the downlink scheduling information (DCI).

[0250] In some embodiments, the first information is also used to indicate the redundancy version (RV) value of the first node.

[0251] In some embodiments, the first transceiver module 1610 is further used to: receive second information; wherein, the second information is used to indicate the joint coding table corresponding to the first node, and the joint coding table includes OCC codewords.

[0252] In some embodiments, the joint coding table further includes the RV value corresponding to the OCC codeword and / or the OCC codeword length.

[0253] In some embodiments, it further includes: a first processing module 1620, configured to determine the first OCC codeword from the joint coding table corresponding to the first node according to the first information and the second information.

[0254] In some embodiments, the first processing module 1620 is further configured to determine a current RV value from the joint coding table corresponding to the first node according to the first information and the second information.

[0255] In some embodiments, the first transceiver module 1610 is further configured to receive third information, where the third information is used to indicate an RV cyclic sequence;

[0256] In some embodiments, the first processing module 1620 is configured to determine the first OCC codeword from the joint coding table corresponding to the first node according to the first information; and determine the current RV value according to the third information.

[0257] In some embodiments, the first transceiver module 1610 is further configured to: perform uplink transmission based on the RV value and the first OCC codeword.

[0258] In some embodiments, the first transceiver module 1610 is further configured to: receive fourth information, where the fourth information is used to indicate the OCC codeword length used by the first node.

[0259] In some embodiments, it further includes: a first processing module 1620, configured to: determine whether to use the OCC codeword for uplink transmission based on the OCC codeword length.

[0260] As an embodiment, the first transceiver module 1610 may be a transceiver 1830, and the first processing module 1620 may be a processor 1810. The first node 1600 may further include a memory 1820, specifically as Figure 18 shown.

[0261] Figure 17 A second node for wireless provided by an embodiment of the present application. The second node may be a network device or a terminal device. As Figure 17 shown, the second node 1700 includes a second transceiver module 1710.

[0262] The second transceiver module 1710 is configured to send first information; where the first information is used to indicate the first orthogonal coverage code (OCC) codeword of the first node; the first node belongs to a first OCC group, and nodes in the same OCC group use the same RV value.

[0263] In some embodiments, the first information is carried in all or part of the RV fields in the downlink scheduling information (DCI).

[0264] In some embodiments, the first information is further used to indicate the redundancy version (RV) value of the first node.

[0265] In some embodiments, the second transceiver module 1710 is further configured to: send second information; wherein the second information is used to indicate the joint coding table corresponding to the first node, and the joint coding table includes OCC codewords.

[0266] In some embodiments, the joint coding table further includes the RV value corresponding to the OCC codeword and / or the OCC codeword length.

[0267] In some embodiments, the second transceiver module 1710 is further configured to: send third information, wherein the third information is used to indicate the RV cyclic sequence.

[0268] In some embodiments, the second transceiver module 1710 is further configured to: receive uplink transmission information.

[0269] As an embodiment, the second transceiver module 1710 may be a transceiver 1830. The second node 1700 may further include a processor 1810 and a memory 1820, specifically as Figure 18 shown.

[0270] Figure 18 is a schematic structural diagram of a communication device according to an embodiment of the present application. Figure 18 The dashed lines in indicate that the unit or module is optional. The device 1800 can be used to implement the method described in the above method embodiments. The device 1800 can be a chip, a user equipment or a network equipment.

[0271] The device 1800 may include one or more processors 1810. The one or more processors 1810 enable the device 1800 to implement the method described in the foregoing method embodiments. The processor 1810 can be a general-purpose processor or a dedicated processor. For example, the processor can be a central processing unit (CPU). Alternatively, the processor can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., and any combination of the foregoing. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0272] The apparatus 1800 may further include one or more memories 1820. Programs are stored on the memories 1820, which can be executed by the processor 1810, so that the processor 1810 executes the methods described in the foregoing method embodiments. The memories 1820 may be independent of the processor 1810 or integrated in the processor 1810.

[0273] The apparatus 1800 may further include a transceiver 1830. The processor 1810 may communicate with other devices or chips through the transceiver 1830. For example, the processor 1810 may transmit and receive data with other devices or chips through the transceiver 1830.

[0274] Figure 19 Schematic diagram of the hardware module of the communication device provided by the embodiments of the present application. Specifically, Figure 19 A block diagram showing a first communication device 1950 and a second communication device 1910 that communicate with each other in an access network is shown.

[0275] The first communication device 1950 includes a controller / processor 1959, a memory 1960, a data source 1967, a transmitting processor 1968, a receiving processor 1956, a multi-antenna transmitting processor 1957, a multi-antenna receiving processor 1958, a transmitter / receiver 1954, and an antenna 1952.

[0276] The second communication device 1910 includes a controller / processor 1975, a memory 1976, a data source 1977, a receiving processor 1970, a transmitting processor 1916, a multi-antenna receiving processor 1972, a multi-antenna transmitting processor 1971, a transmitter / receiver 1918, and an antenna 1920.

[0277] In the transmission from the second communication device 1910 to the first communication device 1950, at the second communication device 1910, upper layer data packets from the core network or from the data source 1977 are provided to the controller / processor 1975. The core network and the data source 1977 represent all protocol layers above the L2 layer. The controller / processor 1975 implements the functionality of the L2 layer. In the transmission from the second communication device 1910 to the first communication device 1950, the controller / processor 1975 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 1950 based on various priority metrics. The controller / processor 1975 is also responsible for retransmission of lost packets and signaling to the first communication device 1950. The transmit processor 1916 and the multi-antenna transmit processor 1971 implement various signal processing functions for the Ll layer (i.e., the physical layer). The transmit processor 1916 implements encoding and interleaving to facilitate forward error correction at the second communication device 1910, and mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying, quadrature phase shift keying, M-phase shift keying, M-quadrature amplitude modulation). The multi-antenna transmit processor 1971 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. The transmit processor 1916 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then uses the inverse fast Fourier transform to generate a physical channel carrying a time-domain multi-carrier symbol stream. Subsequently, the multi-antenna transmit processor 1971 performs transmit analog precoding / beamforming operations on the time-domain multi-carrier symbol stream. Each transmitter 1918 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 1971 into a radio frequency stream and then provides it to different antennas 1920.

[0278] In the transmission from the second communication device 1910 to the first communication device 1950, at the first communication device 1950, each receiver 1954 receives signals via its respective antenna 1952. Each receiver 1954 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream provided to the receive processor 1956. The receive processor 1956 and the multi-antenna receive processor 1958 perform various signal processing functions of the L1 layer. The multi-antenna receive processor 1958 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receivers 1954. The receive processor 1956 uses the fast Fourier transform to convert the baseband multi-carrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receive processor 1956, where the reference signal will be used for channel estimation, and the data signal recovers any spatial streams destined for the first communication device 1950 after multi-antenna detection in the multi-antenna receive processor 1958. The symbols on each spatial stream are demodulated and recovered in the receive processor 1956, and soft decisions are generated. Subsequently, the receive processor 1956 decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 1910 on the physical channel. Subsequently, the upper layer data and control signals are provided to the controller / processor 1959. The controller / processor 1959 performs the functions of the L2 layer. The controller / processor 1959 may be associated with a memory 1960 that stores program code and data. The memory 1960 may be referred to as a computer-readable medium. In the transmission from the second communication device 1910 to the first communication device 1950, the controller / processor 1959 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the second communication device 1910. Subsequently, the upper layer data packets are provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 for L3 processing.

[0279] In the transmission from the first communication device 1950 to the second communication device 1910, at the first communication device 1950, an upper layer data packet is provided to the controller / processor 1959 using the data source 1967. The data source 1967 represents all protocol layers above the L2 layer. Similar to the transmission function described at the second communication device 1910 in the transmission from the second communication device 1910 to the first communication device 1950, the controller / processor 1959 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels, and implements L2 layer functions for the user plane and the control plane. The controller / processor 1959 is also responsible for retransmitting lost packets and signaling to the second communication device 1910. The transmit processor 1968 performs modulation mapping and channel coding processing. The multi-antenna transmit processor 1957 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Subsequently, the transmit processor 1968 modulates the generated spatial streams into multi-carrier / single-carrier symbol streams, and after analog precoding / beamforming operations in the multi-antenna transmit processor 1957, provides them to different antennas 1952 via the transmitter 1954. Each transmitter 1954 first converts the baseband symbol stream provided by the multi-antenna transmit processor 1957 into a radio frequency symbol stream and then provides it to the antenna 1952.

[0280] In the transmission from the first communication device 1950 to the second communication device 1910, the functions at the second communication device 1910 are similar to the receiving functions described at the first communication device 1950 in the transmission from the second communication device 1910 to the first communication device 1950. Each receiver 1918 receives radio frequency signals through its corresponding antenna 1920, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receive processor 1972 and the receive processor 1970. The receive processor 1970 and the multi-antenna receive processor 1972 jointly implement the Ll layer functions. The controller / processor 1975 implements the L2 layer functions. The controller / processor 1975 may be associated with a memory 1976 that stores program code and data. The memory 1976 may be referred to as a computer-readable medium. In the transmission from the first communication device 1950 to the second communication device 1910, the controller / processor 1975 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packets from the first communication device 1950. The upper layer data packets from the controller / processor 1975 may be provided to the core network or all protocol layers above the L2 layer, and various control signals may also be provided to the core network or L3 for L3 processing.

[0281] As an embodiment, the first communication device 1950 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor.

[0282] As an embodiment, the first communication device 1950 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program causing actions when executed by at least one processor.

[0283] As an embodiment, the first communication device 1950 corresponds to the first node in the present application.

[0284] As an embodiment, the second communication device 1910 corresponds to the second node in the present application.

[0285] As an embodiment, the first communication device 1950 is a user equipment, and this user equipment can act as a relay node.

[0286] As an embodiment, the first communication device 1950 is a network control relay.

[0287] As an embodiment, the first communication device 1950 is a relay wireless repeater.

[0288] As an embodiment, the first communication device 1950 is a relay.

[0289] As an embodiment, the first communication device 1950 is a V2X-supported terminal device, and this terminal device can act as a relay node. As an embodiment, the first communication device 1950 is a D2D-supported terminal device, and this terminal device can act as a relay node.

[0290] As an embodiment, the second communication device 1910 is a base station.

[0291] As an embodiment, the antenna 1952, the receiver 1954, the multi-antenna receiving processor 1958, the receiving processor 1956, and the controller / processor 1959 are used to receive messages.

[0292] As an embodiment, the antenna 1952, the receiver 1954, the multi-antenna receiving processor 1958, the receiving processor 1956, and the controller / processor 1959 are used to update parameters according to messages.

[0293] As an example, the antenna 1920, the transmitter 1918, the multi-antenna transmission processor 1971, the transmission processor 1916, and the controller / processor 1975 are used to send messages.

[0294] An embodiment of the present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the terminal or network device provided in the embodiment of the present application, and the program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of the present application.

[0295] An embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal or network device provided in the embodiment of the present application, and the program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of the present application.

[0296] An embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided in the embodiment of the present application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of the present application.

[0297] It should be understood that the terms "system" and "network" in the present application can be used interchangeably. Additionally, the terms used in the present application are only for explaining the specific embodiments of the present application and are not intended to limit the present application. The terms "first", "second", "third", and "fourth", etc. in the specification, claims, and drawings of the present application are used to distinguish different objects rather than to describe a specific order. Furthermore, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion.

[0298] In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or can also represent an associated relationship. For example, A indicates B, which can mean that A directly indicates B. For example, B can be obtained through A; it can also mean that A indirectly indicates B. For example, A indicates C, and B can be obtained through C; it can also mean that there is an associated relationship between A and B.

[0299] In the embodiments of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A. B can also be determined according to A and / or other information.

[0300] In the embodiments of the present application, the term "corresponding" can represent a direct or indirect corresponding relationship between two things, can also represent an associated relationship between two things, or can also be a relationship such as indication and being indicated, configuration and being configured, etc.

[0301] In the embodiments of the present application, "predefined" or "preconfigured" can be implemented by pre-saving corresponding codes, tables or other means that can be used to indicate relevant information in a device (for example, including user equipment and network equipment). The present application does not limit its specific implementation manner. For example, predefined can refer to that defined in a protocol.

[0302] In the embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field. For example, it can include LTE protocol, NR protocol, and related protocols applied to future communication systems. The present application does not limit this.

[0303] In the embodiments of the present application, the term "and / or" is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0304] In various embodiments of the present application, the magnitudes of the serial numbers of the above processes do not mean the order of execution. The execution order of each process should be determined by its function and internal logic. Two or more of the steps can be combined into one step, and it should not constitute any limitation to the implementation process of the embodiments of the present application.

[0305] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical or other form.

[0306] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place, or can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0307] In addition, in each embodiment of the present application, the functional units can be integrated in one processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0308] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more integrated available media. The available medium may be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0309] As described above, the foregoing are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily conceive of changes or substitutions within the technical scope disclosed in the present application, and all such changes or substitutions should be covered by the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method in a first node for wireless communication, characterized in that, including: receiving first information; wherein, the first information is used to indicate a first orthogonal cover code (OCC) codeword of the first node; the first node belongs to a first OCC group, and nodes in the same OCC group use the same redundancy version (RV) value.

2. The method according to claim 1, wherein the first information is carried in all or part of the RV fields in the downlink control information (DCI).

3. The method according to claim 1 or 2, characterized in that, the first information is further used to indicate the redundancy version (RV) value of the first node.

4. The method according to claim 1 or 2, characterized in that, further including: receiving second information; wherein, the second information is used to indicate a joint coding table corresponding to the first node, and the joint coding table includes OCC codewords.

5. The method according to claim 4, characterized in that, the joint coding table further includes the RV value corresponding to the OCC codeword and / or the length of the OCC codeword.

6. The method according to claim 4, wherein further including: determining the first OCC codeword from the joint coding table corresponding to the first node according to the first information and the second information.

7. The method according to claim 6, characterized in that further including: determining the current RV value from the joint coding table corresponding to the first node according to the first information and the second information.

8. The method according to claim 4, characterized in that further including: receiving third information, wherein the third information is used to indicate an RV cyclic sequence; determining the first OCC codeword from the joint coding table corresponding to the first node according to the first information; and determining the current RV value according to the third information.

9. The method according to claim 7 or 8, characterized in that, further including: performing an uplink transmission based on the RV value and the first OCC codeword.

10. The method according to claim 1 or 2, characterized in that, further including: receiving fourth information, and the fourth information is used to indicate the length of the OCC codeword used by the first node.

11. The method according to claim 10, characterized in that, further including: determining whether to use the OCC codeword for uplink transmission based on the length of the OCC codeword.

12. A method in a second node for wireless communication, characterized in that, including: sending first information; wherein, the first information is used to indicate a first orthogonal cover code (OCC) codeword of a first node; the first node belongs to a first OCC group, and nodes in the same OCC group use the same RV value.

13. The method according to claim 12, wherein the first information is carried in all or part of the RV fields in the downlink control information (DCI).

14. The method according to claim 12 or 13, characterized in that the first information is further used to indicate the redundancy version (RV) value of the first node.

15. The method according to claim 12 or 13, characterized in that further including: sending second information; wherein, the second information is used to indicate a joint coding table corresponding to the first node, and the joint coding table includes OCC codewords.

16. The method according to claim 15, characterized in that, the joint coding table further includes the RV value corresponding to the OCC codeword and / or the length of the OCC codeword.

17. The method according to claim 15, wherein further including: sending third information, wherein the third information is used to indicate an RV cyclic sequence.

18. The method according to claim 12, characterized in that further including: receiving uplink transmission information.

19. A first node for wireless communication, characterized in that, characterized by including: a first transceiver module, configured to receive first information; wherein, the first information is used to indicate a first orthogonal cover code (OCC) codeword of the first node; the first node belongs to a first OCC group, and nodes in the same OCC group use the same redundancy version (RV) value.

20. The first node according to claim 19, characterized in that, the first information is carried in all or part of the RV fields in the downlink control information (DCI).

21. The first node according to claim 19 or 20, characterized in that, the first information is further used to indicate the redundancy version (RV) value of the first node.

22. The first node according to claim 19 or 20, characterized in that, the first transceiver module is further configured to: receive second information; wherein, the second information is used to indicate a joint coding table corresponding to the first node, and the joint coding table includes OCC codewords.

23. The first node according to claim 22, wherein The combined coding table further includes the RV value corresponding to the OCC codeword and / or the OCC codeword length.

24. The first node according to claim 22, wherein Further included: A first processing module, configured to determine the first OCC codeword from the combined coding table corresponding to the first node according to the first information and the second information.

25. The first node according to claim 24, wherein: The first processing module is further configured to determine the current RV value from the combined coding table corresponding to the first node according to the first information and the second information.

26. The first node according to claim 22, wherein: The first transceiver module is further configured to receive third information, where the third information is used to indicate the RV cyclic sequence; Further included: A first processing module, configured to determine the first OCC codeword from the combined coding table corresponding to the first node according to the first information; and determine the current RV value according to the third information.

27. The first node according to claim 25 or 26, characterized in that, The first transceiver module is further configured to: Perform uplink transmission based on the RV value and the first OCC codeword.

28. The first node according to claim 19 or 20, characterized in that, The first transceiver module is further configured to: Receive fourth information, where the fourth information is used to indicate the OCC codeword length used by the first node.

29. The first node according to claim 28, wherein Further included: A first processing module, configured to: determine whether to use the OCC codeword for uplink transmission based on the OCC codeword length.

30. A second node for wireless communication, characterized in that, Included: A second transceiver module, configured to send first information; where the first information is used to indicate the first orthogonal coverage code (OCC) codeword of the first node; The first node belongs to a first OCC group, and nodes in the same OCC group use the same redundancy version (RV) value.

31. The second node according to claim 30, wherein The first information is carried in all or part of the RV fields in the downlink scheduling information (DCI).

32. The second node according to claim 30 or 31, characterized in that The first information is further used to indicate the redundancy version (RV) value of the first node.

33. The second node according to claim 30 or 31, characterized in that, The second transceiver module is further configured to: Send second information; where the second information is used to indicate the combined coding table corresponding to the first node, and the combined coding table includes OCC codewords.

34. The second node according to claim 33, characterized in that, The combined coding table further includes the RV value corresponding to the OCC codeword and / or the OCC codeword length.

35. The second node according to claim 33, wherein The second transceiver module is further configured to: Send third information, where the third information is used to indicate the RV cyclic sequence.

36. The second node according to claim 32, characterized in that, The second transceiver module is further configured to: Receive uplink transmission information.

37. A node used for wireless communication, characterized in that, Including a transceiver, a memory, and a processor, where the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals, so that the node executes the method according to any one of claims 1-11 or 12-18.

38. A communication device, characterized in that, Including a processor, configured to call a program from a memory, so that the device executes the method according to any one of claims 1-11 or 12-18.

39. A chip, characterized in that, Including a processor, configured to call a program from a memory, so that the device installed with the chip executes the method according to any one of claims 1-11 or 12-18.

40. A computer-readable storage medium, characterized in that, Stored thereon is a program, and the program causes a computer to execute the method according to any one of claims 1-11 or 12-18.

41. A computer program product, characterized in that, Comprising a program that causes a computer to perform the method according to any one of claims 1 - 11 or 12 - 18.

42. A computer program, characterized in that, The computer program causes a computer to perform the method according to any one of claims 1 - 11 or 12 - 18.

Images