Method and apparatus for wireless communication

Abstract

A method and apparatus for wireless communication are provided to enhance uplink capacity and coverage. The method comprises the following steps: a first terminal device performs repeated transmission of first uplink data according to a first sequence; wherein the first sequence is one of a plurality of mutually orthogonal sequences, the plurality of sequences are used for multiplexing a first resource by a plurality of terminal devices, the first resource is used for repeatedly transmitting a plurality of uplink data by the plurality of terminal devices, and the plurality of terminal devices comprise the first terminal device. The plurality of pieces of uplink data comprise the first uplink data.

Description

Technical Field

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

[0002] In a non-terrestrial network (NTN) system, due to long transmission delays and large path losses, a terminal device can enhance the uplink capacity and reliability by repeatedly transmitting multiple times. However, an NTN cell needs to serve a large number of terminal devices. Therefore, how to improve uplink coverage enhancement and spectrum utilization efficiency in an NTN system has become a technical problem that urgently needs to be solved. Summary of the Invention

[0003] This application provides a method and apparatus for wireless communication. The following introduces various aspects related to the embodiments of this application.

[0004] In a first aspect, a method for wireless communication is provided, including: a first terminal device repetitively transmits first uplink data according to a first sequence; wherein, the first sequence belongs to a plurality of mutually orthogonal sequences, the plurality of sequences are used for a plurality of terminal devices to multiplex a first resource, the first resource is used for the plurality of terminal devices to respectively perform repetitive transmissions of a plurality of uplink data, the plurality of terminal devices include the first terminal device, and the plurality of uplink data include the first uplink data.

[0005] In a second aspect, a method for wireless communication is provided, including: a network device receives repetitive transmissions of a plurality of uplink data from a plurality of terminal devices; wherein, the repetitive transmissions of the plurality of uplink data are multiplexed on a first resource based on a plurality of mutually orthogonal sequences, the plurality of sequences include a first sequence, the first sequence is used for a first terminal device among the plurality of terminal devices to perform repetitive transmission of first uplink data, and the plurality of uplink data include the first uplink data.

[0006] In a third aspect, a device for wireless communication is provided, the device being a first terminal device, the device including: a transceiver unit, configured to repetitively transmit first uplink data according to a first sequence; wherein, the first sequence belongs to a plurality of mutually orthogonal sequences, the plurality of sequences are used for a plurality of terminal devices to multiplex a first resource, the first resource is used for the plurality of terminal devices to respectively perform repetitive transmissions of a plurality of uplink data, the plurality of terminal devices include the first terminal device, and the plurality of uplink data include the first uplink data.

[0007] Fourth aspect, a device for wireless communication is provided. The device is a network device and includes a transceiver unit configured to receive repeated transmissions of multiple uplink data from multiple terminal devices. Among them, the repeated transmissions of the multiple uplink data multiplex a first resource based on multiple mutually orthogonal sequences. The multiple sequences include a first sequence, and the first sequence is used for a first terminal device among the multiple terminal devices to perform repeated transmission of first uplink data. The multiple uplink data include the first uplink data.

[0008] Fifth aspect, a communication device is provided, including a memory and a processor. The memory is configured to store a program, and the processor is configured to call the program in the memory to execute the method described in the first aspect or the second aspect.

[0009] Sixth aspect, a device is provided, including a processor configured to call a program from a memory to execute the method described in the first aspect or the second aspect.

[0010] Seventh aspect, a chip is provided, including a processor configured to call a program from a memory, such that a device installed with the chip executes the method described in the first aspect or the second aspect.

[0011] Eighth aspect, a computer-readable storage medium is provided, on which a program is stored. The program causes a computer to execute the method described in the first aspect or the second aspect.

[0012] Ninth aspect, a computer program product is provided, including a program. The program causes a computer to execute the method described in the first aspect or the second aspect.

[0013] Tenth aspect, a computer program is provided. The computer program causes a computer to execute the method described in the first aspect or the second aspect.

[0014] In the embodiments of the present application, the first terminal device may determine a first sequence for repeatedly transmitting first uplink data based on multiple mutually orthogonal sequences. The multiple mutually orthogonal sequences can be used for multiple terminal devices including the first terminal device to multiplex a first resource. Thus, multiple terminal devices can perform repeated transmissions of uplink data on the first resource based on orthogonal sequences, thereby effectively enhancing the uplink capacity and improving the spectrum utilization efficiency. Description of the Drawings

[0015] Figure 1 is a wireless communication system to which the embodiments of the present application are applied.

[0016] Figure 2 is an NTN system to which the embodiments of the present application are applied.

[0017] Figure 3It is another NTN system to which the embodiments of the present application are applied.

[0018] Figure 4 It is a schematic flowchart of a method for wireless communication provided by an embodiment of the present application.

[0019] Figure 5 It is Figure 4 A schematic diagram of a possible implementation manner of the method shown.

[0020] Figure 6 It is Figure 4 A schematic diagram of another possible implementation manner of the method shown.

[0021] Figure 7 It is Figure 4 A schematic diagram of yet another possible implementation manner of the method shown.

[0022] Figure 8 It is Figure 4 A schematic flowchart of a possible implementation manner of the method shown.

[0023] Figure 9 It is a schematic structural diagram of a device for wireless communication provided by an embodiment of the present application.

[0024] Figure 10 It is a schematic structural diagram of another device for wireless communication provided by an embodiment of the present application.

[0025] Figure 11 It is a schematic structural diagram of a communication device provided by an embodiment of the present application. Detailed implementation manners

[0026] Next, the technical solutions in the embodiments of the present application will be described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application.

[0027] Embodiments of the present application can be applied to various communication systems. For example: Embodiments of the present application can be applied to a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS) system, a long term evolution (LTE) system, an advanced long term evolution (LTE-A) system, a new radio (NR) system, an evolved system of the NR system, an LTE-based access to unlicensed spectrum (LTE-U) system, an NR-based access to unlicensed spectrum (NR-U) system, a universal mobile telecommunication system (UMTS), a wireless local area networks (WLAN) system, a wireless fidelity (WiFi) system, a 5th-generation (5G) communication system. Embodiments of the present application can also be applied to other communication systems, such as a 6th-generation (6G) mobile communication system, or a future communication system such as a satellite communication system, etc.

[0028] Traditional communication systems support a limited number of connections and are also easy to implement. However, with the development of communication technologies, communication systems can not only support traditional cellular communications, but also support one or more other types of communications. For example, a communication system can support one or more of the following communications: device to device (D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), enhanced MTC (eMTC), vehicle to vehicle (V2V) communication, and vehicle to everything (V2X) communication, etc. Embodiments of this application can also be applied to communication systems that support the above communication methods.

[0029] The communication system in the embodiments of this application can be applied to a carrier aggregation (CA) scenario, can also be applied to a dual connectivity (DC) scenario, and can also be applied to a standalone (SA) networking scenario.

[0030] The communication system in the embodiments of this application can be applied to unlicensed spectrum. This unlicensed spectrum can also be considered as shared spectrum. Alternatively, the communication system in the embodiments of this application can also be applied to licensed spectrum. This licensed spectrum can also be considered as dedicated spectrum.

[0031] Embodiments of this application can be applied to an NTN system. As an example, this NTN system can be an NTN system based on 4G, can be an NTN system based on NR, can also be an NTN system based on the internet of things (IoT) or an NTN system based on narrow band internet of things (NB-IoT).

[0032] A communication system can include one or more terminal devices. The terminal devices mentioned in the embodiments of this application can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc.

[0033] In some embodiments, the terminal device may be a station (ST) in a WLAN. In some embodiments, the terminal device may be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication function, computing device, or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a next-generation communication system (such as an NR system), or terminal device in a future evolved public land mobile network (PLMN) network, etc.

[0034] In some embodiments, the terminal device may be a device that provides voice and / or data connectivity to the user. For example, the terminal device may be a handheld device, in-vehicle device, etc. with wireless connection function. As some specific examples, the terminal device may be a mobile phone, tablet (Pad), laptop, palmtop computer, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.

[0035] In some embodiments, the terminal device may be deployed on land. For example, the terminal device may be deployed indoors or outdoors. In some embodiments, the terminal device may be deployed on water, such as on a ship. In some embodiments, the terminal device may be deployed in the air, such as on an airplane, balloon, and satellite.

[0036] In addition to the terminal device, the communication system may further include one or more network devices. The network device in the embodiments of the present application may be a device for communicating with the terminal device, and this network device may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. The base station may generally cover various names as follows, or be replaced with the following names, such as: Node B, evolved Node B (eNB), next generation Node B (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station may be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. The base station may also refer to a communication module, a modem or a chip disposed in the foregoing device or apparatus. The base station may also be a mobile switching center and a device that undertakes the base station function in D2D, V2X, M2M communications, a network-side device in a 6G network, a device that undertakes the base station function in a future communication system, etc. The base station may support networks of the same or different access technologies. The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the network device.

[0037] The base station may be fixed or mobile. For example, a helicopter or a drone may be configured to act as a mobile base station, and one or more cells may move according to the position of the mobile base station. In other examples, a helicopter or a drone may be configured to be a device for communicating with another base station.

[0038] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device includes a CU and a DU. The gNB may further include an AAU.

[0039] By way of example and not limitation, in the embodiments of the present application, the network device may have mobility characteristics. For example, the network device may be a mobile device. In some embodiments of the present application, the network device may be a satellite or a balloon station. In some embodiments of the present application, the network device may also be a base station located at positions such as on land or in water areas.

[0040] In the embodiments of the present application, the network device may provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or in other words, spectrum resources). The cell may be a cell corresponding to the network device (such as a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. Here, the small cell may include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage range and low transmission power, and are suitable for providing high-rate data transmission services.

[0041] Exemplarily, Figure 1 It is a schematic diagram of the architecture of a wireless communication system provided for the embodiments of the present application. Figure 1 The shown wireless communication system 100 includes a network device and multiple terminal devices. The network device 110 may provide communication coverage for a specific geographical area and may communicate with the terminal devices located within the coverage area. Multiple terminal devices such as Figure 1 the terminal devices 120a to 120j among them.

[0042] Optionally, Figure 1 the shown wireless communication system 100 may also include multiple network devices and the coverage range of each network device may include other numbers of terminal devices. The embodiments of the present application do not limit this.

[0043] Exemplarily, Figure 2 It is a schematic diagram of an architecture of the NTN system mentioned above. Figure 2 The shown NTN system 200 uses the satellite 210 as an aerial platform. As Figure 2 shown, the satellite radio access network includes the satellite 210, the serving link 220, the feeder link 230, the terminal device 240, the gateway (GW) 250, and the network 260 including the base station and the core network.

[0044] The satellite 210 is a space-based spacecraft. The service link 220 refers to the link between the satellite 210 and the terminal device 240. The feeder link 230 refers to the link between the gateway 250 and the satellite 210. The earth-based gateway 250 connects the satellite 210 to the base station or the core network, depending on the choice of the NTN architecture.

[0045] Figure 2 The NTN architecture shown is a bent-pipe transponder architecture. In this architecture, the base station is located on the earth behind the gateway 250, and the satellite 210 acts as a relay. The satellite 210 operates as a repeater to forward the signals of the feeder link 230 to the service link 220, or to forward the signals of the service link 220 to the feeder link 230. That is to say, the satellite 210 does not have the function of a base station, and the communication between the terminal device 240 and the base station in the network 260 needs to be relayed by the satellite 210.

[0046] Exemplarily, Figure 3 is another schematic diagram of the NTN system architecture. As Figure 3 shown, the satellite radio access network 300 includes a satellite 310, a service link 320, a feeder link 330, a terminal device 340, a gateway 350, and a network 360. Different from Figure 2 the above, there is a base station 312 on the satellite 310, and the network 360 behind the gateway 350 only includes the core network.

[0047] Figure 3 The NTN architecture shown is a regenerative transponder architecture. In this architecture, the satellite 310 carries the base station 312 and can be directly connected to the earth-based core network through a link. The satellite 310 has the function of a base station, and the terminal device 340 can communicate directly with the satellite 310. Therefore, the satellite 310 can be called a network device.

[0048] In Figure 2 and Figure 3 the communication systems of the shown architectures, multiple network devices may be included, and other numbers of terminal devices may be included within the coverage range of each network device. The embodiments of the present application do not limit this.

[0049] In the embodiments of the present application, Figures 1 to 3 the shown communication system may further include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF). The embodiments of the present application do not limit this.

[0050] It should be understood that in the embodiments of the present application, a device with communication functions in the network / system may be called a communication device.Figure 1 Taking the illustrated communication system 100 as an example, the communication devices may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above, which will not be elaborated here; the communication devices may also include other devices in the communication system 100, such as other network entities like a network controller and a mobility management entity. The embodiments of the present application do not limit this.

[0051] For ease of understanding, some related technical knowledge involved in the embodiments of the present application will be introduced first. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them 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.

[0052] With the development of communication technologies, communication systems (e.g., 5G) will integrate the market potential of satellite and terrestrial network infrastructures. For example, the 5G standard makes NTN including the satellite segment a recognized part of the 5G connection infrastructure of the 3rd generation partnership project (3GPP).

