Method and apparatus for wireless communication

Abstract

Provided are a method and apparatus for wireless communication for enhancing uplink capacity and coverage. The method comprises: a first terminal device performs repetitive transmission of first uplink data on the basis of a first sequence, wherein the first sequence is one of 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 transmission of a plurality of pieces of uplink data, the plurality of terminal devices comprise the first terminal device, and the plurality of pieces of uplink data comprise the first uplink data.

Description

Methods and apparatus for wireless communication Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method and apparatus for wireless communication. Background Technology

[0002] In non-terrestrial network (NTN) systems, due to transmission delays and high path losses, terminal devices can enhance uplink capacity and reliability by repeatedly transmitting data. However, NTN cells need to serve a large number of terminal devices; therefore, improving uplink coverage and spectrum utilization efficiency in NTN systems has become an urgent technical challenge. Summary of the Invention

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

[0004] In a first aspect, a method for wireless communication is provided, comprising: a first terminal device repeatedly transmitting 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 multiple terminal devices to reuse first resources, the first resources are used for the plurality of terminal devices to repeatedly transmit a plurality of uplink data respectively, the plurality of terminal devices includes the first terminal device, and the plurality of uplink data includes the first uplink data.

[0005] In a second aspect, a method for wireless communication is provided, comprising: a network device receiving repeated transmissions of multiple uplink data from multiple terminal devices; wherein the repeated transmissions of the multiple uplink data reuse a first resource based on multiple mutually orthogonal sequences, the multiple sequences including a first sequence, the first sequence being used by a first terminal device among the multiple terminal devices to perform repeated transmissions of first uplink data, the multiple uplink data including the first uplink data.

[0006] Thirdly, an apparatus for wireless communication is provided, the apparatus being a first terminal device, the apparatus comprising: a transceiver unit, configured to repeatedly 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 multiple terminal devices to reuse first resources, the first resources are used for the plurality of terminal devices to repeatedly transmit a plurality of uplink data respectively, the plurality of terminal devices includes the first terminal device, and the plurality of uplink data includes the first uplink data.

[0007] Fourthly, an apparatus for wireless communication is provided, the apparatus being a network device, the apparatus comprising: a transceiver unit for receiving repeated transmissions of multiple uplink data from multiple terminal devices; wherein the repeated transmission of the multiple uplink data is based on multiple orthogonal sequences multiplexing a first resource, the multiple sequences including a first sequence, the first sequence being used by a first terminal device among the multiple terminal devices to perform repeated transmission of first uplink data, the multiple uplink data including the first uplink data.

[0008] Fifthly, a communication device is provided, including a memory and a processor, the memory for storing a program, and the processor for calling the program in the memory to perform the method as described in the first or second aspect.

[0009] A sixth aspect provides an apparatus including a processor for calling a program from memory to perform the method as described in the first or second aspect.

[0010] A seventh aspect provides a chip including a processor for calling a program from memory, causing a device having the chip mounted to perform the method as described in the first or second aspect.

[0011] Eighthly, a computer-readable storage medium is provided having a program stored thereon that causes a computer to perform the method as described in the first or second aspect.

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

[0013] In a tenth aspect, a computer program is provided that causes a computer to perform the method as described in the first or second aspect.

[0014] In this embodiment, the first terminal device can determine a first sequence for repeatedly transmitting first uplink data based on multiple mutually orthogonal sequences. These multiple mutually orthogonal sequences can be used by multiple terminal devices, including the first terminal device, to multiplevert the first resource. Therefore, multiple terminal devices can perform repeated uplink data transmission on the first resource based on orthogonal sequences, thereby effectively enhancing uplink capacity and improving spectrum utilization efficiency. Attached Figure Description

[0015] Figure 1 shows the wireless communication system used in an embodiment of this application.

[0016] Figure 2 shows an NTN system used in an embodiment of this application.

[0017] Figure 3 shows another NTN system used in an embodiment of this application.

[0018] Figure 4 is a flowchart illustrating a method for wireless communication provided in an embodiment of this application.

[0019] Figure 5 is a schematic diagram of one possible implementation of the method shown in Figure 4.

[0020] Figure 6 is a schematic diagram of another possible implementation of the method shown in Figure 4.

[0021] Figure 7 is a schematic diagram of another possible implementation of the method shown in Figure 4.

[0022] Figure 8 is a flowchart illustrating one possible implementation of the method shown in Figure 4.

[0023] Figure 9 is a schematic diagram of a device for wireless communication provided in an embodiment of this application.

[0024] Figure 10 is a schematic diagram of another device for wireless communication provided in an embodiment of this application.

[0025] Figure 11 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0026] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0027] The embodiments of this application can be applied to various communication systems. For example, the embodiments of this application can be applied to Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A), New Radio (NR), evolution systems of NR, LTE-based access to unlicensed spectrum (LTE-U), NR-based access to unlicensed spectrum (NR-U), Universal Mobile Telecommunications System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), and 5th-generation (5G) systems. The embodiments of this application can also be applied to other communication systems, such as 6th-generation (6G) mobile communication systems, or future communication systems such as satellite communication systems.

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

[0029] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

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

[0031] The embodiments of this application can be applied to NTN systems. As an example, the NTN system can be a 4G-based NTN system, an NR-based NTN system, an Internet of Things (IoT)-based NTN system, or a narrowband Internet of Things (NB-IoT)-based NTN system.

[0032] A communication system may include one or more terminal devices. The terminal devices mentioned in the embodiments of this application may 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 equipment, 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 capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a next-generation communication system (e.g., NR system), or terminal device in a future 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 a user. For example, the terminal device may be a handheld device, an in-vehicle device, etc., with wireless connectivity. As some specific examples, the terminal device may be a mobile phone, tablet, laptop, PDA, 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, or satellite.

[0036] In addition to terminal devices, the communication system may also include one or more network devices. In this embodiment, the network device can be a device for communicating with the terminal device; 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. In this embodiment, the network device may refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (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, radio node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0037] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0038] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0039] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be a satellite or a balloon station. In some embodiments of this application, the network device may also be a base station located on land, water, or other similar locations.

[0040] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0041] For example, FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application. The wireless communication system 100 shown in FIG1 includes a network device and multiple terminal devices. The network device 110 can provide communication coverage for a specific geographical area and can communicate with terminal devices located within the coverage area. The multiple terminal devices are, for example, terminal devices 120a to 120j in FIG1.

[0042] Optionally, the wireless communication system 100 shown in FIG1 may further include multiple network devices and each network device may include other number of terminal devices within its coverage area. This application embodiment does not limit this.

[0043] For example, Figure 2 is a schematic diagram of an architecture of the NTN system mentioned above. The NTN system 200 shown in Figure 2 uses satellite 210 as an airborne platform. As shown in Figure 2, the satellite radio access network includes satellite 210, service link 220, feeder link 230, terminal equipment 240, gateway (GW) 250, and network 260 including base stations and core network.

[0044] Satellite 210 is a spacecraft based on a space platform. Service link 220 refers to the link between satellite 210 and terminal equipment 240. Feeder link 230 refers to the link between gateway 250 and satellite 210. The Earth-based gateway 250 connects satellite 210 to the base station or core network, depending on the NTN architecture chosen.

[0045] The NTN architecture shown in Figure 2 is a bend-tube transponder architecture. In this architecture, the base station is located on Earth behind gateway 250, and satellite 210 acts as a relay. Satellite 210 operates as a relay that forwards signals from feeder link 230 to serving link 220, or forwards signals from serving link 220 to feeder link 230. That is, satellite 210 does not have the function of a base station; communication between terminal device 240 and the base station in network 260 needs to be relayed through satellite 210.

[0046] For example, Figure 3 is a schematic diagram of another architecture of the NTN system. As shown in Figure 3, 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. Unlike Figure 2, the satellite 310 has a base station 312, and the network 360 behind the gateway 350 only includes the core network.

[0047] Figure 3 shows the NTN architecture, which is a regenerative transponder architecture. In this architecture, satellite 310 carries base station 312, which can be directly connected to the Earth-based core network via a link. Satellite 310 has the function of a base station, and terminal device 340 can communicate directly with satellite 310. Therefore, satellite 310 can be referred to as a network device.

[0048] The communication system with the architecture shown in Figures 2 and 3 may include multiple network devices, and each network device may include other terminal devices within its coverage area. This application embodiment does not limit this.

[0049] In the embodiments of this application, the communication system shown in Figures 1 to 3 may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), which are not limited in this embodiment.

[0050] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system 100 shown in FIG1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 can be the specific devices described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities. This application embodiment does not limit this.

[0051] To facilitate understanding, some related technical knowledge involved in the embodiments of this application is first introduced. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0052] With the development of communication technologies, communication systems (such as 5G) will integrate the market potential of satellite and terrestrial network infrastructure. For example, the 5G standard makes NTN, including satellite segments, part of the recognized 3rd generation partnership project (3GPP) 5G connectivity infrastructure.

[0053] NTN refers to a network or network segment that uses radio frequency (RF) resources on spacecraft (e.g., satellites) or unmanned aerial system (UAS) platforms. Satellites are classified according to their orbital altitude, including low Earth orbit (LEO), medium Earth orbit (MEO), geostationary Earth orbit (GEO), and highly elliptical orbit (HEO). LEO is a geocentric orbit with an altitude of 2000 km or less, or at least 11.25 cycles per day, with an eccentricity of less than 0.25. Most man-made objects in outer space are located in LEO. LEO satellites orbit the Earth at high speeds (mobility), but in predictable or deterministic orbits.

