Communication method, apparatus and system for feedback

CN122910588APending Publication Date: 2026-10-13HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480089510.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-03-14
Filing Date
2024-06-07
Publication Date
2026-10-13

AI Technical Summary

Technical Problem

[0004]但是,在当前反馈机制中,UE必须等待上行传输机会来发送ACK/NACK信号

Benefits of technology

[0045]根据第九方面,本申请提供了一种计算机程序产品。当计算机读取并执行该计算机程序产品时,使得计算机能够执行第一方面至第二方面的任何一种可能的设计中的方法。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122910588A_ABST
    Figure CN122910588A_ABST
Patent Text Reader

Abstract

Embodiments of the present application provide a communication method, device and system for feedback. In the method, a user equipment receives control information from a base station, wherein the control information indicates a first physical resource for feedback information, and the first physical resource is associated with a first frequency division duplex (FDD) frequency band; and the user equipment sends the feedback information to the base station on the first FDD frequency band. The method guarantees the feedback opportunity of the user equipment, and can improve the reliability of the feedback.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related applications cross-application This application claims priority to U.S. Provisional Patent Application No. 63 / 565,339, filed March 14, 2024, entitled “Method, Apparatus, and System for Crossing FDD-TDD scheduling,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more specifically, to communication methods, apparatus, and systems for feedback. Background Technology

[0003] In wireless communication, feedback mechanisms can provide reliable data transmission. For example, Hybrid Automatic Repeat Request (HARQ) is a feedback mechanism involving either an acknowledgement (ACK) signal or a non-acknowledgment (NACK) signal. The base station (BS) sends data to the user equipment (UE). If the data is successfully received (or decoded), the UE can send an ACK signal to the BS. If the data is not successfully received (or decoded), the receiver can send a NACK signal to the BS, and the BS can then perform a retransmission.

[0004] However, in the current feedback mechanism, the UE must wait for an uplink transmission opportunity to send an ACK / NACK signal. The waiting time may introduce significant delays.

[0005] Therefore, a pressing technical problem is how to improve the reliability of feedback. Summary of the Invention

[0006] The present invention provides a communication method, apparatus and system for feedback, which can improve the reliability of feedback.

[0007] According to the first aspect, a communication method is described. This method can be applied to the terminal side, for example, to a terminal or a module, circuit, or chip within the terminal (e.g., a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip including a modem core), responsible for communication functions within the terminal. For example, the method is applied to a terminal. In this method, the terminal receives control information, wherein the control information indicates a first physical resource for feedback information, the first physical resource being associated with a first frequency division duplex (FDD) band; the terminal transmits feedback information on the first FDD band.

[0008] According to the second aspect, the method can be applied to the network side, such as a positioning server on the network side or components (e.g., circuits, chips, or chip systems) within the positioning server. For example, the method is applied to a positioning server. In this method, the positioning server sends control information, wherein the control information indicates a first physical resource for feedback information, the first physical resource being associated with a first frequency division duplex (FDD) band; the positioning server receives the feedback information on the first FDD band.

[0009] According to the above method, the network side (e.g., the positioning server) can indicate a dedicated first FDD frequency band to the terminal side (e.g., the terminal), so the terminal can use the first FDD frequency band to send feedback information, thereby ensuring the feedback opportunity. This can improve the reliability of the feedback.

[0010] According to the first or second aspect, in one possible design, the control information also indicates a second physical resource for downlink data.

[0011] According to the method described above, the first physical resource used for feedback information and the second physical resource used for downlink data can be indicated by the same control information. This allows the feedback to be synchronized with the downlink data and improves the reliability of the feedback.

[0012] According to the first or second aspect, in one possible design, the second physical resource is associated with one or more frequency bands, which include one or more of the following: at least one FDD frequency band and at least one time division duplex (TDD) frequency band.

[0013] According to the method described above, the second physical resource can be associated with one or more frequency bands, meaning downlink data can be transmitted on one or more frequency bands. This can improve the utilization rate of spectrum resources.

[0014] According to the first or second aspect, in one possible design, control information is received / transmitted on one or more frequency bands.

[0015] Using the method described above, control information and downlink data can be received / transmitted on the same one or more frequency bands. This co-location simplifies the coordination between control information and the corresponding downlink data.

[0016] According to the first or second aspect, in one possible design, feedback information indicates whether some or all downlink data was successfully or unsuccessfully received, wherein the downlink data is associated with at least one frequency band.

[0017] Based on the method described above, the network side can determine whether to perform a retransmission based on whether downlink data has been successfully received. This feedback mechanism can provide more reliable wireless transmission.

[0018] According to the first or second aspect, in one possible design, downlink data is associated with multiple frequency bands, and feedback information also indicates one or more corresponding frequency bands associated with some or all of the downlink data.

[0019] Using the method described above, the feedback information can identify one or more frequency bands and their corresponding downlink data. This further improves the reliability of the feedback.

[0020] According to the first or second aspect, in one possible design, the second physical resource is associated with the first TDD band, and control information is received / transmitted on the first TDD band.

[0021] According to the above method, downlink data and control information can be received / transmitted on the same first TDD frequency band, and co-addressing simplifies the coordination between control information and the corresponding downlink data.

[0022] According to the first or second aspect, in one possible design, the second physical resource is associated with a second TDD band and a third TDD band, and control information is received / transmitted on the second TDD band or the third TDD band.

[0023] According to the above method, downlink data and control information can be received / transmitted on the same second TDD band or third TDD band, and co-addressing simplifies the coordination between control information and corresponding downlink data.

[0024] According to the first or second aspect, in one possible design, the second physical resource is associated with a second FDD band, and control information is received / transmitted on the second FDD band.

[0025] According to the above method, downlink data and control information can be received / transmitted on the same second FDD frequency band, and co-addressing simplifies the coordination between control information and corresponding downlink data.

[0026] According to the first or second aspect, in one possible design, the second physical resource is associated with the fourth TDD band and the third FDD band, and control information is received / transmitted on the fourth TDD band.

[0027] According to the above method, downlink data and control information can be received / transmitted on the same fourth TDD frequency band, and co-addressing simplifies the coordination between control information and corresponding downlink data.

[0028] According to the first or second aspect, in one possible design, the control information includes timing information for feedback information, which is associated with one or more of the following: a set of parameters associated with a first FDD band, and a set of parameters associated with the band for receiving / transmitting control information.

[0029] According to the above method, the interpretation of timing information can be associated with the parameter set associated with the first FDD band (e.g., the feedback information parameter set) and / or the parameter set associated with the band receiving control information (e.g., the control information parameter set) so that the timing information can be correctly interpreted.

[0030] According to the first aspect, in one possible design, the method further includes: the terminal receiving configuration information indicating a resource set including the first physical resource.

[0031] According to the second aspect, in one possible design, the method further includes: the location server sending configuration information indicating a resource set including the first physical resource.

[0032] According to the method described above, configuration and control information can be used to instruct the first physical resource. This method supports flexible resource scheduling.

[0033] According to the first or second aspect, in one possible design, the feedback information includes ACK or NACK; and / or the feedback information includes channel state information (CSI).

[0034] According to the first or second aspect, in one possible design, the control information is downlink control information (DCI).

[0035] According to the first or second aspect, in one possible design, downlink data is carried in at least one physical downlink shared channel (PDSCH).

[0036] According to a third aspect, a communication device is described. This communication device has the functions of the first aspect. For example, the communication device includes corresponding modules, units, or means for performing the operations of the first aspect. These modules, units, or means can be implemented in software, in hardware, or a combination of software and hardware.

[0037] According to the fourth aspect, a communication device is described. This communication device has the functions of the second aspect. For example, the communication device includes corresponding modules, units, or means for performing the operations of the second aspect. These modules, units, or means can be implemented in software, in hardware, or a combination of software and hardware.

[0038] According to the fifth aspect, another communication device is described. The communication device includes a memory and one or more processors. The memory stores some or all of a computer program or instructions necessary for implementing the functions of the first aspect. The one or more processors can execute the computer program or instructions, which, when executed, enable the communication device to implement the methods in any possible design or implementation of the first aspect.

[0039] In some possible implementations, the communication device may also include interface circuitry, through which the processor communicates with another device or component.

[0040] In some possible implementations, the communication device may also include a memory.

[0041] The communication device can be a terminal, a module in the terminal, or a chip in the terminal that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC chip or SIP chip that includes a modem module.

[0042] According to the sixth aspect, another communication device is described. The communication device includes a memory and one or more processors. The memory stores some or all of a computer program or instructions necessary for implementing the functions of the second aspect. The one or more processors can execute the computer program or instructions, which, when executed, enable the communication device to implement the methods in any possible design or implementation of the second aspect.

[0043] According to a seventh aspect, a communication system is described. The communication system includes communication means implementing the first aspect and communication means implementing the second aspect.

[0044] According to the eighth aspect, a computer-readable storage medium is described. The computer-readable storage medium stores computer-readable instructions that, when read and executed by a computer, enable the computer to perform any of the possible methods in the design of the first to second aspects.

[0045] According to a ninth aspect, this application provides a computer program product. When a computer reads and executes the computer program product, it enables the computer to perform any of the possible methods in the design of the first to second aspects. Attached Figure Description

[0046] Figure 1 This is a schematic diagram of the application scenario provided in this application; Figure 2 An exemplary communication system 100 is shown; Figure 3 Another example of an ED and a base station is shown; Figure 4 This shows the units or modules in the device; Figure 5 A schematic flowchart of a communication method 500 provided in an embodiment of this application is shown; Figure 6 A schematic diagram of a first example of the implementation provided in this application is shown; Figure 7 A schematic diagram illustrating a second example of the implementation provided in this application is shown; Figure 8 A schematic diagram of a third example of the implementation provided in this application is shown; Figure 9 A schematic diagram of a fourth example of the implementation provided in this application is shown; Figure 10 and Figure 11 This is a schematic block diagram of a possible device provided in the embodiments of this application. Detailed Implementation

[0047] The technical solution of this application is described below with reference to the accompanying drawings.

[0048] Figure 1 This is a schematic diagram of an application scenario provided in the embodiments of this application.