[0053] NTN refers to a network or network segment that uses radio frequency (RF) resources on a spacecraft (e.g., a satellite) or an unmanned aerial system (UAS) platform. Satellites are classified into low earth orbit (LEO) satellites, medium earth orbit (MEO) satellites, geostationary earth orbit (GEO) satellites, high elliptical orbit (HEO) satellites, etc. according to different orbital altitudes. Among them, LEO is an earth-centered orbit with a height of 2000 kilometers or less, or at least 11.25 cycles per day, and an eccentricity of less than 0.25. Most artificial objects in outer space are located in LEO. LEO satellites orbit the earth at high speed (mobility) but in a predictable or determinable orbit.

[0054] Satellites with different orbital altitudes have different orbital periods. Exemplarily, the typical height of LEO is 250 - 1500 kilometers, and the orbital period is 90 - 120 minutes; the typical height of MEO is 5000 - 25000 kilometers, and the orbital period is 3 - 15 hours; the height of GEO is about 35786 kilometers, and the orbital period is 24 hours.

[0055] As described above with the satellite as an example Figure 2 andFigure 3 It can be seen that typical scenarios for a terminal device to access an NTN system involve NTN transparent payloads or NTN regenerative payloads. Among them, Figure 2 The shown bent pipe transponder architecture corresponds to NTN transparent payloads, and the satellite or UAS platform acts as a relay; Figure 3 The shown regenerative transponder architecture corresponds to NTN regenerative payloads, and there is a base station on the satellite or UAS platform. In Figure 2 and Figure 3 In the shown network architecture, the base station can be involved in various communication systems, such as NB-IoT.

[0056] In an NTN system, a terminal device communicates with network devices through a spaceborne or airborne platform. Since the coverage area of an aerial platform such as a satellite is large, the number of terminal devices served in an NTN cell is usually much larger than that in a terrestrial network (TN) cell. To meet the uplink transmission requirements of terminal devices in the cell, the communication requirements of the uplink are usually relatively large. Therefore, in an NTN system, how to enhance the capacity and coverage of the uplink and improve the spectrum utilization efficiency is a problem worthy of research.

[0057] As an example, in communication systems such as NTN based on the Internet of Things, the number of available spectrums in a serving cell is limited, and the serving cell needs to serve a large number of terminal devices. Therefore, how to improve the uplink capacity of the system is a technical problem that needs to be solved.

[0058] To enhance the capacity and coverage of the uplink in an NTN system, relevant technologies can be introduced. In some embodiments, in an NTN system, retransmission (or repeated transmission) of the physical uplink shared channel (PUSCH) and / or hybrid automatic repeat request (HARQ) can be supported, but it will cause the burden and overhead of uplink transmission.

[0059] Optionally, retransmission of PUSCH can be dynamically scheduled via the physical downlink control channel (PDCCH), or triggered by configuring a retransmission timer. In addition to the dynamic scheduled transmission of PUSCH, semi-static PUSCH transmission can also be performed, i.e., configured grant (CG) or pre-configured grant. For configured grant type 1, all parameters for PUSCH transmission take effect immediately after being configured by radio resource control (RRC). For configured grant type 2, RRC configures a part of the high-layer parameters for PUSCH transmission, and the remaining parameters are indicated when activated by the downlink control information (DCI) format. The DCI also includes resource allocation indications in the frequency domain and time domain. For example, the DCI can point to the row index of a table through the time-domain resource indication field, and this row indicates the slot offset, start symbol, and number of symbols. The DCI can specify a part of a slot for uplink transmission and also support that the allocation of slot resources can be changed across different slots.

[0060] Optionally, some communication systems (e.g., NR) can configure PUSCH retransmission with repetition type A in a slot, i.e., repeated PUSCH transmission. For PUSCH repeated transmission, it is not indicated by table-based dynamic signaling, but configured through a separate RRC signaling. For example, for a scenario where the same transport block can be repeated on up to 8 slots, it is configured through RRC signaling.

[0061] In some embodiments, in the NTN system, orthogonal cover code (OCC) can also be used to improve the system capacity / frequency efficiency. For example, multiple terminal devices multiplex the same physical resource block (PRB) using OCC. Specifically, each terminal device can use the allocated sub-PRB, thereby generating a higher uplink capacity gain and maintaining uplink coverage. Among them, OCC is a technology that can achieve resource multiplexing in a communication system. OCC is a set of mutually orthogonal codewords that can be transmitted simultaneously on the same frequency resource without interfering with each other, thereby improving the uplink transmission efficiency of PUSCH.

[0062] Optionally, in a multi-user scenario, OCC can be used for resource allocation among multiple terminal devices in the same PRB. For example, the multiple terminal devices can select a set of orthogonal codes from the available OCC groups.

[0063] Optionally, due to the mutual orthogonality of OCC, the superimposed signals do not interfere with each other in the frequency domain, thus realizing multi-user frequency domain resource reuse. At the receiving end, corresponding demodulation and decoding techniques can be used to separate the superimposed signal into the original data of each user. However, in order to ensure that the superimposed signal can be effectively separated and decoded at the receiving end, appropriate synchronization and channel estimation need to be performed on each PRB to cope with the possible delay and channel fading in the transmission.

[0064] The PUSCH retransmission and OCC mechanisms that can enhance the uplink coverage are introduced above. In the NTN scenario, introducing OCC on PUSCH retransmission allows multiple terminal devices to use a large number of PUSCH retransmissions to meet the link budget requirements. However, the combination of PUSCH retransmission and OCC mechanisms will face new technical problems. This is because different terminal devices determine the retransmission configuration of PUSCH through DCI or RRC signaling. These terminal devices and their corresponding PUSCH retransmission configurations may be different. When these terminal devices perform PUSCH retransmission by multiplexing the same resources based on OCC, various problems may occur.

[0065] For example, the number of PUSCH retransmissions of different terminal devices is different, so the required resource sizes are different.

[0066] For another example, the PUSCH retransmission resources of some terminal devices may need to be multiplexed with uplink control information (UCI). UCI multiplexing is an important feature of the physical uplink control channel (PUCCH), which will improve the transmission delay and robustness. When UCI is multiplexed on one of the multiple PUSCH retransmissions, due to the different signal structures of the PUSCH retransmissions, the orthogonality within the OCC group will be destroyed. Therefore, if UCI is multiplexed on one of the PUSCH retransmissions, OCC will not be used for these PUSCH retransmissions. It can be seen that it is difficult to jointly configure UCI multiplexing and OCC, and it is necessary to avoid configuring OCC on the retransmissions with UCI multiplexing. In other words, for PUSCH transmissions with multiple retransmissions having OCC, UCI multiplexing needs to be avoided.

[0067] For another example, some terminal devices do not support OCC-based resource multiplexing or do not have the relevant capabilities of OCC. How to multiplex terminal devices with OCC capabilities and those without OCC capabilities is also an issue that needs to be considered.

[0068] In summary, in the NTN system, how to combine PUSCH repeated transmission and OCC to better improve the uplink capacity becomes a technical problem to be solved.

[0069] It should be noted that the problem of how to combine PUSCH repeated transmission and OCC in the NTN system mentioned above is only an example. The embodiments of the present application can be applied to any communication scenario where uplink data repeated transmission in NTN is combined with OCC, and are also applicable to the TN system.

[0070] In view of the above problems, the embodiments of the present application propose a method for wireless communication. Through this method, the first terminal device can perform repeated transmission of the first uplink data according to the first sequence. Multiple terminal devices can respectively multiplex the first resource based on a plurality of mutually orthogonal sequences to achieve repeated transmission of multiple uplink data, thereby enhancing the uplink capacity and coverage and improving the spectrum utilization rate by introducing orthogonal sequences in the repeated transmission of uplink data. Optionally, this method is mainly aimed at enhancing the uplink capacity and coverage in systems with long communication delays such as NTN. Therefore, the first terminal device and the network device can be the terminal device and the network-side device in NTN respectively.

[0071] For ease of understanding, the method proposed in the embodiments of the present application will be described in detail below. Figure 4 from the perspective of the interaction between the first terminal device and the network device. Figure 4 The first terminal device can be any type of communication terminal or relay for uplink transmission, which is not limited herein. In some embodiments, the first terminal device can be any terminal device in the NTN system, such as a UE. In some embodiments, the first terminal device can be any terminal device in the NB-IoT system, such as a meter. In some embodiments, the first terminal device can be any communication terminal within the coverage of the network device, such as

[0072] terminal devices 120a to 120j in Figure 1 .

[0073] As an embodiment, the first terminal device is located within the coverage area of the NTN satellite. For example, the first device is an NTN Internet of Things terminal.

[0074] As an embodiment, the first terminal device is a communication device that sends uplink data to the network-side device in any communication system.

[0075] In some embodiments, the first terminal device is any one of a plurality of terminal devices. The plurality of terminal devices may be at least two communication devices that reuse the same resources. The plurality of terminal devices that reuse the same resources may belong to a terminal device group, that is, the first terminal device group.

[0076] As an embodiment, the plurality of terminal devices that reuse the same resources as the first terminal device belong to the first terminal device group. One or more terminal devices that reuse the same resources as the first terminal device may also be referred to as paired devices of the first terminal device.

[0077] The network device may be any one of the aforementioned network-side communication devices. In some embodiments, the network device includes a satellite in the NTN system, and the first terminal device may communicate with the network device through the satellite. Exemplarily, when a base station is deployed on the satellite, the first terminal device communicates directly with the base station on the satellite. Exemplarily, when the satellite acts as a relay, the first terminal device communicates with a network device located on the ground through the satellite. As an embodiment, when the network device includes a satellite, the first terminal device is within the service area of the satellite at the current moment to perform an uplink transmission to the network device through the satellite.

[0078] In some embodiments, the plurality of terminal devices within the first terminal device group are within the coverage range of the same satellite at the current moment.

[0079] Figure 4 The method shown includes step S410, which will be introduced below.

[0080] In step S410, the first terminal device performs repeated transmission of first uplink data according to a first sequence. For the network device, it can receive repeated transmissions of a plurality of uplink data from a plurality of terminal devices.

[0081] The first uplink data may be any kind of data to be transmitted by the first terminal device. As an embodiment, the first uplink data may be a first transport block. As an embodiment, the first uplink data may include a first transport block. As an embodiment, the first uplink data may include a first codeword. As an embodiment, the first uplink data may be a first codeword.

[0082] In some embodiments, the first uplink data may be carried on an uplink channel. As an example, the first uplink data may be sent through a first uplink data channel. For example, the first uplink data may be carried on a first PUSCH.

[0083] As an example, the repeated transmission of the first uplink data can be sent through multiple data channels. For example, the repeated transmission of the first uplink data can be carried in multiple first PUSCHs of repeated transmission respectively, that is, the first PUSCH repeated transmission. That is to say, the repeated transmission of the first uplink data can be replaced by the repeated transmission of the first PUSCH.

[0084] In the above embodiment, the first PUSCH is repeatedly transmitted based on OCC, and this transmission can be referred to as PUSCH repeated within the OCC group.

[0085] In the above embodiment, multiple terminal devices including the first terminal device can respectively perform the repeated transmission of multiple uplink data. The repeated transmission of multiple uplink data can be replaced by the repeated transmission of multiple PUSCHs, that is, multiple PUSCH repeated transmissions.

[0086] In some embodiments, the repeated transmission of the first uplink data can be determined according to the configuration of the network side or a higher layer. As an example, the configuration of the first PUSCH repeated transmission can be indicated by DCI sent by a network device. As an example, the configuration of the first PUSCH repeated transmission can be indicated by a higher layer parameter.

[0087] As an example, the first PUSCH repeated transmission corresponding to the first terminal device can be dynamically scheduled by the uplink (UL) grant in DCI, or can be configured through different types of configured grants. That is to say, the configuration of the first PUSCH repeated transmission can be semi-static scheduling or dynamic scheduling, which is not limited herein.

[0088] In the above embodiment, different types of configured grants include the configured grant type 1 and the configured grant type 2 described above. The configured grant type 1 is semi-static configuration. Under the configured grant type 1, the repeated transmission of the first uplink data is usually performed after receiving the GrantConfig configured by a higher layer. The configured grant type 2 is dynamic configuration. Under the configured grant type 2, the repeated transmission of the first uplink data can be semi-persistently scheduled by the uplink grant at the effective active DCI.

[0089] As an implementation, the terminal device can distinguish the types of configured grants according to the parameters included in the higher layer configuration. When the received GrantConfig parameter in the higher layer configuration includes rrc ConfiguredPlunkGrant, the terminal device directly performs the corresponding operations of type 1 without detecting the uplink grant in the DCI. After receiving the higher layer configuration GrantConfig parameter that does not include rrcConfiguredPlunkGrant, the terminal device determines that the configuration type is type 2. If GrantConfigToAddModList is configured, on the bandwidth part (BWP) where the serving cell is active, multiple configured grants corresponding to configured grant type 1 and / or configured grant type 2 may be active simultaneously.