[0054] Satellites at different orbital altitudes have different orbital periods. For example, typical LEO altitudes are 250-1500 km with orbital periods of 90-120 minutes; typical MEO altitudes are 5000-25000 km with orbital periods of 3-15 hours; and GEO altitudes are approximately 35786 km with orbital periods of 24 hours.

[0055] As shown in Figures 2 and 3 above, which use satellite as an example, typical scenarios for terminal devices accessing the NTN system involve either a transparent NTN payload or a regenerative NTN payload. Specifically, the bent-tube transponder architecture shown in Figure 2 corresponds to a transparent NTN payload, with the satellite or UAS platform acting as a relay; the regenerative transponder architecture shown in Figure 3 corresponds to a regenerative NTN payload, with a base station on the satellite or UAS platform. In the network architectures shown in Figures 2 and 3, the base station can involve various communication systems, such as NB-IoT.

[0056] In NTN systems, terminal devices communicate with network equipment via satellite or airborne platforms. Satellites and other airborne platforms cover a larger area; therefore, the number of terminal devices served within an NTN cell is typically much greater than in a terrestrial network (TN) cell. To meet the uplink transmission needs of these terminal devices, the uplink (UL) communication requirements are usually quite high. Therefore, enhancing uplink capacity and coverage, and improving spectrum utilization efficiency are worthy of research in NTN systems.

[0057] As an example, in communication systems such as NTN based on the Internet of Things, the amount of available spectrum in the 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 uplink capacity and coverage in NTN systems, relevant technologies can be introduced. In some embodiments, retransmission (or duplicate transmission) of the Physical Uplink Shared Channel (PUSCH) and / or Hybrid Automatic Repeat ReQuest (HARQ) can be supported in NTN systems, but this will increase the burden and overhead on uplink transmission.

[0059] Optionally, PUSCH retransmissions can be dynamically scheduled via the physical downlink control channel (PDCCH) or triggered by a configured retransmission timer. Besides dynamically scheduled PUSCH transmissions, semi-static PUSCH transmissions are also possible, i.e., configured grants (CG) or pre-configured grants. For configured grant type 1, all parameters for PUSCH transmission are configured by radio resource control (RRC) and take effect immediately. For configured grant type 2, RRC configures a subset of higher-layer parameters for PUSCH transmission, with the remaining parameters indicated by the downlink control information (DCI) format upon activation. The DCI also includes frequency and time domain resource allocation indications. For example, the DCI can use a time domain resource indication field to point to a row index of a table indicating the slot offset, start symbol, and number of symbols. The DCI can specify a portion of a slot for uplink transmission and supports the ability to change slot resource allocation across different slots.

[0060] Optionally, some communication systems (e.g., NR) can configure repeated PUSCH transmissions with repetition type A within time slots, i.e., repeated PUSCH transmissions. For repeated PUSCH transmissions, instead of being indicated by table-based dynamic signaling, they are configured via a separate RRC signaling. For example, in scenarios where the same transport block can be repeatedly transmitted on up to eight time slots, this is configured via RRC signaling.

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

[0062] Optionally, in multi-user scenarios, 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 group.

[0063] Optionally, due to the mutual orthogonality of OCCs, the superimposed signals will not interfere with each other in the frequency domain, thus realizing frequency domain resource multiplexing for multiple users. At the receiver, appropriate 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 receiver, appropriate synchronization and channel estimation are required on each PRB to cope with possible time delays and channel fading during transmission.

[0064] The preceding sections introduced PUSCH retransmission and OCC mechanisms, which can enhance uplink coverage. In NTN scenarios, introducing OCC over PUSCH retransmission allows multiple terminal devices to use a large number of PUSCH retransmissions to meet link budget requirements. However, combining PUSCH retransmission and OCC mechanisms presents new technical challenges. This is because different terminal devices determine their PUSCH retransmission configurations via DCI or RRC signaling. These terminal devices and their corresponding PUSCH retransmission configurations may differ. When these terminal devices reuse the same resources for PUSCH retransmission based on OCC, various problems may arise.

[0065] For example, different terminal devices may transmit PUSCH a different number of times, thus requiring different amounts of resources.

[0066] For example, some terminal devices may need to multiplex PUSCH repetition transmission resources with uplink control information (UCI). UCI multiplexing is an important feature of the physical uplink control channel (PUCCH), which improves transmission latency and robustness. When UCI is multiplexed on one of multiple PUSCH repetitions, the orthogonality within the OCC group is disrupted due to the different signal structures of the PUSCH repetitions. Therefore, if UCI is multiplexed on one of the PUSCH repetitions, OCC will not be used for those PUSCH repetitions. It is evident that UCI multiplexing and OCC are difficult to configure jointly, and OCC should be avoided on repetitions with UCI multiplexing. In other words, for multiple PUSCH transmissions with OCC, UCI multiplexing should be avoided.

[0067] For example, some terminal devices do not support OCC-based resource reuse, or lack the relevant OCC capabilities. How to multiplex OCC-capable terminal devices with non-OCC-capable terminal devices is also a problem that needs to be considered.

[0068] In summary, in NTN systems, how to combine PUSCH retransmission and OCC to better improve uplink capacity is a technical problem that needs to be solved.

[0069] It should be noted that the above-mentioned issue of how to combine PUSCH retransmission and OCC in the NTN system is only an example. The embodiments of this application can be applied to communication scenarios in NTN where uplink data retransmission is combined with OCC, and are also applicable to TN systems.

[0070] To address the aforementioned problems, this application proposes a method for wireless communication. This method allows a first terminal device to repeatedly transmit first uplink data based on a first sequence. Multiple terminal devices can reuse first resources based on multiple mutually orthogonal sequences to achieve repeated transmission of multiple uplink data, thereby enhancing uplink capacity and coverage and improving spectrum utilization by introducing orthogonal sequences into the repeated transmission of uplink data. Optionally, this method is primarily aimed at enhancing uplink capacity and coverage in systems with long communication latency, such as NTN (Network Network Technology). Therefore, the first terminal device and the network device can be a terminal device and a network-side device in the NTN, respectively.

[0071] To facilitate understanding, the method proposed in the embodiments of this application will be described in detail below with reference to Figure 4. Figure 4 is presented from the perspective of the interaction between the first terminal device and the network device.

[0072] The first terminal device can be any type of communication terminal or relay for uplink transmission, without limitation. 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 an electricity meter. In some embodiments, the first terminal device can be any communication terminal within the coverage of the network device, such as terminal devices 120a to 120j in FIG1.

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

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