[0049] refer to Figure 1The simplified schematic diagram of the communication system is provided as an illustrative example and not a limitation. Communication system 100 (which may be a wireless system) includes a radio access network (RAN) 120. The RAN 120 may be an advanced (or future) RAN or a conventional (e.g., 5G, 4G, 3G, or 2nd generation, 2G) RAN. In the RAN 120, one or more electronic devices (EDs) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (collectively referred to as 110) may be interconnected with each other or connected to one or more network nodes (170a, 170b, collectively referred to as 170). Core network 130 may be part of the communication system and may depend on or be independent of the radio access technology used in communication system 100. The communication system 100 may also include a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0050] Typically, communication system 100 enables multiple wireless or wired components to transmit data and other content. Communication system 100 can provide voice, data, video, and / or text content through broadcasting, multicast, unicast, etc. Communication system 100 can provide a wide range of communication services and applications (e.g., earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery, and mobility). Services and / or applications may be mobile broadband (MBB) services, ultra-reliable low-latency communication (URLLC) services, or machine-type communication (MTC) services.

[0051] The communication system 100 can operate by sharing resources (such as carrier spectrum bandwidth) among its components.

[0052] Figure 2 An example of a communication system is shown.

[0053] Communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. Communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can enable a heterogeneous network comprising multiple layers. Heterogeneous networks can achieve better overall performance through efficient multi-link joint operation, more flexible function sharing, and faster physical layer link switching between terrestrial and non-terrestrial networks.

[0054] Terrestrial communication systems and non-terrestrial communication systems can be considered as subsystems of a communication system.

[0055] and Figure 1 The example shown is the same, in Figure 2In the example shown, communication system 100 may include ED 110a, 110b, 110c, 110d (collectively referred to as ED 110) and RAN 120a, 120b. Furthermore, communication system 100 may also include a non-terrestrial communication network 120c. Communication system 100 may also include one or more of a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. RAN 120a, 120b include corresponding RAN nodes, such as base stations (BS) 170a, 170b, which may be collectively referred to as terrestrial transmit and receive points (T-TRP) 170a, 170b. In one implementation, non-terrestrial communication network 120c includes RAN nodes, such as access nodes (or base stations) 172, which may be collectively referred to as non-terrestrial transmit and receive points (NT-TRP) 172. As can be inferred from the similarities in the reference numerals, the non-terrestrial communication network 120c can be considered a radio access network with common operational aspects to RAN 120a and RAN 120b. In another implementation, the non-terrestrial communication network 120c may include at least one non-terrestrial network (NTN) device and at least one corresponding terrestrial network device, wherein the at least one NTN device operates as a transport layer device, the at least one corresponding terrestrial network device operates as a RAN node, and the at least one corresponding terrestrial network device communicates with the ED through the NTN device. Furthermore, an NTN gateway (i.e., referred to as a terrestrial network device) may also exist on the ground as a transport layer device for communicating with both the NTN device and the RAN node, and the RAN node communicates with the ED through the NTN device and the NTN gateway. In some implementations, the NTN gateway and the RAN node may reside in the same device.

[0056] Alternatively or additionally, any ED 110 can be used to access, connect to, or communicate with any T-TRP 170a and 170b and NT-TRP 172, Internet 150, core network 130, PSTN 140, other network 160, or any combination thereof. In some examples, ED 110a can transmit uplink (UL) and / or downlink (DL) data with T-TRP 170a via terrestrial air interface 190a. In some examples, ED 110a, 110b, 110c, and 110d can also communicate directly with each other via one or more sidelink (SL) air interfaces 190b. In some examples, ED 110d can transmit uplink and / or downlink data with NT-TRP 172 via non-terrestrial air interface 190c.

[0057] Air interfaces 190a and 190b can use similar communication technologies, such as any suitable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, such as code division multiple access (CDMA), space division multiple access (SDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA) (also known as discrete Fourier transform spread OFDMA (DFT-s-OFDMA)). Air interfaces 190a and 190b can use other higher-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.

[0058] The non-terrestrial air interface 190c enables communication between the ED 110d and one or more NT-TRP 172s via a wireless link (or simply a link). For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of ED 110s and one or more NT-TRP 172s for multicast transmission.

[0059] RANs 120a and 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 120b and / or core network 130 may communicate directly or indirectly with one or more other RANs (not shown), which may (or may not) be directly served by core network 130 and may (or may not) employ the same radio access technology as RANs 120a, RAN 120b, or both. Core network 130 may also serve as a gateway access between (i) RANs 120a and 120b, or EDs 110a, 110b, and 110c, or both, and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Furthermore, some or all of EDs 110a, 110b, and 110c may include the ability to communicate with different wireless networks via different radio links using different radio technologies and / or protocols. Instead of wireless communication (or other than wireless communication), ED 110a, 110b, and 110c can also communicate with service providers or exchanges (not shown) via wired communication channels and with the Internet 150. PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include computer networks and / or subnets (internal networks) and include protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating according to various wireless access technologies and include multiple transceivers required to support these technologies.

[0060] Furthermore, the communication system 100 may include a sensing agent (not shown) for managing sensing data from ED 110 and / or T-TRP 170 and / or NT-TRP 172. In one implementation, the sensing agent is located within T-TRP 170 and / or NT-TRP 172. In another implementation, the sensing agent is a separate node with an interface for communicating with core network 130 and / or RAN 120 (e.g., T-TRP 170 and / or NT-TRP 172).

[0061] Figure 3 Another example of an electronic device (ED) and a base station is shown.

[0062] Figure 3 An example is shown of a device 310 provided in one embodiment wirelessly communicating with at least one of two devices (e.g., device 320a and device 320b, referred to as device 320) in a communication system (e.g., communication system 100). Device 310 may be a UE (e.g., Figure 3 ED 110 in the middle). Device 320a can be a terrestrial network device (e.g., ED 110). Figure 3 The T-TRP170 shown), device 320b can be a non-terrestrial network device (e.g., Figure 3 (NT-TRP 172 shown). However, this is not mandatory. For example, according to the present invention, device 320a can be NT-TRP, device 320b can be T-TRP, and both device 320a and device 320b can be either T-TRP or NT-TRP. In the following description, ED 110 is used as an example of device 310, T-TRP 170 is used as an example of device 320a, and NT-TRP 172 is used as an example of device 320a. Although only one device 310, one device 320a, and one device 320b are shown, it should be noted that the number of devices 310 (e.g., ED 110) can be one or more, and the number of devices 320a and / or 320b can be one or more. For example, an ED 110 can be served by only one T-TRP 170 (or one NT-TRP 172), can be served by more than one T-TRP 170, can be served by more than one NT-TRP 172, or can be served by one or more T-TRP 170 and one or more NT-TRP 172.

[0063] The ED 110 is used to connect people, things, and machines. It can be widely applied in various scenarios, including, for example, cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), MTC, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), mixed reality (MR), metaverse, digital twins, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, and mobility.

[0064] Each ED 110 represents any suitable end-user equipment used for wireless operation and may include (or be referred to as, but not limited to): user equipment (UE) / terminal equipment, wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), MTC equipment, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics, smartbook, vehicle, automobile, truck, bus, train, or IoT device, wearable device (e.g., watch, glasses, head-mounted device, etc.), industrial equipment, or devices within the aforementioned devices (e.g., communication modules, modems, or chips) or devices composed of the aforementioned devices, etc. Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs and are referred to hereinafter as T-TRP 170. Also as Figure 3 As shown, the non-terrestrial (NT) device is referred to below as NT-TRP 172. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically enabled (i.e., established, activated, or enabled), disabled (i.e., released, deactivated, or disabled), and / or configured in response to one or more of the following: connectivity availability and connectivity necessity.

[0065] like Figure 3As shown, ED 110 includes at least one processor 210. Only one processor 210 is shown in the figure to avoid congestion. ED 110 may also include a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is shown in the figure to avoid congestion. Alternatively, one, some, or all of the antennas 204 may be panels. For example, the transmitter 201 and receiver 203 may be integrated as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver is also used to demodulate data or other content received by at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals. ED 110 may include at least one memory 208. For simplicity, only transmitter 201, receiver 203, processor 210, memory 208 and antenna 204 are shown, but ED 110 may include one or more other components.

[0066] Memory 208 stores instructions. Memory 208 may also store data used, generated, or acquired by ED 110. For example, memory 208 may store software instructions or modules that are executed by one or more processing units (e.g., processor 210) to implement some or all of the functions and / or embodiments described herein. Each memory 208 includes one or more of any suitable volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory may be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, processor cache, etc.

[0067] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g. Figure 1 (Wired interface of Internet 150 in the network). Input / output devices or interfaces can interact with users or other devices in the network. Each input / output device or interface includes any suitable structure for providing or receiving information from the user and / or for communication on the network interface. For example, suitable structures include speakers, microphones, keypads, keyboards, displays, touchscreens, etc.

[0068] Processor 210 performs (or controls ED 110 to perform) operations described herein as being performed by ED 110, as shown below and elsewhere in the invention. For example, processor 210 performs or controls ED 110 to perform the following operations: receive a transport block (TB), use resources to decode one TB from the received TB, release resources to decode another TB from the received TB, and / or receive configuration information for configuration resources. Specifically, operations may include those related to preparing for uplink transmissions to NT-TRP 172 and / or T-TRP 170; those related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170; and those related to processing sidelink transmissions to and from another ED 110. Processing operations related to preparing for uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to downlink transmissions may include receive beamforming, demodulation and decoding of received symbols, etc. Processing operations related to downlink transmissions may include transmit / receive beamforming, modulation / demodulation and encoding / decoding of symbols, etc. According to an embodiment, receiver 203 may receive downlink transmissions (possibly using receive beamforming), and processor 210 may extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). Examples of signaling may be reference signals transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 210 performs transmit beamforming and / or receive beamforming based on beam direction indications (e.g., beam angle information (BAI)) received from T-TRP 170. In some embodiments, processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding and acquiring system information, etc. In some embodiments, the processor 210 may perform channel estimation using reference signals received from NT-TRP 172 and / or T-TRP 170, etc.

[0069] Although not shown, processor 210 may form part of transmitter 201 and / or receiver 203. Although not shown, memory 208 may form part of processor 210.

