Methods, apparatus and systems for flexible scheduling

By introducing a flexible scheduling scheme that supports scheduling units with variable scheduling granularity, the problem of inflexible resource scheduling in wireless communication systems is solved, thereby improving system performance and communication efficiency.

CN123125995APending Publication Date: 2026-11-17HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090254.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-03-28
Filing Date
2024-05-30
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing wireless communication systems struggle to achieve flexible resource scheduling on data channels, resulting in insufficient system performance robustness.

Method used

By introducing a flexible scheduling scheme, supporting variable and configurable scheduling granularity, and using scheduling units (SU) to represent resource scheduling, it adapts to different application types and system parameters, reduces transmission latency, and improves system throughput.

Benefits of technology

It achieves efficient use of resources and improved system performance, reduces signal overhead, and improves communication efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125995A_ABST
    Figure CN123125995A_ABST
Patent Text Reader

Abstract

This application relates to communication methods and communication apparatus. An example method includes: receiving scheduling granularity information indicating the number of symbols in at least one scheduling unit (SU) for resource scheduling for communication between user equipment (UE) and network equipment; and communicating with the network equipment based on at least one SU.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 571,092, filed March 28, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to wireless communications. In particular, this disclosure relates to a method, apparatus, and system for flexible scheduling. Background Technology

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

[0005] In wireless communication, for data channels, a hybrid automatic repeat request (HARQ) process is implemented to support the retransmission of the same data as well as a hybrid combination of the original transmission and retransmission of the same data, thereby offsetting channel impairments and improving the robustness of system performance.

[0006] The purpose of providing this background information is to disclose information that the applicant believes may be relevant to this disclosure. It is not necessarily intended to acknowledge, nor should any of the foregoing information be construed as prior art to this disclosure.

[0007] The following will describe specific example embodiments of this disclosure. Summary of the Invention

[0008] One or more implementations of this application provide a communication method and a communication apparatus. The techniques described in this application can improve scheduling flexibility.

[0009] According to a first aspect, a method is provided. The method can be executed on a user equipment (UE) side. The method includes: receiving scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one scheduling unit (SU) for resource scheduling for communication with a network device; and communicating with the network device based on the at least one SU.

[0010] In conjunction with the first aspect, in some implementations, the at least one SU includes multiple SUs, and the scheduling granularity information indicates that one of the multiple SUs is the default SU.

[0011] In conjunction with the first aspect, in some implementations, the at least one SU includes multiple SUs, each SU corresponding to one of the multiple system parameters (numerology).

[0012] In conjunction with the first aspect, in some implementations, the scheduling granularity information indicates that the number of symbols in the first SU corresponding to the first system parameter is the same as the number of symbols in the second SU corresponding to the second system parameter, wherein the first SU and the second SU belong to the plurality of SUs, and the first system parameter and the second system parameter belong to the plurality of system parameters.

[0013] In conjunction with the first aspect, in some implementations, the scheduling granularity information indicates that the number of symbols in the first SU corresponding to the first system parameter is different from the number of symbols in the second SU corresponding to the second system parameter, wherein the first SU and the second SU belong to the plurality of SUs, and the first system parameter and the second system parameter belong to the plurality of system parameters.

[0014] In conjunction with the first aspect, in some implementations, the scheduling granularity information includes one or more of radio resource control (RRC) messages, media access control-control element (MAC-CE) messages, or downlink control information (DCI).

[0015] In conjunction with the first aspect, in some implementations, the number of symbols in the at least one SU is 3, 6, 7, 12, 14, 24, 28 or 48.

[0016] In conjunction with the first aspect, in some implementations, the method further includes: receiving information indicating the location of the physical downlink control channel (PDCCH) based on the alignment point in the frame or the subframe.

[0017] In conjunction with the first aspect, in some implementations, the alignment point is configured based on one or more of a frame, subframe, time slot, or symbol; the time position of the alignment point differs from the start time or boundary of any of the frame, subframe, or time slot.

[0018] In conjunction with the first aspect, in some implementations, the method further includes: receiving downlink control information (DCI) in the PDCCH, wherein the DCI includes time offset information indicating the time offset of the scheduled resource relative to the alignment point.

[0019] In conjunction with the first aspect, in some implementations, the method further includes: receiving downlink control information (DCI) in the PDCCH, wherein the DCI includes time offset information indicating the time offset of the scheduled resource relative to the position of the PDCCH.

[0020] In conjunction with the first aspect, in some implementations, the method further includes: receiving downlink control information (DCI), wherein the DCI includes a start and length indicator value (SLIV) field for determining the location of a scheduled resource, the SLIV field indicating the starting symbol index (S) and the number of consecutive symbols (L) within a SU, the SU being one of the at least one SUs.

[0021] In conjunction with the first aspect, in some implementations, the SLIV field includes an index indicating one of the combinations of total quantities (S, L).

[0022] In conjunction with the first aspect, in some implementations, the SLIV field includes an index indicating a subset of combinations of total quantities (S, L).

[0023] In conjunction with the first aspect, in some implementations, the method further includes: receiving downlink control information (DCI), the DCI including a time allocation index indicating a combination of (k, S, L) combinations, where k represents the time offset, S represents the starting symbol index, and L represents the number of consecutive symbols of the scheduled resource. It should be noted that S and L in the (k, S, L) combination refer to the time resource having the SU; furthermore, the DCI includes resource scheduling for one or more (individual) time allocations. This description also applies to the paragraphs below describing the relevant DCI and scheduling.

[0024] In conjunction with the first aspect, in some implementations, the method further includes: receiving information indicating one of the at least one SUs to receive DCI in the PDCCH.

[0025] According to a second aspect, a method is provided. The method can be performed at a network device. The method includes: sending scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one scheduling unit (SU) for resource scheduling for communication with user equipment (UE); and communicating with the UE based on the at least one SU.

[0026] In conjunction with the second aspect, in some implementations, the at least one SU includes multiple SUs, and the scheduling granularity information indicates that one of the multiple SUs is the default SU.

[0027] In conjunction with the second aspect, in some implementations, the at least one SU includes multiple SUs, each SU corresponding to one of the multiple system parameters.

[0028] In conjunction with the second aspect, in some implementations, the scheduling granularity information indicates that the number of symbols in the first SU corresponding to the first system parameter is the same as the number of symbols in the second SU corresponding to the second system parameter, wherein the first SU and the second SU belong to the plurality of SUs, and the first system parameter and the second system parameter belong to the plurality of system parameters.

[0029] In conjunction with the second aspect, in some implementations, the scheduling granularity information indicates that the number of symbols in the first SU corresponding to the first system parameter is different from the number of symbols in the second SU corresponding to the second system parameter, wherein the first SU and the second SU belong to the plurality of SUs, and the first system parameter and the second system parameter belong to the plurality of system parameters.

[0030] In conjunction with the second aspect, in some implementations, the scheduling granularity information includes one or more of radio resource control (RRC) messages, media access control-control element (MAC-CE) messages, or downlink control information (DCI).

[0031] In conjunction with the second aspect, in some implementations, the number of symbols in the at least one SU is 3, 6, 7, 12, 14, 24, 28 or 48.

[0032] In conjunction with the second aspect, in some implementations, the method further includes: sending alignment point information, the alignment point information indicating an alignment point used to determine the position of the physical downlink control channel (PDCCH) in a subframe.

[0033] In conjunction with the second aspect, in some implementations, the alignment point is configured based on one or more of a frame, subframe, time slot, or symbol; the temporal position of the alignment point differs from the start time or boundary of any of the frame, subframe, or time slot.

[0034] In conjunction with the second aspect, in some implementations, the method further includes: sending downlink control information (DCI) in the PDCCH, wherein the DCI includes time offset information indicating the time offset of the scheduled resource relative to the alignment point.

[0035] In conjunction with the second aspect, in some implementations, the method further includes: sending downlink control information (DCI) in the PDCCH, wherein the DCI includes time offset information indicating the time offset of the scheduled resource relative to the position of the PDCCH.

[0036] In conjunction with the second aspect, in some implementations, the method further includes: sending downlink control information (DCI), wherein the DCI includes a start and length indicator value (SLIV) field for determining the location of a scheduled resource, the SLIV field indicating the starting symbol index (S) and the number of consecutive symbols (L) within a SU, the SU being one of the at least one SU.

[0037] In conjunction with the second aspect, in some implementations, the SLIV field includes an index indicating one of the combinations of total quantities (S, L).

[0038] In conjunction with the second aspect, in some implementations, the SLIV field includes an index indicating a subset of combinations of total quantities (S, L).

[0039] In conjunction with the second aspect, in some implementations, the method further includes: sending downlink control information (DCI), the DCI including a time allocation index of one of a combination of indicators (k, S, L), where k represents the time offset, S represents the starting symbol index, and L represents the number of consecutive symbols of the scheduled resources.

[0040] In conjunction with the second aspect, in some implementations, the method further includes: sending information instructing one of the at least one SUs to send DCI in the PDCCH.

[0041] According to a third aspect, a communication device is provided. The communication device is used to perform the method according to the first aspect or one or more implementations of the first aspect, or the method according to the second aspect or one or more implementations of the second aspect.