[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, namely the first terminal device group.

[0076] As one embodiment, multiple terminal devices that share the same resources as the first terminal device belong to the first terminal device group. One or more terminal devices that share the same resources as the first terminal device can also be referred to as paired devices of the first terminal device.

[0077] The network device can be any of the network-side communication devices described above. In some embodiments, the network device includes a satellite in an NTN system, and the first terminal device can communicate with the network device via the satellite. For example, when a base station is deployed on a satellite, the first terminal device communicates directly with the base station on the satellite. For example, when the satellite acts as a relay, the first terminal device communicates with a network device located on the ground via the satellite. As an embodiment, when the network device includes a satellite, the first terminal device is currently located within the service area of ​​that satellite to perform uplink transmission to the network device via the satellite.

[0078] In some embodiments, multiple terminal devices within the first terminal device group are currently within the coverage area of ​​the same satellite.

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

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

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

[0082] In some embodiments, the first uplink data may be carried in an uplink channel. As an example, the first uplink data may be transmitted via a first uplink data channel. For instance, the first uplink data may be carried in a first PUSCH.

[0083] As one embodiment, 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 repeated transmissions of the first PUSCH, i.e., repeated transmission of the first PUSCH. In other words, 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, which can be referred to as PUSCH repetition within the OCC group.

[0085] In the above embodiments, multiple terminal devices, including the first terminal device, can each perform repeated transmissions of multiple uplink data. The repeated transmission of multiple uplink data can be replaced by the repeated transmission of multiple PUSCHs, i.e., repeated transmission of multiple PUSCHs.

[0086] In some embodiments, the retransmission of the first uplink data can be determined based on network-side or higher-layer configuration. As an example, the configuration for the first PUSCH retransmission can be indicated by a DCI sent by the network device. As another example, the configuration for the first PUSCH retransmission can be indicated by higher-layer parameters.

[0087] As one example, the first PUSCH repetition transmission corresponding to the first terminal device can be dynamically scheduled by uplink (UL) licensing in DCI, or it can be configured by configuring different types of licensing. That is to say, the configuration of the first PUSCH repetition transmission can be semi-static scheduling or dynamic scheduling, and there is no limitation here.

[0088] In the above embodiments, the different types of configuration authorization include configuration authorization type 1 and configuration authorization type 2 as described above. Configuration authorization type 1 is a semi-static configuration. Under configuration authorization type 1, the retransmission of the first uplink data is typically performed after receiving the GrantConfig from the higher-level configuration. Configuration authorization type 2 is a dynamic configuration. Under configuration authorization type 2, the retransmission of the first uplink data can be semi-persistently scheduled by the uplink authorization when DCI is effectively activated.

[0089] As one implementation, the terminal device can distinguish the configuration authorization type based on the parameters included in the higher-layer configuration. When the terminal device receives the GrantConfig parameter of the higher-layer configuration, which includes rrc ConfiguredPlunkGrant, it directly performs the corresponding operation for type 1 without detecting the uplink authorization in the DCI. Upon receiving the GrantConfig parameter of the higher-layer configuration, which does not include rrc ConfiguredPlunkGrant, the terminal device determines the configuration type to be type 2. If GrantConfigToAddModList is configured, multiple configuration authorizations corresponding to configuration authorization type 1 and / or configuration authorization type 2 may be active simultaneously on the bandwidth part (BWP) where the serving cell is active.

[0090] The first sequence belongs to a plurality of mutually orthogonal sequences. These 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 set of first sequences, which may also be called a set of orthogonal sequences.

[0091] As one embodiment, the first sequence can be one of a plurality of mutually orthogonal sequences. That is, the first sequence can be a single sequence. The first terminal device can perform repeated transmission of the first uplink data based on this single sequence.

[0092] As one embodiment, the first sequence can be at least two sequences from a plurality of mutually orthogonal sequences. That is, the first sequence can be multiple sequences. The first terminal device can perform repeated transmission of the first uplink data based on these multiple sequences.

[0093] As one implementation, the number of multiple sequences used for repeated transmission of the first uplink data is related to the number of repetitions. For example, the number of multiple sequences in the first sequence is equal to the number of repetitions, so each sequence corresponds to multiple transmissions of the first uplink data. Alternatively, when the first sequence is an OCC sequence, each element of the OCC sequence can be mapped to each repetition of the uplink data.

[0094] In another implementation, the data in the multiple sequences used for repeated transmission of the first uplink data is independent of the number of transmissions. For example, regardless of the number of transmissions, the first sequence always includes two orthogonal sequences, which are used alternately for each transmission of the first uplink data.

[0095] In some embodiments, the first sequence belongs to a set of multiple mutually orthogonal sequences that belong to an OCC group; that is, the multiple sequences form a set 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 repeated transmissions of uplink data.

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

[0097] Optionally, the first sequence set can use a Hadamard matrix as an orthogonal code. A Hadamard matrix is ​​a special type of orthogonal matrix where each row is mutually orthogonal. When the rows of a Hadamard matrix are used as orthogonal covering codes, the first sequence is any row sequence of the Hadamard matrix. Multiple sequences including the first sequence can be all or some row sequences of the Hadamard matrix.

[0098] Optionally, the multiple sequences including the first sequence can employ comb-shaped orthogonal codes, such that the multiple sequences have a fixed interval. For example, the multiple sequences can have a fixed time interval, that is, they are equally spaced in the time domain. By designing equal intervals in the time domain, the mutual interference between orthogonal codes used on different time domain units can be minimized, thereby improving the system performance.

[0099] Optionally, the multiple sequences including the first sequence can be orthogonal in the frequency domain or in the time domain, without limitation.

[0100] Multiple sequences, including the first sequence, can be used by multiple terminal devices, including the first terminal device, to reuse the first resource. Therefore, the first resource can be used for repeated transmission of the first uplink data. When resource reuse is implemented, the first resource can be used by the multiple terminal devices to perform repeated transmission of multiple uplink data respectively, thereby improving uplink coverage.

[0101] In some embodiments, the first resource can be any type of transmission resource that can be multiplexed by multiple terminal devices, and is not limited thereto. As an example, the first resource can be a time-domain resource or a frequency-domain resource, or it can be a code-domain resource or a spatial-domain resource. As an example, the first resource can be a combination of any number of time-domain resources, frequency-domain resources, spatial-domain resources, or code-domain resources.

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

[0103] In some embodiments, when the first sequence is a first OCC sequence, the OCC length corresponding to the first sequence is related to the number of terminal devices reusing the same resources. For example, for time slot OCCs with OCC lengths of 2 and 4 respectively, a maximum of 2 or 4 terminal devices can be reused.

[0104] The above, with reference to Figure 4, describes an embodiment of a method for repeated uplink data transmission based on orthogonal sequences. This method enables multiple terminal devices to reuse a first resource for repeated transmission of multiple uplink data, effectively enhancing uplink capacity / coverage. As mentioned earlier, when multiple terminal devices repeatedly transmit multiple uplink data based on orthogonal sequences, problems may arise such as uplink data and UCI multiplexing, and differences in the capabilities or resource sizes of different terminal devices. To address these issues, the method embodiment proposed in this application will be described below.

[0105] In some embodiments, multiple terminal devices may include at least one second terminal device that does not support resource reuse. That is, a first terminal device that supports resource reuse can share a first resource with a second terminal device that does not support resource reuse. In this way, system throughput can be doubled without allocating any additional time-domain or frequency-domain resources for different terminal devices. Terminal devices supporting resource reuse can refer to the terminal device having the ability to transmit uplink data based on orthogonal sequences. For example, a terminal device with OCC functionality is a terminal device that supports resource reuse, and correspondingly, a terminal device without OCC functionality is a terminal device that does not support resource reuse.

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

[0107] As an example, a network device can determine whether a terminal device supports resource reuse based on the capability information reported by the terminal device.

[0108] As one example, information regarding whether orthogonal sequences associated with a terminal device are enabled can be used to determine whether the terminal device supports resource reuse. For instance, an OCC enable / disable flag can indicate to the terminal device whether OCC is applied. Network devices can also use these flags to distinguish between terminal devices that perform OCC and those that do not.

[0109] In some embodiments, when multiple terminal devices include a second terminal device, the reuse of the first resource needs to satisfy at least one of the following: multiple uplink data correspond to the same redundant version (RV); the first resource is not used for UCI reuse or for UCI reuse based on 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, repeatedly transmitted PUSCHs can be assigned the same redundant version. Furthermore, the redundant versions within an OCC group must also remain unchanged; for example, in an NR NTN with inter-slot time-domain OCCs, the redundant versions within an OCC group should be consistent. It should be noted that when a PUSCH repeats across multiple OCC groups, cross-OCC group RV looping can be used to achieve coding gains for different redundant versions. Multiple OCC groups can include multiple OCC lengths. Traditional RV looping mechanisms can be extended to the unit of OCC groups.

[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 network device allocates time-frequency resources as the first resource to a terminal device configured with an OCC of length 4, the network device may want multiple terminal devices configured with an OCC of length 2 to reuse the first resource. Since the first resource supports inter-slot OCCs of length 4, the terminal devices configured with OCCs of length 2 can be instructed to turn off the RV loop. That is, for inter-slot OCCs, the RV loop can be executed based on multiple OCC lengths according to the network (NW) configuration / instruction.

[0112] It should be understood that in dynamically licensed PUSCH transmissions, different redundant versions are typically applied to adjacent PUSCH repetitions in a certain order. However, if inter-slot OCC groups are applied, the redundant 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 instance, a first PUSCH repeat transmission based on OCC does not multiplex the first resource with UCI. This means that if a network device schedules a terminal device with repeated PUSCH and UCI multiplexing, the network device will not configure OCC for that terminal device. Furthermore, the network device will not schedule other terminal devices to multiplex with that terminal device in the same time-domain and / or frequency-domain resources.

[0114] As an example, when the UCI reuses the first resource, it executes according to the first information, which will be described in detail below in conjunction with the first information.

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

[0116] As an example, the first time period corresponding to the first resource should maintain phase continuity. The first time period can be part or all of the time domain segment corresponding to the first resource. In an NTN system, since Doppler shift may cause phase discontinuities, phase continuity needs to be ensured when reusing the first resource. For example, when a terminal device reuses the first resource based on OCC, it needs to meet the phase continuity requirement between time slots corresponding to the OCC group, especially when the receiver uses a conventional OCC de-optimization algorithm for data reception.

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

[0118] In some embodiments, when the first terminal device and the second terminal device reuse the first resource, the first sequence corresponding to the first terminal device can be one of multiple OCC sequences, and the second terminal device can be considered to have a specific OCC sequence. For example, the second terminal device corresponds to a second sequence where all codewords are 1. That is, for traditional terminal devices, it can be considered to have applied 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 versions of terminal devices in the relevant network. Through backward compatibility design, terminal devices with different capabilities or different versions can be directly multiplexed based on OCC sequences.

[0119] As an example, the second sequence can be one of a plurality of mutually orthogonal sequences.

[0120] In some embodiments, when at least a portion of the transmission resources of the first UCI overlap with the first resource, or when the number of retransmissions of the first UCI differs from the number of retransmissions of the first uplink data, the first terminal device can determine the transmission mode of the first UCI based on the first information. For example, when performing PUSCH repetition based on inter-slot OCC groups, 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 based on the first information. As another example, 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 based on the first information.

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

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

[0123] In some embodiments, the transmission method 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 transmitted preferentially on the first resource, and the repeated transmission of multiple uplink data is cancelled; the first UCI and the first uplink data are transmitted together on the first resource. Therefore, the first UCI may or may not be transmitted on the first resource.

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

[0125] As one implementation, 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 repeated transmission of the first uplink data, thereby avoiding the problem of different signal structures caused by the multiplexing of a single UCI, which would lead to the destruction of orthogonality. For example, when the first UCI is transmitted together with multiple repeatedly transmitted PUSCHs on the first resource, the first UCI can be multiplexed onto each of the repeatedly transmitted PUSCHs.

[0126] For example, a base station can allocate a set of time slots and frequency domain resources for repeated PUSCH transmission within an OCC group. The number of repetitions of a PUSCH within an OCC group is N. All repetitions can use the same OCC encoding or different OCC encodings. The payload corresponding to the first UCI is added to the PUSCH, ensuring that each repeated PUSCH within the OCC group carries the same UCI payload, thus guaranteeing reliability.

[0127] To facilitate understanding, the following explanation is provided with reference to Figure 5. In Figure 5, an OCC of length 2 is used for repeated PUSCH transmission by multiple terminal devices. The transmission resources of the PUCCH carrying UCI are determined based on 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 transmitted twice, the UCI payload on the PUCCH can be added to each PUSCH, thereby achieving multiplexing of UCI and PUSCH.

[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 instructions of the network device. That is, 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 into a single PUSCH transmission, without sharing it with other PUSCHs corresponding to the OCC group. Therefore, each PUSCH transmission needs to be multiplexed independently to avoid interference when sharing resources within the group. In this scenario, the base station can allocate resources for multiple PUSCH repetitive transmissions to the terminal device, but does not configure inter-slot orthogonal coding for these repetitions.

[0130] It should be noted that the base station can configure each PUSCH repeat to have independent resources, or specify that a PUSCH repeat is independent from other PUSCH repeats. Optionally, any two independent PUSCH repeats can be isolated in the following ways: time-domain isolation and frequency-domain isolation. For time-domain isolation, different PUSCH repeats can use different time slots. For frequency-domain isolation, different PUSCH repeats can be allocated different PRBs.

[0131] For example, a base station can instruct a first terminal device on a specific PUSCH to carry the first UCI. The base station can instruct the first terminal device on PUSCH resource allocation and UCI multiplexing rules via DCI. Optionally, the UCI multiplexing configuration can include indicating 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, while other PUSCH repetitions only carry PUSCH data. The base station can determine, based on scheduling information, which repetitions carry the UCI payload and which do not. This specific payload can be decoded individually. The remaining repetitions of the PUSCH only decode data.

[0132] To facilitate understanding, the following explanation is based on Figures 6 and 7. Unlike Figure 5, when the resources of the PUCCH partially or completely overlap with the resources of a PUSCH that is transmitted twice, the UCI payload on the PUCCH is only added to one PUSCH. In Figure 6, the UCI is carried on the first PUSCH, and in Figure 7, the UCI is carried on the second PUSCH, both achieving resource multiplexing.

[0133] It should be noted that the embodiments of this application may allow some PUSCHs to reuse OCC for orthogonal multiplexing, while other PUSCH reuses provide non-OCC independence to support flexible UCI embedding. For example, when a specific PUSCH needs to embed a UCI payload, that specific PUSCH can be reused independently of other PUSCHs, and the other PUSCH reuses can use OCC for orthogonal multiplexing. As another example, when the number of PUSCH reuses differs between two terminal devices reusing the first resource, some resources may not involve orthogonal multiplexing. Reused transmission resources in the first resource that do not involve orthogonal multiplexing can provide non-OCC independence.

[0134] As one implementation, network devices can periodically configure independent PUSCH resources. These periodically configured PUSCH resources can be dedicated to carrying the UCI of multiple terminal devices that reuse the same resources.

[0135] As an example, when the first UCI is preferentially transmitted on the first resource and duplicate transmissions of multiple uplink data are 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 duplicate uplink data transmissions based on OCC. For example, when it is determined that the PUCCH resource conflicts with duplicate PUSCH transmissions within the OCC group, the network device can prioritize scheduling the PUCCH resource to ensure the transmission integrity of the UCI. To avoid interference from duplicate PUSCH transmissions to the PUCCH, all duplicate PUSCH transmissions within the OCC group can be discarded.

[0136] In the above embodiments, the network device can instruct multiple terminal devices to cancel repeated PUSCH transmissions within the OCC group. When the first resource only allows UCI transmission on the PUCCH, the discarded repeated PUSCH transmissions will no longer use the first resource. Resources in the first resource not used for PUCCH transmission can be used for other purposes (such as allocating them to other terminal devices) or kept 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 will not transmit the first UCI on the first resource. For example, when an OCC-based PUSCH overlaps with a PUCCH in a time slot, and transmitting the UCI may cause severe interference or resource conflicts, the UCI transmission of the terminal device will be cancelled. The base station may send an indication message to the terminal device to inform it that the UCI has been cancelled. It should be understood that the cancellation of the first UCI transmission means not transmitting the first UCI, which may include cancelling some UCIs or cancelling all UCIs.

[0138] In one implementation, the network device can send first control information to the first terminal device, which instructs the first terminal device to cancel the transmission of the first UCI. The first control information can be RRC signaling or a medium access control element (MAC CE). For example, for inter-slot OCC, the first control information can instruct the first terminal device to cancel the UCI transmission in the current time slot.

[0139] In the above embodiments, when the first terminal device determines that it will not transmit the first UCI on the first resource, the first terminal device does not need to perform uplink transmission of the first UCI, or it can transmit according to the reallocated resources. In some scenarios, if a conflict is unavoidable (e.g., due to insufficient resources), the network device can reallocate the time slot or frequency resources of the PUCCH or PUSCH to avoid the conflict. For example, the network device can allocate a new PRB for the PUCCH to avoid overlapping with the PUSCH, or move the PUCCH to a new time slot for transmission.

[0140] In the above embodiments, the transmission method of the first UCI can 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 includes at least the following: the first UCI does not reuse the first resource, the first UCI is multiplexed to all PUSCH repetitions, and the first UCI is multiplexed to a specific PUSCH repetition.

[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; and the resource requirements of the first terminal device.

[0142] As an example, the priority of the first UCI can be determined based on 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, a high-priority UCI is, for example, HARQ-ACK, a medium-priority UCI is, for example, SR, and a low-priority UCI is, for example, CSI. Optionally, a high-priority UCI is, for example, SR. Optionally, a high-priority UCI is, for example, CSI.

[0143] As one implementation method, the priority of UCI can be set by network devices; for example, base stations can set the importance of UCI types.

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

[0145] In some embodiments, the first terminal device can determine the transmission mode of the first UCI based on its priority. 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 all types of UCI (such as HARQ-ACK, CSI, SR) transmissions to be cancelled.

[0147] As one example, whether a first UCI is cancelled can be determined based on its priority. For instance, high-priority UCIs generally cannot be cancelled, and network devices will prioritize adjusting PUSCH duplication or PUCCH resources to avoid cancellation. Alternatively, medium-priority UCIs can be selectively cancelled based on resource usage. Furthermore, low-priority UCIs can be directly cancelled to reduce interference.

[0148] In the above embodiments, by introducing a priority scheduling mechanism, network devices or terminal devices can determine their processing method based on the type and importance of UCI transmissions. For important UCI transmissions, redundancy strategies can be adopted (such as multiplexing to multiple PUSCHs). 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 based on the transmission priority of the first UCI relative to the first uplink data. That is, the transmission priority of the first UCI may be determined relative to the repeated transmission of uplink data. For example, the transmission priority of the first UCI may be higher than the transmission priority of repeated PUSCH, or it may be lower than the transmission priority of repeated PUSCH.

[0150] As an example, when the transmission of the first UCI takes precedence over the repeated transmission of the first uplink data, the first terminal device does not send repeated transmissions of multiple uplink data on the first resource. That is, when the transmission priority of the first UCI is higher than the transmission priority of the repeated transmission of the first uplink data, the first terminal device may give up performing repeated transmissions 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 based on 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 the sufficiency of resources.

[0152] As an example, if time-domain resources are limited but high-reliability transmission is required, the first UCI can be embedded in each PUSCH repetition to ensure redundant transmission. If resources are sufficient and transmission reliability requirements are low, the first UCI can be embedded only in one or two specific PUSCH repetitions, with other repetitions used for data transmission. When frequency-domain resources are sufficient, and the first UCI is embedded in a single PUSCH repetition or part of a PUSCH repetition, a frequency-domain isolation scheme can be preferred to avoid interference from the UCI to other repetitions or centralized multiplexing schemes.

[0153] In some embodiments, the network device or the first terminal device may dynamically select the multiplexing strategy of the first UCI, i.e. 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 example, during the resource allocation phase, the network device can detect whether there is a conflict between the PUCCH and the repeated PUSCH within the OCC group. For example, the network device can check whether there is OCC overlap between PUCCH and PUSCH time slots, and check whether the terminal device needs to perform UCI multiplexing. The network device can obtain information about HARQ-ACK, CSI, SR, and other requirements through signaling.

[0155] In the above embodiments, the network device can determine a variety of transmission strategies based on the importance of the UCI.

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

[0157] For medium-priority UCIs (such as SRs): some conflicts or resource trade-offs are allowed.

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

[0159] In the above embodiments, after 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 number of PUSCH repetitions N, resource locations (time slots, PRBs), and can also specify the location and multiplexing rules of UCI multiplexing (such as specific repetitions or all repetitions).

[0160] The preceding text, with reference to Figures 4 to 7, described how multiple terminal devices repeatedly transmit uplink data on a first resource based on multiple mutually orthogonal sequences, and how this repeated transmission is multiplexed with UCI. For any one of the multiple terminal devices, determining the configuration parameters of the corresponding orthogonal sequence is also a problem that needs to be solved. The following explanation uses the first sequence corresponding to the first terminal device as an example.

[0161] In some embodiments, the first terminal device may determine the configuration parameters of the first sequence based on the configuration of the first sequence or a plurality of sequences including the first sequence. The configuration method or configuration parameters of the first sequence may be determined based on the configuration of repeated transmission of the first uplink data. That is, the configuration parameters of the first sequence may be indicated by the configuration of repeated transmission of the first uplink data. For example, the configuration parameters of the first sequence may be related to the transmission parameters of the first uplink data, or may be carried in the configuration signaling of repeated transmission of the first uplink data.

[0162] As an example, the configuration parameters of the first sequence can be carried in one or more of the following information: higher-layer signaling; DCI; RRC signaling; parameters related to the repeated transmission of the first uplink data. For example, an NTN network can use DCI to assign multiple orthogonal sequences to multiple terminal devices so that multiple terminal devices can reuse the same PRB.

[0163] As an example, the configuration of the first sequence can be determined based on the transmission configuration of repeated PUSCHs. For instance, for multiple repeatedly transmitted PUSCHs, the configuration parameters of the first sequence can be included in the parameters of the transmission configuration of repeated PUSCHs.

[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; transmission parameters of PUSCH repetition.

[0165] To facilitate understanding, the following explanation uses multiple sequences including the first sequence as examples to illustrate various configuration methods for the first sequence. For the OCC, the relevant parameters include the OCC index and the OCC length. For example, the configuration parameters of the first sequence may include the codeword index of the first OCC sequence and the lengths of the multiple OCC sequences, so that the first terminal device can determine the first sequence according to this configuration.

[0166] As one implementation, the configuration parameters of the first sequence can be carried in higher-layer signaling. As one implementation, when the PUSCH repeating transmission configuration corresponds to configuration authorization type 1, the configuration parameters of the first sequence can be included in the GrantConfig of the higher-layer configuration. For example, the configuration parameters of the first OCC sequence can be included in the rrc ConfiguredPlunkGrant of GrantConfig. As another implementation, when the PUSCH repeating transmission configuration corresponds to configuration authorization type 2, the configuration parameters of the first sequence can also be included in GrantConfig. As yet another implementation, for PUSCH transmissions with uplink authorization scheduling, OCC-related parameters can be included in higher-layer signaling.

[0167] As one implementation, the configuration parameters of the first sequence can be carried in the DCI. As one implementation, when the PUSCH repetition transmission configuration corresponds to configuration license type 2, the PUSCH repetition transmission is activated by a DCI scrambled with the configured scheduling-radio network temporary identifier (CS-RNTI), and 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, for uplink licensed PUSCH transmissions, OCC-related parameters can also be included in the DCI.

[0168] In the above embodiments, as the PUSCH capacity via OCC increases, the PDCCH capacity may become a bottleneck, limiting the possibility of granting multiple PUSCH repetitive transmissions based on OCC to a large number of terminal devices. This is seen in scenarios with multiple terminal devices or multiple cells, such as broadcast / multicast. Therefore, RAN1 specifies a single DCI scheduling among multiple terminal devices / cells, which can support scheduling multiple PUSCH repetitive transmissions based on OCC using a single DCI. This single DCI can schedule a group of terminal devices. The DCI format can be newly configured, in which case the OCC sequence index indication can correspond to each terminal device or each group of terminal devices.

[0169] As one implementation method, DCI can instruct the terminal device which codeword to use. Dynamic signaling configuration of codewords is desirable, as it helps network devices dynamically pair multiple terminal devices multiplexing the same resources based on information such as data arrival status and power imbalance. For example, DCI can instruct the OCC parameters corresponding to the first terminal device: the OCC codeword (CW) and the 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, meaning that the first terminal device can determine the configured OCC length based on the OCC factor.

[0171] For example, an OCC codeword (CW) can represent the codeword used by a terminal device. For an OCC factor of value M, there are M possible codewords. Given an OCC factor, the DCI can inform the first terminal device which codeword from the OCC to use.

[0172] As one implementation, 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 a traditional indication field.

[0173] As an example, the number of bits in the first indicator field is related to the number of multiple terminal devices that reuse the first resource. For example, when supporting four terminal devices to reuse the first resource, the minimum number of bits in the first indicator field is two.

[0174] As an example, the first indicator field can indicate the number of mutually orthogonal sequences and the index of the first sequence within the sequences. The number of mutually orthogonal sequences is related to the number of terminal devices multiplexing the first resource. When the mutually orthogonal sequences form an OCC group, the first indicator field can indicate the number of codewords in the OCC group, i.e., the OCC length, or OCC factor. The index of the first sequence within the sequences is used by the first terminal device to select the first sequence from the sequences. When the mutually orthogonal sequences form an OCC group, the first indicator field can indicate which codeword in the OCC group the first sequence belongs to through the OCC codeword index.

[0175] As an example, when the first indication field reuses a traditional indication field, the first indication field also needs to indicate the content that the traditional indication field needs to indicate. For example, the first indication field is also used to indicate the demodulation reference signal (DMRS) port. That is, the DMRS port can be jointly encoded with the OCC parameters.

[0176] In the example above, the first indication field can be the indication field corresponding to the antenna port in the DCI format, i.e., the antenna port field.

[0177] As one implementation, the UL PUSCH antenna port field can be combined with OCC indication. For example, the DMRS port, OCC factor, and CW index (CW idx) can be jointly encoded. In this case, the number of bits can be determined based on the number of multiplexed terminal devices and the multiple-input multiple-output (MIMO) configuration. The MIMO configuration can be related to the codeword, precoding, and number of layers. For example, four bits are allocated in the DCI (e.g., DCI format 0_1) for scheduling the UL PUSCH for the antenna port. Combined with multi-user (MU) MIMO support, if the NTN UL is to operate using 1Tx / Rx, bits in the antenna port field can be reused to indicate the OCC factor and OCC codeword. For example, to support OCC for up to four terminal devices (including those without OCC), one (without OCC) + two (OCC factor 2 + two CWs) + four (OCC factor 4 + four CWs) entries are needed to indicate the OCC configuration. Through conversion, 7 entries require 3 bits to indicate.

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

[0179] Table 1

[0180] Table 1 illustrates one implementation of OCC configuration. The first column in Table 1 can be the value of the first indicator field. The first terminal device can determine the corresponding OCC factor and CW index based on the value of the first indicator field to determine the codeword of the first sequence. When the value of the first indicator field is 6, it indicates that OCC is not present. Alternatively, when the OCC factor is 1, it indicates that OCC is disabled.

[0181] As one example, the configuration parameters of the first sequence can be carried in the RRC signaling. As another implementation, for configured license-based PUSCH transmissions, since the resources for PUSCH transmissions 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.

[0182] As one example, the configuration parameters of the first sequence can be carried in the transmission parameters of the PUSCH repetition. As one implementation, based on dynamically authorized PUSCH repetition transmission, the length of the OCC can be determined by the number of PUSCH repetitions.

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

[0184] In the above embodiments, when there is no corresponding OCC length for the number of repeated transmissions, the OCC length can be selected based on the nearest value among the multiple OCC lengths. For example, when the number of repeated transmissions is m, the OCC length corresponding to the first sequence is the value closest to m among multiple OCC lengths.

[0185] As one implementation, the configuration parameters of the first sequence can be carried in any of the aforementioned information. As one implementation, for PUSCH retransmissions based on dynamic authorization, 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 retransmissions. 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 retransmissions.

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

[0187] As one embodiment, the first terminal device may receive second information from the network device, the second information indicating whether the first sequence and / or multiple sequences including the first sequence are enabled.

[0188] As an example, the second information can be either RRC signaling or DCI. Taking OCC enabling and disabling as an example, for dynamic grant (DG) PUSCH repetition, i.e., DG-PUSCH, OCC enabling / disabling can be indicated by RRC signaling, i.e., the second information is RRC signaling. When RRC signaling indicates that OCC is enabled, DCI can indicate the configuration parameters of the first sequence corresponding to the first terminal device. For example, in scenarios where PUSCH transmission resources are predefined, whether OCC is enabled should be explicitly indicated in the RRC signaling. Alternatively, the indication field related to the first sequence in DCI can implicitly indicate whether OCC is enabled.

[0189] For example, when OCC parameters are carried in DCI, they can be jointly encoded with other parameters. Network devices can impose additional constraints to maintain maximum flexibility in PUSCH scheduling with and without OCC, while minimizing overhead. For instance, OCC can be used for smaller bandwidth allocations, such as a PRB. Furthermore, OCC performance is expected to be better when Transmission Block Over Multiple Slots (TBoMS) processing is enabled, in which case OCC can be enabled.

[0190] For example, instead of using separate flags for OCC enabling / disabling, networks and end devices can deduce OCC enabling / disabling from several conditions indicated in the DCI. For instance, if the transmission bandwidth is 1 PRB (determined based on the frequency domain resource assignment (FDRA) field), the modulation and coding scheme (MCS) modulation is no higher than quadrature phase shift keying (QPSK) (based on the MCS field), the time slots used for TBoMS are 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 end devices and networks can implicitly deduce that uplink communication with OCC is enabled from these conditions. If these conditions are not met, end devices and networks can implicitly assume that the scheduled transmissions are not using OCC and can interpret the DCI according to conventional rules. This implicit indication can help reduce the overhead of configuring OCC in the DCI.

[0191] The previous section introduced methods for configuring and indicating multiple sequences in the first sequence when multiple terminal devices perform repeated uplink data transmissions based on orthogonal sequences. In NTN systems, due to the very wide service area of ​​an NTN cell, the uplink transmission (UL RX) power between different terminal devices within an NTN cell can often vary significantly. Therefore, when OCC is applied to repeated PUSCH transmissions, the UL RX power of different PUSCH transmissions from different terminal devices may vary greatly due to proximity issues, leading to a reduction in the CDM effect. Therefore, when supporting repeated uplink data transmissions by multiple terminal devices based on OCC, it may be necessary to carefully determine which group of terminal devices can be the target for resource reuse.

[0192] In some embodiments, multiple terminal devices, including a first terminal device, may belong to a first terminal device group. The first terminal device group may be one of multiple terminal device groups, which are determined based on 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; and the remaining service time corresponding to all terminal devices.

[0193] As an example, multiple terminal device groups can be determined based on the frequency offset range corresponding to all terminal devices. Frequency offset is one of the important factors affecting performance. Generally, the frequency offset of terminal devices 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 crystal oscillators, if 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 for a certain period of time. Typically, network devices have already performed frequency offset estimation during the initial access phase, which means that the network devices already have a basic understanding of the frequency offset of the terminal devices before PUSCH scheduling in the connected state. For example, network devices can perform frequency offset estimation through physical random access channel (PRACH) or sounding reference signal (SRS). Therefore, for terminal devices based on OCC resource reuse, network devices can group terminal devices with similar frequency offsets together.

[0194] As one implementation, assuming the frequency offset range of the terminal devices is [-200Hz, 200Hz], the network device can group terminal devices with similar carrier frequency offsets (CFO) or within a certain range for inter-slot OCC resource reuse. For example, using 100Hz as the group boundary, they can be divided into 4 groups: [-200Hz, -100Hz], [-100Hz, 0Hz], [0Hz, 100Hz], and [100Hz, 200Hz]. Terminal devices within each group can be multiplexed together in time slots based on the length of the OCC code.

[0195] As one implementation method, the frequency offset range is related to the number of terminal devices within the corresponding terminal device group. Network devices can dynamically adjust the frequency offset range based on the number of terminal devices within the group. For example, network devices can use the frequency offset distribution of PRACH and SRS for dynamic grouping: if there are many terminal devices in certain frequency ranges, the group width for that range can be reduced (e.g., from 100Hz to 50Hz) to reduce interference between terminal devices within the same group; if there are fewer terminal devices in certain ranges, the group width can be increased (e.g., from 100Hz to 150Hz) to improve resource utilization.

[0196] As one implementation, network devices can allocate a specific frequency offset range to each group of terminal devices and adjust the time slot reuse position. For example, terminal device group 1 (offset range, for example, (-200Hz, -100Hz)) is assigned to time slot 1, and terminal device group 2 (offset range, for example, (-100Hz, 0Hz)) is assigned to time slot 2, avoiding the simultaneous use of groups with adjacent frequency offsets.

[0197] As one example, multiple terminal device groups can be determined based on the sub-regions where all terminal devices reside. In an NTN system, multiple sub-regions, such as NTN1, NTN2, NTN3, etc., can be formed based on the segmentation of NTN regions. Since the signal strength and other characteristics of all terminal devices within a sub-region are similar, the terminal devices within each region can form a group. Terminal devices within each group can be multiplexed together in time slots based on the length of the OCC code. In addition to using OCC coding for time slot multiplexing, terminal devices in each sub-region can also be isolated in the frequency domain (e.g., allocated different frequency sub-bands).

[0198] As one embodiment, multiple terminal device groups can be determined based on the remaining service time corresponding to all terminal devices. The remaining service time corresponding to a terminal device can be the remaining service time of the terminal device's current satellite or cell. When the remaining service time is short, the terminal device needs to perform satellite handover as soon as possible, so the remaining service time can indicate the urgency of handover.

[0199] As one implementation method, multiple terminal device groups can be determined based on the T-service time. Due to the different trajectories and directions of satellite motion, the network equipment in the NTN serving cell where the terminal devices reside knows which terminal devices will subsequently undergo handover. If it is known that handover may occur to other NTN service areas, the network equipment can group those currently requiring handover into one group and those subsequently requiring handover into another. Alternatively, the network equipment can group terminal devices that are handovering to the same network device into one group, and the terminal devices within each group can be multiplexed together in time slots based on the length of their OCC codes.

[0200] As one implementation method, multiple terminal device groups can be determined based on the service time of the service or the remaining service time of the service.

[0201] As one implementation method, network devices can group terminal devices based on their remaining service time or handover urgency, prioritizing the allocation of urgent handover devices to adjacent time slots or frequency resources. For handover-priority groups of terminal devices, higher reuse priority or more OCC sequences can be allocated to ensure sufficient resources. For example, in inter-satellite cooperation, multiple satellites or ground base stations share handover information of terminal devices, reserving frequency and time slot resources in advance in the handover target area. As another example, in inter-base station cooperation, relay links can be used to pre-allocate frequency resources or OCC sequences to the target base station, reducing handover latency.

[0202] As one embodiment, multiple terminal device groups can be determined based on any of the aforementioned information. For example, for terminal devices within a service area, the network device first divides the area into sub-regions based on characteristics such as signal strength and frequency offset. Within each sub-region, the network device further groups the terminal devices according to their handover goals or remaining service time, ensuring that the signal characteristics and handover requirements of the terminal devices within a group are consistent. Terminal devices in different areas are isolated through frequency domain or time slot isolation to avoid inter-area interference.

[0203] In one implementation, a first terminal equipment group within a multi-terminal equipment group performs satellite handover. The multi-terminal equipment group also includes a second terminal equipment group that does not perform satellite handover, and the terminal equipment within the second terminal equipment group does not reuse resources. That is, the terminal equipment group performing satellite handover (also called the handover UE group) repeatedly transmits uplink data based on resource reuse; the terminal equipment group not performing satellite handover (non-handover UE group) does not repeatedly transmit uplink data based on resource reuse. For example, the handover UE group within the satellite service area uses OCC encoding for time slot multiplexing, while the non-handover UE group uses conventional transmission methods.

[0204] In some embodiments, frequency domain isolation is performed between any two terminal device groups within a plurality of terminal device groups. Frequency domain isolation can be used between multiple terminal device groups, while OCC time slot multiplexing is used within each group to avoid inter-group interference. For example, by utilizing the boundaries and directivity of satellite beams, sub-regions can be further subdivided within a beam, and terminal devices within each beam can be multiplexed according to OCC, with frequency domain isolation between beams.

[0205] The preceding text introduced several implementation methods for performing PUSCH repetition transmission based on multiple orthogonal sequences by various communication devices. The following example illustrates this using an IoT-based NTN system. In an IoT system, terminal devices can wirelessly access or transmit uplink information and data through various uplink channels. Taking NB-IoT as an example, terminal devices can transmit uplink data through a narrow-band physical uplink shared channel (NPUSCH).

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

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

[0208] As an example, DMRS symbols are spread before the application of OCC. For instance, DMRS are spread according to the following formula:

[0209] Where M is the OCC length, and q is the OCC codeword assigned to the terminal device. It is a reference signal sequence.

[0210] Alternatively, the reference signal sequence can be represented as:

[0211] Where c(n) is a binary sequence, initialized to c at the start of NPUSCH transmission. init =35; Indicates the number of repetitions associated with NPUSCH; N RU Indicates the number of resource units (RUs); It is the number of time slots in a resource unit.

[0212] As an example, DMRS symbols are not spread before OCC is applied. OCC can be applied to complex-valued DMRS symbols. For example, the conventional complex-valued DMRS symbols used in slots 1 and 2 can be represented as: For example, OCC can be applied to other complex-valued DMRS symbols in slot 1 and slot 2.

[0213] In the above embodiments, during the repeated transmission of NPUSCH, the time slot corresponding to the OCC codeword can use conventional complex-valued DMRS symbols. Different DMRS sequences are used for multiplexing by the terminal equipment.

[0214] As an example, different DMRS sequences can be used for different time slots depending on the OCC codeword.

[0215] As an example, if the DMRS symbols are not spread, multiple terminal devices do not use OCC for resource reuse.

[0216] The method embodiments of this application have been described in detail above with reference to Figures 1 to 8. The apparatus embodiments of this application are described in detail below with reference to Figures 9 to 11. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any parts not described in detail can be referred to the foregoing method embodiments.

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

[0218] The determining unit 910 can be used to repeatedly transmit first uplink data according to a first sequence; wherein, the first sequence belongs to multiple mutually orthogonal sequences, the multiple sequences are used for multiple terminal devices to reuse the first resource, the first resource is used for multiple terminal devices to repeatedly transmit multiple uplink data respectively, the multiple terminal devices include the first terminal device, and the multiple uplink data includes the first uplink data.

[0219] Optionally, 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: multiple uplink data correspond to the same redundant version; the first resource is not used for UCI reuse or for UCI reuse based on 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.

[0220] Optionally, the second terminal device corresponds to the second sequence where all codewords are 1.

[0221] Optionally, when at least a portion 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 mode of the first UCI is determined according to the first information.

[0222] 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; and the resource requirements of the first terminal device.

[0223] 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: feedback information has the highest priority; feedback information has a higher priority than scheduling request; feedback information has a higher priority than channel state information; scheduling request has a higher priority than channel state information; and channel state information has the lowest priority.

[0224] 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 transmitted preferentially on the first resource, and the repeated transmission of multiple uplink data is cancelled; the first UCI and the first uplink data are transmitted together on the first resource.

[0225] 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 repeated transmission of the first uplink data.

[0226] Optionally, 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 the first uplink channel among the multiple uplink channels, and the first uplink channel is determined according to the instructions of the network device.

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

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

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

[0230] Optionally, the first indicator field is used to indicate the number of multiple sequences and the index of the first sequence in the multiple sequences.

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

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

[0233] Optionally, multiple terminal devices belong to a first terminal device group, which is one of the multiple terminal device groups. The multiple terminal device groups are determined based on 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; and the remaining service time corresponding to all terminal devices.

[0234] Optionally, when multiple terminal device groups are determined based on the frequency offset range corresponding to all terminal devices, the frequency offset range is related to the number of terminal devices in the corresponding terminal device group.

[0235] Optionally, when multiple terminal device groups are determined based on the remaining service time corresponding to all terminal devices, the first terminal device group in the multiple terminal device groups performs satellite handover. The multiple terminal device groups also include a second terminal device group that does not perform satellite handover, and the terminal devices in the second terminal device group do not reuse resources.

[0236] Optionally, frequency domain isolation can be performed between any two terminal device groups among the multiple terminal device groups.

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

[0238] Figure 10 is a schematic block diagram of another device for wireless communication according to an embodiment of this application. The device 1000 can be any of the second devices described above. The second device may include a network device. The device 1000 shown in Figure 10 includes a transceiver unit 1010.

[0239] The transceiver unit 1010 can be used to receive repeated transmissions of multiple uplink data from multiple terminal devices; wherein, the repeated transmission of multiple uplink data is based on multiple orthogonal sequences multiplexing a first resource, the multiple sequences include a first sequence, the first sequence is used by the first terminal device among the multiple terminal devices to perform repeated transmission of first uplink data, and the multiple uplink data includes the first uplink data.

[0240] Optionally, 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: multiple uplink data correspond to the same redundant version; the first resource is not used for UCI reuse or for UCI reuse based on 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.

[0241] Optionally, the second terminal device corresponds to the second sequence where all codewords are 1.

[0242] Optionally, when at least a portion 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 mode of the first UCI is determined according to the first information.

[0243] 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; and the resource requirements of the first terminal device.

[0244] 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: feedback information has the highest priority; feedback information has a higher priority than scheduling request; feedback information has a higher priority than channel state information; scheduling request has a higher priority than channel state information; and channel state information has the lowest priority.

[0245] 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 transmitted preferentially on the first resource, and the repeated transmission of multiple uplink data is cancelled; the first UCI and the first uplink data are transmitted together on the first resource.

[0246] 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 repeated transmission of the first uplink data.

[0247] Optionally, 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 the first uplink channel among the multiple uplink channels, and the first uplink channel is determined according to the instructions of the network device.

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

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

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

[0251] Optionally, the first indicator field is used to indicate the number of multiple sequences and the index of the first sequence in the multiple sequences.

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

[0253] Optionally, the transceiver unit 1010 is further configured to transmit second information; wherein the second information is configured to indicate whether the first sequence and / or multiple sequences are enabled.

[0254] Optionally, multiple terminal devices belong to a first terminal device group, which is one of the multiple terminal device groups. The multiple terminal device groups are determined based on 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; and the remaining service time corresponding to all terminal devices.

[0255] Optionally, when multiple terminal device groups are determined based on the frequency offset range corresponding to all terminal devices, the frequency offset range is related to the number of terminal devices in the corresponding terminal device group.

[0256] Optionally, when multiple terminal device groups are determined based on the remaining service time corresponding to all terminal devices, the first terminal device group in the multiple terminal device groups performs satellite handover. The multiple terminal device groups also include a second terminal device group that does not perform satellite handover, and the terminal devices in the second terminal device group do not reuse resources.

[0257] Optionally, frequency domain isolation can be performed between any two terminal device groups among the multiple terminal device groups.

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

[0259] Figure 11 is a schematic diagram of the structure of a communication device according to an embodiment of this application. The dashed lines in Figure 11 indicate that the unit or module is optional. This device 1100 can be used to implement the methods described in the above method embodiments. Device 1100 can be a chip, a terminal device, or a network device.

[0260] Apparatus 1100 may include one or more processors 1110. The processor 1110 may support apparatus 1100 in implementing the methods described in the preceding 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 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 any conventional processor.

[0261] The apparatus 1100 may further include one or more memories 1120. The memories 1120 store a program that can be executed by the processor 1110, causing the processor 1110 to perform the methods described in the preceding method embodiments. The memories 1120 may be independent of the processor 1110 or integrated within the processor 1110.

[0262] The device 1100 may also include a transceiver 1130. The processor 1110 can communicate with other devices or chips via the transceiver 1130. For example, the processor 1110 can send and receive data with other devices or chips via the transceiver 1130.

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

[0264] The computer-readable storage medium can be any available medium that a computer can read, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

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

[0266] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as 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, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0267] This application also provides a computer program. This computer program can be applied to a terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0268] In this application, the terms "system" and "network" are used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0269] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0270] In the embodiments of this application, the term "correspondence" may indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0271] In the embodiments of this application, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0272] In the embodiments of this application, determining B based on A or based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0273] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0274] In the embodiments of this application, the order of the above-mentioned process numbers does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0275] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0277] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0278] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for wireless communication, comprising: include: The first terminal device repeatedly transmits the first uplink data according to the first sequence; Wherein, the first sequence is a plurality of mutually orthogonal sequences, the plurality of sequences are used for multiple terminal devices to reuse the first resource, the first resource is used for the plurality of terminal devices to repeatedly transmit multiple uplink data, the plurality of terminal devices include the first terminal device, and the plurality of uplink data includes the first uplink data.