[0090] The first sequence belongs to a plurality of mutually orthogonal sequences. The plurality of sequences may be some or all of the sequences in a set of orthogonal codes. In some embodiments, the plurality of mutually orthogonal sequences may form a first sequence set, which may also be referred to as an orthogonal sequence set.

[0091] As an embodiment, the first sequence may be one of the plurality of mutually orthogonal sequences. That is to say, the first sequence may be a single sequence. The first terminal device may perform repeated transmission of the first uplink data according to the single sequence.

[0092] As an embodiment, the first sequence may be at least two of the plurality of mutually orthogonal sequences. That is to say, the first sequence may be a plurality of sequences. The first terminal device may perform repeated transmission of the first uplink data according to the plurality of sequences.

[0093] As an implementation, the number of the plurality of sequences for the repeated transmission of the first uplink data is related to the number of repeated transmissions. For example, the number of the plurality of sequences in the first sequence is equal to the number of repeated transmissions, so the plurality of sequences respectively correspond to multiple transmissions of the first uplink data. Another example is that when the first sequence is an OCC sequence, each element of the OCC sequence may be mapped to each repetition of the uplink data.

[0094] As another implementation, the data of the plurality of sequences for the repeated transmission of the first uplink data is independent of the number of repeated transmissions. For example, regardless of the number of repeated transmissions, the first sequence includes 2 orthogonal sequences, which are alternately used for each transmission of the first uplink data.

[0095] In some embodiments, the multiple mutually orthogonal sequences to which the first sequence belongs belong to an OCC group. That is to say, the multiple sequences are a group of OCC sequences, and the first sequence is the first OCC sequence. As an example, the multiple sequences in the first sequence set are a set of orthogonal codes selected from available OCC groups, and each sequence is also called an OCC orthogonal code. For example, for inter-slot time-domain OCC, the OCC sequence can be directly associated with the repeated transmission of uplink data.

[0096] Optionally, the first sequence set may adopt Zadoff-Chu (ZC) sequences as orthogonal codes. ZC sequences are sequences with good orthogonality. For example, the multiple sequences including the first sequence can be a group of ZC sequences.

[0097] Optionally, the first sequence set may adopt a Hadamard matrix as an orthogonal code. A Hadamard matrix is a special orthogonal matrix, and each row of it is mutually orthogonal. When the rows of the Hadamard matrix are used as orthogonal covering codes. The first sequence is any row sequence of the Hadamard matrix. The multiple sequences including the first sequence can be all or part of the row sequences in the Hadamard matrix.

[0098] Optionally, the multiple sequences including the first sequence may adopt a comb-shaped orthogonal code such that the multiple sequences have a fixed interval. For example, the multiple sequences may have a fixed time interval, that is, they have equal intervals in the time domain. Through the equal-interval design in the time domain, it can be ensured that the mutual interference between the orthogonal codes used on different time-domain units is as small as possible, thereby improving the performance of the system.

[0099] Optionally, the multiple sequences including the first sequence can achieve orthogonality in the frequency domain or in the time domain, which is not limited herein.

[0100] The multiple sequences including the first sequence can be used for multiple terminal devices including the first terminal device to multiplex the first resource. Therefore, the first resource can be used for the repeated transmission of the first uplink data. When resource multiplexing is achieved, the first resource can be used for the multiple terminal devices to respectively perform the repeated transmission of multiple uplink data to improve the uplink coverage.

[0101] In some embodiments, the first resource can be any transmission resource that can be used for multiplexing by multiple terminal devices, which is not limited herein. As an example, the first resource can be a time-domain resource or a frequency-domain resource, and can also be a code-domain resource or a space-domain resource. As an example, the first resource can be a combination of any multiple resources among time-domain resources, frequency-domain resources, space-domain resources, or code-domain resources.

[0102] As an example, the first resource may be one or more PRBs. For the allocation of more than 1 PRB, the same multiplexing capability can be achieved by first reducing the PRB allocation to 1 PRB and then applying OCC within 1 PRB. For example, applying OCC with a length of 4 to 2 PRBs is equivalent to applying OCC with a length of 2 to two different allocations of 1 PRB.

[0103] In some embodiments, when the first sequence is the first OCC sequence, the OCC length corresponding to the first sequence is related to the number of terminal devices multiplexing the same resource. For example, for inter-slot OCC with OCC lengths of 2 and 4 respectively, up to 2 or 4 terminal devices can be multiplexed.

[0104] As described above in connection with Figure 4 Method embodiments for repeating the transmission of uplink data based on orthogonal sequences have been introduced. This method enables multiple terminal devices to multiplex the first resource to repeat the transmission of multiple uplink data based on orthogonal sequences, effectively enhancing the uplink capacity / coverage. As mentioned above, when multiple terminal devices repeat the transmission of multiple uplink data based on orthogonal sequences, problems such as the multiplexing of uplink data and UCI, different capabilities of different terminal devices, or different resource sizes may be faced. To address these problems, the method embodiments proposed in this application will be described below.

[0105] In some embodiments, the multiple terminal devices may include at least one second terminal device that does not support resource multiplexing. That is to say, the first terminal device that supports resource multiplexing can multiplex the first resource together with the second terminal device that does not support resource multiplexing. In this way, the system throughput can be doubled without allocating any additional time-domain or frequency-domain resources to different terminal devices. A terminal device supporting resource multiplexing may refer to a terminal device having the function of sending uplink data based on orthogonal sequences. For example, a terminal device with an OCC function is a terminal device supporting resource multiplexing, and correspondingly, a terminal device without an OCC function is a terminal device not supporting resource multiplexing.

[0106] In some embodiments, when certain conditions are met, the first terminal device and the second terminal device can multiplex the first resource. For example, for inter-slot time-domain OCC with PUSCH repetition type A, the network device (e.g., gNB) can multiplex a terminal device with an OCC function and a terminal device without OCC capability under certain conditions.

[0107] As an example, the network device can determine whether the terminal device supports resource multiplexing according to the capability information reported by the terminal device.

[0108] As an example, information on whether an orthogonal sequence related to a terminal device is enabled can be used to determine whether the terminal device supports resource multiplexing. For example, an OCC enable / disable flag can indicate to the terminal device whether to apply OCC. The network device can also distinguish between terminal devices that perform OCC and those that do not perform OCC through these flags.

[0109] In some embodiments, when multiple terminal devices include a second terminal device, the multiplexing of the first resource needs to satisfy at least one of the following: multiple uplink data correspond to the same redundancy version (RV); the first resource is not used for UCI multiplexing or UCI multiplexing is performed according to the first information; there is no frequency hopping on the first resource; the phase is continuous within the first time period corresponding to the first resource.

[0110] As an example, repeated PUSCH transmissions can be assigned the same redundancy version. In addition, the redundancy version within an OCC group also needs to remain unchanged. For example, in NR NTN with inter-slot time-domain OCC, the redundancy version within the OCC group should be consistent. It should be noted that when PUSCH repetition corresponds to multiple OCC groups, the RV cycle across OCC groups can be used to achieve the coding gain of different redundancy versions. Multiple OCC groups can include multiple OCC lengths. The traditional RV cycle mechanism can be extended to the unit of the OCC group.

[0111] In the above embodiments, when the OCC configuration parameters corresponding to the first terminal device do not match the resource configuration, the resource configuration parameters can be adjusted or the resource configuration can be turned off. For example, when the time-frequency resource allocated by the network device for a terminal device configured with OCC of length 4 is the first resource, the network device may want multiple terminal devices configured with OCC of length 2 to multiplex the first resource. Since the first resource supports inter-slot OCC of length 4, it can be indicated that the terminal device configured with OCC of length 2 turns off the RV cycle. That is to say, for inter-slot OCC, the RV cycle can be performed based on multiple OCC lengths according to the configuration / indication of the network (NW).

[0112] It should be understood that in PUSCH transmissions based on dynamic authorization, different redundancy versions are usually applied to adjacent PUSCH repetitions in a certain order. However, if inter-slot OCC groups are applied, the redundancy versions of PUSCH repetitions within the OCC group should remain unchanged to maintain orthogonality.

[0113] As an example, the first resource is not used for UCI multiplexing. For example, the first PUSCH retransmission based on OCC does not multiplex the UCI with the first resource. This means that if the network device schedules a terminal device with repeated PUSCH and UCI multiplexing, the network device will not configure OCC for this terminal device. Further, the network device will not schedule other terminal devices to multiplex with this terminal device in the same time domain and / or frequency domain resources.

[0114] As an example, when the UCI multiplexes the first resource, it is performed according to the first information, which will be specifically introduced in combination with the first information later.

[0115] As an example, the frequency hopping on the first resource may affect the structure of multiple PUSCH repetitions, thereby destroying the OCC orthogonality.

[0116] As an example, the first time period corresponding to the first resource should maintain phase continuity. The first time period may be part or all of the time domain segment corresponding to the first resource. In the NTN system, since the Doppler frequency shift may cause phase discontinuity, it is necessary to ensure phase continuity when multiplexing the first resource. For example, when the terminal device multiplexes the first resource based on OCC, it is necessary to meet the phase continuity requirements between the time slots corresponding to the OCC group, especially when the receiver uses a conventional de-OCC algorithm for data reception.

[0117] As an example, if at least the following conditions are met, a terminal device with OCC function can send PUSCH of repeated type A by multiplexing the first resource with a terminal device without OCC function (for example, the second terminal device): The CG-PUSCH has the same RV, there is no UCI on any time slot on the PUSCH, there is no frequency hopping on the first resource, and the phase is continuous within the first time period.

[0118] In some embodiments, when the first terminal device and the second terminal device multiplex the first resource, the first sequence corresponding to the first terminal device may be one of multiple OCC sequences, and the second terminal device can be regarded as having a specific OCC sequence. For example, the second sequence corresponding to the second terminal device is all 1s. That is to say, for a traditional terminal device, it can be regarded as applying an OCC sequence with all 1s, such as [+1, +1] or [+1, +1, +1, +1]. Since the time domain OCC between time slots does not change the traditional resource mapping, this method takes into account the situation where there are traditional terminal devices and subsequent version terminal devices in the relevant network. Through the design of backward compatibility, terminal devices with different capabilities or different versions can directly multiplex based on the OCC sequence.

[0119] As an example, the second sequence may be one of multiple mutually orthogonal sequences.

[0120] In some embodiments, when at least some of the transmission resources of the first UCI overlap with the first resources, or when the number of retransmissions of the first UCI is different from the number of retransmissions of the first uplink data, the first terminal device may determine the transmission mode of the first UCI according to the first information. For example, when repeating the PUSCH based on the inter-slot OCC group, if the resources of a PUCCH (including the first UCI) overlap with the resources corresponding to any inter-slot OCC, the transmission mode of the first UCI is determined according to the first information. Another example is that if the number of repetitions of the PUCCH including the first UCI is inconsistent with the number of repetitions of the PUSCH, the transmission mode of the first UCI is determined according to the first information.

[0121] In some embodiments, the first UCI is uplink information that can reuse the same resources as the retransmitted uplink data. As an example, the first UCI may include at least one of feedback information, a scheduling request (SR), and channel state information (CSI). The feedback information is, for example, an acknowledgement (ACK) in HARQ, that is, HARQ-ACK; or a negative acknowledgement (NACK) in HARQ.

[0122] It should be noted that in UCI multiplexing, the number of resource elements (REs) for transmitting UCI in each orthogonal frequency division multiplexing (OFDM) symbol remains unchanged. For the inter-slot time-domain OCC of repetition type A, the first terminal device may transmit multiple PUSCHs on one or more slots scheduled by the DCI format, or transmit multiple PUSCHs on one or more slots. When UCI multiplexing is introduced, the first terminal device may transmit a PUCCH with HARQ-ACK and / or CSI signals on a single slot that overlaps with the PUSCH transmission in one or more slots. Under the condition that the PUSCH transmission in one or more slots is used to multiplex the HARQ-ACK and / or CSI signals, the first terminal device may also multiplex the HARQ-ACK and / or CSI signals in the PUSCH transmission in one or more slots.

[0123] In some embodiments, the transmission mode of the first UCI includes one of the following: the transmission of the first UCI on the first resource is cancelled; the first UCI is preferentially transmitted on the first resource, and the repeated transmission of multiple uplink data is cancelled; the first UCI is transmitted together with the first uplink data on the first resource. Thus, it can be seen that the first UCI can be transmitted on the first resource or not transmitted on the first resource.

[0124] As an embodiment, when the first UCI is transmitted together with the first uplink data on the first resource, the first UCI can multiplex the PUSCH carrying the first uplink data, that is to say, the first UCI can be carried on the PUSCH. When the first UCI is allowed to be multiplexed through the PUSCH, the first terminal device can preferentially add UCI payloads on the PUSCH. For example, when it is determined that there is an OCC overlap between time slots in the PUSCH repetitions within the PUCCH and OCC group, the network device can instruct the first terminal device to multiplex the UCI payloads into all the PUSCH repetitions within the OCC group. Optionally, the UCI payload can be added to the PUSCH through a physical layer multiplexing method (such as embedding at the modulation symbol level).