[0070] The processing components of processor 210, transmitter 201, and receiver 203 may each be implemented by the same or different one or more processors, which execute instructions stored in memory (e.g., memory 208). Alternatively, some or all of the processing components of processor 210, transmitter 201, and receiver 203 may each be implemented using dedicated circuitry, such as a programmable field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), or hardware accelerators such as graphics processing unit (GPU) or artificial intelligence (AI) accelerators.

[0071] In some implementations, ED 110 may be a device (also referred to as a component), such as a communication module, modem, chip, or chipset, which includes at least one processor 210 and an interface or at least one pin. In this scenario, the transmitter 201 and receiver 203 may be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as sending information to an interface or at least one pin, or as sending information to NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin. Receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 can be referred to as receiving information from an interface or at least one pin, or as receiving information from NT-TRP 172 and / or T-TRP 170 and / or another ED 110 via an interface or at least one pin. This information may include control signaling and / or data.

[0072] like Figure 3As shown, the T-TRP 170 includes at least one processor 260. Only one processor 260 is shown in the figure to avoid congestion. The T-TRP 170 may also include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figure to avoid congestion. Alternatively, one, some, or all of the antennas 256 may be a panel. The transmitter 252 and receiver 254 may be integrated as a transceiver. The T-TRP 170 may also include at least one memory 258. The T-TRP 170 may also include a scheduler 253. For simplicity, only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256, and scheduler 253 are shown, but the T-TRP may include one or more other components.

[0073] In some implementations, T-TRP 170 may be known by other names, such as base station, basetransceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, base station (Node B), evolved NodeB (eNodeB or eNB), femtocell, future generation NodeB (gNB), transmission point (TP), site controller, access point (AP) or wireless router, relay station, ground node, ground network device, ground base station, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. T-TRP 170 can be a macro base station (BS), pico BS, relay node, host node, or a combination thereof. T-TRP 170 may refer to the aforementioned equipment or a device within the aforementioned equipment (e.g., a communication module, modem, or chip).

[0074] In some embodiments, portions of T-TRP 170 may be distributed. For example, some modules of T-TRP 170 may be located remotely from the device housing the antenna 256 for T-TRP 170 and may be coupled to the device housing the antenna 256 via a communication link (not shown) (e.g., a common public radio interface, CPRI) sometimes referred to as a fronthaul. Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations such as determining the location of ED 110, resource allocation (scheduling), message generation, and encoding / decoding, and are not necessarily part of the device housing the antenna 256 of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs that work together, for example, using coordinated multicast transmissions, to serve ED 110.

[0075] Processor 260 performs operations related to: preparing transmissions for downlink transmissions to ED 110; processing uplink transmissions received from ED 110; preparing transmissions for backhaul transmissions to T-TRP 170 and / or NT-TRP 172; and processing transmissions received via backhaul from T-TRP 170 and / or NT-TRP 172. Processing operations related to preparing transmissions for downlink or backhaul transmissions may include encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via backhaul may include receive beamforming, demodulating received symbols, and decoding received symbols. Processor 260 may also perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating the contents of a synchronization signal block (SSB) and generating system information. In some embodiments, processor 260 also generates a beam direction indication, such as a BAI, which can be scheduled by scheduler 253 for transmission. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110, determining where to deploy NT-TRP 172, etc. In some embodiments, processor 260 may generate signaling, for example, to configure one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252.

[0076] Scheduler 253 may be coupled to or integrated into processor 260. Scheduler 253 may be included within T-TRP 170 or operate separately from T-TRP 170. Scheduler 253 may schedule uplink, downlink, lateral link, and / or backhaul transmissions, including issuing scheduling authorizations and / or configuring unscheduled (e.g., "configured authorization") resources.

[0077] Memory 258 is used to store information, and optionally data. Memory 258 stores instructions and data used, generated, or acquired by T-TRP 170. For example, memory 258 may store software instructions or modules executed by processor 260 for implementing some or all of the functions and / or embodiments described herein.

[0078] Although not shown, processor 260 may form part of transmitter 252 and / or receiver 254. Furthermore, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may form part of processor 260.

[0079] The processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may each be implemented by the same or different one or more processors, which execute instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented using dedicated circuitry such as programmable FPGAs, hardware accelerators (e.g., GPUs or AI accelerators), or ASICs.

[0080] When T-TRP 170 is a device (also referred to as a component, such as a communication module, modem, chip, or chipset) in a device, it includes at least one processor, an interface, or at least one pin. In this scenario, transmitter 252 and receiver 254 can be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., chips, memory, or buses). Therefore, sending information to NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as sending information to an interface or at least one pin, and receiving information from NT-TRP 172 and / or T-TRP 170 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. This information may include control signaling and / or data.

[0081] Although the NT-TRP 172 is shown as an example of a drone only, it can be implemented in any suitable non-terrestrial form, such as satellites and high-altitude platforms, including international mobile communication base stations and unmanned aerial vehicles. Furthermore, the NT-TRP 172 may be referred to by other names in some implementations, such as non-terrestrial node, non-terrestrial network device, or non-terrestrial base station.

[0082] like Figure 3 As shown, the T-TRP 170 may also include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is shown in the figure to avoid congestion. Alternatively, one, some, or all of the antennas 256 may be a panel. The transmitter 252 and receiver 254 may be integrated as a transceiver. The T-TRP 170 may also include at least one memory 258. The T-TRP 170 may also include a scheduler 253. For simplicity, only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256, and scheduler 253 are shown, but the T-TRP may include one or more other components.

[0083] like Figure 3 As shown, the NT-TRP 172 includes at least one processor 276. Only one processor 276 is shown in the figure to avoid congestion. The NT-TRP 172 may include a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is shown in the figure to avoid congestion. Alternatively, one, some, or all of the antennas may be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 may also include at least one memory 278. The NT-TRP 172 may also include a scheduler. For simplicity, only the transmitter 272, receiver 274, processor 276, memory 278, and antenna 280 are shown, but the NT-TRP may include one or more other components.

[0084] NT-TRP 172 includes a processor 276 for performing operations, including operations related to: preparing a transmission for downlink transmission to ED 110; processing an uplink transmission received from ED 110; preparing a transmission for backhaul transmission to T-TRP 170 and / or another NT-TRP 172; and processing a transmission received from T-TRP 170 and / or another NT-TRP 172 via backhaul. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received in the uplink or via backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, for example, to configure one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-level functions such as medium access control (MAC) or radio link control (RLC) layer functions. Since this is only an example, more generally, NT-TRP 172 may implement higher-level functions in addition to physical layer processing.

[0085] Memory 278 is used to store information, and optionally data. Memory 258 stores instructions and data used, generated, or acquired by NT-TRP 172. For example, memory 278 may store software instructions or modules executed by processor 276 for implementing some or all of the functions and / or embodiments described herein.

[0086] Although not shown, processor 276 may form part of transmitter 272 and / or receiver 274. Although not shown, memory 278 may form part of processor 276.

[0087] The processing components of processor 276, transmitter 272, and receiver 274 may each be implemented by the same or different one or more processors, which execute instructions stored in memory (e.g., memory 278). Alternatively, some or all of the processing components of processor 276, transmitter 272, and receiver 274 may be implemented using dedicated circuitry such as a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC. In some embodiments, NT-TRP 172 may actually be multiple NT-TRPs that work together, for example, through coordinated multicast transmissions, to serve ED 110.

[0088] When NT-TRP 172 is a device (e.g., a communication module, modem, chip, or chipset) within a device, it includes at least one processor, an interface, or at least one pin. In this scenario, transmitter 272 and receiver 257 can be replaced by an interface or at least one pin, wherein the interface or at least one pin is used to connect the device (e.g., a chip) and other devices (e.g., a chip, memory, or bus). Therefore, sending information to T-TRP 170 and / or another NT-TRP 172 and / or ED 110 can be referred to as sending information to an interface or at least one pin, and receiving information from T-TRP 170 and / or another NT-TRP 172 and / or ED 110 can be referred to as receiving information from an interface or at least one pin. This information may include control signaling and / or data.

[0089] It should be noted that, as used in this document, "transmit / receive point (TRP)" can refer to either T-TRP or NT-TRP. T-TRP can also be called terrestrial network TRP (TNTRP), and NT-TRP can also be called non-terrestrial network TRP (NTN TRP). T-TRP170, NT-TRP 172, and / or ED 110 may include other components, but for clarity, these components are omitted.

[0090] It should be noted that, for simplicity, the term "signaling" used in this document can be referred to as control signaling, control message, control information, or message. Signaling between a BS (e.g., network node 170) and a terminal or sensing device (e.g., ED 110), or between different terminals or sensing devices (e.g., between ED 110i and ED 110j), can be carried in physical layer signaling (also known as dynamic signaling), which is transmitted in the physical layer control channel. For the downlink, physical layer signaling can be called downlink control information (DCI), which is transmitted in the physical downlink control channel (PDCCH). For the uplink, physical layer signaling can be called uplink control information (UCI), which is transmitted in the physical uplink control channel (PUCCH). For sidelinks, signaling between different terminals or sensing devices (e.g., between ED 110i and ED 110j) can be called sidelink control information (SCI), which is transmitted in the physical sidelink control channel (PSCCH). Signaling can be carried in higher-layer signaling (e.g., above the physical layer), which is transmitted in physical layer data channels. For example, downlink signaling is transmitted in the physical downlink shared channel (PDSCH), uplink signaling in the physical uplink shared channel (PUSCH), and sidelink signaling in the physical sidelink shared channel (PSSCH). Higher-layer signaling can also be called static signaling or semi-static signaling. Higher-layer signaling can be radio resource control (RRC) protocol signaling or media access control-control element (MAC-CE) signaling. Signaling can be included in a combination of physical layer signaling and higher layer signaling.

[0091] It should be noted that in this invention, "information" (when different from "message") can be carried in a single message or in more than one single message.

[0092] Figure 4 This is an example of the conceptual structure of a network system.

[0093] according to Figure 4 One or more steps of the method provided by the present invention can be executed by the corresponding unit or module. Figure 4 The diagram illustrates units or modules within a device or apparatus (e.g., in ED 110, T-TRP 170, or NT-TRP 172). For example, signals may be transmitted by a transmitting unit or a transmitting module. Signals may be received by a receiving unit or a receiving module. Signals may be processed by a processing unit or a processing module. Other steps may be performed by an artificial intelligence (AI) or machine learning (ML) module. The respective units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more of the units or modules may be circuits such as integrated circuits. Examples of integrated circuits include programmable FPGAs, GPUs, or ASICs. For example, one or more of the units or modules may be logic, such as logical functions executed by circuits, a portion of an integrated circuit, or software instructions executed by a processor. It should be understood that if the aforementioned modules are implemented using software executed by a processor, etc., these modules may be retrieved by the processor, wholly or partially, individually or collectively, for processing, or in one or more instances as needed, and these modules themselves may include instructions for further deployment and instantiation.