2. The method of claim 1, wherein, The plurality of terminal devices includes at least one second terminal device that does not support resource reuse, wherein the reuse of the first resource requires at least one of the following: The multiple uplink data correspond to the same redundant version; The first resource is not used for uplink control information UCI multiplexing or for UCI multiplexing based on 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.

3. The method of claim 2, wherein, The second terminal device corresponds to the second sequence where all codewords are 1.

4. The method according to claim 2 or 3, characterized in that, When at least a portion 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 mode of the first UCI is determined according to the first information.

5. The method of claim 4, wherein, 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; Resource requirements of the first terminal device.

6. The method of claim 5, wherein, 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 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-6, characterized in that, The first UCI transmission method includes one of the following: The transmission of the first UCI on the first resource was cancelled; The first UCI is transmitted preferentially on the first resource, and the 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 of claim 7, wherein, 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 repeated transmission of the first uplink data.

9. The method of claim 7, wherein, 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 the first uplink channel among the multiple uplink channels. The first uplink channel is determined according to the instructions of the network device.

10. The method according to any one of claims 1-9, characterized in that, The first uplink data is carried on the 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-10, characterized in that, The configuration parameters of the first sequence are carried in one or more of the following information: Higher-level signaling; Downlink Control Information (DCI); Radio Resource Control (RRC) signaling; The retransmission parameters of the first uplink data.