[0042] In conjunction with the third aspect, in some implementations, the communication device includes: a receiving unit for receiving scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one resource scheduling unit (SU) for communication between the communication device and the network device; and a communication unit for communicating with the network device based on the at least one SU.

[0043] In conjunction with the third aspect, in some implementations, the communication device includes: a transmitting unit for transmitting scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one resource scheduling unit (SU) for communication between the user equipment (UE) and the communication device; and a communication unit for communicating with the UE based on the at least one SU.

[0044] In conjunction with the third aspect, in some implementations, the communication device includes: one or more processors; and interface circuitry for: receiving scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one resource scheduling unit (SU) for communication between the communication device and the network device; and communicating with the network device based on the at least one SU.

[0045] In conjunction with the third aspect, in some implementations, the communication device includes: one or more processors; and interface circuitry for: transmitting scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one resource scheduling unit (SU) for communication between the user equipment (UE) and the communication device; and communicating with the UE based on the at least one SU.

[0046] In conjunction with the third aspect, in some implementations, the interface circuitry includes one or more transceivers.

[0047] According to a fourth aspect, an apparatus is provided. The apparatus includes one or more processors and one or more memories. The one or more memories store instructions that, when executed by the one or more processors, cause the apparatus to perform the method according to the first aspect or one or more implementations of the first aspect, or the method according to the second aspect or one or more implementations of the second aspect.

[0048] According to a fifth aspect, a communication system is provided. The communication system includes a first communication device for performing the method according to the first aspect or one or more implementations thereof. The communication system further includes a second communication device for performing the method according to a second aspect or one or more implementations thereof.

[0049] According to a sixth aspect, a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage has instructions stored thereon that, when executed by a device, cause the device to perform the method according to the first aspect or one or more implementations of the first aspect, or the method according to the second aspect or one or more implementations of the second aspect. Attached Figure Description

[0050] Figure 1 A schematic diagram of an exemplary communication system is shown;

[0051] Figure 2 Another exemplary communication system is shown;

[0052] Figure 3 An example of a device for wireless communication with at least one of two devices in a communication system is shown;

[0053] Figure 4 Examples of units or modules in a device or apparatus are shown;

[0054] Figure 5 An exemplary flexible scheduling scheme is shown;

[0055] Figure 6 An exemplary flexible scheduling scheme with time-domain resource allocation indication is shown;

[0056] Figure 7 An exemplary table is shown for a set of time resource allocation indications for a normal cyclic prefix (NCP);

[0057] Figure 8A set of exemplary tables are shown for time resource allocation indications for extended cyclic prefixes (ECPs);

[0058] Figure 9 Another exemplary flexible scheduling scheme with time-domain resource allocation indication is shown;

[0059] Figure 10 An exemplary table is shown for a set of physical downlink shared channel (PDSCH) time resource allocation indications for NCP;

[0060] Figure 11 An exemplary table is shown for a set of physical uplink shared channel (PUSCH) time resource allocation indications for NCP;

[0061] Figure 12 A flowchart illustrating an exemplary communication method for flexible scheduling is shown;

[0062] Figure 13 An exemplary table is shown, which has a scheduling granularity index for multiple scheduling units (SUs) corresponding to multiple system parameters. Detailed Implementation

[0063] Wireless communication systems such as fourth-generation (4G) systems (e.g., Long-Term Evolution (LTE) systems), fifth-generation (5G) systems (e.g., New Radio (NR) systems), and sixth-generation (6G) systems can provide a wide range of applications (e.g., messaging, voice, video, and other data) and various service types, use cases, and / or system parameter options. Flexible scheduling schemes are described in contrast to fixed, slot-based scheduling (where the scheduling granularity is slots with a fixed number (14) scheduling symbols). For example, by supporting resource scheduling across slot boundaries, flexible scheduling schemes can facilitate the flexible and efficient use of time-frequency resources for wireless communication.

[0064] In some implementations, flexible scheduling schemes support variable and configurable scheduling granularity (e.g., represented by scheduling units (SUs)). A SU can be represented or defined by multiple scheduled symbols (e.g., orthogonal frequency-division multiplexing (OFDM) symbols). In some implementations, a SU can be represented by another parameter or absolute time. In some implementations, multiple SUs can be configured with different numbers of symbols instead of a fixed number (14). In some implementations, one or more SUs can be selected to assign, allocate, or otherwise schedule one or more resources for a specific data transmission. In some implementations, one or more SUs can be selected, for example, based on application type, service type, use case, and / or system parameters, to suit the needs or attributes of a specific data transmission. In some implementations, flexible scheduling schemes can reduce transmission latency and increase system throughput by using one or more configurable SUs.

[0065] In some implementations, scheduling information or signaling (e.g., information indicating the location of a scheduled resource) can be configured based on a configurable scheduling granularity. For example, scheduling information may include a reference point (also called an alignment point) and / or a time-domain allocation of the scheduled resource. In some implementations, the format and size of the scheduling signaling can be designed according to the configurable scheduling granularity. In some implementations, techniques for reducing the number of bits required for scheduling signaling are described, which can reduce signaling overhead and improve communication efficiency.

[0066] refer to Figure 1As a non-limiting illustrative example, a simplified schematic diagram of a communication system is provided. Communication system 100 (which may be a wireless system) includes a radio access network (RAN) 120. The RAN 120 may be a next-generation (e.g., sixth-generation, 6G, or later) RAN or a traditional (e.g., 5G, 4G, 3G, or second-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 interconnect with each other or be connected to one or more network nodes (170a and 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.

[0067] 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 via broadcast, multicast, ensemble, unicast, etc. Furthermore, 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). These services and / or applications can be mobile broadband (MBB) services, ultra-reliable low-latency communication (URLLC) services, or machine-type communication (MTC) services.

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

[0069] Figure 2A more detailed example of communication system 100 is shown. 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 non-terrestrial communication systems (or components thereof) into terrestrial communication systems can form a heterogeneous network that can be considered as having multiple layers. Heterogeneous networks can achieve better overall performance through efficient multi-link joint operation between terrestrial and non-terrestrial networks, more flexible function sharing, and faster physical layer link switching.

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

[0071] 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 are generally referred to as terrestrial transmit and receive points (T-TRPs) 170a, 170b. In one implementation, non-terrestrial communication network 120c includes RAN nodes, such as access nodes (or base stations) 172, which are generally referred to as non-terrestrial transmit and receive points (NT-TRPs) 172. As can be inferred from the similarity of the reference numerals in the accompanying drawings, the non-terrestrial communication network 120c can be considered a radio access network that shares operational similarities with RANs 120a and 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, and the at least one corresponding terrestrial network device operates as a RAN node, which 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 communicating with the NTN device, and the RAN node communicates with the ED through both the NTN device and the NTN gateway. In some implementations, the NTN gateway and the RAN node may reside in the same device.

[0072] Alternatively or additionally, any ED 110 can be used to connect, access, or communicate with T-TRP 170a, 170b, and NT-TRP 172, the Internet 150, the core network 130, the PSTN 140, other networks 160, or any combination thereof. In some examples, ED 110a can communicate with T-TRP 170a via uplink (UL) and / or downlink (DL) transmissions through 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 communicate with NT-TRP 172 via non-terrestrial air interface 190c for uplink and / or downlink transmissions.

[0073] Air interfaces 190a and 190b can employ 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 utilize other higher-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.

[0074] 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 via a link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection for multicast transmission between a group of ED 110s and one or more NT-TRP 172s.

[0075] RANs 120a and 120b communicate with the 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 the core network 130, can communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by the core network 130, and may or may not use the same radio access technology as RANs 120a and / or RAN 120b. The core network 130 can also serve as a gateway access between (i) RANs 120a and 120b, and / or EDs 110a, 110b, and 110c 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 functions for communicating 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 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 a network of computers and / or subnets (internal networks) and incorporate 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 under various wireless access technologies and incorporating multiple transceivers required to support these technologies.

[0076] Furthermore, the communication system 100 may include a sensing agent (not shown) to manage 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).

[0077] Figure 3An example of a device 310 is shown in a communication system (e.g., communication system 100) that wirelessly communicates with at least one of two devices (e.g., device 320a and device 320b, referred to as device 320) according to one embodiment. Device 310 may be a UE (e.g., Figure 3 ED 110 in the example). Device 320a can be a terrestrial network device (e.g., such as ED 110). Figure 3 The T-TRP 170 shown), device 320b can be a non-terrestrial network device (e.g., such as...). Figure 3 (NT-TRP 172 shown). However, this is not a necessary condition. For example, according to this disclosure, device 320a can be NT-TRP, while device 320b can be T-TRP, and both devices 320a and 320b can be either T-TRP or NT-TRP. ED 110 is described below as an example of device 310, T-TRP 170 is described as an example of device 320a, and NT-TRP 172 is described as an example of device 320a. Although there is only one device 310, one device 320a, and one device 320b, 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), or by more than one T-TRP 170, or by more than one NT-TRP 172, or by one or more T-TRP 170 and one or more NT-TRP 172.

[0078] The ED 110 is used to connect people, objects, and machines. It can be widely used 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.