[0125] As an implementation manner, when the first UCI is transmitted together with the first uplink data on the first resource, the first UCI is carried on all the uplink channels used for repeating the transmission of the first uplink data, thereby avoiding the problem of orthogonality breakdown caused by different signal structures due to single UCI multiplexing. For example, when the first UCI is transmitted together with multiple repeated PUSCHs on the first resource, the first UCI can be multiplexed onto each repeated PUSCH.

[0126] For example, the base station can allocate a set of time slots and frequency domain resources for the PUSCH repetitions within the OCC group. The number of repetitions of the PUSCH within the OCC group is N, and the same OCC coding can be used for all repetitions, or different OCC codings can be used. By adding the load corresponding to the first UCI to the PUSCH, each repeated PUSCH within the OCC group will carry the same UCI load, thereby ensuring reliability.

[0127] For ease of understanding, the following is combined with Figure 5 for illustration. In Figure 5Among them, the OCC with a length of 2 is used for multiple terminal devices to perform PUSCH repeated transmission. The transmission resources of the PUCCH carrying UCI are determined according to the physical downlink shared channel (PDSCH) and the time period T. When the resources of the PUCCH partially or completely overlap with the resources of the PUSCH repeated twice, the UCI payload on the PUCCH can be added to each PUSCH, so as to realize the multiplexing of UCI and PUSCH repetition.

[0128] As another implementation, the repeated transmission of the first uplink data is carried on multiple uplink channels. When the first UCI is transmitted together with the first uplink data, the first UCI is carried on the first uplink channel among the multiple uplink channels, and the first uplink channel is determined according to the indication of the network device. That is to say, the network device can instruct the first terminal device to carry the first UCI only on a specific first uplink channel.

[0129] For example, the UCI payload can be directly embedded in a single PUSCH transmission and not shared with other PUSCHs not corresponding to the OCC group. Therefore, each PUSCH transmission needs to be independently multiplexed to avoid interference during in-group resource sharing. In this scenario, the base station can allocate resources for multiple PUSCH repeated transmissions to the terminal device, but does not configure orthogonal coding between OCC time slots for these repetitions.

[0130] It should be noted that the base station can configure the resources of each PUSCH repetition to be independent, or specify the independence between a PUSCH repetition and other PUSCH repetitions. Optionally, isolation between any two independent PUSCH repetitions can be achieved in the following ways: time-domain isolation and frequency-domain isolation. For time-domain isolation, different PUSCH repetitions can use different time slots. For frequency-domain isolation, different PUSCH repetitions can be allocated different PRBs.

[0131] Another example is that the base station can instruct the first terminal device on which PUSCH to carry the first UCI. The base station can indicate the PUSCH resource allocation and UCI multiplexing rule of the first terminal device through DCI. Optionally, the UCI multiplexing configuration can include an indication of which PUSCH repetition is used to carry the UCI payload. Optionally, the UCI multiplexing configuration can also indicate that the UCI payload is transmitted only on a specific PUSCH repetition, and other PUSCH repetitions only carry PUSCH data. The base station can know which repetition carries the UCI payload and which does not according to the scheduling information. For this specific bearer, decoding can be performed separately. The PUSCHs of the remaining repetitions only decode the data.

[0132] For ease of understanding, the following is combined withFigure 6 and Figure 7 will be described. Different from Figure 5 , when the resources of PUCCH partially or completely overlap with the resources of PUSCH with 2 - time repeated transmission, the UCI payload on PUCCH is added only in one PUSCH. Figure 6 The UCI in Figure 7 is carried on the first PUSCH, and the UCI in

[0133] is carried on the second PUSCH, and resource multiplexing can be achieved. It should be noted that the embodiments of this application can allow some PUSCHs to reuse OCC for orthogonal multiplexing, and other PUSCH repetitions provide non - OCC independence to support the flexible embedding of UCI. For example, when a specific PUSCH needs to embed a UCI payload, this specific PUSCH can be repeated independently of other PUSCHs, and other PUSCH repetitions can use OCC for orthogonal multiplexing. Another example is that when the PUSCH repetition times of two terminal devices multiplexing the first resource are different, some resources may not be involved in orthogonal multiplexing. The repeated transmission resources in the first resource that are not involved in orthogonal multiplexing can provide non - OCC independence.

[0134] As an implementation, the network device can periodically configure PUSCH resources with independence. These periodically configured PUSCH resources can be specifically used to carry the UCI of multiple terminal devices multiplexing the same resources.

[0135] As an embodiment, when the first UCI is preferentially transmitted on the first resource and the repeated transmission of multiple uplink data is cancelled, the first terminal device can transmit the first UCI carried on the PUCCH on the first resource. In this scenario, the first terminal device can discard the OCC - based uplink data repetition. For example, when it is determined that there is a conflict between the PUCCH resource and the PUSCH repetition within the OCC group, the network device can preferentially schedule the PUCCH resource to achieve the transmission integrity of UCI transmission. To avoid the interference of PUSCH repetition to PUCCH, all PUSCH repetitions within the OCC group can be discarded.

[0136] In the above - mentioned embodiments, the network device can respectively instruct multiple terminal devices to cancel the PUSCH repeated transmission within the OCC group. When the first resource only allows UCI transmission on the PUCCH, the discarded PUSCH repetitions no longer use the first resource. The resources in the first resource that are not used for PUCCH transmission can be used for other purposes (such as allocating to other terminal devices) or remain idle to reduce interference.

[0137] As an example, when the transmission of the first UCI on the first resource is cancelled, the first terminal device does not transmit the first UCI on the first resource. For example, when there is an inter-slot OCC overlap between the PUSCH repetition based on OCC and the PUCCH, and transmitting the UCI may cause severe interference or resource conflict, the UCI transmission of the terminal device is cancelled. The base station may send indication information to the terminal device to inform that the UCI has been cancelled. It should be understood that cancelling the first UCI transmission means not sending the first UCI, which may include cancelling part of the UCI or all of the UCI.

[0138] As an implementation manner, the network device may send first control information to the first terminal device, and the first control information is used to instruct the first terminal device to cancel the transmission of the first UCI. The first control information may be RRC signaling or a medium access control control element (MAC CE). For example, for inter-slot OCC, the first control information may instruct the first terminal device to cancel the UCI transmission in the current slot.

[0139] In the above embodiment, when the first terminal device determines not to send the first UCI on the first resource, the first terminal device does not need to perform the uplink transmission of the first UCI any more, or transmits according to the reallocated resources. In some scenarios, if the conflict is inevitable (such as insufficient resources), the network device may reallocate the time slots or frequency resources of the PUCCH or PUSCH to avoid the conflict. For example, the network device may allocate new PRBs for the PUCCH to avoid overlapping with the PUSCH, or move the PUCCH to a new time slot for transmission.

[0140] In the above multiple embodiments, the transmission manner of the first UCI may also be referred to as the multiplexing strategy of the first UCI. As can be seen from the foregoing, the multiplexing strategy of the first UCI at least includes that the first UCI does not multiplex the first resource, the first UCI is multiplexed to all PUSCH repetitions, and the first UCI is multiplexed to specific PUSCH repetitions.

[0141] In some embodiments, the first information may include one or more of the following: the priority of the first UCI; the transmission priority of the first UCI relative to the first uplink data; the load of the network where the first terminal device is located; the resource requirements of the first terminal device.

[0142] As an example, the priority of the first UCI can be determined according to the priority indication of the UCI. The priority of the UCI can be used to indicate the importance of different UCI types. Based on the priority indication, the UCI can include high-priority UCI, medium-priority UCI, and low-priority UCI. Optionally, the high-priority UCI is, for example, HARQ-ACK, the medium-priority UCI is, for example, SR, and the low-priority UCI is, for example, CSI. Optionally, the high-priority UCI is, for example, SR. Optionally, the high-priority UCI is, for example, CSI.

[0143] As an implementation, the priority of the UCI can be set by a network device. For example, a base station can set the importance of UCI types.

[0144] As an implementation, the priority of the first UCI includes at least one of the following: the priority of feedback information is the highest; the priority of feedback information is higher than the priority of a scheduling request (SR); the priority of feedback information is higher than the priority of channel state information (CSI); the priority of the scheduling request is higher than the priority of channel state information; the priority of channel state information is the lowest.

[0145] In some embodiments, the first terminal device can determine the transmission mode of the first UCI according to the priority of the first UCI. As an example, when the network device sets the importance or priority of the UCI, this priority can be used to determine whether to cancel some or all of the first UCI. For example, when the priority of the first UCI is lower than a first threshold, the first terminal device does not send the first UCI.

[0146] In the above embodiments, when a conflict occurs, the network device can also schedule the cancellation of the transmission of all types of UCI (such as HARQ-ACK, CSI, SR).

[0147] As an example, whether the transmission of the first UCI is cancelled can be determined according to the priority of the first UCI. For example, high-priority UCI generally cannot be cancelled, and the network device will preferentially adjust PUSCH repetition or PUCCH resources to avoid cancellation. Also, for example, medium-priority UCI can be selectively cancelled according to resource usage. Also, for example, low-priority UCI can be directly cancelled to reduce interference.

[0148] In the above embodiments, after introducing the priority scheduling mechanism, the network device or the terminal device can decide its processing method according to the type and importance of the UCI. For important UCI transmissions, a redundancy strategy (such as multiplexing to multiple PUSCH repetitions) can be adopted. For relatively unimportant UCI transmissions, the transmission can be directly cancelled.

[0149] In some embodiments, the first terminal device may determine the transmission mode of the first UCI according to the transmission priority of the first UCI relative to the first uplink data. That is to say, the transmission priority of the first UCI may be determined relative to the retransmission of the uplink data. For example, the transmission priority of the first UCI may be higher than the transmission priority of the PUSCH retransmission, or may be lower than the transmission priority of the PUSCH retransmission.

[0150] As an embodiment, when the transmission priority of the first UCI is higher than the retransmission of the first uplink data, the first terminal device does not send the retransmission of multiple uplink data on the first resource. That is to say, when the transmission priority of the first UCI is higher than the transmission priority of the retransmitted first uplink data, the first terminal device may abandon the retransmission of multiple uplink data on the first resource.

[0151] In some embodiments, the network device or the first terminal device may determine the transmission mode of the first UCI according to the load of the network where the first terminal device is located or the resource requirements of the first terminal device. Both network load and resource requirements are related to whether resources are sufficient.

[0152] As an embodiment, if the time-domain resources are tight but high-reliability transmission is required, the first UCI may be embedded in each PUSCH retransmission to ensure redundant transmission. If the resources are sufficient and the transmission reliability requirement is low, the first UCI may be embedded only in one or two specific PUSCH retransmissions, and the other retransmissions are used for data transmission. When the frequency-domain resources are sufficient and the first UCI is embedded in a single PUSCH retransmission or a partial PUSCH retransmission, a frequency-domain isolation scheme may be preferentially selected to avoid interference of the UCI on other retransmissions or the concentrated multiplexing scheme.

[0153] In some embodiments, the network device or the first terminal device may dynamically select the multiplexing strategy of the first UCI, that is, the transmission mode of the first UCI, based on the load of the network where the first terminal device is located, the resource requirements of the first terminal device, and the priority of the first UCI.

[0154] As an embodiment, in the resource allocation phase, the network device may detect whether there is a conflict between the PUCCH and the PUSCH retransmissions within the OCC group. For example, the network device may check whether there is an inter-slot OCC overlap between the PUCCH and the PUSCH, and check whether the terminal device needs to perform UCI multiplexing. Among them, the network device may obtain requirements such as HARQ-ACK, CSI, and SR through signaling.

[0155] In the above embodiments, the network device may determine the following multiple transmission strategies according to the importance of the UCI.

[0156] For high-priority UCI (such as HARQ-ACK): Redundant transmission is adopted to ensure successful transmission with priority.

[0157] For medium-priority UCI (such as SR): A certain degree of conflict or resource compromise is allowed.

[0158] For low-priority UCI (such as CSI): The transmission frequency can be cancelled or restricted.

[0159] In the above embodiments, when the network device determines the transmission strategy, it can send a scheduling instruction to the terminal device according to the selected strategy. This instruction can be used to allocate the PUSCH repetition times N, resource locations (time slots, PRBs), and can also specify the location and multiplexing rule of UCI multiplexing (such as specific repetition or all repetitions).

[0160] As described above in combination with Figures 4 to 7 It is introduced that multiple terminal devices repetitively transmit uplink data on the first resource according to multiple mutually orthogonal sequences and the multiplexing method of this repetitive transmission with UCI. For any one of the multiple terminal devices, how to determine the configuration parameters of the corresponding orthogonal sequence is also a problem to be solved. Hereinafter, an example of the first sequence corresponding to the first terminal device will be described.

[0161] In some embodiments, the first terminal device can determine the configuration parameters of the first sequence according to the configuration of the first sequence or multiple sequences including the first sequence. The configuration manner or configuration parameters of the first sequence can be determined according to the configuration of the repetitive transmission of the first uplink data. That is to say, the configuration parameters of the first sequence can be indicated by the configuration of the repetitive transmission of the first uplink data. For example, the configuration parameters of the first sequence can be related to the transmission parameters of the first uplink data, or can be carried in the configuration signaling of the repetitive transmission of the first uplink data.