12. The method of claim 11, wherein, The configuration parameters of the first sequence are carried in the first indication field of the DCI, and the number of bits in the first indication field is related to the number of the plurality of terminal devices.

13. The method of claim 12, wherein, The first indication field is used to indicate the number of the plurality of sequences and the index of the first sequence in the plurality of sequences.

14. The method according to claim 12 or 13, characterized in that, 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 demodulation reference signal DMRS port.

15. The method of any one of claims 1-14, wherein, The method further includes: The first terminal device receives the second information; The second information is used to indicate whether the first sequence and / or the plurality of sequences are enabled.

16. The method of any one of claims 1-15, wherein, The plurality of terminal devices belong to a first terminal device group, which is one of the plurality of terminal device groups. The plurality of terminal device groups are determined based on one or more of the following information: Frequency offset range for all terminal devices; The sub-region where all terminal devices are located; Remaining service time for all terminal devices.

17. The method of claim 16, wherein, When the multiple terminal device groups are determined based on the frequency offset range corresponding to all the terminal devices, the frequency offset range is related to the number of terminal devices in the corresponding terminal device group.

18. The method of claim 16, wherein, When the plurality of terminal device groups are determined based on the remaining service time corresponding to all terminal devices, the first terminal device group in the plurality of terminal device groups performs satellite handover. The plurality of terminal device groups also includes a second terminal device group that does not perform satellite handover, and the terminal devices in the second terminal device group do not reuse resources.