[0094] Additional details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, for clarity, these details are omitted herein.

[0095] Wireless communication systems such as fourth-generation (4G) systems (e.g., long-term evolution (LTE) systems) and fifth-generation (5G) systems (e.g., new radio (NR) systems) have been deployed to provide various types of applications, such as messaging, voice, video, and other data.

[0096] The purpose of the background information is to illustrate information that the applicant believes may be relevant to this invention. It is neither necessary nor appropriate to acknowledge that any of the above information constitutes prior art in relation to this invention.

[0097] This invention is intended to relate to devices such as UEs, IoT devices, and automobiles. Envisioned network scenario types may include terrestrial TRPs such as base stations, and / or non-terrestrial TRPs such as drones, balloons, high-altitude platform stations (HAPS), and satellites, as well as any such devices supporting wireless access technologies (e.g., 5G NR, advanced, future, or other technologies).

[0098] For the purpose of illustration, specific exemplary embodiments will be explained in more detail with reference to the accompanying drawings and the system, ED, and TRP described above.

[0099] The embodiments described herein represent information sufficient to practice the claimed subject matter and illustrate methods for practicing such subject matter. Upon reading the following description with reference to the accompanying drawings, those skilled in the art will understand the concepts of the claimed subject matter and will recognize that the application of these concepts is not specifically described herein. It should be understood that these concepts and applications are within the scope of the invention and the appended claims.

[0100] In traditional cellular systems such as 5G NR, the UE can receive, detect, and measure reference signals, such as SS / PBCH blocks and NZP-CSI-RS. These reference signals are based on pseudo random noise (PRN) binary sequences, such as the Gold sequence, which can be initialized using common or UE-specific scrambling identifiers. For example, the primary synchronization signal (PSS) sequence and the secondary synchronization signal (SSS) sequence are initialized using the physical cell identity (PCI) value, which is a common scrambling identifier. The NZP-CSI-RS sequence is initialized using UE-specific scrambling identifiers, which are configured to the UE by the network.

[0101] 5G NR Rel-17 introduces support for non-terrestrial networks by introducing several enhancements to timing relationships, such as timing advance, reference timing for channel state information (CSI) resources, transmission timing for DCI scheduling PUSCH, transmission timing for random access responses carried by PUSCH, and transmission timing for HARQ-ACK on PUCCH.

[0102] In 5G NR Rel-17, NTN support was introduced, enabling UEs to support DL / UL communication with satellites in "bend-edge" scenarios. In this scenario, the ground station sends signals to satellites in space, and the satellites reflect the signals back to the UE on the ground. To assist UEs in NTN operations, dedicated signaling related to NTN was introduced. Higher-layer signaling (such as RRC) incorporates signaling related to satellite ephemeris, satellite position, satellite signal polarization, timing advance offset, system information block (SIB), and satellite epoch to support NTN operations. Other introduced features include extending the hybrid automatic repeat request (HARQ) procedure to 32 to accommodate scenarios with large propagation delays, and disabling HARQ-ACK feedback.

[0103] Before introducing the communication method provided in this application, some concepts will be introduced for better understanding.

[0104] (1) Feedback mechanism The sending and receiving process may involve: (a) the transmitter sending data to the receiver; (b) the receiver sending feedback information to the transmitter; and (c) the transmitter determining whether to perform a retransmission based on the feedback information. It should be noted that the feedback information can indicate whether the data was successfully received (or decoded). If the feedback information indicates that the data was successfully received (or decoded), the transmitter may not perform a retransmission. If the feedback information indicates that the data was not successfully received (or decoded), the transmitter may perform the corresponding retransmission.

[0105] In some implementations, the feedback information may include an acknowledgement (ACK) signal or a non-acknowledgement (NACK) signal. Steps (a), (b), and (c) can be referred to as the hybrid automatic repeat request (HARQ) process.

[0106] HARQ is a mechanism for providing reliable wireless transmission. It combines forward error correction (FEC) and automatic repeat request (ARQ). In HARQ, the initial transmission is an FEC codeword with cyclic redundancy check (CRC) bits to support error detection on the receiver side. If a decoding error is detected, the receiver sends a NACK signal back to the transmitter to notify of the error and request a retransmission. The retransmission bits can be selected directly from the initial transmission bits or incrementally generated code bits, which, together with the initial transmission bits, form a longer codeword. The former is called chase-combining HARQ (CC-HARQ), and the latter is called incremental-redundancy HARQ (IR-HARQ). Generally, IR-HARQ outperforms CC-HARQ due to the additional coding gain from incremental redundancy.

[0107] In 5G NR, HARQ plays a crucial role in ensuring reliable data transmission. The HARQ process relies on a feedback mechanism between the base station (gNB) and the UE to identify and correct errors. The following is a summary of the 5G HARQ feedback mechanism: Data transmission and channel coding (Step 1): The gNB sends data to the UE using a format called a transport block (TB). Before transmission, the payload data is encoded using channel coding. Redundancy introduced during channel coding helps the UE detect and potentially correct errors.

[0108] Decoding at UE (Step 2): The UE receives the data and attempts to decode it using forward error correction (FEC) codes.

[0109] Feedback from UE (Step 3): ACK / NACK: If the UE successfully decodes the data, it sends an ACK signal to the gNB. If an error is detected and cannot be corrected, it sends a NACK signal.

[0110] HARQ Retransmission (Step 3): If a NACK is received, the gNB retransmits the data using a different coding scheme or higher power (or a specific CBG) to improve reception. The number of retransmission attempts is limited to avoid excessive latency and decoding complexity. The HARQ process ends when an ACK is received or after the maximum number of retransmissions has been reached.

[0111] It should be noted that this application does not limit the type of feedback information. The UE can use various feedback types. This can provide more granular feedback than simple ACK / NACK. For example, feedback information may include channel state information (CSI). This provides the gNB with detailed information about the signal quality experienced by the UE. This information is valuable for adjusting future transmissions based on real-time channel conditions.

[0112] In some implementations, the UE can send more specific ACK / NACK formats. These formats can indicate which parts of the TB were received correctly or incorrectly. For example, the TB can be further divided into multiple CB groups (CBGs), each CBG containing multiple CBs. This allows for more targeted retransmissions.

[0113] In wireless communication, for data channels, the HARQ process is implemented to support the retransmission of the same data as well as a hybrid combination of original transmission and retransmission, thereby combating channel impairments and improving the robustness of system performance.

[0114] (2) Time division duplex (TDD) and frequency division duplex (FDD) TDD and FDD are both spectrum usage technologies. TDD is a communication technology in which the transmitter and receiver use the same frequency band (which can be called the TDD band) but transmit and receive traffic at different times. FDD is a full-duplex technology that uses two different frequencies (which can be called the FDD band) for transmission and reception.

[0115] (3) Cross-carrier scheduling Traditional scheduling involves allocating resources (e.g., resource blocks (RBs)) on a single carrier for user data transmission. In cross-carrier scheduling, the gNB (base station) coordinates the scheduling on different carriers where the UE resides.

[0116] Scheduling information: The gNB determines which UEs need to send data and which carriers have available resources.

[0117] Scheduling information (including the carriers used and the resources allocated) is sent to the UE.

[0118] Two options: Self-scheduling: Scheduling information (scheduling grant, SG) and actual data (scheduling assignment, SA) are transmitted on the same carrier. The UE receives both on the same carrier.

[0119] Cross-carrier scheduling (CCS): The SG (Signaling Target) and the actual data are transmitted on different carriers. The UE receives the SG on one carrier, and the SG instructs the UE to switch to another carrier for data transmission.

[0120] In the current feedback mechanism, the PDSCH-ACK / NACK timing indicator defines the time interval between sending the PDSCH and receiving the PUCCH that carries the ACK / NACK for the PDSCH.

[0121] Current uplink feedback mechanisms have some limitations that may hinder the efficiency and responsiveness of advanced (or future) networks.

[0122] Feedback delays due to uplink transmission opportunities: User equipment (UE) must wait for a designated uplink transmission opportunity to send feedback information. This waiting time can introduce significant latency, especially in scenarios with limited uplink scheduling opportunities.

[0123] Uncertain feedback timing in TDD frame structure: Due to the inherent frame structure of time division duplex (TDD) frames, which alternates between uplink (UL) and downlink (DL) time slots, a fast feedback opportunity cannot be guaranteed (it must be in the UL time slot). This leads to inefficiency in the feedback process.

[0124] Insufficient timeliness of slot-level scheduling: Existing feedback slot-level scheduling methods are considered insufficient to meet the needs of future networks. These methods may not provide the necessary granularity to ensure timely and effective feedback transmission.

[0125] There are several reasons for accelerating uplink feedback in advanced link adaptation techniques.

[0126] Therefore, this application provides a method for allocating dedicated resources for feedback information, ensuring feedback opportunities, and improving feedback reliability.

[0127] In some implementations, the present invention generally relates to wireless communication. Specifically, the present invention relates to a method, apparatus, and system for cross-FDD-TDD scheduling.

[0128] The following will explain specific exemplary embodiments of the present invention.

[0129] The implementation of this application can be applied to any of the communication scenarios described above. For example, the network-side method is shown for the BS, and the terminal-side method is shown for the UE.

[0130] Figure 5 A schematic flowchart of a communication method 500 provided in an embodiment of this application is shown.

[0131] In step 510, the BS sends control information to the UE. Correspondingly, the UE receives control information from the BS.

[0132] The control information indicates a first physical resource for transmitting feedback information, which is associated with a first FDD frequency band. Therefore, the UE can transmit feedback information on the first FDD frequency band. In other words, the first physical resource can be dedicated to the transmission of feedback information, guaranteeing feedback opportunities and improving feedback reliability.