[0162] As an embodiment, the configuration parameters of the first sequence can be carried in one or more of the following information: higher layer signaling; DCI; RRC signaling; relevant parameters of the repetitive transmission of the first uplink data. For example, the NTN network can allocate multiple orthogonal sequences to multiple terminal devices through DCI to facilitate the multiplexing of the same PRB by multiple terminal devices.

[0163] As an embodiment, the configuration of the first sequence can be determined according to the transmission configuration of PUSCH repetition. For example, for multiple repetitively transmitted PUSCHs, the configuration parameters of the first sequence can be included in the parameters of the transmission configuration of this PUSCH repetition.

[0164] In the above embodiments, when the configuration of the first sequence is related to the transmission configuration of PUSCH repetition, the configuration parameters of the first sequence are carried in one or more of the following information: higher layer signaling; DCI; RRC signaling; PUSCH repetition transmission parameters.

[0165] For ease of understanding, the following uses the case where multiple sequences including the first sequence are OCC to illustrate various configuration methods of the first sequence. For OCC, the relevant parameters of OCC include the OCC index and the OCC length. Exemplarily, the configuration parameters of the first sequence may include the codeword index of the first OCC sequence and the lengths of multiple OCC sequences, so that the first terminal device can determine the first sequence according to this configuration.

[0166] As an embodiment, the configuration parameters of the first sequence can be carried in higher layer signaling. As an implementation manner, when the transmission configuration of PUSCH repetition corresponds to configuration grant type 1, the configuration parameters of the first sequence can be included in GrantConfig configured by the higher layer. For example, the configuration parameters of the first OCC sequence can be included in rrcConfiguredPlunkGrant of GrantConfig. As another implementation manner, when the transmission configuration of PUSCH repetition corresponds to configuration grant type 2, the configuration parameters of the first sequence can also be included in GrantConfig. As yet another implementation manner, for the PUSCH transmission scheduled by uplink grant, the OCC related parameters can be included in higher layer signaling.

[0167] As an embodiment, the configuration parameters of the first sequence can be carried in DCI. As an implementation manner, when the transmission configuration of PUSCH repetition corresponds to configuration grant type 2, the PUSCH repetition transmission is activated by DCI scrambled with a configured scheduling-radio network temporary identifier (CS-RNTI), and the OCC related parameters can be included in the DCI. For example, the configuration parameters of the first sequence can be included in the PUSCH configuration. As another implementation manner, for the PUSCH transmission scheduled by uplink grant, the OCC related parameters can also be included in the DCI.

[0168] In the above embodiments, as the PUSCH capacity passing through OCC increases, the capacity of PDCCH may become a bottleneck, limiting the possibility of granting a large number of terminal devices for repeated transmissions of multiple PUSCHs based on OCC. For example, multiple terminal devices in a broadcast / multicast scenario, or multiple cell scenarios. Therefore, RAN1 designates a single DCI scheduling among multiple terminal devices / cells, which can support a single DCI to schedule repeated transmissions of multiple PUSCHs based on OCC. This single DCI can schedule a group of terminal devices. The DCI format can be newly set, and at this time, the indication of the OCC sequence index can correspond to each terminal device or each group of terminal devices.

[0169] As an implementation manner, the DCI can indicate which codeword the terminal device is to use. Dynamic signaling configuration of codewords is desirable, which helps the network device to dynamically pair multiple terminal devices multiplexing the same resources based on information such as data arrival and power imbalance. For example, the DCI can indicate the OCC parameters corresponding to the first terminal device: OCC codeword (CW) and OCC factor.

[0170] For example, the OCC factor can be configured semi-statically using RRC or dynamically using DCI. The OCC factor can represent the OCC length M, that is to say, the first terminal device can determine the configured OCC length according to the OCC factor.

[0171] For another example, the OCC codeword (CW) can represent the codeword used by the terminal device. For an OCC factor with a value of M, there are M possible codewords. After a given OCC factor, the DCI can notify the first terminal device which codeword in the OCC to use.

[0172] As an implementation manner, the configuration parameters of the first sequence can be carried in the first indication field of the DCI. The first indication field can be determined according to the control information format corresponding to the DCI. For different control information formats, the first indication field can be designed differently. As an example, the first indication field can be a newly added indication field, or the configuration parameters of the orthogonal sequence can be added to the traditional indication field.

[0173] As an example, the number of bits of the first indication field is related to the number of multiple terminal devices multiplexing the first resource. For example, when supporting 4 terminal devices to multiplex the first resource, the number of bits of the first indication field is at least 2 bits.

[0174] As an example, the first indication field may indicate the number of a plurality of mutually orthogonal sequences and the index of the first sequence among the plurality of sequences. The number of the mutually orthogonal sequences is related to the number of terminal devices multiplexing the first resource. When the plurality of mutually orthogonal sequences are OCC groups, the first indication field may indicate the number of codewords of the OCC group, that is, the OCC length, i.e., the OCC factor. The index of the first sequence among the plurality of sequences is used for the first terminal device to select the first sequence among the plurality of sequences. When the plurality of mutually orthogonal sequences are OCC groups, the first indication field may indicate which codeword in the OCC group the first sequence is through the OCC codeword index.

[0175] As an example, when the first indication field multiplexes a conventional indication field, the first indication field also needs to indicate what the conventional indication field needs to indicate. For example, the first indication field is also used to indicate the demodulation reference signal (DMRS) port. That is to say, the DMRS port and the OCC parameters can be jointly encoded.

[0176] In the above example, the first indication field may be the indication field corresponding to the antenna port in the DCI format, that is, the antenna port field.

[0177] As an implementation manner, the UL PUSCH antenna port field can be combined with the OCC indication. For example, the DMRS port, the OCC factor, and the CW index (CW idx) can be jointly encoded. In this case, the number of bits can be determined according to the number of multiplexed terminal devices and the multiple-input multiple-output (MIMO) situation. The MIMO situation may be related to codewords, precoding, and the number of layers. For example, four bits are allocated in the DCI (such as DCI format 0_1) for scheduling the UL PUSCH for the antenna port. Combining the support for multi-user (MU)-MIMO capabilities, if the NTN UL is going to operate using 1Tx / Rx, the bits in the antenna port field can be reused to indicate the OCC factor and the OCC codeword. For example, to support OCC (including no OCC) for up to 4 terminal devices, 1 (no OCC) + 2 (OCC factor 2 + 2 CWs) + 4 (OCC factor 4 + 4 CWs) entries are required to indicate the OCC configuration. Through conversion, 7 entries require 3 bits to indicate.

[0178] For example, when the DMRS ports are jointly encoded with the OCC parameters, Table 1 shows an example of the mapping from DMRS ports to the OCC parameters in DCI. The number of code division multiplexing (CDM) groups with / without data (CDM groups w / o data), DMRS ports, and the number of front-loaded symbols in Table 1 are related parameters of the antenna ports.

[0179] Table 1

[0180] value Number of CDM groups with / without data DMRS port Number of preamble symbols OCC factor CW index 0 2 0 1 2 0 1 2 1 1 2 1 2 2 0 1 4 0 3 2 1 1 4 1 4 2 2 1 4 2 5 2 3 1 4 3 6 2 0 1 1 0 7 x x x x x

[0181] Table 1 is an implementation for indicating the OCC configuration. The first column in Table 1 can be the value of the first indication field. The first terminal device can determine the corresponding OCC factor and CW index according to the value of the first indication field to determine the codeword of the first sequence. When the value of the first indication field is 6, it can indicate that there is no OCC. Or rather, when the OCC factor is 1, it can indicate that the OCC is disabled.

[0182] As an embodiment, the configuration parameters of the first sequence can be carried in the RRC signaling. As an implementation, for the configured grant-based PUSCH transmission, since the resources for PUSCH transmission are predefined, the OCC sequence index can be indicated in the RRC so that the terminal device can select a suitable OCC sequence from the sequence pool.

[0183] As an embodiment, the configuration parameters of the first sequence can be carried in the transmission parameters of the PUSCH repetition. As an implementation, for the dynamic grant-based PUSCH repetition transmission, the length of the OCC can be determined by the number of repetitions of the PUSCH transmission.

[0184] In the above embodiment, the length of the OCC can be less than or equal to the number of repetitions. For example, if the number of repetitions is less than 4, the indicated sequence index can refer to the table with an OCC length of 2, otherwise, the indicated sequence index comes from the table with an OCC length of 4.

[0185] In the above embodiment, when there is no corresponding OCC length for the number of repetitions, the OCC length can be selected nearby according to the number of repetitions. For example, when the number of repetitions is m, the OCC length corresponding to the first sequence is the value closest to m among multiple OCC lengths.

[0186] As an example, the configuration parameters of the first sequence can be carried in any of the above-mentioned multiple types of information. As an implementation, for dynamic grant-based PUSCH repeated transmission, considering the limited DCI size, the most basic OCC indication (OCC sequence index) can be carried in the DCI, and the length of the OCC is determined by the number of repeated transmissions. As another implementation, the OCC sequence index can be indicated in the RRC, and the length of the OCC is determined by the number of repeated transmissions.

[0187] In some embodiments, the configuration of the first sequence may further include whether the first sequence is enabled. The first terminal device can determine whether the corresponding first sequence and / or multiple sequences including the first sequence are enabled according to the received second information.

[0188] As an example, the first terminal device can receive second information from the network device, and the second information can indicate whether the first sequence and / or multiple sequences including the first sequence are enabled.

[0189] As an example, the second information can be RRC signaling or DCI. Taking the enabling and disabling of OCC as an example, for the repeated transmission of PUSCH with dynamic grant (DG), that is, DG-PUSCH, the enabling / disabling of OCC can be indicated by RRC signaling, that is, the second information is RRC signaling. When the RRC signaling indicates that OCC is enabled, the DCI can indicate the configuration parameters of the first sequence corresponding to the first terminal device. Another example is that in the scenario where the PUSCH transmission resources are predefined, it should be clearly indicated in the RRC signaling whether OCC is enabled. Another example is that the indication field related to the first sequence in the DCI can implicitly indicate whether OCC is enabled.

[0190] Exemplarily, when the OCC parameters are carried in the DCI, the OCC parameters can be jointly encoded with other parameters. The network device can impose other restrictions to maintain the maximum flexibility of PUSCH scheduling with and without OCC and minimize the overhead. For example, OCC can be used for allocations with a smaller bandwidth, such as one PRB. Another example is that when the processing of transmission block over multiple slots (TBoMS) is enabled, the performance of OCC is expected to be better, and OCC can be enabled.

[0191] Exemplarily, the network and the terminal device can derive the OCC enable / disable from several conditions indicated in the DCI, rather than using a separate flag for OCC enable / disable. For example, if the transmission bandwidth is 1 PRB (determined based on the frequency domain resource assignment (FDRA) field), the modulation of the modulation and coding scheme (MCS) is not higher than quadrature phase shift keying (QPSK) (based on the MCS field), the time slot for the TBoMS is greater than or equal to M (based on the time domain resource assignment (TDRA) field), and the uplink shared channel (UL-SCH) flag is set to 1, then the terminal device and the network can implicitly derive from these conditions that the uplink communication with OCC is enabled. If these conditions are not met, the terminal device and the network can implicitly assume that the scheduled transmission does not use OCC and can interpret the DCI according to traditional rules. This implicit indication may help reduce the overhead in the DCI for configuring OCC.

[0192] The foregoing introduced the method of how multiple sequences including the first sequence are configured and indicated when multiple terminal devices perform repeated transmission of uplink data based on orthogonal sequences. In the NTN system, since the NTN cell has a very wide service area, there may usually be a large difference in the uplink transmit (UL RX) power between different terminal devices within the NTN cell. Therefore, when OCC is applied to PUSCH repeated transmission, the UL RX power difference between different PUSCH transmissions sent by different terminal devices may be very large due to the near-far problem, which may further lead to a reduction in the CDM effect. Therefore, when supporting multiple terminal devices for repeated transmission of uplink data based on OCC, it may be necessary to carefully determine which group of terminal devices can be the target for resource multiplexing.

[0193] In some embodiments, multiple terminal devices including the first terminal device may belong to the first terminal device group. The first terminal device group may be one of multiple terminal device groups, and the multiple terminal device groups are determined according to one or more of the following information: the frequency offset range corresponding to all terminal devices; the sub-region where all terminal devices are located; the remaining service time corresponding to all terminal devices.

[0194] As an example, multiple groups of terminal devices can be determined according to the frequency offset ranges corresponding to all terminal devices. Frequency offset is one of the important factors affecting performance. Generally speaking, the frequency offset of a terminal device is mainly due to the crystal oscillator error in the terminal device deviating from its nominal frequency, and also includes residual synchronization or pre-compensation errors. For a crystal oscillator, if the external conditions (such as temperature and pressure) remain relatively stable, the frequency error of the crystal oscillator is usually relatively stable. Therefore, the frequency offset caused by the crystal oscillator error will also remain within a relatively constant range within a certain period of time. Usually, the network device has performed frequency offset estimation in the initial access phase, which means that before PUSCH scheduling in the connected state, the network device already has a basic understanding of the frequency offset of the terminal device. For example, the network device can perform frequency offset estimation through a physical random access channel (PRACH) or a sounding reference signal (SRS), etc. Therefore, for the resource multiplexing of terminal devices based on OCC, the network device can divide terminal devices with similar frequency offsets into a group.