19. The method of any one of claims 16-18, wherein, Frequency domain isolation is performed between any two terminal device groups among the plurality of terminal device groups.

20. The method of any one of claims 1-19, wherein, The multiple sequences belong to the Orthogonal Cover Code (OCC) group.

21. A method for wireless communication, comprising: 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 orthogonal sequences that reuse a first resource. The multiple sequences include a first sequence, which is used by a first terminal device among the multiple terminal devices to repeatedly transmit the first uplink data. The multiple uplink data includes the first uplink data.

22. The method of claim 21, wherein, The plurality of terminal devices includes at least one second terminal device that does not support resource reuse, wherein the reuse of the first resource requires at least one of the following: The multiple uplink data correspond to the same redundant version; The first resource is not used for uplink control information UCI multiplexing or for UCI multiplexing based on 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.

23. The method of claim 22, wherein, The second terminal device corresponds to the second sequence where all codewords are 1.

24. The method of claim 22 or 23, wherein, When at least a portion 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 mode of the first UCI is determined according to the first information.

25. The method of claim 24, wherein, 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; Resource requirements of the first terminal device.

26. The method of claim 25, wherein, 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 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 of any one of claims 24-26, wherein, The first UCI transmission method includes one of the following: The transmission of the first UCI on the first resource was cancelled; The first UCI is transmitted preferentially on the first resource, and the 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 of claim 27, wherein, 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 repeated transmission of the first uplink data.