[0133] It should be noted that in the implementation of this application, physical resources are associated with frequency bands (e.g., the first physical resource is associated with the first FDD frequency band), which means that the physical resource is within the frequency band. For example, for a UL FDD frequency band (or DLFDD frequency band), the physical resource in the frequency domain is the UL frequency (or DL ​​frequency) of the FDD frequency band, and UL information (or DL ​​information) is transmitted through the UL frequency (or DL ​​frequency). As another example, for a TDD frequency band, the physical resource in the time domain is the UL timeslot (or DL ​​timeslot) of the TDD frequency band, and UL information (or DL ​​information) is transmitted in the UL timeslot (or DL ​​timeslot).

[0134] Feedback information can be of various types. As mentioned above, feedback information may include ACK or NACK and / or feedback information may include CSI. This application does not exclude other possible types of feedback information.

[0135] In some implementations, feedback information indicates whether some or all of the downlink data was successfully received or not, wherein the downlink data is associated with at least one frequency band.

[0136] It should be noted that the first FDD band is a UL FDD band, meaning that uplink feedback information and downlink data are transmitted on different frequency bands. The first FDD band can be dedicated to the transmission of feedback information. This dedicated first FDD band ensures the opportunity for feedback information transmission and provides timely feedback.

[0137] In some implementations, feedback information can be included in PUCCH and / or PUSCH. For example: Dedicated feedback channel: In some implementations, specific control channels are designated for HARQ feedback transmission from the UE to the gNB (base station). These channels are separate from those used for user data transmission.

[0138] Types of feedback channels: PUCCH: HARQ feedback can be sent on PUCCH. This can be used for short feedback messages with a small number of TBs or CBGs.

[0139] PUSCH: UCIs, including HARQ feedback, can be sent on the PUSCH. If there happens to be uplink data transmission, the UCI is multiplexed with the data packet.

[0140] Advanced link adaptation techniques heavily rely on timely feedback transmitted via the uplink channel. This implementation details the benefits of faster uplink feedback for two key HARQ feedback mechanisms: ACK / NACK and channel state information (CSI). For example: Reduce interference and power consumption through faster ACK / NACK: When the base station (BS) quickly receives an ACK signal, it can immediately terminate the transmission of data packets that the user equipment (UE) has successfully decoded. This reduces unnecessary air interface time usage, thereby: Reduce overall interference in the network so that all users can benefit; Reduce transmission power consumption at the BS and improve energy efficiency; Reduce the decoding complexity at the UE, because the UE no longer needs to process redundant information.

[0141] Faster CSI feedback improves spectral efficiency: Faster CSI feedback enables the BS to more accurately track dynamic changes in channel conditions. With real-time information about the channel state, the BS can optimize: Modulation and coding scheme (MCS) selection: Selecting the most suitable MCS based on the current channel quality ensures efficient and error-free data transmission; Precoding schemes: These techniques can be dynamically adjusted to mitigate channel impairments and improve signal reception at the UE.

[0142] Control information can indicate the first physical resource in various ways. In some implementations, the control information can implicitly indicate the first physical resource. For example, the control information may include an indication (e.g., an index) of the first physical resource. The UE can determine the first physical resource based on the indication and other parameters known to the UE. In some implementations, the control information can explicitly indicate the first physical resource. For example, the control information may include a first field and a second field, wherein the first field indicates the location of the first physical resource in the frequency domain and the second field indicates the location of the first physical resource in the time domain. This application does not limit this approach.

[0143] It should be noted that feedback information and downlink data can be transmitted on different frequency bands. Therefore, control information can indicate the frequency band for receiving / transmitting feedback information. For example, control information may include frequency information indicating the frequency band, carrier, or other frequency element for feedback information. This application does not limit this.

[0144] In some implementations, the control information may include timing information for the feedback information, which is associated with one or more of the following: a set of parameters associated with a first FDD band, and a set of parameters associated with the band where the control information is received. The timing information may indicate the feedback timing when the UE receives the feedback information.

[0145] It should be noted that the parameter set can refer to the physical waveform characteristics in terms of subcarrier spacing and corresponding time-domain length. Different frequency bands can correspond to different parameter sets. Since feedback and control information can be transmitted on different frequency bands, timing information can be interpreted in multiple ways.

[0146] For example, timing information can be obtained from a reference timing and a first offset. The reference timing can be referred to as a base position in the time domain, and some timing offset will be added to this base position. For example: The reference timing position can serve as the starting time position in terms of either the slot index or the symbol index. It can be indicated by the DCI field "reference timing indicator," sometimes also called n0, which specifies the starting position as the base to which any timing offset value will be added for n0.

[0147] The first offset can be defined based on the timing of receiving control information or the timing of receiving downlink data. For example, the feedback timing can be expressed as a first offset relative to the timing of control information (e.g., DCI) or downlink data (e.g., PDSCH).

[0148] In some implementations, the control information may include an indicator for reference timing and / or an indicator for a first offset.

[0149] It should be noted that the interpretation of the reference timing and first offset indicators may be related to the following: the parameter set associated with the first FDD band (hereinafter also referred to as the feedback parameter set) and / or the parameter set associated with the band receiving control information (hereinafter also referred to as the DCI parameter set).

[0150] For example, the reference timing indicator is a reference time position relative to the DCI timing or PDSCH transmission, and the reference timing unit depends on the parameter set.

[0151] Reference timing indicators can be defined using either the DCI parameter set or the feedback parameter set.

[0152] For example, the feedback timing indication is an offset relative to the DCI timing or PDSCH transmission, and the offset unit depends on the parameter set.

[0153] The DCI field “PDSCH-to-HARQ_feedback timing indicator,” sometimes also called k1, specifies the delay between the end of the slot used to transmit data (PDSCH) and the start of the slot where the UE transmits ACK / NACK (HARQ feedback) for that data. For example: Timing offset unit: The offset k1 is indicated by a time slot, TTI, or other time resource unit; or The offset k1 in terms of sub-slots or symbols is indicated to enable finer-grained and low-delay feedback.

[0154] Timing offset parameter set: Using the DCI parameter set μ1 to indicate offset k1, it is converted into the feedback parameter set μ2, that is, the actual feedback timing in the feedback frequency band is... When μ1 > μ2, the result may be a fraction, which needs to be converted to an integer using rounding down / rounding up / rounding up operations; or Based on the above transformation, the offset k1' is directly indicated by the feedback parameter set μ2.

[0155] A method for time alignment and feedback timing indication based on parameter sets is provided.

[0156] In some implementations, the control information also indicates a second physical resource for downlink data. The first and second physical resources can be indicated by the same control information, which allows feedback to be synchronized with the downlink data and improves the reliability of the feedback.

[0157] Downlink data can be included in at least one PDSCH. Although not shown, the BS can transmit downlink data using a second physical resource, and correspondingly, the UE can receive downlink data on the second physical resource based on control information.

[0158] In some implementations, the second physical resource is associated with one or more frequency bands, which include one or more of the following: at least one FDD band and at least one time division duplex (TDD) band. The second physical resource is allocated to downlink data, which can be carried in at least one FDD band and at least one TDD band. The BS can transmit downlink data to the UE using a format called a transport block (TB). A TB can be allocated to one or more frequency bands. This helps improve spectrum utilization.

[0159] In some implementations, codewords can be mapped to part or all of one or more frequency bands associated with a second physical resource. Codewords can correspond to a TB or a code block group (CBG). A single codeword can be assigned to at least one FDD band, at least one TDD band, or a combination of at least one TDD band and at least one FDD band. For example, a single codeword can be mapped to multiple TDD bands simultaneously. This flexible codeword mapping mechanism can help to utilize resources efficiently. This application does not limit this.

[0160] For example, flexible codeword mapping: During codeword mapping, individual codewords (e.g., TB or CBG) can be mapped with greater flexibility. It can: Allocate to a single TDD band; Allocate to a single FDD band; Simultaneously allocated to multiple TDD frequency bands; A combination of TDD and FDD frequency bands.

[0161] This flexibility helps to use resources efficiently and adapt to various network conditions.

[0162] Therefore, the present invention provides a method. This method provides a feedback scheme across FDD-TDD frequency bands. Specifically, it provides joint TDD downlink and FDD uplink transmission, and may include the following features: Downlink data traffic: Downlink data traffic is transmitted on TDD and / or FDD bands, providing flexibility in spectrum usage; Uplink feedback on a dedicated FDD band (e.g., the first band): Uplink feedback information is transmitted on a dedicated FDD band, independent of the downlink data channel. This separation allows feedback transmission to be more timely and efficient.

[0163] It should be noted that the number and type of one or more frequency bands associated with downlink data in this application are not limited.

[0164] The control information may implicitly or explicitly indicate the second physical resource. For example, the control information may include an indicator of the second physical resource. As another example, the control information may include a third field and a fourth field, wherein the third field indicates the location of the second physical resource in the frequency domain and the fourth field indicates the location of the second physical resource in the time domain. This application does not limit this.

[0165] It should be noted that in some implementations, the control information may include at least two parameter sets, one of which indicates a first physical resource, and the remaining parameter sets indicate a second physical resource. The number of parameter sets indicating the second physical resource is related to the number of frequency bands associated with the second physical resource. This application does not impose any limitation on this. For example: Resource allocation information (i.e., control information) based on DCI: DCI messages carry specific time and frequency resource allocation information for downlink and uplink transmissions. It should be noted that DCI includes at least two sets of fields: one dedicated to PDSCH resource allocation, and the other for PUCCH resource allocation.

[0166] For example, the second physical resource is associated with both FDD and TDD bands. Enhanced DCI resource allocation information: DCI messages have been expanded to provide more comprehensive time and frequency resource allocation information. Specifically, DCI now includes at least three sets of fields: Two sets are dedicated to PDSCH resource allocation, one for each used TDD band and one for FDD band; A set is used for PUCCH resource allocation. This extension supports precise scheduling of downlink transmissions between TDD and FDD bands.

[0167] In some implementations, control information can be DCI, and control information can be included in PDCCH. A single piece of control information (e.g., DCI) can be used to schedule a first physical resource (for feedback information) and a second resource (for downlink data), thereby reducing signaling overhead.

[0168] In some implementations, control information can indicate the first physical resource and / or the second physical resource at various granularities. For example, the first physical resource and / or the second physical resource can be allocated based on time slots, symbols, orthogonal frequency division multiplexing (OFDM) symbols, or other time units in the time domain. The frequency units of the first physical resource and / or the second physical resource can be subcarriers, sub-bands, etc. This application does not limit this.