[0195] As an implementation manner, assuming that the frequency offset range of the terminal device is [-200Hz, 200Hz], the network device can divide terminal devices with similar carrier frequency offsets (CFOs) or frequency offsets within a certain range into a group for resource multiplexing of inter-slot OCC. For example, with a grouping boundary determined at 100Hz, it can be divided into 4 groups, namely [-200Hz, -100Hz], [-100Hz, 0Hz], [0Hz, 100Hz], [100Hz, 200Hz]. The terminal devices within each group can be multiplexed together in time slots according to the length of the OCC code.

[0196] As an implementation manner, the frequency offset range is related to the number of terminal devices within the corresponding terminal device group. The network device can dynamically adjust the frequency offset range according to the number of terminal devices within the terminal device group. For example, the network device can perform dynamic grouping by using the frequency offset distribution of PRACH and SRS: if there are more terminal devices in certain frequency ranges, the grouping width of this range can be reduced (for example, from 100Hz to 50Hz) to reduce interference between terminal devices within the same group; if there are fewer terminal devices in certain ranges, the grouping width can be increased (such as from 100Hz to 150Hz) to improve resource utilization.

[0197] As an implementation, the network device can allocate a specific frequency offset range for each terminal device group and adjust the time slot multiplexing position at the same time. For example, terminal device group 1 (the offset range is (-200 Hz, -100 Hz) for example) is allocated to time slot 1, and terminal device group 2 (the offset range is (-100 Hz, 0 Hz) for example) is allocated to time slot 2, to avoid using groups with adjacent frequency offsets simultaneously.

[0198] As an embodiment, multiple terminal device groups can be determined according to the sub-regions where all terminal devices are located. In the NTN system, based on the division of the NTN region, multiple sub-regions can be formed, such as NTN1, NTN2, NTN3,.... Since the signal strengths of all terminal devices in the sub-region are similar, the terminal devices in each region can form a group. The terminal devices within each group can be multiplexed together in time slots according to the length of the OCC code. In addition to using the OCC code for time slot multiplexing, the terminal devices in each sub-region can also perform resource isolation in the frequency domain (such as allocating different frequency sub-bands).

[0199] As an embodiment, multiple terminal device groups can be determined according to the remaining service time corresponding to all terminal devices. The remaining service time corresponding to the terminal device can be the remaining service time of the current satellite or cell of the terminal device. When the remaining service time is short, the terminal device needs to perform satellite handover etc. as soon as possible. Therefore, the remaining service time can represent the handover urgency.

[0200] As an implementation, multiple terminal device groups can be determined according to the time of the T-service. Due to the different trajectories and directions of satellite movement, the network device of the NTN service cell where the terminal device is located knows which terminal devices will perform handover subsequently. If it is known that the handover may occur to the NTN service area of other satellites, the network device can divide the terminal devices that need to be handed over currently into one group and the terminal devices that need to be handed over subsequently into one group. Or, the network device can divide the terminal devices that will be handed over to the same network device into one group, and the terminal devices within each group can be multiplexed together in time slots according to the length of the OCC code.

[0201] As an implementation, multiple terminal device groups can be determined according to the service time of the service or the remaining service time of the service.

[0202] As an implementation, the network device can group the terminal devices according to the remaining service time or handover urgency of the terminal devices, and preferentially allocate the terminal devices with urgent handovers to adjacent time slots or frequency resources. For the group of terminal devices with high handover priority, a higher multiplexing priority or more OCC sequences can be allocated to ensure sufficient resources. For example, for inter-satellite cooperation, multiple satellites or ground base stations share the handover information of the terminal devices and reserve frequency and time slot resources in advance in the handover target area. Another example is that for base station cooperation, through the relay link, the handover target base station pre-allocates frequency resources or OCC sequences to reduce the handover delay.

[0203] As an embodiment, multiple groups of terminal devices can be determined according to any of the above-mentioned multiple pieces of information. For example, for the terminal devices within the service area, the network device first divides the sub-regions according to characteristics such as signal strength and frequency offset. Within the sub-region, the network device further groups the terminal devices according to the handover target or remaining service time of the terminal devices to ensure that the signal characteristics and handover requirements of the terminal devices within the group are consistent. The terminal devices in different regions are isolated by frequency domain or time slot to avoid interference between regions.

[0204] As an implementation, the first group of terminal devices among multiple groups of terminal devices performs satellite handover, and the multiple groups of terminal devices further include a second group of terminal devices that do not perform satellite handover, and the terminal devices within the second group of terminal devices do not perform resource multiplexing. That is to say, the group of terminal devices that perform satellite handover (which can also be called the handover UE group) performs repeated transmission of uplink data based on resource multiplexing; the group of terminal devices that do not perform satellite handover (non-handover UE group) does not perform repeated transmission of uplink data based on resource multiplexing. For example, the handover UE group within the satellite service area uses OCC coding for multiplexing within the time slot, and the non-handover UE group uses the conventional transmission method.

[0205] In some embodiments, frequency domain isolation is performed between any two groups of terminal devices among the multiple groups of terminal devices. Frequency domain isolation can be adopted between the groups of the multiple groups of terminal devices, and OCC time slot multiplexing is adopted within the group to avoid interference between groups. For example, by using the boundary and directivity of the satellite beam, the sub-regions are further subdivided within the beam, and the terminal devices within each beam can be multiplexed according to OCC, and frequency domain isolation is adopted between the beams.

[0206] The above text introduced the method embodiments of multiple communication devices performing PUSCH repeated transmission based on multiple orthogonal sequences. Hereinafter, an example of an NTN system based on the Internet of Things will be used for exemplary illustration. In the Internet of Things system, the terminal device can perform wireless access or send uplink information and data through multiple uplink channels. Taking NB-IoT as an example, the terminal device can transmit uplink data through the narrow-band physical uplink shared channel (NPUSCH).

[0207] In NB-IoT, the uplink physical channel can support single-tone transmission and multi-tone transmission. For different subcarrier spacings (SCS), the single-tone transmission includes transmission schemes corresponding to 3.75 kHz and 15 kHz respectively. For example, NPUSCH can support transmission schemes of single-tone 3.75 kHz, single-tone 15 kHz, and multi-tone 15 kHz.

[0208] For the single-tone 15 kHz SCS in NPUSCH format 1, the terminal device can also introduce OCC to achieve resource multiplexing. In some embodiments, the resource multiplexing based on OCC can be related to whether DMRS is spread-spectrum.

[0209] As an embodiment, the DMRS symbol is spread-spectrum before applying OCC. For example, DMRS is spread-spectrum according to the following formula:

[0210]

[0211] where M is the OCC length, q is the OCC codeword allocated to the terminal device, is the reference signal sequence.

[0212] Optionally, the reference signal sequence can be expressed as:

[0213]

[0214] where c(n) is a binary sequence, which is initialized to c init = 35 at the start of NPUSCH transmission; represents the number of repetitions related to NPUSCH; N RU represents the number of resource units (RU); is the number of time slots in a resource unit.

[0215] As an embodiment, before applying OCC, the DMRS symbol is not spread-spectrum. OCC can be applied to the complex-valued DMRS symbol. For example, the traditional complex-valued DMRS symbol used in time slot 1 and time slot 2 can be expressed as: Also, for example, OCC can be applied to other complex-valued DMRS symbols corresponding to time slot 1 and time slot 2.

[0216] In the above embodiments, in the repeated transmission of NPUSCH, the time slots corresponding to the OCC codeword can use the traditional complex-valued DMRS symbol. Different DMRS sequences are used for multiplexing of the terminal device.

[0217] As an embodiment, according to the OCC codewords, different time slots may use different DMRS sequences.

[0218] As an embodiment, if the DMRS symbols are not spread spectrum, multiple terminal devices do not use OCC for resource multiplexing.

[0219] As described above in conjunction with Figures 1 to 8 , the method embodiments of the present application have been described in detail. Below in conjunction with Figures 9 to 11 , the apparatus embodiments of the present application will be described in detail. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, for parts not described in detail, reference may be made to the previous method embodiments.

[0220] Figure 9 FIG. is a schematic block diagram of an apparatus for wireless communication according to an embodiment of the present application. The apparatus 900 may be any of the first devices described above. The first device may include a terminal device. Figure 9 The apparatus 900 shown in FIG. includes a transceiver unit 910.

[0221] A determination unit 910, configured to perform repeated transmission of first uplink data according to a first sequence; wherein, the first sequence belongs to a plurality of mutually orthogonal sequences, and the plurality of sequences are used for multiple terminal devices to multiplex a first resource, the first resource is used for multiple terminal devices to respectively perform repeated transmission of multiple uplink data, the multiple terminal devices include a first terminal device, and the multiple uplink data include first uplink data.

[0222] Optionally, the multiple terminal devices include at least one second terminal device that does not support resource multiplexing. The multiplexing of the first resource needs to satisfy at least one of the following: the multiple uplink data correspond to the same redundancy version; the first resource is not used for UCI multiplexing or UCI multiplexing is performed according to the first information; there is no frequency hopping on the first resource; the phase is continuous within the first time period corresponding to the first resource.

[0223] Optionally, the second terminal device corresponds to a second sequence with all codewords being 1.

[0224] Optionally, when at least part of the transmission resources of the first UCI overlap with the first resource, or when the number of repeated transmissions of the first UCI is different from the number of repeated transmissions of the first uplink data, the transmission manner of the first UCI is determined according to the first information.

[0225] Optionally, the first information includes one or more of the following: the priority of the first UCI; the transmission priority of the first UCI relative to the first uplink data; the load of the network where the first terminal device is located; the resource requirements of the first terminal device.

[0226] Optionally, the first UCI includes at least one of feedback information, scheduling request, and channel state information, and the priority of the first UCI includes at least one of the following: the priority of the feedback information is the highest; the priority of the feedback information is higher than the priority of the scheduling request; the priority of the feedback information is higher than the priority of the channel state information; the priority of the scheduling request is higher than the priority of the channel state information; the priority of the channel state information is the lowest.

[0227] Optionally, the transmission mode of the first UCI includes one of the following: the transmission of the first UCI on the first resource is cancelled; the first UCI is preferentially transmitted on the first resource, and the repeated transmission of multiple uplink data is cancelled; the first UCI is transmitted together with the first uplink data on the first resource.

[0228] Optionally, when the first UCI is transmitted together with the first uplink data on the first resource, the first UCI is carried on all uplink channels used for repeating the transmission of the first uplink data.

[0229] Optionally, the repeated transmission of the first uplink data is carried on multiple uplink channels. When the first UCI is transmitted together with the first uplink data on the first resource, the first UCI is carried on the first uplink channel among the multiple uplink channels, and the first uplink channel is determined according to the indication of the network device.

[0230] Optionally, the first uplink data is carried on the first PUSCH, and the configuration of the first sequence is related to the configuration of the repeated transmission of the first PUSCH.

[0231] Optionally, the configuration parameters of the first sequence are carried in one or more of the following information: higher layer signaling; DCI; RRC signaling; the repeated transmission parameters of the first uplink data.

[0232] Optionally, the configuration parameters of the first sequence are carried in the first indication field of the DCI, and the number of bits of the first indication field is related to the number of multiple terminal devices.

[0233] Optionally, the first indication field is used to indicate the number of multiple sequences and the index of the first sequence among the multiple sequences.

[0234] Optionally, the first indication field is determined according to the control information format corresponding to the DCI, and the first indication field is also used to indicate the DMRS port.

[0235] Optionally, the transceiver unit 910 is further configured to receive a second piece of information; wherein, the second piece of information is used to indicate whether the first sequence and / or multiple sequences are enabled.

[0236] Optionally, multiple terminal devices belong to a first terminal device group, which is one of multiple terminal device groups. The multiple terminal device groups are determined according to one or more of the following information: the frequency offset range corresponding to all terminal devices; the sub-region where all terminal devices are located; the remaining service time corresponding to all terminal devices.

[0237] Optionally, when the multiple terminal device groups are determined according to the frequency offset range corresponding to all terminal devices, the frequency offset range is related to the number of terminal devices within the corresponding terminal device group.

[0238] Optionally, when the multiple terminal device groups are determined according to the remaining service time corresponding to all terminal devices, the first terminal device group among the multiple terminal device groups performs satellite handover. The multiple terminal device groups further include a second terminal device group that does not perform satellite handover, and the terminal devices within the second terminal device group do not perform resource multiplexing.

[0239] Optionally, frequency domain isolation is performed between any two of the multiple terminal device groups.

[0240] Optionally, multiple sequences belong to an OCC group.

[0241] Figure 10 It is a schematic block diagram of another apparatus for wireless communication according to an embodiment of the present application. The apparatus 1000 may be any one of the second devices described above. The second device may include a network device. Figure 10 The illustrated apparatus 1000 includes a transceiver unit 1010.