29. The method of claim 27, wherein, 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 the first uplink channel among the multiple uplink channels. The first uplink channel is determined according to the instructions of the network device.

30. The method of any one of claims 21-29, wherein, The first uplink data is carried on the 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 of any one of claims 21-30, wherein, The configuration parameters of the first sequence are carried in one or more of the following information: Higher-level signaling; Downlink Control Information (DCI); Radio Resource Control (RRC) signaling; The retransmission parameters of the first uplink data.

32. The method of claim 31, wherein, The configuration parameters of the first sequence are carried in the first indication field of the DCI, and the number of bits in the first indication field is related to the number of the plurality of terminal devices.

33. The method of claim 32, wherein, The first indication field is used to indicate the number of the plurality of sequences and the index of the first sequence in the plurality of sequences.

34. The method of claim 32 or 33, wherein, 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 demodulation reference signal DMRS port.

35. The method of any one of claims 21-34, wherein, The method further includes: The network device sends the second information; The second information is used to indicate whether the first sequence and / or the plurality of sequences are enabled.

36. The method of any one of claims 21-35, wherein, The plurality of terminal devices belong to a first terminal device group, which is one of the plurality of terminal device groups. The plurality of terminal device groups are determined based on one or more of the following information: Frequency offset range for all terminal devices; The sub-region where all terminal devices are located; Remaining service time for all terminal devices.