[0169] For example, mini-slot / symbol scheduling: PUSCH resources can be further divided into smaller time units called mini-slots. This allows for more granular scheduling of feedback transmissions, especially when dealing with a large number of UEs.

[0170] In some implementations, control information is received (or transmitted) on one or more frequency bands associated with the second physical resource. For example, control information can be carried on any one of the one or more frequency bands. Control information and downlink data can be received / transmitted on the same one or more frequency bands. This co-location simplifies the coordination between control information and the corresponding downlink data.

[0171] In some embodiments, when one or more frequency bands associated with the second physical resource include at least one TDD frequency band, control information may be transmitted on at least one TDD frequency band. For example: The scheduling of downlink data traffic and uplink feedback opportunities is dynamically achieved through a single downlink DCI message (e.g., control information). However, the transmission of this DCI message itself varies depending on the selected downlink frequency band. DCI can be transmitted on TDD bands: When downlink data uses TDD bands, DCI messages can also be transmitted on these TDD bands.

[0172] The relative position of DCI in the FDD / PUCCH parameter set: If the downlink data uses the FDD band, the relative timing position of the DCI message in the FDD / PUCCH parameter set (including the reference timing position and the feedback timing position) is predefined.

[0173] To facilitate understanding of how this application is implemented, some examples are provided below.

[0174] In the first example, the second physical resource is associated with the first TDD band, and control information is received on the first TDD band. Details of this example will be provided in conjunction with... Figure 6 Provided.

[0175] In the second example, the second physical resource is associated with both a second and a third TDD band, and control information is received on either the second or third TDD band. Details of this example will be provided in conjunction with... Figure 7 Provided.

[0176] In the third example, the second physical resource is associated with the second FDD band, and control information is received on the second FDD band. Details of this example will be provided in conjunction with... Figure 8 Provided.

[0177] In the fourth example, the second physical resource is associated with both the fourth TDD band and the third FDD band, and control information is received on the fourth TDD band. Details of this example will be provided in conjunction with... Figure 9 Provided.

[0178] It should be noted that the above examples are given for illustrative purposes only, and this application is not limited thereto.

[0179] In step 520, the UE sends feedback information to the BS. Correspondingly, the BS receives feedback information from the UE.

[0180] In some implementations, downlink data is associated with multiple frequency bands, and feedback information also indicates one or more corresponding frequency bands associated with some or all of the downlink data.

[0181] As mentioned above, in some implementations, multiple TBs (for downlink data) can be mapped to multiple frequency bands. Multiple TBs from different frequency bands can be decoded simultaneously. Therefore, the feedback information can identify one or more specific frequency bands and their corresponding downlink data responses. For example: Multiplexing Uplink Feedback Using Band Identifiers: In scenarios where a single TB is mapped to a single frequency band (TDD or FDD), it is possible to decode multiple TBs from different frequency bands (TDD or FDD) simultaneously. To address this, the system can support a mechanism for multiplexing corresponding uplink feedback messages on the PUCCH. Each feedback message can include a flag identifying a specific frequency band (TDD or FDD) and its corresponding PDSCH transmission. If dedicated feedback opportunities are reserved for TBs mapped across multiple TDD and FDD frequency bands, these flags can potentially be embedded in the uplink control information (UCI) payload.