[0079] Each ED 110 represents any suitable end-user equipment used for wireless operation and may include (or may be referred to as, but is not limited to, the following devices): 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, smart book, vehicle, car, truck, bus, train, or IoT device, wearable device (e.g., watch, glasses, head-mounted device, etc.), industrial equipment, or devices that include or incorporate the above-mentioned devices (e.g., communication module, modem, or chip), etc. Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs and will be referred to as T-TRP 170 below. Similarly, Figure 3 As shown, the non-terrestrial (NT) device will be referred to as NT-TRP172 below. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically turned on (i.e., established, activated, or enabled), turned off (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connectivity availability or connectivity necessity.

[0080] 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. One, some, or all of the antennas 204 may alternatively be panels. The transmitter 201 and receiver 203 may, for example, 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 through at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or 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.

[0081] Memory 208 stores instructions. Memory 208 may also store data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein and executed by one or more processing units (e.g., processor 210). Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory can 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, and on-processor cache, etc.

[0082] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., connected to...). 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 network interface communication. Suitable structures include, for example, speakers, microphones, keypads, keyboards, displays, touch screens, etc.

[0083] Processor 210 performs (or controls ED 110 to perform) operations described herein as being performed by ED 110, as shown below and elsewhere in this disclosure. For example, processor 210 performs or controls ED 110 to perform the following operations: receive a transport block (TB), decode one TB from the received TB using resources, release resources to decode another TB from the received TB, and / or receive configuration information for configuring resources. Specifically, this operation may include: operations related to preparing to send an uplink transmission to NT-TRP 172 and / or T-TRP 170; operations related to processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170; and operations related to processing bidirectional sidelink transmissions with another ED 110. Processing operations related to preparing to send an uplink transmission may include operations such as encoding, modulation, transmission beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receiving beamforming, demodulating, and decoding received symbols. Processing operations related to downlink transmissions can include transmit / receive beamforming, modulation / demodulation, and symbol encoding / decoding. According to this embodiment, downlink transmissions can be received by receiver 203 using receive beamforming, and processor 210 can extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). Examples of signaling can be reference signals transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 210 implements 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 can 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. In some embodiments, processor 210 can perform channel estimation, for example, using reference signals received from NT-TRP 172 and / or T-TRP 170.

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

[0085] The processing components of processor 210, transmitter 201, and receiver 203 can each be implemented using one or more processors, which may be the same or different, to 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 can 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.

[0086] In some implementations, ED 110 may be a device (also called 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., the chip) to other devices (e.g., chips, memory, or buses). 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; while 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.

[0087] 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. One, some, or all of the antennas 256 may alternatively be panels. 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.

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

[0089] In some embodiments, the portions of T-TRP 170 may be distributed. For example, some modules of T-TRP 170 may be located at a remote location from the device housing the antenna 256 of T-TRP 170, and may be coupled to the device housing the antenna 256 via a communication link (not shown) sometimes referred to as a fronthaul (e.g., a common public radio interface (CPRI)). Therefore, in some embodiments, the term "T-TRP 170" may also refer to network-side modules 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 operating together to serve ED 110, for example, through cooperative multicast.

[0090] The operations performed by processor 260 include those related to: preparing to send downlink transmissions to ED 110, processing uplink transmissions received from ED 110, preparing to send return transmissions to T-TRP 170 and / or NT-TRP 172, and processing transmissions received from T-TRP 170 and / or NT-TRP 172 via return. Processing operations related to preparing to send downlink or return 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 return 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 an indication of beam direction (e.g., BAI), which scheduler 253 can schedule for transmission. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110, determining the deployment location of NT-TRP 172, etc. In some embodiments, processor 260 can 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.

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

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

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

[0094] The processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 can each be implemented using one or more processors, which are the same or different, to 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 can be implemented using dedicated circuitry, such as a programmed FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC.

[0095] 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 and 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) to other devices (e.g., chips, memory, or a bus). 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.

[0096] 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 telecommunications base stations and unmanned aerial vehicles. Additionally, in some implementations, the NT-TRP 172 may be referred to by other names, such as non-terrestrial node, non-terrestrial network device, or non-terrestrial base station.

[0097] 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. One, some, or all of the antennas 256 may alternatively be panels. 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.

[0098] 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. One, some, or all of these antennas may alternatively 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.

[0099] NT-TRP 172 includes a processor 276 for performing operations including: preparing to transmit downlink transmissions to ED 110, processing uplink transmissions received from ED 110, preparing to transmit backhaul transmissions to T-TRP 170 and / or another NT-TRP 172, and processing transmissions received from T-TRP 170 and / or another NT-TRP 172 via backhaul. Processing operations related to preparing to transmit downlink or backhaul transmissions 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 not higher-layer functions, such as those in the medium access control (MAC) layer or radio link control (RLC) layer. Since this is merely an example, more generally, NT-TRP 172 may implement higher-layer functions in addition to physical layer processing.

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

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

[0102] The processing components of processor 276, transmitter 272, and receiver 274 can each be implemented using one or more processors, which may be the same or different, to 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 can be implemented using dedicated circuitry, such as a programmed FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC. In some embodiments, NT-TRP 172 may actually be multiple NT-TRPs operating together to serve ED110, for example, through cooperative multicast.