[0242] The transceiver unit 1010 is configured to receive repeated transmissions of multiple uplink data from multiple terminal devices; wherein, the repeated transmissions of the multiple uplink data multiplex a first resource based on multiple mutually orthogonal sequences. The multiple sequences include a first sequence, and the first sequence is used for the first terminal device among the multiple terminal devices to perform repeated transmission of first uplink data. The multiple uplink data include first uplink data.

[0243] Optionally, the multiple terminal devices include at least one second terminal device that does not support resource multiplexing. The multiplexing of the first resource needs to satisfy at least one of the following: the multiple uplink data correspond to the same redundancy version; the first resource is not used for UCI multiplexing or is used for UCI multiplexing according to the first information; there is no frequency hopping on the first resource; the phase is continuous within the first time period corresponding to the first resource.

[0244] Optionally, the second terminal device corresponds to a second sequence with all codewords being 1.

[0245] Optionally, when at least part of the transmission resources of the first UCI overlap with the first resource, or when the number of retransmission times of the first UCI is different from the number of retransmission times of the first uplink data, the transmission mode of the first UCI is determined according to the first information.

[0246] Optionally, the first information includes one or more of the following: the priority of the first UCI; the transmission priority of the first UCI relative to the first uplink data; the load of the network where the first terminal device is located; the resource requirements of the first terminal device.

[0247] Optionally, the first UCI includes at least one of feedback information, scheduling request, and channel state information, and the priority of the first UCI includes at least one of the following: the priority of the feedback information is the highest; the priority of the feedback information is higher than the priority of the scheduling request; the priority of the feedback information is higher than the priority of the channel state information; the priority of the scheduling request is higher than the priority of the channel state information; the priority of the channel state information is the lowest.

[0248] Optionally, the transmission mode of the first UCI includes one of the following: the transmission of the first UCI on the first resource is cancelled; the first UCI is preferentially transmitted on the first resource, and the retransmission of multiple uplink data is cancelled; the first UCI is transmitted together with the first uplink data on the first resource.

[0249] Optionally, when the first UCI is transmitted together with the first uplink data on the first resource, the first UCI is carried on all uplink channels used for retransmitting the first uplink data.

[0250] Optionally, the retransmission of the first uplink data is carried on multiple uplink channels. When the first UCI is transmitted together with the first uplink data on the first resource, the first UCI is carried on the first uplink channel among the multiple uplink channels, and the first uplink channel is determined according to the indication of the network device.

[0251] Optionally, the first uplink data is carried on the first PUSCH, and the configuration of the first sequence is related to the configuration of the retransmission of the first PUSCH.

[0252] Optionally, the configuration parameters of the first sequence are carried in one or more of the following information: higher layer signaling; DCI; RRC signaling; the retransmission parameters of the first uplink data.

[0253] Optionally, the configuration parameters of the first sequence are carried in the first indication field of the DCI, and the number of bits of the first indication field is related to the number of multiple terminal devices.

[0254] Optionally, the first indication field is used to indicate the number of multiple sequences and the index of the first sequence among the multiple sequences.

[0255] Optionally, the first indication field is determined according to the control information format corresponding to the DCI, and the first indication field is further used to indicate the DMRS port.

[0256] Optionally, the transceiver unit 1010 is further configured to send a second piece of information; wherein, the second piece of information is used to indicate whether the first sequence and / or multiple sequences are enabled.

[0257] Optionally, the multiple terminal devices belong to a first terminal device group, the first terminal device group is one of the multiple terminal device groups, and the multiple terminal device groups are determined according to one or more of the following information: the frequency offset range corresponding to all the terminal devices; the sub-region where all the terminal devices are located; the remaining service time corresponding to all the terminal devices.

[0258] Optionally, when the multiple terminal device groups are determined according to the frequency offset range corresponding to all the terminal devices, the frequency offset range is related to the number of terminal devices within the corresponding terminal device group.

[0259] Optionally, when the multiple terminal device groups are determined according to the remaining service time corresponding to all the terminal devices, the first terminal device group among the multiple terminal device groups performs satellite handover, and the multiple terminal device groups further include a second terminal device group that does not perform satellite handover, and the terminal devices within the second terminal device group do not perform resource multiplexing.

[0260] Optionally, frequency domain isolation is performed between any two of the multiple terminal device groups.

[0261] Optionally, the multiple sequences belong to an OCC group.

[0262] Figure 11 The figure shows a schematic structural diagram of a communication device according to an embodiment of the present application. Figure 11 The dotted line in it indicates that the unit or module is optional. The device 1100 can be used to implement the method described in the above method embodiment. The device 1100 can be a chip, a terminal device or a network device.

[0263] Device 1100 may include one or more processors 1110. The processor 1110 may support the device 1100 in implementing the methods described in the foregoing method embodiments. The processor 1110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may 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. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0264] Device 1100 may also include one or more memories 1120. A program is stored on the memory 1120, and the program may be executed by the processor 1110, so that the processor 1110 executes the methods described in the foregoing method embodiments. The memory 1120 may be independent of the processor 1110 or integrated in the processor 1110.

[0265] Device 1100 may also include a transceiver 1130. The processor 1110 may communicate with other devices or chips through the transceiver 1130. For example, the processor 1110 may send and receive data with other devices or chips through the transceiver 1130.

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

[0267] 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 a data center that includes one or more integrated available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)), etc.

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

[0269] 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 can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can 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.).

[0270] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal device or network device provided by the embodiments of the present application, and the computer program enables the computer to execute the methods performed by the terminal or network device in the various embodiments of the present application.

[0271] In the present application, the terms "system" and "network" 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" in the specification, claims, and drawings of the present application are used to distinguish different objects and not to describe a specific order. Furthermore, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion.

[0272] In the embodiments of the present application, the "indication" mentioned can be a direct indication, an indirect indication, or a representation of an association 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 association relationship between A and B.

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

[0274] 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 terminal devices and network devices). The present application does not limit its specific implementation manner. For example, predefined can refer to that defined in a protocol.

[0275] In the embodiments of the present application, determining B according to A or determining B based on A does not mean determining B only according to A. B can also be determined according to A and / or other information.

[0276] In the embodiments of the present application, the term "and / or" is merely a description of the associated 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.

[0277] In the embodiments of the present application, the magnitudes of the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0278] 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, direct coupling, or communication connection to each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical, or other forms.

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

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

[0281] As described above, the above 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 within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for wireless communication, characterized in that: include: The first terminal device repeatedly transmits the first uplink data according to the first sequence; The first sequence belongs to a plurality of mutually orthogonal sequences, the plurality of sequences are used for multiple terminal devices to multiplex a first resource, the first resource is used for the multiple terminal devices to respectively perform repeated transmission of a plurality of uplink data, the plurality of terminal devices include the first terminal device, and the plurality of uplink data include the first uplink data.

2. The method according to claim 1, characterized in that: The multiple terminal devices include at least one second terminal device that does not support resource reuse, and the reuse of the first resource needs to meet at least one of the following requirements: The multiple uplink data correspond to the same redundancy version; The first resource is not used for uplink control information UCI multiplexing or UCI multiplexing is performed according to the first information; There is no frequency hopping on the first resource; The phase is continuous in a first time period corresponding to the first resource.

3. The method according to claim 2, characterized in that The second terminal device corresponds to a second sequence in which all code words are 1.

4. The method according to claim 2 or 3, characterized in that: When at least part of the transmission resources of the first UCI overlap with the first resources, or when the number of repeated transmissions of the first UCI is different from the number of repeated transmissions of the first uplink data, the transmission mode of the first UCI is determined according to the first information.

5. The method according to claim 4, characterized in that The first information includes one or more of the following: the priority of the first UCI; a transmission priority of the first UCI relative to the first uplink data; The load of the network where the first terminal device is located; The resource requirements of the first terminal device.

6. The method according to claim 5, characterized in that The first UCI includes at least one of feedback information, a scheduling request, and channel state information, and the priority of the first UCI includes at least one of the following: The feedback information has the highest priority; The priority of the feedback information is higher than the priority of the scheduling request; The priority of the feedback information is higher than the priority of the channel state information; The priority of the scheduling request is higher than the priority of the channel state information; The channel state information has the lowest priority.

7. The method according to any one of claims 4 to 6, characterized in that: The transmission mode of the first UCI includes one of the following: Transmission of the first UCI on the first resource is canceled; The first UCI is preferentially transmitted on the first resource, and repeated transmission of the multiple uplink data is cancelled; The first UCI and the first uplink data are transmitted together on the first resource.

8. The method according to claim 7, characterized in that When the first UCI and the first uplink data are transmitted together on the first resource, the first UCI is carried on all uplink channels used for repeatedly transmitting the first uplink data.

9. The method according to claim 7, characterized in that: The repeated transmission of the first uplink data is carried on multiple uplink channels. When the first UCI and the first uplink data are transmitted together on the first resource, the first UCI is carried on a first uplink channel among the multiple uplink channels, and the first uplink channel is determined according to an instruction of a network device.

10. The method according to any one of claims 1 to 9, characterized in that The first uplink data is carried on a first physical uplink data channel PUSCH, and the configuration of the first sequence is related to the configuration of repeated transmission of the first PUSCH.

11. The method according to any one of claims 1 to 10, characterized in that The configuration parameters of the first sequence are carried in one or more of the following information: Higher layer signaling; Downlink control information DCI; Radio Resource Control RRC signaling; The repetition transmission parameter of the first uplink data.

12. The method according to claim 11, characterized in that The configuration parameters of the first sequence are carried in a first indication field of the DCI, and the number of bits of the first indication field is related to the number of the multiple terminal devices.

13. The method according to claim 12, characterized in that The first indication field is used to indicate the number of the multiple sequences and the index of the first sequence in the multiple sequences.

14. The method according to claim 12 or 13, characterized in that The first indication field is determined according to a control information format corresponding to the DCI, and the first indication field is also used to indicate a demodulation reference signal DMRS port.

15. The method according to any one of claims 1 to 14, characterized in that The method further comprises: The first terminal device receives second information; The second information is used to indicate whether the first sequence and / or the multiple sequences are enabled.

16. The method according to any one of claims 1 to 15, characterized in that The multiple terminal devices belong to a first terminal device group, the first terminal device group is one of multiple terminal device groups, and the multiple terminal device groups are determined according to one or more of the following information: Frequency offset range corresponding to all terminal devices; The sub-area where all terminal devices are located; The remaining service time corresponding to all terminal devices.

17. The method according to claim 16, characterized in that When the multiple terminal device groups are determined according to the frequency offset ranges corresponding to all the terminal devices, the frequency offset ranges are related to the number of terminal devices in the corresponding terminal device groups.

18. The method according to claim 16, characterized in that When the multiple terminal device groups are determined based on the remaining service time corresponding to all the terminal devices, the first terminal device group among the multiple terminal device groups performs satellite switching, and the multiple terminal device groups also include a second terminal device group that does not perform satellite switching, and the terminal devices in the second terminal device group do not perform resource multiplexing.

19. The method according to any one of claims 16 to 18, characterized in that: Frequency domain isolation is performed between any two terminal device groups among the multiple terminal device groups.

20. The method according to any one of claims 1 to 19, characterized in that The multiple sequences belong to an orthogonal cover code OCC group.

21. A method for wireless communication, characterized in that: include: The network device receives repeated transmissions of multiple uplink data from multiple terminal devices; The repeated transmission of the multiple uplink data is based on multiple mutually orthogonal sequences multiplexing the first resource, the multiple sequences include a first sequence, the first sequence is used for the first terminal device among the multiple terminal devices to repeatedly transmit the first uplink data, and the multiple uplink data include the first uplink data.

22. The method according to claim 21, characterized in that The multiple terminal devices include at least one second terminal device that does not support resource reuse, and the reuse of the first resource needs to meet at least one of the following requirements: The multiple uplink data correspond to the same redundancy version; The first resource is not used for uplink control information UCI multiplexing or UCI multiplexing is performed according to the first information; There is no frequency hopping on the first resource; The phase is continuous in a first time period corresponding to the first resource.

23. The method according to claim 22, characterized in that The second terminal device corresponds to a second sequence in which all code words are 1.

24. The method according to claim 22 or 23, characterized in that When at least part of the transmission resources of the first UCI overlap with the first resources, or when the number of repeated transmissions of the first UCI is different from the number of repeated transmissions of the first uplink data, the transmission mode of the first UCI is determined according to the first information.

25. The method according to claim 24, characterized in that The first information includes one or more of the following: the priority of the first UCI; a transmission priority of the first UCI relative to the first uplink data; The load of the network where the first terminal device is located; The resource requirements of the first terminal device.

26. The method according to claim 25, characterized in that The first UCI includes at least one of feedback information, a scheduling request, and channel state information, and the priority of the first UCI includes at least one of the following: The feedback information has the highest priority; The priority of the feedback information is higher than the priority of the scheduling request; The priority of the feedback information is higher than the priority of the channel state information; The priority of the scheduling request is higher than the priority of the channel state information; The channel state information has the lowest priority.