[0182] As described above, the UE can obtain parameters related to the first physical resource and / or the second physical resource (e.g., one or more parameters in the frequency domain, one or more parameters in the time domain, etc.) in various ways. In some implementations, the relevant parameters can be dynamically indicated by the BS (e.g., in physical layer control signaling (e.g., DCI); or semi-statically indicated by the BS, for example, in radio resource control (RRC) signaling or in the medium access control (MAC) layer; or predefined based on the application scenario; or determined by the UE based on other parameters known to the UE; or fixed by the standard, for example. This application does not limit this.

[0183] For example, a combination of dynamic signaling and semi-static signaling can be implemented. Exemplarily, control information can be carried in dynamic signaling, and the BS can also send semi-static signaling before the control information. That is, the BS and UE can also perform step 530 before step 510.

[0184] Optionally, in step 530, the BS sends configuration information to the UE. Correspondingly, the UE receives configuration information from the BS.

[0185] Configuration information can indicate the resource set that includes the first physical resource.

[0186] In some implementations, configuration information can be included in RRC signaling. For example: RRC used to configure resource sets: The feedback time / frequency resource set can be pre-configured by RRC. The resource set can include multiple pairs of carrier indicators and feedback timing offsets as candidate feedback resources. Specifically, the configuration can include several tables, where each row corresponds to both time-domain and frequency-domain resources.

[0187] The DCI field "HARQ_feedback resource indicator" (e.g., control information) can be used to further specify which resource to use. Specifically, the row index in the aforementioned RRC resource configuration table can be indicated in the DCI to indicate the actual physical resource used for feedback.

[0188] Using resource sets provides great flexibility in resource allocation: in the case of multiple feedback, if a resource is already occupied, the UE can try to place the feedback on other available candidate resources.

[0189] In addition, in some implementations, some semi-static scheduling information (e.g., partial bandwidth and carrier index) is pre-configured via RRC to improve overall efficiency.

[0190] For example, dynamic scheduling: the gNB can control the scheduling of feedback transmissions on PUCCH / PUSCH. Resource allocation can be pre-configured by RRC and further indicated by DCI.

[0191] In some implementations, the configuration information may also indicate a resource set that includes the second physical resource. For details, please refer to the description of the first physical resource above; for brevity, this will be omitted here.

[0192] In some implementations, the configuration information may also indicate the parameter set associated with the first frequency band and / or the parameter set associated with the frequency band for receiving / transmitting control information. For example: Both the DCI parameter set μ1 and the feedback parameter set μ2 are configured in RRC (SIB1).

[0193] According to the above technical solution, the first physical resource associated with the FDD band can be dedicated to the transmission of feedback information, which can guarantee feedback opportunities and improve feedback reliability.

[0194] As described above, the second physical resource can be associated with at least one FDD frequency band and / or at least one TDD frequency band. For ease of understanding of the embodiments of this application, and for illustrative purposes, in conjunction with... Figures 6 to 9 Some detailed examples are given.

[0195] Below are some detailed examples.

[0196] exist Figures 6 to 9 In this diagram, blocks marked with the symbol "U" represent uplink physical resources, and blocks marked with the symbol "D" represent downlink physical resources. Downlink data is represented as PDSCH, feedback information as PUCCH, and control information as DCI located in the control resource set (CORESET).

[0197] Figure 6 A schematic diagram of a first example of an implementation provided by this application is shown. A second physical resource is associated with a first TDD frequency band, and control information is received on the first TDD frequency band. For example: In one possible implementation, a method is provided for data transmission on a TDD band and feedback on an FDD band.

[0198] The main features of this method are described below, such as Figure 6 As shown.

[0199] Scheduling via DCI on PDCCH This method utilizes a single DCI message sent on the PDCCH to schedule downlink data transmission and uplink control information (e.g., ACK / NACK). This combined scheduling offers several key advantages: Efficiency: By including both downlink and uplink scheduling information in a single DCI message, system signaling overhead is reduced and overall efficiency is improved; Synchronization: The scheduling information used for both types of transmissions is located in the same DCI, thereby ensuring proper synchronization between downlink data and uplink feedback.

[0200] Channel allocation PDCCH and PDSCH: The PDCCH, responsible for transmitting DCI messages, and the PDSCH, used for downlink data transmission, are both located on the same TDD frequency band. This co-location simplifies the coordination between scheduling information and the corresponding downlink data.

[0201] PUCCH: Used to transmit uplink control information (ACK / NACK), located on a separate FDD band. This distinct allocation allows for dedicated and timely transmission of uplink feedback, independent of downlink data traffic on the TDD band.

[0202] Several key aspects contribute to the functionality of this design: Scheduling granularity: Figure 6 The sub-blocks shown can represent various time-domain transmission units, depending on the required scheduling granularity. These units can be time slots, orthogonal frequency-division multiplexing (OFDM) symbols, or other related time divisions.

[0203] Pre-configuration via RRC: Specific TDD bands, FDD bands, and carrier configurations (e.g., bandwidth part (BWP)) are predefined via RRC signaling. This pre-configuration establishes an overall framework for resource allocation.

[0204] Timing offset interpretation: In scenarios where PDCCH schedules PUCCH transmission on carriers with different parameter sets (subcarrier spacing) than the PDCCH itself, any timing offset specified in the scheduling allocation is interpreted relative to the PUCCH parameter set to ensure correct synchronization.

[0205] It should be noted that PDCCH corresponds to the control resource set (CORESET), which means that the PDCCH carrying DCI is mapped to the resources of CORESET.

[0206] Figure 7A schematic diagram of a second example of an implementation of this application is shown. The second physical resource is associated with a second TDD band and a third TDD band, and control information is received on the second TDD band. Although not shown, control information may also be received on the third TDD band. For example: In another possible implementation, such as Figure 7 As shown, a method is provided for transmitting data on multiple TDD frequency bands and providing feedback on one FDD frequency band.

[0207] Two features can be used to enhance flexibility and improve resource utilization: Downlink carrier aggregation (CA): Downlink transmission utilizes carrier aggregation, enabling the simultaneous use of multiple TDD frequency bands. This method maximizes spectral efficiency by utilizing available resources across different frequency bands.

[0208] Multiplexing uplink feedback: A single PUCCH on an FDD band can be associated with transmissions on multiple PDSCHs across various TDD bands. This UCI multiplexing capability enables efficient uplink feedback even in scenarios involving downlink transmissions across multiple TDD bands.

[0209] Optionally, additional design considerations are described below: Enhanced DCI Resource Allocation Information: DCI messages have been expanded to carry more granular time and frequency resource allocation information. Specifically, DCI now includes at least three sets of fields: two dedicated to PDSCH resource allocation for each used TDD band, and one set for PUCCH resource allocation. This expansion supports precise scheduling of downlink transmissions across multiple TDD bands.

[0210] Codeword mapping and multiplexing: During codeword mapping, a single codeword (transport block (TB) or code block group (CBG)) can be mapped to a single TDD band or simultaneously to multiple TDD bands. This flexibility helps to utilize resources efficiently.

[0211] Multiplexing Uplink Feedback Using Band Identifiers: In scenarios where a single TB is mapped to only one TDD band, multiple TBs from different TDD bands may be decoded simultaneously. To address this, the system needs a mechanism to multiplex corresponding uplink feedback messages on the PUCCH. Each feedback message should include a flag identifying the specific TDD band PDSCH transmission it acknowledges. If dedicated feedback opportunities are reserved for TBs mapped across multiple TDD bands, these flags can be embedded in the UCI payload.

[0212] Figure 8 A schematic diagram of a third example provided by the implementation of this application is shown. The second physical resource is associated with a second FDD frequency band, and control information is received on the second FDD frequency band. For example: In another possible implementation, such as Figure 8 As shown, a method is provided for transmitting data on one FDD band and providing feedback on another FDD band.

[0213] This method utilizes a single DCI message sent on the PDCCH to schedule downlink data transmission on the PDSCH and uplink control information (specifically ACK / NACK) on the PUCCH. It's important to note that the PDCCH and PDSCH reside on the same FDD band, which facilitates coordinated scheduling and transmission. Conversely, the PUCCH occupies a separate FDD band, allowing uplink feedback to be sent dedicatedly and promptly, independent of downlink data traffic. Allocating the PUCCH to a separate FDD band ensures timely and reliable transmission of uplink control information even in scenarios with downlink traffic congestion on the PDSCH.

[0214] Figure 9 A schematic diagram of a fourth example provided by the implementation of this application is shown. The second physical resource is associated with a fourth TDD band and a third FDD band, and control information is received on the fourth TDD band. For example: In another possible implementation, such as Figure 9 As shown, a method is provided for transmitting data on multiple TDD and FDD frequency bands and providing feedback on a single FDD frequency band.

[0215] In this method, two features can be used to improve resource utilization and enhance flexibility: Downlink carrier aggregation: Downlink transmission utilizes carrier aggregation, enabling the simultaneous use of multiple TDD bands. Furthermore, the system can combine FDD bands for downlink transmission, further enhancing spectrum utilization flexibility. This combination approach maximizes spectrum efficiency by utilizing available resources across different frequency bands.

[0216] Multiplexing uplink feedback on a single FDD PUCCH: A single PUCCH on an FDD band can be associated with transmissions on multiple PDSCHs across various TDD and FDD bands. This multiplexing capability enables efficient uplink feedback even in scenarios involving downlink transmissions over a combination of TDD and FDD bands.

[0217] DCI fields used to indicate feedback timing and carrier index: The "Feedback band / carrier indicator" is used to specify the uplink feedback frequency resources. Because the feedback may occur on different frequency bands / carriers, it needs to be specified as a HARQ-related field in the DCI; FDD band and / or TDD band.

[0218] The above text combines Figures 6 to 9 The method according to embodiments of this application is described in detail below. (Followed by...) Figure 10 and Figure 11 The apparatus provided in the embodiments of this application will be described in detail. The description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, any content not described in detail can be referred to the above method embodiments. For the sake of brevity, it will not be repeated here.

[0219] refer to Figure 10 The diagram illustrates a schematic block diagram of a communication device according to an embodiment of this application. The communication device 10 includes a transceiver unit 11 and a processing unit 12. The transceiver unit 11 can implement corresponding communication functions, and the processing unit 11 is used to perform data processing. The transceiver unit 11 can also be referred to as a communication interface or a communication unit.

[0220] In some implementations, the communication device 10 may further include a storage unit. The storage unit may be used to store instructions and / or data. The processing unit 12 may read the instructions and / or data from the storage unit to enable the communication device to implement the method embodiments described above.

[0221] The communication device 10 can be used to perform actions performed by the UE in the above method embodiments. In this case, the communication device 10 can be the UE or a component that can be configured in the UE. The transceiver unit 11 is used to perform communication-related (e.g., transceiver-related) operations on the UE side in the above method embodiments. The processing unit 12 is used to perform processing-related operations on the UE side in the above method embodiments.

[0222] Communication device 10 can implement the embodiments of this application. Figures 6 to 9 The steps or procedures performed by the UE. The communication device 10 may include steps or procedures for performing... Figures 6 to 9 The unit is the one that executes the method by the UE. Furthermore, the units in the communication device 10 and the other operations and / or functions described above are respectively used to implement... Figures 6 to 9 The corresponding process in the text.

[0223] Alternatively, the communication device 10 can be used to perform the actions performed by the BS in the above method embodiments. In this case, the communication device 10 can be the BS or a component that can be configured in the BS. The transceiver unit 11 is used to perform communication-related (e.g., transceiver-related) operations on the BS side in the above method embodiments. The processing unit 12 is used to perform processing-related operations on the BS side in the above method embodiments.

[0224] Communication device 10 can implement the embodiments of this application. Figures 6 to 9 The steps or processes performed by the BS. Communication device 10 may include methods for performing... Figures 6 to 9 The unit is the one that executes the method by the BS. Furthermore, the units in the communication device 10 and the other operations and / or functions described above are respectively used to implement... Figures 10 to 1 The corresponding process in 5.

[0225] The specific process of the unit performing the corresponding steps described above has been explained in detail in the above method embodiments. For the sake of brevity, it will not be repeated here.

[0226] refer to Figure 11 The diagram illustrates a schematic block diagram of another communication device according to an embodiment of this application. The communication device 20 includes a processor 21. The processor 21 is coupled to a memory 22. The memory 22 is used to store computer programs or instructions and / or data. The processor 21 is used to execute the computer programs or instructions and / or data stored in the memory 22 to perform the methods described in the above method embodiments.

[0227] In some embodiments, the communication device 20 includes one or more processors 21.

[0228] In one example, such as Figure 11 As shown, the communication device 20 may also include a memory 22.

[0229] In some embodiments, the communication device 20 may include one or more memories 22.

[0230] In one example, memory 22 may be integrated with processor 21 or may be set up separately from processor 21.

[0231] In one example, such as Figure 11 As shown, the communication device 20 may further include a transceiver 23, wherein the transceiver 23 is used to receive and / or transmit signals. For example, the processor 21 may be used to control the transceiver 23 to receive and / or transmit signals.

[0232] In some embodiments, the communication device 20 may be a UE or a component (e.g., a chip, circuit, or processing system) that can be configured in the UE; or, the communication device 20 may be a BS or a component (e.g., a chip, circuit, or processing system) that can be configured in the BS.

[0233] In one embodiment, the communication device 20 is used to perform the operations performed by the UE in the above method embodiments.

[0234] For example, processor 21 can be used to perform processing-related operations performed by the UE in the above method embodiments, and transceiver 23 can be used to perform communication-related (e.g., transmission-reception related) operations performed by the UE in the above method embodiments.

[0235] In another embodiment, the communication device 20 is used to perform the operations performed by the BS in the above method embodiment.

[0236] For example, processor 21 can be used to perform processing-related operations performed by the BS in the above method embodiments, and transceiver 23 can be used to perform communication-related (e.g., send / receive related) operations performed by the BS in the above method embodiments.

[0237] In some aspects of the invention, a device / chipset system is provided, including components (e.g., at least one processor) for implementing a method implemented by a UE (or implemented at the UE) of the invention. The device / chipset system may be a UE (i.e., a terminal device) or a module / component within the UE. Specifically, the at least one processor may execute instructions stored in a computer-readable medium to implement the method.

[0238] In some aspects of the invention, a device / chipset system is provided, including components (e.g., at least one processor) for implementing a method implemented by a BS (e.g., a satellite) of the present invention (or implemented at the BS (e.g., a satellite)). The device / chipset system may be a BS or a module / component within a BS. Specifically, the at least one processor may execute instructions stored in a computer-readable medium to implement the method.

[0239] In some aspects of the invention, a system is provided, comprising at least one of a device in (or at the UE) of the invention or a device in (or at the BS) of the invention.

[0240] In some aspects of the invention, a method is provided performed by a system comprising at least one of means in (or at) the UE of the invention and means in (or at) the BS of the invention.

[0241] In some aspects of the invention, a computer program comprising instructions is provided. When executed by a processor, the instructions enable the processor to implement the method of the invention.

[0242] This application also provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions for implementing the methods executed by the UE or the BS in the above method embodiments.

[0243] For example, when a computer program is executed by a computer, it can enable the computer to implement the method executed by the UE or the method executed by the BS in the above method embodiments.

[0244] In some aspects of the invention, a method is provided performed by a system comprising at least one of means in (or at the UE) of the invention and means in (or at the network device) of the invention.

[0245] In some aspects of the invention, a computer program comprising instructions is provided. When executed by a processor, the instructions enable the processor to implement the method of the invention.

[0246] In some aspects of the invention, a non-transitory computer-readable medium is provided that stores instructions which, when executed by a processor, enable the processor to implement the method of the invention.

[0247] The explanations and benefits of any of the communication devices provided above can be found in the corresponding method embodiments provided above. Further details will not be repeated here.

[0248] In some aspects of the invention, a device / chipset system is provided, including components (e.g., at least one processor) for implementing a method implemented by a UE (or implemented at the UE) of the invention. The device / chipset system may be a UE (i.e., a terminal device) or a module / component within the UE. Specifically, the at least one processor may execute instructions stored in a computer-readable medium to implement the method.

[0249] In some aspects of the invention, an apparatus / chipset system is provided, including components (e.g., at least one processor) for implementing a method implemented by (or at the location of) a network device (e.g., a base station) of the invention. The apparatus / chipset system may be a network device or a module / component within a network device. Specifically, at least one processor may execute instructions stored in a computer-readable medium to implement the method. In some aspects of the invention, a system is provided, including at least one of a device in (or at the location of) a UE of the invention or a device in (or at the location of) a network device of the invention.

[0250] The solutions described in this invention are applicable to advanced (or future) networks or traditional (e.g., 5G, 4G, 3G, or 2G) networks.

[0251] It is understood that any module, component, or device that executes instructions disclosed herein may include or otherwise access one or more non-transitory computer / processor-readable storage media to store information, such as computer / processor-readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer / processor-readable storage media includes magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, compact disc read-only memory (CD-ROM), digital video disc or digital versatile disc (DVD), Blu-ray Disc™ and other optical discs, volatile and non-volatile, removable and non-removable media implemented in any method or technology, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other storage technologies. Any of these non-transitory computer / processor-readable storage media may be part of a device / apparatus or may be accessed or connected to a device. Computer / processor-readable / executable instructions used to implement the methods, applications, or modules described herein may be stored by such non-transitory computer / processor-readable storage media or otherwise preserved.

[0252] It should be noted that the message in this invention can be replaced with information, which can be carried in a single message or in more than one single message.

[0253] Unless otherwise specified, the terms “apparatus” and “equipment” are used interchangeably, as are the terms “identifier” and “identifier”.

[0254] In this invention, when used in conjunction with the terms "comprising" or "including" in the claims and / or specification, the word "a" or "an" may refer to "one," but it also has the same meaning as "one or more," "at least one," and "one or more," unless explicitly stated otherwise. Similarly, the word "another" may refer to at least a second or more, unless explicitly stated otherwise.

[0255] In this invention, when used before the same term (e.g., UE or operation step), the words "first," "second," etc., do not imply an order or sequence of the terms. For example, unless otherwise specified, "first UE" and "second UE" refer to two different UEs; similarly, unless otherwise specified, "first step" and "second step" refer to two different operation steps, but this does not mean that the first step must occur before the second step. The actual order depends on the logic of the two steps.

[0256] The terms “coupling” or “connection” as used herein can have several different meanings depending on the context in which they are used. For example, the terms “coupling” or “connection” as used herein can indicate that two elements or devices are directly connected to each other or connected to each other via mechanical elements through one or more intermediate elements or devices, depending on the specific context.

[0257] It should be noted that, as used herein, the expression "at least one of A or B" is interchangeable with the expression "A and / or B". It refers to a list in which A, or B, or both A and B can be selected. Similarly, as used herein, "at least one of A, B, or C" is interchangeable with "A and / or B and / or C" or "A, B, and / or C". It refers to a list in which: A or B or C, or both A and B, or both A and C, or both B and C, or all of A, B, and C. The same principle applies to longer lists with the same format.

[0258] This invention includes various implementations, including not only method implementations but also apparatus implementations and other implementations related to non-transitory computer-readable storage media. Implementations may be combined individually or in combination with the features disclosed herein.

[0259] The terms “receive,” “detect,” and “decode” as used herein can have several different meanings depending on the context in which they are used. For example, without specific indication, the term “receive” can indicate that information (e.g., DCI, MAC-CE, RRC signaling, or TB) has been successfully received by the receiving node, meaning that the receiving side correctly detected and decoded the information. In this scenario, “receive” can include both “detect” and “decode,” or it can mean the same thing; for example, “receive paging” means that the paging was correctly decoded and successfully obtained, and correspondingly, “received paging” means that the receiving side did not detect and / or decode the paging. “Not received paging” means that the receiving side attempted to detect and / or decode the paging but was unsuccessful in obtaining it. The term “receive” can sometimes indicate that a signal has arrived at the receiving side, but this does not necessarily mean that the information in the signal has been correctly detected and decoded. In this case, the receiving side needs to detect and decode the signal to obtain the information carried in it. In this scenario, “receive,” “detect,” and “decode” can represent different processes by which the receiving side obtains the information.

[0260] Although this invention refers to illustrative implementations, it is not intended to be interpreted in a limiting sense. Various modifications and combinations of the illustrative implementations, as well as other implementations of the invention, will be apparent to those skilled in the art upon reference to this specification. When two or more implementations are combined, not all features of the implementations to be combined are necessary for the combination.

[0261] Features disclosed herein in the context of any particular implementation may also be implemented, or alternatively, in other implementations. For example, method implementations may also be implemented, or alternatively, in apparatus, system, and / or computer program product implementations. Furthermore, while implementations are described primarily in the context of methods and apparatuses, other implementations are also contemplated, for example, as instructions stored in one or more non-transitory computer-readable media. These media may store programs or instructions for performing any of the various methods consistent with the present invention.

Claims

1. A communication method, characterized in that, include: Receive control information, wherein the control information indicates a first physical resource for feedback information, the first physical resource being associated with a first frequency division duplex (FDD) band; The feedback information is sent on the first FDD frequency band.

2. The method according to claim 1, characterized in that, The control information also indicates a second physical resource for downlink data.

3. The method according to claim 2, characterized in that, The second physical resource is associated with one or more frequency bands, which include one or more of the following: at least one FDD frequency band and at least one time-division duplex (TDD) frequency band.

4. The method according to claim 3, characterized in that, The control information is received on one or more frequency bands.

5. The method according to any one of claims 1 to 4, characterized in that, The feedback information indicates whether some or all of the downlink data was successfully received or not, wherein the downlink data is associated with at least one frequency band.

6. The method according to claim 5, characterized in that, The downlink data is associated with multiple frequency bands, and the feedback information also indicates one or more corresponding frequency bands associated with some or all of the downlink data.

7. The method according to any one of claims 3 to 6, characterized in that, The second physical resource is associated with the first TDD band, and the control information is received on the first TDD band.

8. The method according to any one of claims 3 to 6, characterized in that, The second physical resource is associated with a second TDD band and a third TDD band, and the control information is received on the second TDD band or the third TDD band.

9. The method according to any one of claims 3 to 6, characterized in that, The second physical resource is associated with a second FDD band, and the control information is received on the second FDD band.

10. The method according to any one of claims 3 to 6, characterized in that, The second physical resource is associated with the fourth TDD band and the third FDD band, and the control information is received on the fourth TDD band.

11. The method according to any one of claims 1 to 10, characterized in that, The control information includes timing information of the feedback information, which is associated with one or more of the following: a set of parameters associated with the first FDD band, and a set of parameters associated with the band receiving the control information.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: Receive configuration information, wherein the configuration information indicates a resource set including the first physical resource.

13. The method according to any one of claims 1 to 12, characterized in that, The feedback information includes ACK or NACK; and / or the feedback information includes Channel State Information (CSI).

14. The method according to any one of claims 1 to 13, characterized in that, The control information is downlink control information (DCI).

15. The method according to any one of claims 2 to 14, characterized in that, The downlink data is carried in at least one Physical Downlink Shared Channel (PDSCH).

16. A communication method, characterized in that, include: Send control information, wherein the control information indicates a first physical resource for feedback information, the first physical resource being associated with a first frequency division duplex (FDD) band; The feedback information is received on the first FDD band.

17. The method according to claim 16, characterized in that, The control information also indicates a second physical resource for downlink data.

18. The method according to claim 17, characterized in that, The second physical resource is associated with one or more frequency bands, which include one or more of the following: at least one FDD frequency band and at least one time-division duplex (TDD) frequency band.

19. The method according to claim 18, characterized in that, The control information is transmitted on one or more frequency bands.

20. The method according to any one of claims 16 to 19, characterized in that, The feedback information indicates whether some or all of the downlink data was successfully received or not, wherein the downlink data is associated with at least one frequency band.

21. The method according to claim 20, characterized in that, The downlink data is associated with multiple frequency bands, and the feedback information also indicates one or more corresponding frequency bands associated with some or all of the downlink data.

22. The method according to any one of claims 18 to 21, characterized in that, The second physical resource is associated with the first TDD band, and the control information is transmitted on the first TDD band.

23. The method according to any one of claims 18 to 21, characterized in that, The second physical resource is associated with a second TDD band and a third TDD band, and the control information is transmitted on the second TDD band or the third TDD band.

24. The method according to any one of claims 18 to 21, characterized in that, The second physical resource is associated with a second FDD frequency band, and the control information is transmitted on the second FDD frequency band.

25. The method according to any one of claims 18 to 21, characterized in that, The second physical resource is associated with the fourth TDD band and the third FDD band, and the control information is transmitted on the fourth TDD band.

26. The method according to any one of claims 16 to 25, characterized in that, The control information includes timing information of the feedback information, which is associated with one or more of the following: a set of parameters associated with the first FDD band, and a set of parameters associated with the band through which the control information is transmitted.

27. The method according to any one of claims 16 to 26, characterized in that, The method further includes: Send configuration information, wherein the configuration information indicates a resource set including the first physical resource.

28. The method according to any one of claims 16 to 27, characterized in that, The feedback information includes ACK or NACK; and / or the feedback information includes Channel State Information (CSI).

29. The method according to any one of claims 16 to 28, characterized in that, The control information is the downlink control information (DCI).

30. The method according to any one of claims 17 to 29, characterized in that, The downlink data is carried in at least one Physical Downlink Shared Channel (PDSCH).

31. A communication device, characterized in that, Used to perform the method according to any one of claims 1 to 15 or the method according to any one of claims 16 to 30.

32. The communication device according to claim 31, characterized in that, include: A receiving unit is configured to receive control information, wherein the control information indicates a first physical resource for feedback information, and the first physical resource is associated with a first frequency division duplex (FDD) frequency band; The transmitting unit is used to transmit the feedback information on the first FDD frequency band.

33. The communication device according to claim 31, characterized in that, include: A transmitting unit is configured to transmit control information, wherein the control information indicates a first physical resource for feedback information, the first physical resource being associated with a first frequency division duplex (FDD) frequency band; The receiving unit is configured to receive the feedback information on the first FDD frequency band.

34. The communication device according to claim 31, characterized in that, include: One or more processors are configured to perform the processing steps according to any one of claims 1 to 15 or the processing steps according to any one of claims 16 to 30; An interface circuit for performing the transmission or reception steps according to any one of claims 1 to 15 or any one of claims 16 to 30.

35. The communication device according to claim 34, characterized in that, The interface circuit includes one or more transceivers.

36. An apparatus, characterized in that, include: One or more processors; The memory stores instructions that, when executed by the one or more processors, cause the apparatus to perform the method according to any one of claims 1 to 15 or the method according to any one of claims 16 to 30.

37. A communication system, characterized in that, The communication system includes a first communication device for performing the method according to any one of claims 1 to 15 and a second communication device for performing the method according to any one of claims 16 to 30.

38. A computer-readable storage medium, characterized in that, The device stores instructions that, when executed by the device, cause the device to perform the method according to any one of claims 1 to 15 or the method according to any one of claims 16 to 30.

39. A computer program product, characterized in that, It has instructions that, when executed, cause the apparatus to perform the method according to any one of claims 1 to 15 or the method according to any one of claims 16 to 30.