[0103] When NT-TRP 172 is a device within a unit (e.g., a communication module, modem, chip, or chipset), it includes at least one processor and 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) to other devices (e.g., chips, memory, or a 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.

[0104] It should be noted that the term "transmit / receive point (TRP)" used in this document can refer to either T-TRP or NT-TRP. T-TRP can be alternatively referred to as terrestrial network TRP ("TNTRP"), and NT-TRP can be alternatively referred to as non-terrestrial network TRP ("NTNTRP"). T-TRP 170, NT-TRP 172, and / or ED 110 may include other components, but these components have been omitted for clarity.

[0105] It should be noted that, for simplicity, the term "signaling" used in this document can also 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 referred to as downlink control information (DCI) transmitted in the physical downlink control channel (PDCCH). For the uplink, physical layer signaling can be referred to as uplink control information (UCI) 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 referred to as sidelink control information (SCI) transmitted in the physical sidelink control channel (PSCCH). Signaling can be carried in higher-layer (e.g., above the physical layer) signaling, which is transmitted in physical layer data channels. For example, for downlink signaling, it is transmitted in the physical downlink shared channel (PDSCH); for uplink signaling, it is transmitted in the physical uplink shared channel (PUSCH); and for sidelink signaling, it is transmitted in the physical sidelink shared channel (PSSCH). Higher-layer signaling can also be referred to as static signaling or semi-static signaling. Higher-layer signaling can also 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.

[0106] It should be noted that in this disclosure, when "information" and "message" are different, they can be carried in a single message or in more than one single message.

[0107] according to Figure 4One or more steps of the methods provided herein may be performed by the corresponding unit or module. Figure 4 Units or modules in devices or apparatuses such as ED 110, T-TRP 170, or NT-TRP 172 are illustrated. For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by an artificial intelligence (AI) module or a machine learning (ML) module. The corresponding 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 these units or modules may be circuits, such as integrated circuits. For example, integrated circuits include programmed FPGAs, GPUs, or ASICs. For example, one or more of these units or modules may be logic devices, 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 these modules are implemented using software executed by a processor, etc., then these modules may be retrieved by the processor, wholly or partially, individually or collectively, for processing as needed, in single or multiple instances, and these modules themselves may include instructions for further deployment and instantiation.

[0108] Other details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted here.

[0109] This disclosure pertains to devices such as UEs, IoT devices, and automobiles. The envisioned network scenario types may include terrestrial TRPs (e.g., base stations) and / or non-terrestrial TRPs (e.g., drones, balloons, high-altitude platform stations (HAPS), satellites), as well as any such devices supporting wireless access technologies such as 5G NR, future 6G, or other technologies.

[0110] For illustrative purposes, specific exemplary embodiments will now be explained in more detail with reference to the accompanying drawings and the above-described system, ED, and TRP.

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

[0112] In 5G networks, scheduling granularity is slot-based. For a normal cyclic prefix (CP), this scheduling granularity always has a fixed number (14) of scheduling symbols, regardless of the user service type, application scenario, or frame structure with one or more system parameters. In other words, slot-based scheduling has a 14-symbol scheduling granularity, and for any system parameter, this scheduling granularity has a fixed number of scheduling symbols, while the slot duration varies depending on the system parameter. Slot-based scheduling can schedule micro-slot resources, i.e., a subset of the 14 symbols in a slot as time-domain resources, but it does not support scheduling resources across slot boundaries. Furthermore, regardless of whether slot-based scheduling schedules all slot symbols or micro-slots (a few symbols), the scheduling granularity is slot-based; scheduling starts from the slot (i.e., the slot boundary) and does not support scheduling across slot boundaries.

[0113] The above approach is inflexible in terms of on-demand (e.g., latency-dependent) symbol scheduling. For example, in future wireless networks such as 6G, wider carrier bandwidth is expected, thus reducing the number of symbols required to carry services (compared to 14 symbols). On the other hand, some application or service types (e.g., video services) may have a large number of services to transmit, making the number of symbols used to carry those services potentially exceed 14. Therefore, scheduling granularity can vary based on application type, service type, use case, and / or system parameter options.

[0114] Therefore, this disclosure provides a method. In this method, by changing the scheduling unit, represented by the number of scheduling symbols, a flexible scheduling scheme is provided to adapt to different application types, service types, use cases, and / or system parameter options.

[0115] For example, flexible scheduling schemes can be implemented by changing the scheduling unit, represented by the number of scheduling symbols, for each scheduling of a transmission, or by using different scheduling granularities. Flexible scheduling schemes are not limited to time slot-based scheduling granularity (e.g., 14 symbols) to accommodate different application types, service types, use cases, mobility, and / or system parameter options.

[0116] The scheduling reference point can be any of the following: frame, subframe, time slot, predefined time reference point, and / or preconfigured time reference point (e.g., absolute time reference point, relative time reference point, etc.). The reference point can be configured via higher-layer signaling (e.g., RRC signaling) or via dynamic signaling. Based on the reference point, one or more time-frequency resources can be scheduled, where the scheduling can allocate one or more time (and / or frequency) resources based on scheduling granularity (e.g., in units of symbols); this scheduling granularity can be configured in either semi-static or dynamic signaling. For multiple system parameter options, the scheduling granularity or the unit used for scheduling symbols can be based on base or reference system parameters, such as 15kHz, 30kHz, 60kHz, 120kHz, 240kHz, or 480kHz subcarrier spacing (SCS) with normal CP (NCP) or extended CP (ECP). For example, the unit could be 7 symbols of a 15kHz SCS with NCP, or 12 symbols of a 60kHz SCS with ECP.

[0117] Furthermore, based on the reference point, control resource set (CORESET) allocation or PDCCH monitoring timing can be configured, where CORESET allocation or PDCCH monitoring timing can be any of the cell common configuration, group common configuration, or UE-specific configuration. The configuration of CORESET allocation or PDCCH monitoring timing can be separate from or independent of the configuration at any scheduling granularity.

[0118] Typically, scheduling granularity (e.g., 7, 14, or 28 symbols based on reference system parameter options) can be configured to suit any of the application or service type, mobility type, or service transmission SCS usage. In some implementations, scheduling granularity (e.g., 7, 14, or 28 symbols based on reference system parameter options) can be configured based on, for example, application or service type, mobility type, or service transmission SCS usage. Different scheduling granularities support flexible scheduling units or scheduling time lengths, for example, to meet different requirements or needs of the SCS options used in application or service type, mobility type, or service transmission. For example, enhanced ultra-reliable low-latency communication (URLLC) services may require faster turnaround times to achieve low latency and high reliability transmission, and therefore, (optionally) smaller scheduling granularity (less than 14 symbols) (e.g., scheduling units of 7 or 6 symbols) can be used to accommodate such latency requirements. On the other hand, for high-load or high-data-rate transmissions, such as enhanced mobile broadband (eMBB) services, a larger scheduling granularity (e.g., a scheduling unit of 28 or 56 symbols) can be used (optionally) to accommodate such data rate requirements.

[0119] Alternatively, when applied to specific system parameters used in service transmissions, the scheduling granularity based on reference system parameters can be associated with the actual scheduling granularity. For example, for signal transmission with system parameters of 30 kHz, a scheduling granularity of 7 symbols based on reference system parameters of 15 kHz SCS can be explicitly configured; or, a scheduling granularity of 7 symbols based on reference system parameters of 15 kHz SCS can implicitly indicate that for signal transmission with system parameters of 30 kHz, an actual scheduling granularity of 14 symbols can be used; for signal transmission with system parameters of 60 kHz, an actual scheduling granularity of 28 symbols can be used, and so on.

[0120] For a scheduling granularity (e.g., RRC-configured), one or more time-domain resource allocations can be indicated within the scheduling granularity via scheduling signaling, such as dynamic signaling (e.g., DCI) or semi-static signaling (e.g., higher-level signaling such as radio resource control (RRC), medium access control-control element (MAC-CE), etc.). Time-domain resource allocations can include a start symbol (S) and a number of consecutive symbols (L) (within the scheduling granularity), which can be represented by a start and length indicator value (SLIV). Alternatively, time-domain resource allocations can include an indication of a predefined or tabulated time allocation resource index for a set of time-domain resource allocations, where each entry (row) in the table includes the start symbol and the number of consecutive symbols. Alternatively, scheduling signaling can also include a reference point (or reference point index) upon which time-domain resource allocations are scheduled. This reference point can be indicated by the number of frames, the number of subframes, the number of time slots, the number of scheduling units, a predefined time period, or a preconfigured time period.

[0121] In one possible implementation, for a scheduling granularity of Lz symbols based on the base or reference system parameters (i.e., a scheduling unit with a granularity of Lz symbols), the time-domain resource allocation with S and L can be represented by an SLIV determined based on the following procedure.

[0122]

[0123] In some implementations, the UE may receive signaling for scheduling granularity to configure or indicate the scheduling granularity, wherein the scheduling granularity is based on reference system parameters and is expressed in symbol quantities. The UE may also receive scheduling signaling including at least one time-domain and frequency-domain resource allocation for downlink (DL) or uplink (UL) transmission; the time-domain resource allocation in this allocation is indicated by a time resource allocation index in a SLIV or a predefined or pre-configured time resource table. Optionally, the scheduling signaling may also include a reference time on which the scheduling time-domain resource allocation is based, wherein the reference time may be a reference point or a PDCCH monitoring timing (as described above). The UE may send or receive services based on the scheduling signaling; the signaling for scheduling granularity is semi-static / higher-layer signaling (e.g., RRC), while the scheduling signaling is dynamic signaling (e.g., DCI).

[0124] The method disclosed herein enables greater flexibility in data transmission and, correspondingly, improves transmission performance.

[0125] The following section will describe in detail several possible implementations of the scheme briefly described above. One possible implementation details a flexible scheduling scheme with alignment points.

[0126] This scheme proposes a flexible scheduling approach by employing different scheduling granularities. The scheduling granularity refers to a basic scheduling unit, expressed in terms of the number of symbols, based on reference system parameters. Scheduling signaling may include one or more time-domain resource allocations within the scheduling granularity for one or more DL and / or UL transmissions (e.g., each time-domain resource allocation has a combination of start symbols and the number of consecutive symbols).

[0127] In this application, the scheduling unit is not limited to a time-slot-based scheduling granularity of 14 symbols. Instead, various scheduling granularities are proposed to accommodate different application types, service types, mobility types, use cases, and / or system parameter options.

[0128] Scheduling signaling or DCI messages can be sent at the PDCCH monitoring time (described in more detail below) or at a time relative to a reference point. The reference point can be any of a frame, subframe, time slot, predefined time reference point, and / or preconfigured time reference point. Scheduling signaling can include one or more time-frequency resource allocations within a scheduling granularity or scheduling unit; wherein, for example, a scheduling unit can be represented by the number of symbols, which can be configured in semi-static signaling (e.g., RRC, MAC-CE) or dynamic signaling (e.g., DCI). In some implementations, different application or service types can be configured with different scheduling granularities. For example, URLLC services may require faster turnaround times to achieve low latency and high reliability transmissions, so a smaller scheduling granularity (less than 14 symbols) (e.g., a scheduling unit of 7 or 6 symbols) can be configured to accommodate such latency requirements; on the other hand, for high-load or high-data-rate transmissions, such as eMBB services, a larger scheduling granularity (e.g., a scheduling unit of 14 or 28 symbols) can be configured to accommodate such data-rate requirements.

[0129] For multiple system parameter options, the unit of the number of symbols in the scheduling signaling can be based on the basic or reference system parameters, such as 15kHz, 30kHz, 60kHz, 120kHz, 240kHz, and 480kHz subcarrier spacing (SCS) with NCP or ECP; for example, a unit of 7 symbols with a 15kHz SCS with NCP, or a unit of 12 symbols with a 60kHz SCS with ECP.

[0130] Furthermore, PDCCH monitoring timing is used for PDCCH transmissions within a CORESET (e.g., transmissions performing DCI), which consists of multiple resource element groups (REGs) within specific time and frequency domain resources. The PDCCH uses control channel elements (CCEs) as its structure. A CCE is a group of REGs, and a PDCCH can consist of one or more CCEs. The number of CCEs used by the PDCCH is called its aggregation level. Higher aggregation levels imply lower coding rates or more robust coding, making it more suitable for UEs with poor channel conditions. CORESET allocation or PDCCH monitoring timing can be configured as a cell-common configuration, group-common configuration, or UE-specific configuration; furthermore, the configuration of CORESET and / or PDCCH monitoring timing can be separate from or independent of scheduling granularity configuration.

[0131] The scheduling granularity can be configured as a UE-specific configuration, a cell-common configuration, or a group-common configuration. The scheduling granularity can also be an application- or service-specific configuration (e.g., URLLC, eMBB, etc.). The scheduling granularity can be configured or indicated in semi-static signaling such as RRC and MAC-CE, and / or dynamic signaling such as DCI, or any combination thereof.

[0132] Scheduling signaling may include one or more time-domain resource allocations within a scheduling granularity or scheduling unit. Each time-domain resource allocation may include a start symbol and a number of consecutive symbols (within the scheduling unit), which may be represented by a SLIV.

[0133] The above process and description can be as follows: Figure 5 As shown. Figure 5 As shown, 15kHz is used as a reference system parameter, and alignment or reference points 510a to 510e (collectively referred to as 520) are defined / configured based on frames, as well as the time lengths 520a and 520b (collectively referred to as 520) between two reference (alignment) points 510 (e.g., expressed in terms of the number of subframes or symbols); scheduling granularity is also configured, such as Figure 5 As shown. It should be noted that the time interval between two adjacent reference points can be configured as follows: Figure 5 The scheduling granularity (e.g., N symbols) can be referenced to a reference or alignment point when sending scheduling signaling. In one possible implementation, the time length between two adjacent reference points and the scheduling granularity can be configured individually or independently, where the time for sending scheduling signaling can be referenced to PDCCH monitoring times 530a, 530b, and 530c (collectively referred to as 530). Figure 5In this context, scheduling signaling or DCI may include indications of one or more time-domain resource allocations in the DCI element field. These indications may require one or more bits (e.g., 7 bits) to indicate one or more time-domain allocations, and additional information bits to indicate one or more frequency-domain resource allocations. In some implementations, frequency-domain allocations may use the same indication techniques used in NR.

[0134] In some possible implementations, given reference system parameters for a 15kHz SCS, when configuring the UE using 30kHz, its symbol duration can be reduced to half the symbol duration of the 15kHz configuration. Therefore, if the scheduling granularity is N symbols represented by 15kHz system parameters and applied to signal scheduling with 30kHz system parameters, the scheduling granularity is 2N symbols, such as... Figure 5 As shown; this scalable rule can be applied to Other system parameter options in the system parameter family, where k is a non-negative integer. In other possible implementations, the N symbols applied to the reference system parameter are also applied to the other system parameters; that is, all system parameters use the same N symbols, but the scheduling granularity (in seconds) differs for different system parameters due to the different symbol lengths. In other possible implementations, the scheduling granularity can be specific to the system parameter configuration, for example, in a semi-static manner (e.g., RRC or MAC-CE), thus making scheduling more flexible due to individual or independent configuration for different system parameter options.

[0135] One possible implementation describes in detail the temporal resource allocation using the SLIV scheme.

[0136] In this scheme, the time-domain resource allocation provided by scheduling signaling such as DCI can include the start symbol (S) and the number of consecutive symbols (L) (within a scheduling unit), which can be represented by SLIV. The scheduling signaling can include an indication of a reference time as a reference for time-domain resource allocation, where the reference time is relative to the start time of the time-domain resource allocation, and this reference time can be represented by the number of scheduling units, subframes, time slots, or symbols relative to the aforementioned reference point 510 or PDCCH monitoring time 530. Therefore, the scheduled time-domain resources can be uniquely determined by the reference time and SLIV. For example, the scheduled time-domain resources can be located within a scheduling unit at an SLIV located N scheduling units (N is a non-negative integer) away from the scheduling time, reference point 510, or PDCCH monitoring time 530.

[0137] Figure 6The document describes DCI indicator option 1, in which the SLIV for time-domain resource allocation is calculated. For scheduling units with a granularity of Lz symbols based on fundamental or reference system parameters such as a 15kHz SCS (with NCP), the SLIV is calculated based on the parameters mentioned above and similarly... Figure 6 The process shown in 610 is used to determine SLIV (assuming the scheduler has time resources of S and L).

[0138] For a given scheduling size Lz (configured scheduling granularity), the total number of (S, L) pairs or time-domain allocations can be uniquely determined, as exemplary Table 620 shows. Figure 6 As shown. Therefore, one or more indicator bits are needed to indicate each of these time-domain allocations, wherein the one or more indicator bits may be included in scheduling signaling or messages (e.g., DCI).

[0139] Figure 6 The indicator bits in Table 620 are based on Figure 6 The result is obtained using the calculation method 610 shown. As an example, the result is as follows: Figure 6 As shown in Table 620, a scheduling granularity with a smaller number of symbols (Lz), such as 6 or 7 symbols (compared to 14 symbols based on time slots), may require fewer bits, such as (at most) 5 bits, and these indicator bits can be included in the DCI element field used to indicate time-domain resource allocation. A scheduling granularity with 14 symbols (Lz) may require (at most) 7 bits, and these indicator bits can be included in the DCI element field used to indicate time-domain resource allocation. A scheduling granularity with a larger number of symbols (Lz), such as 28 symbols (compared to 14 symbols based on time slots), may require more bits, such as (at most) 9 bits, and these indicator bits can be included in the DCI element field used to indicate time-domain resource allocation.

[0140] Different scheduling granularities can be configured for different UEs, application or service types, mobility types, and / or system parameters. Alternatively, different scheduling granularities can be configured based on different requirements or needs regarding latency, data rate, reliability, or other key performance indicators.

[0141] One possible implementation describes time-domain resource allocation with resource indexes in detail.

[0142] In this scheme, time-domain resource allocation may include the number of start symbols and consecutive symbols (within the scheduling unit). This time-domain resource allocation can be indicated by one or more time allocation resource indices, which are predefined or tabulated for a set of time resource allocations. Each time resource allocation includes the number of start symbols and consecutive symbols, such as... Figure 7(Regarding NCP) and Figure 8 (For ECP) ​​as shown.

[0143] For a given Lz, the total number of (S, L) pairs or time-domain allocations can be uniquely determined for the scheduling granularity (or unit). A portion or all of the total number of (S, L) pairs or time-domain allocations can be tabulated, such as... Figure 7 and Figure 8 As shown. If a portion of the total number of (S, L) pairs or time-domain allocations within the scheduling granularity is tabulated, a reduced number of indicator bits can be used for time resource indication; in this way, the number of indicator bits included in the scheduling signaling or DCI for time-domain resources can be reduced.

[0144] like Figure 7 and Figure 8 As shown, the temporal resource allocation of PDSCH or PUSCH (e.g., PDSCH or PUSCH 540a, 540b) can be configured through scheduling granularity or scheduling unit Lz (for NCP) or The resource index (PDSCH or PUSCH) is used to indicate (for ECP). The number of indicator bits required to uniquely indicate each time-domain resource allocation depends on the total number of time-domain resource allocations in each table. In some implementations, a portion of the total time-domain resource allocations is selected. For example, L values ​​of 2, 4, and / or 7 are used to form the resource allocation table, thereby reducing the number of rows in the resource allocation table, where the number of indicator bits can be reduced to indicate the time-domain resource allocation (in a row).

[0145] Different scheduling granularities can be configured for different UEs, application or service types, mobility types, and / or system parameters. Alternatively, different scheduling granularities can be configured based on different requirements or needs regarding latency, data rate, reliability, or other key performance indicators.

[0146] Figure 9 Another exemplary flexible scheduling scheme with time-domain resource allocation indication is shown. In this example, such as Figure 9 As shown at the top, 15kHz is used as the reference system parameter, while Figure 9 The bottom shows 30kHz, whose symbol duration can be reduced to half that of 15kHz. Figure 9 The diagram shows that for 15kHz system parameters, the scheduling granularity in the scheduling unit is N = 4 symbols.

[0147] like Figure 9As shown, alignment or reference points 910a, 910b, and 910c (collectively referred to as 910) are defined / configured within the frame; scheduling granularity, represented by scheduling units (SUs) 950a or 950b (collectively referred to as 950), is also configured. Figure 5 Unlike other scheduling granularities, the scheduling granularity represented by SU 950 can differ from the time length 920 between two adjacent alignment points 910. For example, the number of symbols included in SU 950 can be less than the number of symbols in the time length 920 between two adjacent alignment points 910. In practice, in some implementations, one or more alignment points can be configured within a frame based on any one or more of subframes, time slots, symbols, SUs (or granularities), etc. In some implementations, subframes can be timestamped using absolute time; for example, absolute time can be provided for one of the frame boundaries using system information. For example, the frame duration might be, for instance, 10 ms, and the subframe duration might be, for instance, 1 ms. In some implementations, one or more alignment points can be configured within a frame based on absolute time.

[0148] Alignment points can be located within the boundaries of frames, subframes, symbols, time slots, and sorted units (SUs), or anywhere within a frame. For example, Figure 5 and Figure 9 The first alignment points 510 and 910 are shown aligned with the frame boundary. In some implementations, alignment points 510 and 910 may be offset relative to the frame or subframe boundary (e.g., offset by a number of symbols, SU, or absolute time).

[0149] In some implementations, predefined or default parameters such as system parameters (e.g., 15kHz), CP type, and scheduling unit can be used for system information broadcasting. Parameters such as cell common or group common scheduling units and alignment points can be updated through system information.

[0150] In some implementations, when a UE accesses the network, certain UE-specific parameters, such as system parameters, PDCCH timing, and scheduling units, can be configured through semi-static methods (e.g., via RRC and / or MAC-CE), dynamic methods (via DCI), or a combination thereof. System parameters can be represented by two parameters: subcarrier spacing and a CP (regular CP or extended CP).

[0151] Figure 5 or Figure 9The configured frame structure shown can be used as a reference time frame for communication. For example, it can support time division duplex (TDD) or frequency division duplex (FDD) transmission / reception of OFDM signals with different system parameters (e.g., 15kHz, 30kHz, 60kHz, etc.) for different UEs or for different data transmission times of the same UE, for example, by using flexible and different scheduling units associated with different system parameters.

[0152] In some implementations, the timing of sending scheduling signaling can refer to the PDCCH monitoring timing (or PDCCH timing). In some implementations, the PDCCH timing can refer to the position of the PDCCH (e.g., 530 or 930) in the time and frequency domain resources. In some implementations, the PDCCH timing can be configured in different ways. As an example, the PDCCH timing (e.g., PDCCH timings 530a, 530b, 930a, or 930c) can be configured based on alignment points defined within a time length of 520 or 920 between two alignment points (e.g., alignment point 510 or 910), and repeated periodically (e.g., at alignment points). As another example, the PDCCH timing (e.g., PDCCH timings 530c, 930b, or 930d) can be configured based on alignment points with offsets defined within a time length of 520 or 920 between two alignment points (e.g., alignment point 510 or 910), and repeated periodically (e.g., at alignment points). As another example, a bitmap can be used to configure the PDCCH timing over a time length of 520 or 920 between two alignment points, and this timing can be repeated periodically (e.g., at the alignment points). In some implementations, the PDCCH timing configuration may also include an applicable period (e.g., valid for 500ms).

[0153] In some implementations, scheduling signaling such as DCI may include indications of one or more time-domain resource allocations in the DCI element field (e.g., the SLIV field), where the indication may include one or more bits (e.g., 7 bits) to indicate one or more time-domain allocations. In some implementations, the scheduling time reference may be a frame start boundary, a reference point, or a scheduling unit (located in the PDCCH timing) that includes scheduling information / DCI. In some implementations, an alignment point may be referenced to indicate a relative time (stamp). For the applicable SU, different scheduling time references can be used to configure the time resource allocation of scheduled resources in the PDSCH or PUSCH. Figure 9The exemplary option 1 shown can indicate a scheduled resource in the PDSCH relative to the alignment point of the UE receiving the DCI (e.g., alignment point 910a), the time-domain location of which is 2SU + SLIV. Figure 9 The exemplary option 2 shown can indicate a scheduled resource in the PDSCH with a time-domain location of 1 SU + SLIV relative to a scheduling unit with a PDCCH (e.g., scheduling unit 950a). These different time reference schemes can be similarly applied to list rows for time allocation or time resource allocation entries in RRC configurations, such as in combination with... Figure 7 and Figure 8 as well as Figure 10 and Figure 11 The discussion.

[0154] In some implementations, one or more allocation tables can be used to map one or more (row) indices to a time-domain allocation / assignment represented by (k, S, L), where k represents the time offset, S represents the start symbol index, and L represents the number of consecutive symbols in the scheduled resource. The time offset can, for example, reference the start time or boundary of a frame, an alignment point, or a scheduling unit (located in the PDCCH timing) that includes scheduling information / DCI. In some implementations, the selected combination of (k, S, L) can be predefined in one or more allocation tables or configured as multiple entries via RRC. The allocation table can include multiple rows of time resource allocation entries, where the number of rows or entries can be used to determine the number of bits required in the DCI to indicate a row / entry. In some implementations, the row index can be represented by a number of bits, for example, in a bitmap or other format.

[0155] Figure 10 An exemplary table is shown for a set of physical downlink shared channel (PDSCH) time resource allocation indications for NCP. Figure 11 An exemplary table 1100 is shown, illustrating a set of physical uplink shared channel (PUSCH) time resource allocation indications for NCP. Additional or different allocation tables can be configured for NCP and / or ECP or other system parameters to map multiple (row) indices or bit representations to multiple time-domain allocations / assignments of multiple (k, S, L) combination representations. In some implementations, a subset of all (k, S, L) combinations can be selected to form a reduced table to reduce the number of bits required to represent the indices, thereby reducing signaling overhead.

[0156] In some implementations, for time-domain DL resource allocation, when the UE is scheduled to receive PDSCH via DCI, the DCI may include a time-domain resource assignment field, where the value m represents the row index m + 1 shown in the allocation table (e.g., exemplary allocation table 1000). This index row defines the time offset K0, the start and length indicator SLIV, or directly defines the start symbol S and the allocation length L. These parameters can be configured based on SU, for example, according to the combination of... Figures 6 to 8 The techniques discussed include: In some implementations, the starting symbol S relative to the start of the time slot and the number of consecutive symbols L counting from the symbol S allocated to the PDSCH are determined based on the start and length indicators SLIV. In some implementations, the total number of bits used to indicate each row in the DCI can be calculated based on candidate values ​​of K0, S, and L. In some implementations, a subset of all (K0, S, L) combinations can be selected to form a reduced table to reduce the number of bits required to represent the index, thereby reducing signaling overhead.

[0157] In some implementations, for time-domain UL resource allocation, when the UE is scheduled to transmit data on the PUSCH via the DCI, the DCI may include a time-domain resource assignment field, where the value m represents the row index m + 1 shown in the allocation table (e.g., exemplary allocation table 1100). This index row defines the time offset K2, the start and length indicator SLIV, or directly defines the start symbol S and the allocation length L. These parameters can be configured based on the SU, for example, according to the combination... Figures 6 to 8 The techniques discussed include: In some implementations, the starting symbol S relative to the SU start point and the number of consecutive symbols L counting from the symbol S assigned to PUSCH are determined based on the start and length indicators SLIV of the index row. In some implementations, the total number of bits used to indicate each row in the DCI can be calculated based on candidate values ​​of K2, S, and L. In some implementations, a subset of all (K2, S, L) combinations can be selected to form a reduced table to reduce the number of bits required to represent the index, thereby reducing signaling overhead.

[0158] Figure 12 A flowchart of an exemplary communication method 1200 for flexible scheduling is shown. The exemplary communication method 1200 can be performed by a communication system including a base station 1205 (e.g., a network node or one of TRPs 170a and 170b, 172) and a UE 1215 (e.g., ED 110). In summary, the signaling flowchart of the above possible schemes may include:

[0159] Step 1210: Base station 1205 sends information indicating one or more of the above parameters, and UE 1215 receives the information accordingly. This information can be carried by any one or any combination of RRC / MAC / DCI signaling.

[0160] In some implementations, this information may include granularity information or scheduling granularity information. In some implementations, the scheduling granularity information indicates the number of symbols (e.g., Lz symbols) in at least one SU for resource scheduling used to communicate between UE 1215 and network device 1205.

[0161] In some implementations, at least one SU comprises multiple SUs. In some implementations, the multiple SUs correspond to different application types, service types, mobility types, use cases, and / or system parameters. In some implementations, at least one SU comprises multiple SUs corresponding to multiple system parameters. System parameters can be represented by two parameters: subcarrier spacing (SCS) and a CP (e.g., NCP or ECP). In some implementations, for ECP, the number of symbols in at least one SU is an integer multiple of 3. ) symbols, for NCP, this number is an integer multiple of 7 ( The number of symbols is P. In some implementations, the number of symbols in the first SU for the 15kHz SCS can be P, the number of symbols in the second SU for the 30kHz SCS can be 2P, the number of symbols in the third SU for the 60kHz SCS can be 4P, and so on. In some implementations, the number of symbols in at least one SU is 3, 6, 7, 12, 14, 24, 28, 48, 56, etc.

[0162] In some implementations, the scheduling granularity information indicates whether the number of symbols in the first SU corresponding to the first system parameters is the same as or different from the number of symbols in the second SU corresponding to the second system parameters. As an example, the first SU corresponding to the first system parameters of 15kHz SCS and NCP and the second SU corresponding to the second system parameters of 30kHz SCS and NCP may each include 7 symbols. As another example, the first SU corresponding to the first system parameters of 15kHz SCS and NCP includes 7 symbols, while the second SU corresponding to the second system parameters of 30kHz SCS and NCP may include 14, 28, or 56 symbols.

[0163] In some implementations, the scheduling granularity information includes a scheduling granularity index, which represents the SU corresponding to one system parameter among multiple candidate SUs corresponding to multiple system parameters. In some implementations, a mapping relationship can be established between multiple scheduling granularity indices and multiple SUs corresponding to multiple system parameters, for example, such as... Figure 13 As shown in Table 1300.

[0164] In some implementations, the scheduling granularity information indicates that one of a plurality of Substations (SUs) is the default SU. For example, the default SU could be a pre-configured SU that base station 1205 and UE 1215 are aware of using without any other signaling notification, change, or update of the SU selection. For example, the default SU could be a legacy-compliant SU (e.g., a slot-based SU with 14 symbols per SU) or another SU. In some implementations, for example, the default SU is configured based on the application or service type of the current data transmission between base station 1205 and UE 1215. The RRC can be unicast, multicast, or broadcast.

[0165] In some implementations, this information may include received information indicating the location of the physical downlink control channel (PDCCH) based on an alignment point in the frame or a subframe. For example, this information may be used by the UE to determine the location of the PDCCH based on an alignment point in the frame or a subframe. In some implementations, this information may include alignment point information indicating an alignment point (e.g., alignment point 512 or 912) used to determine the location of the PDCCH in a subframe. In some implementations, the alignment point is configured based on one or more of a frame, subframe, time slot, or symbol (e.g., via an RRC message or MAC-CE). In some implementations, the time position of the alignment point differs from the start time or boundary of one or any of the frame, subframe, time slot, or symbol. For example, the time position of the alignment point differs from the start time or boundary of any of the frame, subframe, or time slot. The time position of the alignment point may be aligned with the start time or boundary of the SU or symbol.

[0166] In some implementations, this information may include information indicating the granularity of the PDCCH resources (e.g., represented by the number of symbols in a SU used for transmitting / receiving PDCCH). For example, this information may indicate to UE 1215 which SU of at least one SU should be used to receive DCI in the PDCCH. In some implementations, this information may initially be sent by base station 1205 to UE 1215 in system information. In some implementations, after configuring (e.g., via RRC messages) multiple SUs, this information may be sent in RRC messages, MAC-CE, or DCI to indicate the SU to be used (or to switch to a new SU to be used). In some implementations, a default SU for transmitting DCI via PDCCH can be configured as described above.

[0167] In some implementations, one or more of the aforementioned parameters or information (e.g., granularity information, information for determining the location of the PDCCH, and information indicating the granularity of the PDCCH resource) may be sent in one step (e.g., in the same data packet), or in multiple steps or at multiple times. For example, some parameters or information (e.g., default or initial parameters) may be sent in a system information message (e.g., a system information block (SIB)) in one time instance, while other parameters or information may be sent in another message or signaling (e.g., an RRC message, MAC-CE, or DCI) in another time instance. In some implementations, multiple flexible granularity and scheduling configurations may be pre-configured, and the DCI may include an index for activating one of the pre-configured ones without sending an RRC to indicate the granularity and scheduling parameters.

[0168] In some implementations, step 1210 is optional; when this step is not present, one or more of the parameters mentioned above are predefined, for example, associated with different scenarios (e.g., different application types, service types, mobility types, use cases, and / or system parameters).

[0169] Step 1220: Base station 1205 sends scheduling information to UE to schedule DL data or UL data, and UE 1215 receives the scheduling information accordingly.

[0170] The scheduling information can be a DCI. The details contained in the DCI are as described above. For example, the DCI includes time offset information indicating the position of the scheduled resource relative to the alignment point or relative to the PDCCH (e.g., in conjunction with...). Figure 5 and Figure 9The time offset (e.g., K0 or K2) of the PDCCH timing discussed. In some implementations, the DCI includes a start and length indicator value (SLIV) field for determining the location of the scheduled resource, wherein the SLIV field indicates the starting symbol index (S) and the number of consecutive symbols (L) within a SU, which belongs to or is one of at least one SU. For example, the SU is the default SU, or other activated / indicated SUs. In some implementations, the SLIV field includes an index indicating one of the combinations of total quantities (S, L). Here, the total quantity (S, L) combinations include all possible combinations with valid S and L.

[0171] In some implementations, the SLIV field includes an index indicating a subset of combinations of the total number of (S, L) combinations, for example, to store the number of bits used to represent that index. In some implementations, a table or other data structure can be used to store the mapping between index values ​​and (S, L) combinations, for example, as... Figure 7 , Figure 8 , Figure 10 and Figure 11 One of the tables is shown in the table. In some implementations, this mapping can be pre-configured and predefined, for example, before step 1210. For example, the base station can send the table to the UE in the system information, or the UE can store, download, or otherwise receive the table. Here, the subset of the total number (S, L) combinations includes possible combinations with valid S and L, but reduced in number, to save bits used to represent the combination.

[0172] In some implementations, the DCI includes a time allocation index indicating one of a combination of (k, S, L) combinations, where k represents the time offset (e.g., K0 or K2), S represents the starting symbol index (S), and L represents the number of consecutive symbols in the scheduled resource (L). In some implementations, S and L may be jointly represented by an SLIV value. The time resource allocation with the selected (k, S, L) combination can be predefined in a table (e.g., Table 1000 or 1100) or configured as multiple entries via RRC messages, for example, as described above.

[0173] In some implementations, to store DCI bits, a subset of these combinations can be selected and stored in one or more tables. Base station 1205 can select one of the one or more tables and choose one of the indexes from the selected table to indicate the time allocation of scheduled resources to UE 1215.

[0174] Step 1230: UE 1215 and base station 1205 perform DL and / or UL data transmission based on this information and scheduling information. For example, UE 1215 and base station 1205 communicate with each other based on at least one SU, for example, by sending / receiving DL and / or UL data using scheduled resources indicated by the DCI (e.g., located in the PDSCH or PUSCH). In some implementations, base station 1205 may determine the scheduled resources in the PDSCH for DL ​​data transmission and / or the scheduled resources in the PUSCH for UL data transmission based on at least one SU. Base station 1205 may include a time allocation indication of the scheduled resources (e.g., (k, S, L) or SLIV field) in the DCI and use the scheduled resources for DL ​​and / or UL data transmission. In some implementations, UE 1215 may receive and decode the DCI, for example, based on information indicating the granularity of the PDCCH resources. UE 1215 can determine the scheduled resources for DL ​​and / or UL data transmission based on at least one SU and a time allocation index (e.g., (k, S, L) or SLIV field) included in the DCI. UE 1215 can then use the scheduled resources for DL ​​and / or UL data transmission.

[0175] In some aspects of this disclosure, an apparatus / chipset system is provided, including components (e.g., at least one processor) for implementing a method implemented by a UE of this disclosure (or implemented at a UE of this disclosure). The apparatus / chipset system may be a UE (i.e., a terminal device) or a module / component within a UE. Specifically, the at least one processor may execute instructions stored in a computer-readable medium to implement the method. For example, the apparatus / chipset system may include corresponding modules or units for implementing the methods and / or embodiments described herein. In some implementations, the apparatus / chipset system may include a processing unit and a communication unit (including one or more of a transmitting unit and a receiving unit), such as... Figure 4As shown. For example, the device / chipset system includes: a receiving unit for receiving scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one resource scheduling unit (SU) for communication between user equipment (UE) and network equipment; and a communication unit for communicating with the network equipment based on the at least one SU. In some implementations, the device / chipset system may include one or more processors / processor cores and interface circuitry. For example, the device / chipset system includes: one or more processors; and interface circuitry for: receiving scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one resource scheduling unit (SU) for communication between user equipment (UE) and network equipment; and communicating with the network equipment based on the at least one SU. Optionally, the device / chipset system may also include a storage unit for storing device program code (or instructions) and / or data.

[0176] In some aspects of this disclosure, an apparatus / chipset system is provided, including components (e.g., at least one processor) for implementing methods implemented by a network device (e.g., a base station) of this disclosure (or at a location within a network device (e.g., a base station) of this disclosure). The apparatus / chipset system may be a network device or a module / component within a network device. Specifically, the at least one processor may execute instructions stored in a computer-readable medium to implement the method. In some aspects of this disclosure, a system is provided, including at least one device in a UE of this disclosure (or at a location within a UE of this disclosure) or in a network device of this disclosure (or at a location within a network device of this disclosure). For example, the apparatus / chipset system may include corresponding modules or units for implementing the methods and / or embodiments described herein. In some implementations, the apparatus / chipset system may include a processing unit and a communication unit (including one or more of a transmitting unit and a receiving unit), such as... Figure 4As shown. For example, the device / chipset system includes: a transmitting unit for transmitting scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one resource scheduling unit (SU) for communication between user equipment (UE) and network equipment; and a communication unit for communicating with the UE based on the at least one SU. In some implementations, the device / chipset system may include one or more processors / processor cores and interface circuitry. For example, the device / chipset system includes: one or more processors; and interface circuitry for: transmitting scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one resource scheduling unit (SU) for communication between user equipment (UE) and network equipment; and communicating with the UE based on the at least one SU. Optionally, the device / chipset system may also include a storage unit for storing device program code (or instructions) and / or data.

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

[0178] In some aspects of this disclosure, a computer program comprising instructions is provided. When executed by a processor, these instructions cause the processor to implement the methods of this disclosure.

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

[0180] The schemes described in this disclosure are applicable to next-generation (e.g., sixth-generation, 6G or higher) networks or traditional (e.g., 5G, 4G, 3G or 2G) networks.

[0181] It should be understood that any module, component, or device disclosing executable instructions herein may include or otherwise access one or more non-transitory computer / processor-readable storage media for storing 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 (i.e., DVD), Blu-ray disc™, or other optical storage devices; volatile and non-volatile, removable and non-removable media implemented using 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 such non-transitory computer / processor storage medium may be part of a device or apparatus, or may be accessible or connected to by a device or apparatus. 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.

[0182] It should be noted that the term "message" in this disclosure can be replaced with "information," which may be carried in a single message or in more than one separate message.

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

[0184] In this disclosure, 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.

[0185] In this disclosure, when used before the same term (e.g., ED or operational step), the words "first," "second," etc., do not imply an order or sequence of the terms. For example, unless otherwise specified, "first ED" and "second ED" refer to two different EDs; similarly, unless otherwise specified, "first step" and "second step" refer to two different operational 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.

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

[0187] It should be noted that the expression "at least one of A or B" used in this document is interchangeable with the expression "A and / or B". This expression refers to a list in which A, or B, or both A and B can be selected. Similarly, the expression "at least one of A, B, or C" used in this document is interchangeable with "A and / or B and / or C" or "A, B, and / or C". This expression 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 can be selected. The same principle applies to longer lists with the same format.

[0188] This disclosure includes various embodiments, not only method embodiments but also other embodiments, such as apparatus embodiments and embodiments related to non-transitory computer-readable storage media. Each embodiment may be incorporated individually or in combination with the features disclosed herein.

[0189] The terms “receive,” “detect,” and “decode” used in this document 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 or 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 indicate the same thing; for example, “received 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 indicate different processes by which the receiving side obtains the information.

[0190] While this disclosure references illustrative embodiments, it is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of this disclosure, will be apparent to those skilled in the art upon reference to this specification. When combining two or more embodiments, not all features of the embodiments to be combined are necessary for the combination.

[0191] Additionally or alternatively, features disclosed herein in the context of any particular embodiment may be implemented in other embodiments. For example, alternatively or alternatively, method embodiments may be implemented in apparatus, system, and / or computer program product embodiments. Furthermore, although embodiments are described primarily in the context of methods and apparatus, other implementations are contemplated as instructions stored in one or more non-transitory computer-readable media, etc. Such media may store programs or instructions to perform any of the methods consistent with this disclosure.

Claims

1. A method, characterized in that, include: Receive scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one scheduling unit (SU) for resource scheduling used to communicate with network devices; The at least one SU communicates with the network device.

2. The method according to claim 1, characterized in that, The at least one SU includes multiple SUs, and the scheduling granularity information indicates that one of the multiple SUs is the default SU.

3. The method according to claim 1 or 2, characterized in that, The at least one SU includes multiple SUs, each SU corresponding to one of the multiple system parameters.

4. The method according to claim 3, characterized in that, The scheduling granularity information indicates that the number of symbols in the first SU corresponding to the first system parameter is the same as the number of symbols in the second SU corresponding to the second system parameter, wherein the first SU and the second SU belong to the plurality of SUs, and the first system parameter and the second system parameter belong to the plurality of system parameters.

5. The method according to claim 3, characterized in that, The scheduling granularity information indicates that the number of symbols in the first SU corresponding to the first system parameter is different from the number of symbols in the second SU corresponding to the second system parameter, wherein the first SU and the second SU belong to the plurality of SUs, and the first system parameter and the second system parameter belong to the plurality of system parameters.

6. The method according to any one of claims 1 to 5, characterized in that, The scheduling granularity information includes one or more of the Radio Resource Control (RRC) message, Media Access Control-Control Element (MAC-CE), or Downlink Control Information (DCI).

7. The method according to any one of claims 1 to 6, characterized in that, The number of symbols in at least one SU is 3, 6, 7, 12, 14, 24, 28 or 48.

8. The method according to any one of claims 1 to 7, characterized in that, Also includes: Receive information indicating the location of the Physical Downlink Control Channel (PDCCH) based on the alignment point in the frame or the subframe.

9. The method according to claim 8, characterized in that, The alignment point is configured based on one or more of a frame, subframe, time slot, or symbol; the time position of the alignment point is different from the start time or boundary of any of the frame, subframe, or time slot.

10. The method according to claim 8, characterized in that, Also includes: A DCI is received in the PDCCH, wherein the DCI includes time offset information indicating the time offset of the scheduled resource relative to the alignment point.

11. The method according to claim 8, characterized in that, Also includes: A DCI is received in the PDCCH, wherein the DCI includes time offset information indicating the time offset of the scheduled resource relative to the position of the PDCCH.

12. The method according to any one of claims 1 to 11, characterized in that, Also includes: Receive a DCI, wherein the DCI includes a start and length indication value SLIV field, the SLIV field indicating the starting symbol index (S) and the number of consecutive symbols (L) within a SU, the SU being one of the at least one SUs.

13. The method according to claim 12, characterized in that, The SLIV field includes an index indicating one of the combinations of total (S, L) combinations.

14. The method according to claim 12, characterized in that, The SLIV field includes an index indicating a subset of combinations of total quantities (S, L).

15. The method according to any one of claims 1 to 14, characterized in that, Also includes: Receive DCI, which includes a time allocation index for one of a combination of (k, S, L) indicators, where k represents the time offset, S represents the starting symbol index, and L represents the number of consecutive symbols of the scheduled resource.

16. The method according to any one of claims 1 to 15, characterized in that, Also includes: Receive information indicating that one of the at least one SUs is used to receive DCI in the PDCCH.

17. A method, characterized in that, include: Send scheduling granularity information, which indicates the number of symbols in at least one SU for resource scheduling used to communicate with the user equipment UE; The SU communicates with the UE based on the at least one SU.

18. The method according to claim 17, characterized in that, The at least one SU includes multiple SUs, and the scheduling granularity information indicates that one of the multiple SUs is the default SU.

19. The method according to claim 17 or 18, characterized in that, The at least one SU includes multiple SUs, each SU corresponding to one of the multiple system parameters.

20. The method according to claim 19, characterized in that, The scheduling granularity information indicates that the number of symbols in the first SU corresponding to the first system parameter is the same as the number of symbols in the second SU corresponding to the second system parameter, wherein the first SU and the second SU belong to the plurality of SUs, and the first system parameter and the second system parameter belong to the plurality of system parameters.

21. The method according to claim 19, characterized in that, The scheduling granularity information indicates that the number of symbols in the first SU corresponding to the first system parameter is different from the number of symbols in the second SU corresponding to the second system parameter, wherein the first SU and the second SU belong to the plurality of SUs, and the first system parameter and the second system parameter belong to the plurality of system parameters.

22. The method according to any one of claims 17 to 21, characterized in that, The scheduling granularity information includes one or more of the Radio Resource Control (RRC) message, Media Access Control-Control Element (MAC-CE), or Downlink Control Information (DCI).

23. The method according to any one of claims 17 to 22, characterized in that, The number of symbols in at least one SU is 3, 6, 7, 12, 14, 24, 28 or 48.

24. The method according to any one of claims 17 to 23, characterized in that, Also includes: Send information indicating the location of the Physical Downlink Control Channel (PDCCH) based on the alignment point in the frame or the subframe.

25. The method according to claim 24, characterized in that, The alignment point is configured based on one or more of a frame, subframe, time slot, or symbol; the time position of the alignment point is different from the start time or boundary of any of the frame, subframe, or time slot.

26. The method according to claim 24, characterized in that, Also includes: Downlink control information (DCI) is transmitted in the PDCCH, wherein the DCI includes time offset information indicating the time offset of the scheduled resource relative to the alignment point.

27. The method according to claim 24, characterized in that, Also includes: Downlink control information (DCI) is transmitted in the PDCCH, wherein the DCI includes time offset information indicating the time offset of the scheduled resource relative to the position of the PDCCH.

28. The method according to any one of claims 17 to 27, characterized in that, Also includes: Send downlink control information (DCI), wherein the DCI includes a start and length indication value (SLIV) field, the SLIV field indicating the start symbol index (S) and the number of consecutive symbols (L) within a SU, the SU being one of the at least one SUs.

29. The method according to claim 28, characterized in that, The SLIV field includes an index indicating one of the combinations of total (S, L) combinations.

30. The method according to claim 28, characterized in that, The SLIV field includes an index indicating a subset of combinations of total quantities (S, L).

31. The method according to any one of claims 17 to 30, characterized in that, Also includes: Send downlink control information (DCI), which includes a time allocation index for one of a combination of indicators (k, S, L), where k represents the time offset, S represents the starting symbol index, and L represents the number of consecutive symbols of the scheduled resource.

32. The method according to any one of claims 17 to 31, characterized in that, Also includes: Send information indicating that one of the at least one SUs is used to send DCI in the PDCCH.

33. A communication device, characterized in that, Used to perform the method according to any one of claims 1 to 32.

34. The communication device according to claim 33, characterized in that, include: A receiving unit is configured to receive scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one resource scheduling unit (SU) for communicating with network devices. A communication unit for communicating with the network device based on the at least one SU.

35. The communication device according to claim 33, characterized in that, include: A sending unit is configured to send scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one SU for resource scheduling used to communicate with a user equipment UE; A communication unit for communicating with the UE based on the at least one SU.

36. The communication device according to claim 33, characterized in that, include: One or more processors; Interface circuit, used for: Receive scheduling granularity information, the scheduling granularity information indicating the number of symbols in at least one SU for resource scheduling used to communicate with network devices; The network device is communicated based on at least one SU.

37. The communication device according to claim 33, characterized in that, include: One or more processors; Interface circuit, used for: Send scheduling granularity information, which indicates the number of symbols in at least one SU for resource scheduling used to communicate with the user equipment UE; The SU communicates with the UE based on the at least one SU.

38. The communication device according to claim 36 or 37, characterized in that, The interface circuit includes one or more transceivers.

39. An apparatus, characterized in that, include: One or more processors; One or more memories storing 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 32.

40. 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 16; and a second communication device for performing the method according to any one of claims 17 to 32.

41. A non-transitory computer-readable storage medium, characterized in that, It stores instructions that, when executed by the device, cause the device to perform the method according to any one of claims 1 to 32.