27. The method according to any one of claims 24 to 26, characterized in that The transmission mode of the first UCI includes one of the following: Transmission of the first UCI on the first resource is canceled; The first UCI is preferentially transmitted on the first resource, and repeated transmission of the multiple uplink data is cancelled; The first UCI and the first uplink data are transmitted together on the first resource.

28. The method according to claim 27, characterized in that When the first UCI and the first uplink data are transmitted together on the first resource, the first UCI is carried on all uplink channels used for repeatedly transmitting the first uplink data.

29. The method according to claim 27, characterized in that The repeated transmission of the first uplink data is carried on multiple uplink channels. When the first UCI and the first uplink data are transmitted together on the first resource, the first UCI is carried on a first uplink channel among the multiple uplink channels, and the first uplink channel is determined according to an instruction of a network device.

30. The method according to any one of claims 21 to 29, characterized in that The first uplink data is carried on a first physical uplink data channel PUSCH, and the configuration of the first sequence is related to the configuration of repeated transmission of the first PUSCH.

31. The method according to any one of claims 21 to 30, characterized in that The configuration parameters of the first sequence are carried in one or more of the following information: Higher layer signaling; Downlink control information DCI; Radio Resource Control RRC signaling; The repetition transmission parameter of the first uplink data.

32. The method according to claim 31, characterized in that The configuration parameters of the first sequence are carried in a first indication field of the DCI, and the number of bits of the first indication field is related to the number of the multiple terminal devices.

33. The method according to claim 32, characterized in that The first indication field is used to indicate the number of the multiple sequences and the index of the first sequence in the multiple sequences.

34. The method according to claim 32 or 33, characterized in that The first indication field is determined according to a control information format corresponding to the DCI, and the first indication field is also used to indicate a demodulation reference signal DMRS port.

35. The method according to any one of claims 21 to 34, characterized in that The method further comprises: The network device sends second information; The second information is used to indicate whether the first sequence and / or the multiple sequences are enabled.

36. The method according to any one of claims 21 to 35, characterized in that The multiple terminal devices belong to a first terminal device group, the first terminal device group is one of multiple terminal device groups, and the multiple terminal device groups are determined according to one or more of the following information: Frequency offset range corresponding to all terminal devices; The sub-area where all terminal devices are located; The remaining service time corresponding to all terminal devices.

37. The method according to claim 36, characterized in that When the multiple terminal device groups are determined according to the frequency offset ranges corresponding to all the terminal devices, the frequency offset ranges are related to the number of terminal devices in the corresponding terminal device groups.

38. The method according to claim 36, characterized in that When the multiple terminal device groups are determined based on the remaining service time corresponding to all the terminal devices, the first terminal device group among the multiple terminal device groups performs satellite switching, and the multiple terminal device groups also include a second terminal device group that does not perform satellite switching, and the terminal devices in the second terminal device group do not perform resource multiplexing.

39. The method according to any one of claims 36 to 38, characterized in that Frequency domain isolation is performed between any two terminal device groups among the multiple terminal device groups.

40. The method according to any one of claims 21 to 39, characterized in that The multiple sequences belong to an orthogonal cover code OCC group.

41. A device for wireless communication, characterized in that: The device is a first terminal device, and the device includes: A transceiver unit, configured to repeatedly transmit first uplink data according to a first sequence; The first sequence belongs to a plurality of mutually orthogonal sequences, the plurality of sequences are used for multiple terminal devices to multiplex a first resource, the first resource is used for the multiple terminal devices to respectively perform repeated transmission of a plurality of uplink data, the plurality of terminal devices include the first terminal device, and the plurality of uplink data include the first uplink data.

42. The device according to claim 41, characterized in that The multiple terminal devices include at least one second terminal device that does not support resource reuse, and the reuse of the first resource needs to meet at least one of the following requirements: The multiple uplink data correspond to the same redundancy version; The first resource is not used for uplink control information UCI multiplexing or UCI multiplexing is performed according to the first information; There is no frequency hopping on the first resource; The phase is continuous in a first time period corresponding to the first resource.

43. The device according to claim 42, characterized in that The second terminal device corresponds to a second sequence in which all code words are 1.

44. The device according to claim 42 or 43, characterized in that When at least part of the transmission resources of the first UCI overlap with the first resources, or when the number of repeated transmissions of the first UCI is different from the number of repeated transmissions of the first uplink data, the transmission mode of the first UCI is determined according to the first information.

45. The device according to claim 44, characterized in that The first information includes one or more of the following: the priority of the first UCI; a transmission priority of the first UCI relative to the first uplink data; The load of the network where the first terminal device is located; The resource requirements of the first terminal device.

46. ​​The device according to claim 45, characterized in that The first UCI includes at least one of feedback information, a scheduling request, and channel state information, and the priority of the first UCI includes at least one of the following: The feedback information has the highest priority; The priority of the feedback information is higher than the priority of the scheduling request; The priority of the feedback information is higher than the priority of the channel state information; The priority of the scheduling request is higher than the priority of the channel state information; The channel state information has the lowest priority.

47. The device according to any one of claims 44 to 46, characterized in that The transmission mode of the first UCI includes one of the following: Transmission of the first UCI on the first resource is canceled; The first UCI is preferentially transmitted on the first resource, and repeated transmission of the multiple uplink data is cancelled; The first UCI and the first uplink data are transmitted together on the first resource.

48. The device according to claim 47, characterized in that When the first UCI and the first uplink data are transmitted together on the first resource, the first UCI is carried on all uplink channels used for repeatedly transmitting the first uplink data.

49. The device according to claim 47, characterized in that The repeated transmission of the first uplink data is carried on multiple uplink channels. When the first UCI and the first uplink data are transmitted together on the first resource, the first UCI is carried on a first uplink channel among the multiple uplink channels, and the first uplink channel is determined according to an instruction of a network device.

50. The device according to any one of claims 41 to 49, characterized in that The first uplink data is carried on a first physical uplink data channel PUSCH, and the configuration of the first sequence is related to the configuration of repeated transmission of the first PUSCH.

51. The device according to any one of claims 41 to 50, characterized in that The configuration parameters of the first sequence are carried in one or more of the following information: Higher layer signaling; Downlink control information DCI; Radio Resource Control RRC signaling; The repetition transmission parameter of the first uplink data.

52. The device according to claim 51, characterized in that The configuration parameters of the first sequence are carried in a first indication field of the DCI, and the number of bits of the first indication field is related to the number of the multiple terminal devices.

53. The device according to claim 52, characterized in that The first indication field is used to indicate the number of the multiple sequences and the index of the first sequence in the multiple sequences.

54. The device according to claim 52 or 53, characterized in that The first indication field is determined according to a control information format corresponding to the DCI, and the first indication field is also used to indicate a demodulation reference signal DMRS port.

55. The device according to any one of claims 41 to 54, characterized in that The transceiver unit is further used to receive second information; wherein the second information is used to indicate whether the first sequence and / or the multiple sequences are enabled.

56. The device according to any one of claims 41 to 55, characterized in that The multiple terminal devices belong to a first terminal device group, the first terminal device group is one of multiple terminal device groups, and the multiple terminal device groups are determined according to one or more of the following information: Frequency offset range corresponding to all terminal devices; The sub-area where all terminal devices are located; The remaining service time corresponding to all terminal devices.

57. The device according to claim 56, characterized in that When the multiple terminal device groups are determined according to the frequency offset ranges corresponding to all the terminal devices, the frequency offset ranges are related to the number of terminal devices in the corresponding terminal device groups.

58. The device according to claim 56, characterized in that When the multiple terminal device groups are determined based on the remaining service time corresponding to all the terminal devices, the first terminal device group among the multiple terminal device groups performs satellite switching, and the multiple terminal device groups also include a second terminal device group that does not perform satellite switching, and the terminal devices in the second terminal device group do not perform resource multiplexing.

59. The device according to any one of claims 56 to 58, characterized in that Frequency domain isolation is performed between any two terminal device groups among the multiple terminal device groups.

60. The device according to any one of claims 41 to 59, characterized in that The multiple sequences belong to an orthogonal cover code OCC group.

61. A device for wireless communication, characterized in that: The device is a network device, and the device includes: A transceiver unit, configured to receive repeated transmissions of multiple uplink data from multiple terminal devices; The repeated transmission of the multiple uplink data is based on multiple mutually orthogonal sequences multiplexing the first resource, the multiple sequences include a first sequence, the first sequence is used for the first terminal device among the multiple terminal devices to repeatedly transmit the first uplink data, and the multiple uplink data include the first uplink data.

62. The device according to claim 61, characterized in that The multiple terminal devices include at least one second terminal device that does not support resource reuse, and the reuse of the first resource needs to meet at least one of the following requirements: The multiple uplink data correspond to the same redundancy version; The first resource is not used for uplink control information UCI multiplexing or UCI multiplexing is performed according to the first information; There is no frequency hopping on the first resource; The phase is continuous in a first time period corresponding to the first resource.

63. The device according to claim 62, characterized in that The second terminal device corresponds to a second sequence in which all code words are 1.

64. The device according to claim 62 or 63, characterized in that When at least part of the transmission resources of the first UCI overlap with the first resources, or when the number of repeated transmissions of the first UCI is different from the number of repeated transmissions of the first uplink data, the transmission mode of the first UCI is determined according to the first information.

65. The device according to claim 64, characterized in that The first information includes one or more of the following: the priority of the first UCI; a transmission priority of the first UCI relative to the first uplink data; The load of the network where the first terminal device is located; The resource requirements of the first terminal device.

66. The device according to claim 65, characterized in that The first UCI includes at least one of feedback information, a scheduling request, and channel state information, and the priority of the first UCI includes at least one of the following: The feedback information has the highest priority; The priority of the feedback information is higher than the priority of the scheduling request; The priority of the feedback information is higher than the priority of the channel state information; The priority of the scheduling request is higher than the priority of the channel state information; The channel state information has the lowest priority.

67. The device according to any one of claims 64 to 66, characterized in that The transmission mode of the first UCI includes one of the following: Transmission of the first UCI on the first resource is canceled; The first UCI is preferentially transmitted on the first resource, and repeated transmission of the multiple uplink data is cancelled; The first UCI and the first uplink data are transmitted together on the first resource.

68. The device according to claim 67, characterized in that When the first UCI and the first uplink data are transmitted together on the first resource, the first UCI is carried on all uplink channels used for repeatedly transmitting the first uplink data.

69. The device according to claim 67, characterized in that The repeated transmission of the first uplink data is carried on multiple uplink channels. When the first UCI and the first uplink data are transmitted together on the first resource, the first UCI is carried on a first uplink channel among the multiple uplink channels, and the first uplink channel is determined according to an instruction of a network device.

70. The device according to any one of claims 61 to 69, characterized in that The first uplink data is carried on a first physical uplink data channel PUSCH, and the configuration of the first sequence is related to the configuration of repeated transmission of the first PUSCH.

71. The device according to any one of claims 61 to 70, characterized in that The configuration parameters of the first sequence are carried in one or more of the following information: Higher layer signaling; Downlink control information DCI; Radio Resource Control RRC signaling; The repetition transmission parameter of the first uplink data.

72. The device according to claim 71, characterized in that The configuration parameters of the first sequence are carried in a first indication field of the DCI, and the number of bits of the first indication field is related to the number of the multiple terminal devices.

73. The device according to claim 72, characterized in that The first indication field is used to indicate the number of the multiple sequences and the index of the first sequence in the multiple sequences.

74. The device according to claim 72 or 73, characterized in that The first indication field is determined according to a control information format corresponding to the DCI, and the first indication field is also used to indicate a demodulation reference signal DMRS port.

75. The device according to any one of claims 61 to 74, characterized in that The transceiver unit is further used to send second information; wherein the second information is used to indicate whether the first sequence and / or the multiple sequences are enabled.

76. The device according to any one of claims 61 to 75, characterized in that The multiple terminal devices belong to a first terminal device group, the first terminal device group is one of multiple terminal device groups, and the multiple terminal device groups are determined according to one or more of the following information: Frequency offset range corresponding to all terminal devices; The sub-area where all terminal devices are located; The remaining service time corresponding to all terminal devices.

77. The device according to claim 76, characterized in that When the multiple terminal device groups are determined according to the frequency offset ranges corresponding to all the terminal devices, the frequency offset ranges are related to the number of terminal devices in the corresponding terminal device groups.

78. The device according to claim 76, characterized in that When the multiple terminal device groups are determined based on the remaining service time corresponding to all the terminal devices, the first terminal device group among the multiple terminal device groups performs satellite switching, and the multiple terminal device groups also include a second terminal device group that does not perform satellite switching, and the terminal devices in the second terminal device group do not perform resource multiplexing.

79. The device according to any one of claims 76 to 78, characterized in that Frequency domain isolation is performed between any two terminal device groups among the multiple terminal device groups.

80. The device according to any one of claims 61 to 79, characterized in that The multiple sequences belong to an orthogonal cover code OCC group.

81. A communication device, characterized in that: The invention comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory to execute the method according to any one of claims 1 to 40.

82. A device, characterized in that The invention comprises a processor, which is used to call a program from a memory to execute the method according to any one of claims 1 to 40.

83. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 40.

84. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 40.

85. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 40.

86. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 40.

Images