37. The method of claim 36, wherein, When the multiple terminal device groups are determined based on the frequency offset range corresponding to all the terminal devices, the frequency offset range is related to the number of terminal devices in the corresponding terminal device group.

38. The method of claim 36, wherein, When the plurality of terminal device groups are determined based on the remaining service time corresponding to all terminal devices, the first terminal device group in the plurality of terminal device groups performs satellite handover. The plurality of terminal device groups also includes a second terminal device group that does not perform satellite handover, and the terminal devices in the second terminal device group do not reuse resources.

39. The method of any one of claims 36-38, wherein, Frequency domain isolation is performed between any two terminal device groups among the plurality of terminal device groups.

40. The method of any one of claims 21-39, wherein, The multiple sequences belong to the 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 is used to repeatedly transmit the first uplink data according to the first sequence. Wherein, the first sequence is a plurality of mutually orthogonal sequences, the plurality of sequences are used for multiple terminal devices to reuse the first resource, the first resource is used for the plurality of terminal devices to repeatedly transmit multiple uplink data, the plurality of terminal devices include the first terminal device, and the plurality of uplink data includes the first uplink data.

42. The device of claim 41, wherein, The plurality of terminal devices includes at least one second terminal device that does not support resource reuse, wherein the reuse of the first resource requires at least one of the following: The multiple uplink data correspond to the same redundant version; The first resource is not used for uplink control information UCI multiplexing or for UCI multiplexing based on 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.

43. The device of claim 42, wherein, The second terminal device corresponds to the second sequence where all codewords are 1.

44. The device of claim 42 or 43, wherein, When at least a portion 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 mode of the first UCI is determined according to the first information.

45. The device of claim 44, wherein, 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; Resource requirements of the first terminal device.

46. ​​The apparatus according to claim 45, characterized in that, 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 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 apparatus according to any one of claims 44-46, characterized in that, The first UCI transmission method includes one of the following: The transmission of the first UCI on the first resource was cancelled; The first UCI is transmitted preferentially on the first resource, and the 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 apparatus according to claim 47, characterized in that, 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 repeated transmission of the first uplink data.

49. The apparatus 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 the first uplink channel among the multiple uplink channels. The first uplink channel is determined according to the instructions of the network device.

50. The apparatus according to any one of claims 41-49, characterized in that, The first uplink data is carried on the 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 apparatus according to any one of claims 41-50, characterized in that, The configuration parameters of the first sequence are carried in one or more of the following information: Higher-level signaling; Downlink Control Information (DCI); Radio Resource Control (RRC) signaling; The retransmission parameters of the first uplink data.

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

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

54. The apparatus according to claim 52 or 53, characterized in that, 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 demodulation reference signal DMRS port.

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

56. The apparatus according to any one of claims 41-55, characterized in that, The plurality of terminal devices belong to a first terminal device group, which is one of the plurality of terminal device groups. The plurality of terminal device groups are determined based on one or more of the following information: Frequency offset range for all terminal devices; The sub-region where all terminal devices are located; Remaining service time for all terminal devices.

57. The apparatus according to claim 56, characterized in that, When the multiple terminal device groups are determined based on the frequency offset range corresponding to all the terminal devices, the frequency offset range is related to the number of terminal devices in the corresponding terminal device group.

58. The apparatus according to claim 56, characterized in that, When the plurality of terminal device groups are determined based on the remaining service time corresponding to all terminal devices, the first terminal device group in the plurality of terminal device groups performs satellite handover. The plurality of terminal device groups also includes a second terminal device group that does not perform satellite handover, and the terminal devices in the second terminal device group do not reuse resources.

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

60. The apparatus according to any one of claims 41-59, characterized in that, The multiple sequences belong to the Orthogonal Cover Code (OCC) group.

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

62. The apparatus according to claim 61, characterized in that, The plurality of terminal devices includes at least one second terminal device that does not support resource reuse, wherein the reuse of the first resource requires at least one of the following: The multiple uplink data correspond to the same redundant version; The first resource is not used for uplink control information UCI multiplexing or for UCI multiplexing based on 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.

63. The apparatus according to claim 62, characterized in that, The second terminal device corresponds to the second sequence where all codewords are 1.

64. The apparatus according to claim 62 or 63, characterized in that, When at least a portion 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 mode of the first UCI is determined according to the first information.

65. The apparatus according to claim 64, characterized in that, 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; Resource requirements of the first terminal device.

66. The device of claim 65, wherein, 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 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 apparatus according to any one of claims 64-66, characterized in that, The first UCI transmission method includes one of the following: The transmission of the first UCI on the first resource was cancelled; The first UCI is transmitted preferentially on the first resource, and the 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 apparatus according to claim 67, characterized in that, 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 repeated transmission of the first uplink data.

69. The apparatus 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 the first uplink channel among the multiple uplink channels. The first uplink channel is determined according to the instructions of the network device.

70. The apparatus according to any one of claims 61-69, characterized in that, The first uplink data is carried on the 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 apparatus according to any one of claims 61-70, characterized in that, The configuration parameters of the first sequence are carried in one or more of the following information: Higher-level signaling; Downlink Control Information (DCI); Radio Resource Control (RRC) signaling; The retransmission parameters of the first uplink data.

72. The device of claim 71, wherein, The configuration parameters of the first sequence are carried in the first indication field of the DCI, and the number of bits in the first indication field is related to the number of the plurality of terminal devices.

73. The device of claim 72, wherein, The first indication field is used to indicate the number of the plurality of sequences and the index of the first sequence in the plurality of sequences.

74. The device of claim 72 or 73, wherein, 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 demodulation reference signal DMRS port.

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

76. The device of any one of claims 61-75, wherein, The plurality of terminal devices belong to a first terminal device group, which is one of the plurality of terminal device groups. The plurality of terminal device groups are determined based on one or more of the following information: Frequency offset range for all terminal devices; The sub-region where all terminal devices are located; Remaining service time for all terminal devices.

77. The device of claim 76, wherein, When the multiple terminal device groups are determined based on the frequency offset range corresponding to all the terminal devices, the frequency offset range is related to the number of terminal devices in the corresponding terminal device group.

78. The device of claim 76, wherein, When the plurality of terminal device groups are determined based on the remaining service time corresponding to all terminal devices, the first terminal device group in the plurality of terminal device groups performs satellite handover. The plurality of terminal device groups also includes a second terminal device group that does not perform satellite handover, and the terminal devices in the second terminal device group do not reuse resources.

79. The device of any one of claims 76-78, wherein, Frequency domain isolation is performed between any two terminal device groups among the plurality of terminal device groups.

80. The device of any one of claims 61-79, wherein, The multiple sequences belong to the Orthogonal Cover Code (OCC) group.

81. A communications device, characterized by It includes a memory and a processor, the memory being used to store a program, and the processor being used to invoke the program in the memory to perform the method as described in any one of claims 1-40.

82. An apparatus, comprising: Includes a processor for calling a program from memory to perform the method as described in any one of claims 1-40.

83. A chip, comprising: Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-40.

84. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-40.

85. A computer program product, characterised in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-40.

86. A computer program characterised in that, The computer program causes the computer to perform the method as described in any one of claims 1-40.

Images