[go: up one dir, main page]

WO2025200119A1 - Procédé, appareil et système de planification flexible - Google Patents

Procédé, appareil et système de planification flexible

Info

Publication number
WO2025200119A1
WO2025200119A1 PCT/CN2024/096314 CN2024096314W WO2025200119A1 WO 2025200119 A1 WO2025200119 A1 WO 2025200119A1 CN 2024096314 W CN2024096314 W CN 2024096314W WO 2025200119 A1 WO2025200119 A1 WO 2025200119A1
Authority
WO
WIPO (PCT)
Prior art keywords
symbols
scheduling
dci
information
numerology
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/096314
Other languages
English (en)
Inventor
Liqing Zhang
Jianglei Ma
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025200119A1 publication Critical patent/WO2025200119A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/14Relay systems
    • H04B7/15Active relay systems
    • H04B7/185Space-based or airborne stations; Stations for satellite systems
    • H04B7/1851Systems using a satellite or space-based relay
    • H04B7/18513Transmission in a satellite or space-based system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/14Relay systems
    • H04B7/15Active relay systems
    • H04B7/185Space-based or airborne stations; Stations for satellite systems
    • H04B7/1853Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H04B7/18539Arrangements for managing radio, resources, i.e. for establishing or releasing a connection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00Modulated-carrier systems
    • H04L27/26Systems using multi-frequency codes
    • H04L27/2601Multicarrier modulation systems
    • H04L27/2602Signal structure
    • H04L27/26025Numerology, i.e. varying one or more of symbol duration, subcarrier spacing, Fourier transform size, sampling rate or down-clocking
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signalling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446Resources in time domain, e.g. slots or frames

Definitions

  • the present disclosure relates generally to wireless communications. Particularly, it relates to a method, apparatus and system for flexible scheduling.
  • Wireless communications system such as fourth generation (4G) system (for example, Long-Term Evolution (LTE) system)
  • fifth generation (5G) system for example, New Radio (NR) system
  • 4G Long-Term Evolution
  • 5G fifth generation
  • applications such as message, voice, video and other data.
  • hybrid automatic repeat request (HARQ) process is implemented to allow re-transmission and hybrid combining of original and re-transmission of the same data to counterattack the channel impairment and improve the robustness of the system performance.
  • HARQ hybrid automatic repeat request
  • One or more implementations of the present application provide communication methods and communication apparatuses.
  • the techniques described in the application can improve scheduling flexibility.
  • a method is provided.
  • the method may be performed at a user equipment (UE) side.
  • the method includes receiving scheduling granularity information that indicates a number of symbols in at least one scheduling unit (SU) for resource scheduling for communications with a network device, and communicating with the network device based on the at least one SU.
  • SU scheduling unit
  • the at least one SU comprises a plurality of SUs
  • the scheduling granularity information indicates one of the plurality of SUs is a default SU.
  • the at least one SU comprises a plurality of SUs, each SU corresponding to one of a plurality of numerologies.
  • the scheduling granularity information indicates that a number of symbols in a first SU corresponding to a first numerology is the same as a number of symbols in a second SU corresponding to a second numerology, wherein the first SU and the second SU belong to the plurality of SUs, the first numerology and the second numerology belong to the plurality of numerologies.
  • the scheduling granularity information indicates a number of symbols in a first SU corresponding to a first numerology is different from a number of symbols in a second SU corresponding to a second numerology, wherein the first SU and the second SU belong to the plurality of SUs, the first numerology and the second numerology belong to the plurality of numerologies.
  • the scheduling granularity information is included in one or more of a radio resource control (RRC) message, media access control–control element (MAC-CE) , or downlink control information (DCI) .
  • RRC radio resource control
  • MAC-CE media access control–control element
  • DCI downlink control information
  • the number of symbols in the at least one SU is 3, 6, 7, 12, 14, 24, 28, or 48.
  • the method further includes receiving information indicating a location of a physical downlink control channel (PDCCH) based on an alignment point or a subframe in a frame.
  • PDCCH physical downlink control channel
  • the alignment point is configured based on one or more of a frame, a subframe, a slot, or a symbol; and a time location of the alignment point is different from a starting time or a boundary of any of the frame, the subframe, or the slot.
  • the method further includes receiving downlink control information (DCI) in the PDCCH, wherein the DCI comprises time offset information indicating a time offset of a scheduled resource relative to the alignment point.
  • DCI downlink control information
  • the method further includes receiving downlink control information (DCI) in the PDCCH, wherein the DCI comprises time offset information indicating a time offset of a scheduled resource relative to the location of the PDCCH.
  • DCI downlink control information
  • the method further includes receiving downlink control information (DCI) , wherein the DCI comprises a start and length indicator value (SLIV) field for determining a location of a scheduled resource, wherein the SLIV field indicates a starting symbol index (S) and a number of consecutive symbols (L) within an SU, wherein the SU is one of the at least one SU.
  • DCI downlink control information
  • SLIV start and length indicator value
  • the SLIV field comprises an index indicating one of a total number of (S, L) combinations.
  • the SLIV field comprises an index indicating one of a subset of a total number of (S, L) combinations.
  • the method further includes receiving downlink control information (DCI) , wherein the DCI comprises a time allocation index indicating one of a (k, S, L) combination, wherein k represents a time offset, S represents a starting symbol index, and L represents a number of consecutive symbols of a scheduled resource.
  • DCI downlink control information
  • the S and L among the (k, S, L) combination refers to time resources with the SU; moreover, the DCI comprises resource scheduling on one or more (separate) time allocations. This note can also be applicable to the following paragraphs for related DCI and scheduling descriptions.
  • the method further includes receiving information that indicates one of the at least one SU for receiving a DCI in a PDCCH.
  • a method is provided.
  • the method may be performed at a network device.
  • the method includes transmitting scheduling granularity information that indicates a number of symbols in at least one scheduling unit (SU) for resource scheduling for communications with a user equipment (UE) ; and communicating with the UE based on the at least one SU.
  • SU scheduling unit
  • UE user equipment
  • the at least one SU comprises a plurality of SUs
  • the scheduling granularity information indicates one of the plurality of SUs is a default SU.
  • the at least one SU comprises a plurality of Sus, each SU corresponding to one of a plurality of numerologies.
  • the scheduling granularity information indicates that a number of symbols in a first SU corresponding to a first numerology is the same as a number of symbols in a second SU corresponding to a second numerology, wherein the first SU and the second SU belong to the plurality of SUs, the first numerology and the second numerology belong to the plurality of numerologies.
  • the scheduling granularity information indicates a number of symbols in a first SU corresponding to a first numerology is different from a number of symbols in a second SU corresponding to a second numerology, wherein the first SU and the second SU belong to the plurality of SUs, the first numerology and the second numerology belong to the plurality of numerologies.
  • the scheduling granularity information is included in one or more of a radio resource control (RRC) message, media access control–control element (MAC-CE) , or downlink control information (DCI) .
  • RRC radio resource control
  • MAC-CE media access control–control element
  • DCI downlink control information
  • the number of symbols in the at least one SU is 3, 6, 7, 12, 14, 24, 28, or 48.
  • the method further includes transmitting an alignment point information that indicates an alignment point for determining a location of a physical downlink control channel (PDCCH) in a subframe.
  • PDCCH physical downlink control channel
  • the alignment point is configured based on one or more of a frame, a subframe, a slot, or a symbol; and a time location of the alignment point is different from a starting time or a boundary of any of the frame, the subframe, or the slot.
  • the method further includes transmitting downlink control information (DCI) in the PDCCH, wherein the DCI comprises time offset information indicating a time offset of a scheduled resource relative to the alignment point.
  • DCI downlink control information
  • the method further includes transmitting downlink control information (DCI) in the PDCCH, wherein the DCI comprises time offset information indicating a time offset of a scheduled resource relative to the location of the PDCCH
  • DCI downlink control information
  • the method further includes transmitting downlink control information (DCI) , wherein the DCI comprises a start and length indicator value (SLIV) field for determining a location of a scheduled resource, wherein the SLIV field indicates a starting symbol index (S) and a number of consecutive symbols (L) within an SU, wherein the SU is one of the at least one SU.
  • DCI downlink control information
  • SLIV start and length indicator value
  • the SLIV field comprises an index indicating one of a total number of (S, L) combinations.
  • the SLIV field comprises an index indicating one of a subset of a total number of (S, L) combinations.
  • the method further includes transmitting downlink control information (DCI) , wherein the DCI comprises a time allocation index indicating one of a (k, S, L) combination, wherein k represents a time offset, S represents a starting symbol index, and L represents a number of consecutive symbols of a scheduled resource.
  • DCI downlink control information
  • the method further includes transmitting information that indicates one of the at least one SU for transmitting a DCI in a PDCCH.
  • a communication apparatus configured to perform the method according to the first aspect or one or more implementations of the first aspect, or the second aspect or one or more implementations of the second aspect.
  • the communication apparatus includes a receiving unit configured to receive scheduling granularity information that indicates a number of symbols in at least one SU for resource scheduling for communications between the communication apparatus and a network device; and a communicating unit configured to communicate with the network device based on the at least one SU.
  • the communication apparatus includes a transmitting unit configured to transmit scheduling granularity information that indicates a number of symbols in at least one SU for resource scheduling for communications between a user equipment (UE) and the communication apparatus; and a communicating unit configured to communicate with the UE based on the at least one SU.
  • a transmitting unit configured to transmit scheduling granularity information that indicates a number of symbols in at least one SU for resource scheduling for communications between a user equipment (UE) and the communication apparatus
  • UE user equipment
  • the communication apparatus includes one or more processors; and an interface circuit configured to receive scheduling granularity information that indicates a number of symbols in at least one SU for resource scheduling for communications between the communication apparatus and a network device; and communicate with the network device based on the at least one SU.
  • the communication apparatus includes one or more processors; and an interface circuit configured to: transmit scheduling granularity information that indicates a number of symbols in at least one SU for resource scheduling for communications between a user equipment (UE) and the communication apparatus; and communicate with the UE based on the at least one SU.
  • UE user equipment
  • the interface circuit comprises one or more transceivers.
  • an apparatus includes one or more processors and one or more memories.
  • the one or more memories store instructions which, 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 second aspect or one or more implementations of the second aspect.
  • a communication system includes a first communication apparatus configured to perform the method according to the first aspect or one or more implementations of the first aspect.
  • the communication system further includes a second communication apparatus configured to perform the method according to the second aspect or one or more implementations of the second aspect.
  • a non-transitory computer-readable storage medium has instructions stored thereon which, when executed by an apparatus, cause the apparatus to perform the method according to the first aspect or one or more implementations of the first aspect, or the second aspect or one or more implementations of the second aspect.
  • FIG. 1 illustrates a schematic illustration of an example communication system.
  • FIG. 2 illustrates another example communication system.
  • FIG. 3 illustrates an example of an apparatus wirelessly communicating with at least one of two apparatuses in a communication system.
  • FIG. 4 illustrates an example of units or modules in a device or apparatus.
  • FIG. 5 illustrates an example flexible scheduling scheme.
  • FIG. 7 illustrates an example table of a group of time resource allocation indications for normal cyclic prefix (NCP) .
  • FIG. 8 illustrates an example table of a group of time resource allocation indications for extended cyclic prefix (ECP) .
  • ECP extended cyclic prefix
  • FIG. 9 illustrates another example flexible scheduling scheme with a time domain resource allocation indication.
  • FIG. 10 illustrates an example table of a group of physical downlink shared channel (PDSCH) time resource allocation indications for NCP.
  • PDSCH physical downlink shared channel
  • FIG. 11 illustrates an example table of a group of physical uplink shared channel (PUSCH) time resource allocation indications for NCP.
  • PUSCH physical uplink shared channel
  • Wireless communications systems such as fourth generation (4G) system (for example, Long-Term Evolution (LTE) system) , fifth generation (5G) system (for example, New Radio (NR) system) , and sixth generation (6G) system can provide various types of applications, such as message, voice, video, and other data, and various service types, use cases, or/and numerology options.
  • 4G Long-Term Evolution
  • 5G Fifth Generation
  • NR New Radio
  • 6G sixth generation
  • 6G can provide various types of applications, such as message, voice, video, and other data, and various service types, use cases, or/and numerology options.
  • 4G Long-Term Evolution
  • 5G for example, New Radio (NR) system
  • 6G sixth generation
  • the flexible scheduling schemes can facilitate flexible and efficient use of time-frequency resources for wireless communications, for example, by allowing scheduling a resource across the slot boundary.
  • the flexible scheduling schemes allow a variable, configurable scheduling granularity, for example, in terms of a scheduling unit (SU) .
  • the SU can be represented or defined by a number of scheduled symbols (e.g., orthogonal frequency-division multiplexing (OFDM) symbols) .
  • the SU can be represented in terms of another parameter or absolute time.
  • multiple SUs with different numbers of symbols can be configured.
  • one or more SUs can be selected to assign, allocate, or otherwise schedule one or more resources for a particular data transmission.
  • scheduling information or signaling can be configured based on the configurable scheduling granularity.
  • the scheduling information can include a reference point (also referred to as an alignment point) and/or time-domain allocation of the scheduled resources.
  • a format and size of the scheduling signaling can be designed, for example, based on the configurable scheduling granularity.
  • techniques for reducing the number of bits required for the scheduling signaling are described, which can reduce signal overhead and improve communication efficiency.
  • the communication system 100 (which may be a wireless system) comprises a radio access network 120.
  • the radio access network (RAN) 120 may be a next generation (e.g. sixth generation (6G) or later) radio access network, or a legacy (e.g. 5G, 4G, 3G or 2nd generation (2G) ) radio access network.
  • 6G sixth generation
  • 2G 2nd generation
  • One or more communication electronic device (ED) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j may be interconnected to one another or connected to one or more network nodes (170a, 170b, generically referred to as 170) in the radio access network 120.
  • a core network 130 may be a part of the communication system and may be dependent or independent of the radio access technology used in the communication system 100.
  • the communication system 100 may also comprise a public switched telephone network (PSTN) 140, the internet 150, and other networks 160.
  • PSTN public switched telephone network
  • the communication system 100 enables multiple wireless or wired elements to communicate data and other content.
  • the communication system 100 may provide content, such as voice, data, video, and/or text, via broadcast, multicast, groupcast, unicast, etc.
  • the communication system 100 may provide a wide range of communication services and applications (such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc. )
  • the services and/or applications may be mobile broadband (MBB) services, ultra-reliable low-latency communication (URLLC) services, or machine type communication (MTC) services.
  • MBB mobile broadband
  • URLLC ultra-reliable low-latency communication
  • MTC machine type communication
  • the communication system 100 may operate by sharing resources, such as carrier spectrum bandwidth, between its constituent elements.
  • the terrestrial communication system and the non-terrestrial communication system could be considered sub-systems of the communication system.
  • the communication system 100 may include ED 110a, 110b, 110c, 110d (generically referred to as ED 110) , and RAN 120a, 120b.
  • the communication system 100 may also include a non-terrestrial communication network 120c.
  • the 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.
  • the RANs 120a, 120b include respective RAN nodes such as base stations (BSs) 170a, 170b, which may be generically referred to as terrestrial transmit and receive points (T-TRPs) 170a, 170b.
  • BSs base stations
  • T-TRPs terrestrial transmit and receive points
  • the non-terrestrial communication network 120c includes a RAN node such as an access node (or base station) 172, which may be generically referred to as a non-terrestrial transmit and receive point (NT-TRP) 172.
  • a RAN node such as an access node (or base station) 172, which may be generically referred to as a non-terrestrial transmit and receive point (NT-TRP) 172.
  • N-TRP non-terrestrial transmit and receive point
  • 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 non-terrestrial network device works as a transport layer device and the at least one corresponding terrestrial network device works as a RAN node, which communicates with the ED via the non-terrestrial network device.
  • NTN gateway in the ground (i.e., referred as a terrestrial network device) also as a transport layer device to communication with both the NTN device, and the RAN node communicates with the ED via the NTN device and the NTN gateway.
  • the NTN gateway and the RAN node may be located in the same device.
  • Any ED 110 may be alternatively or additionally configured to interface, access, or communicate with any T-TRP 170a, 170b and NT-TRP 172, the Internet 150, the core network 130, the PSTN 140, the other networks 160, or any combination of the preceding.
  • ED 110a may communicate an uplink (UL) and/or downlink (DL) transmission over a terrestrial air interface 190a with T-TRP 170a.
  • the EDs 110a, 110b, 110c, and 110d may also communicate directly with one another via one or more sidelink (SL) air interfaces 190b.
  • ED 110d may communicate an uplink and/or downlink transmission over a non-terrestrial air interface 190c with NT-TRP 172.
  • the air interfaces 190a and 190b may use similar communication technology, such as any suitable radio access technology.
  • the communication system 100 may implement one or more channel access methods, 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) in the air interfaces 190a and 190b.
  • CDMA code division multiple access
  • SDMA space division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • the air interfaces 190a and 190b may utilize other higher dimension signal spaces, which may involve a combination of orthogonal and/or non-orthogonal dimensions.
  • the non-terrestrial air interface 190c can enable communication between the ED 110d and one or multiple NT-TRPs 172 via a wireless link or simply a link.
  • the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs 110 and one or multiple NT-TRPs 172 for multicast transmission.
  • the RANs 120a and 120b are in communication with the core network 130 to provide the EDs 110a 110b, and 110c with various services such as voice, data, and other services.
  • the RANs 120a and 120b and/or the core network 130 may be in direct or indirect communication with one or more other RANs (not shown) , which may or may not be directly served by core network 130, and may or may not employ the same radio access technology as RAN 120a, RAN 120b or both.
  • the core network 130 may also serve as a gateway access between (i) the RANs 120a and 120b or EDs 110a 110b, and 110c or both, and (ii) other networks (such as the PSTN 140, the Internet 150, and the other networks 160) .
  • the EDs 110a 110b, and 110c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and/or protocols. Instead of wireless communication (or in addition thereto) , the EDs 110a 110b, and 110c may communicate via wired communication channels to a service provider or switch (not shown) , and to the Internet 150.
  • PSTN 140 may include circuit switched telephone networks for providing plain old telephone service (POTS) .
  • Internet 150 may include a network of computers and subnets (intranets) or both, and incorporate protocols, such as Internet Protocol (IP) , Transmission Control Protocol (TCP) , User Datagram Protocol (UDP) .
  • IP Internet Protocol
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • EDs 110a 110b, and 110c may be multimode devices capable of operation according to multiple radio access technologies, and incorporate multiple transceivers necessary to support such.
  • the communication system 100 may comprising a sensing agent (not shown in the figure) to manage the sensed data from ED110 and or the T-TRP 170 and/or NT-TRP 172.
  • the sensing agent is located in the T-TRP 170 and/or NT-TRP 172.
  • the sensing agent is a separate node which has interface to communicate with the core network 130 and/or the RAN 120 (e.g., the T-TRP 170 and/or NT-TRP 172) .
  • FIG. 3 illustrates example of an Apparatus 310 wirelessly communicating with at least one of two apparatuses (e.g., Apparatus 320a and Apparatus 320b, referred as Apparatus 320) in a communication system, e.g., the communication system 100, according to one embodiment.
  • the Apparatus 310 may be a UE (e.g., ED 110 in FIG. 3) .
  • the Apparatus 320a may be a terrestrial network device (e.g., T-TRP 170 as shown in FIG. 3)
  • Apparatus 320b may be a non-terrestrial network device (e.g., NT-TRP 172 as shown in FIG. 3) .
  • Apparatus 320a may be a NT-TRP, and 320b may be a T-TRP, both Apparatus 320a and 320b may be T-TRPs or NT-TRPs, according to present disclosure.
  • the ED 110 as an example of the Apparatus 310 is described, and T-TRP 170 as an example of Apparatus 320a is described, and NT-TRP 172 as an example of Apparatus 320a is described.
  • the number of Apparatus 310 e.g.
  • ED 110 could be one or more, and the number of Apparatus 320a and/or 320b could be one or more.
  • one ED110 may be served by only one T-TRP 170 (or one NT-TRP172) , by more than one T-TRP 170, by more than one NT-TRP 172, or by one or more T-TRP 170 and one or more NT-TRP172.
  • the ED 110 is used to connect persons, objects, machines, etc.
  • the ED 110 may be widely used in various scenarios including, for example, cellular communications, 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 twin, industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.
  • D2D device-to-device
  • V2X vehicle to everything
  • P2P peer-to-peer
  • M2M machine-to-machine
  • MTC internet of things
  • IoT internet of things
  • VR virtual reality
  • AR augmented reality
  • Each ED 110 represents any suitable end user device for wireless operation and may include such devices (or may be referred to but not limited to) as a user equipment/terminal device (UE) , a wireless transmit/receive unit (WTRU) , a mobile station, a fixed or mobile subscriber unit, a cellular telephone, a station (STA) , a MTC device, a personal digital assistant (PDA) , a smartphone, a laptop, a computer, a tablet, a wireless sensor, a consumer electronics device, a smart book, a vehicle, a car, a truck, a bus, a train, or an IoT device, wearable devices (such as a watch, a pair of glasses, head mounted equipment, etc.
  • UE user equipment/terminal device
  • WTRU wireless transmit/receive unit
  • mobile station a fixed or mobile subscriber unit
  • STA station
  • MTC device a MTC device
  • PDA personal digital assistant
  • smartphone a laptop
  • a computer
  • the base station 170a and 170b is a T-TRP and will hereafter be referred to as T-TRP 170. Also shown in FIG. 3, a non-terrestrial (NT) device will hereafter be referred to as NT-TRP 172.
  • NT non-terrestrial
  • 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 of more of: connection availability and connection necessity.
  • the ED 110 include at least one processor 210. Only one processor 210 is illustrated to avoid congestion in the drawing.
  • the ED 110 may further include a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 204 may alternatively be panels.
  • the transmitter 201 and the receiver 203 may be integrated, e.g. as a transceiver.
  • the transceiver is configured to modulate data or other content for transmission by at least one antenna 204 or network interface controller (NIC) .
  • NIC network interface controller
  • the transceiver is also configured to demodulate data or other content received by the 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 by wire.
  • Each antenna 204 includes any suitable structure for transmitting and/or receiving wireless or wired signals.
  • the ED 110 may include at least one memory 208. Only the transmitter 201, receiver 203, processor 210, memory 208, and antenna 204 is illustrated for simplicity, but the ED 110 may include one or more other components.
  • the memory 208 stores instructions.
  • the memory 208 may also stores data used, generated, or collected by the ED 110.
  • the memory 208 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by one or more processing unit (s) (e.g., a processor 210) .
  • Each memory 208 includes any suitable volatile and/or non-volatile storage and retrieval device (s) . Any suitable type of memory may be used, such as random access memory (RAM) , read only memory (ROM) , hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, on-processor cache, and the like.
  • RAM random access memory
  • ROM read only memory
  • SIM subscriber identity module
  • SD secure digital
  • the processor 210 performs (or controlling the ED110 to perform) operations described herein as being performed by the ED110. As illustrated below and elsewhere in the present disclosure. For example, the processor 210 performs or controls the ED110 to perform receiving transport blocks (TBs) , using a resource for decoding of one of the received TBs, releasing the resource for decoding of another of the received TBs, and/or receiving configuration information configuring a resource.
  • TBs transport blocks
  • the operation may include those operations related to preparing a transmission for uplink transmission to the NT-TRP 172 and/or the T-TRP 170; those operations related to processing downlink transmissions received from the NT-TRP 172 and/or the T-TRP 170; and those operations related to processing sidelink transmission to and from another ED 110.
  • Processing operations related to preparing a transmission for uplink transmission may include operations such as encoding, modulating, transmit beamforming, and generating symbols for transmission.
  • Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulating and decoding received symbols.
  • Processing operations related to processing sidelink transmissions may include operations such as transmit/receive beamforming, modulating/demodulating and encoding/decoding symbols.
  • a downlink transmission may be received by the receiver 203, possibly using receive beamforming, and the processor 210 may extract signaling from the downlink transmission (e.g. by detecting and/or decoding the signaling) .
  • An example of signaling may be a reference signal transmitted by the NT-TRP 172 and/or by the T-TRP 170.
  • the processor 210 implements the transmit beamforming and/or the receive beamforming based on the indication of beam direction, e.g. beam angle information (BAI) , received from the T-TRP 170.
  • the processor 210 may perform operations relating to network access (e.g.
  • the processor 210 may perform channel estimation, e.g. using a reference signal received from the NT-TRP 172 and/or from the T-TRP 170.
  • the processor 210 may form part of the transmitter 201 and/or part of the receiver 203.
  • the memory 208 may form part of the processor 210.
  • the processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory (e.g. in the memory 208) .
  • some or all of the processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented using dedicated circuitry, such as a programmed field-programmable gate array (FPGA) , an application-specific integrated circuit (ASIC) , or a hardware accelerator such as a graphics processing unit (GPU) or an artificial intelligence (AI) accelerator.
  • FPGA programmed field-programmable gate array
  • ASIC application-specific integrated circuit
  • AI artificial intelligence
  • the ED 110 may an apparatus (also called component) for example, communication module, modem, chip, or chipset, it includes at least one processor 210, and an interface or at least one pin.
  • the transmitter 201 and receiver 203 may be replaced by the interface or at least one pin, wherein the interface or at least one pin is to connect the apparatus (e.g., chip) and other apparatus (e.g., chip, memory, or bus) .
  • the transmitting information to the NT-TRP 172 and/or the T-TRP 170 and/or another ED 110 may be referred as transmitting information to the interface or at least one pin, or as transmitting information to the NT-TRP 172 and/or the T-TRP 170 and/or another ED 110 via the interface or at least one pin, and receiving information from the NT-TRP 172 and/or the T-TRP 170 and/or another ED 110 may be referred as receiving information from the interface or at least one pin, or as receiving information from the NT-TRP 172 and/or the T-TRP 170 and/or another ED 110 via the interface or at least one pin.
  • the information may include control signaling and/or data.
  • the T-TRP 170 include at least one processor 260. Only one processor 260 is illustrated to avoid congestion in the drawing.
  • the T-TRP 170 may further include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 256 may alternatively be panels.
  • the transmitter 252 and the receiver 254 may be integrated as a transceiver.
  • the T-TRP 170 may further include at least one memory 258.
  • the T-TRP 170 may further include scheduler 253. Only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256 and scheduler 253 are illustrated for simplicity, but the T-TRP may include one or more other components.
  • the T-TRP 170 may be known by other names in some implementations, such as a base station, a base transceiver station (BTS) , a radio base station, a network node, a network device, a device on the network side, a transmit/receive node, a Node B, an evolved NodeB (eNodeB or eNB) , a Home eNodeB, a next Generation NodeB (gNB) , a transmission point (TP) , a site controller, an access point (AP) , a wireless router, a relay station, a terrestrial node, a terrestrial network device, a terrestrial base station, a base band unit (BBU) , a remote radio unit (RRU) , an active antenna unit (AAU) , a remote radio head (RRH) , a central unit (CU) , a distributed unit (DU) , a positioning node, among other possibilities.
  • BBU base band unit
  • RRU remote radio unit
  • the parts of the T-TRP 170 may be distributed.
  • some of the modules of the T-TRP 170 may be located remote from the equipment that houses the antennas 256 for the T-TRP 170, and may be coupled to the equipment that houses the antennas 256 over a communication link (not shown) sometimes known as front haul, such as common public radio interface (CPRI) .
  • the term T-TRP 170 may also refer to modules on the network side that perform processing operations, such as determining the location of the ED 110, resource allocation (scheduling) , message generation, and encoding/decoding, and that are not necessarily part of the equipment that houses the antennas 256 of the T-TRP 170.
  • the modules may also be coupled to other T-TRPs.
  • the T-TRP 170 may actually be a plurality of T-TRPs that are operating together to serve the ED 110, e.g. through the use of coordinated multipoint transmissions.
  • the processor 260 performs operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to the T-TRP 170 and/or NT-TRP 172, and processing a transmission received over backhaul from the T-TRP 170 and/or NT-TRP 172.
  • Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. multiple input multiple output (MIMO) precoding) , transmit beamforming, and generating symbols for transmission.
  • MIMO multiple input multiple output
  • Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols.
  • the processor 260 may also perform operations relating to network access (e.g. initial access) and/or downlink synchronization, such as generating the content of synchronization signal blocks (SSBs) , generating the system information, etc.
  • the processor 260 also generates an indication of beam direction, e.g. BAI, which may be scheduled for transmission by a scheduler 253.
  • the processor 260 performs other network-side processing operations described herein, such as determining the location of the ED 110, determining where to deploy the NT-TRP 172, etc.
  • the processor 260 may generate signaling, e.g. to configure one or more parameters of the ED 110 and/or one or more parameters of the NT-TRP 172. Any signaling generated by the processor 260 is sent by the transmitter 252.
  • the scheduler 253 may be coupled to the processor 260 or integrated in the processor 260.
  • the scheduler 253 may be included within or operated separately from the T-TRP 170.
  • the scheduler 253 may schedule uplink, downlink, sidelink, and/or backhaul transmissions, including issuing scheduling grants and/or configuring scheduling-free (e.g., “configured grant” ) resources.
  • the memory 258 is configured to store information, and optionally data.
  • the memory 258 stores instructions and data used, generated, or collected by the T-TRP 170.
  • the memory 258 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by the processor 260.
  • the processor 260 may form part of the transmitter 252 and/or part of the receiver 254. Also, although not illustrated, the processor 260 may implement the scheduler 253. Although not illustrated, the memory 258 may form part of the processor 260.
  • the processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 258.
  • some or all of the processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC.
  • the T-TRP 170 When the T-TRP 170 is an apparatus (also called as component, for example, 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, the transmitter 252 and receiver 254 may be replaced by the interface or at least one pin, wherein the interface or at least one pin is to connect the apparatus (e.g., chip) and other apparatus (e.g., chip, memory, or bus) .
  • the apparatus e.g., chip
  • other apparatus e.g., chip, memory, or bus
  • the transmitting information to the NT-TRP 172 and/or the T-TRP 170 and/or ED 110 may be referred as transmitting information to the interface or at least one pin, and receiving information from the NT-TRP 172 and/or the T-TRP 170 and/or ED 110 may be referred as receiving information from the interface or at least one pin.
  • the information may include control signaling and/or data.
  • the NT-TRP 172 is illustrated as a drone only as an example, the NT-TRP 172 may be implemented in any suitable non-terrestrial form, such as satellites and high altitude platforms, including international mobile telecommunication base stations and unmanned aerial vehicles, for example. Also, the NT-TRP 172 may be known by other names in some implementations, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station.
  • the T-TRP 170 may further include at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 256 may alternatively be panels.
  • the transmitter 252 and the receiver 254 may be integrated as a transceiver.
  • the T-TRP 170 may further include at least one memory 258.
  • the T-TRP 170 may further include scheduler 253. Only the transmitter 252, receiver 254, processor 260, memory 258, antenna 256 and scheduler 253 are illustrated for simplicity, but the T-TRP may include one or more other components.
  • the NT-TRP 172 include at least one processor 276. Only one processor 276 is illustrated to avoid congestion in the drawing.
  • 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 illustrated to avoid congestion in the drawing. One, some, or all of the antennas may alternatively be panels.
  • the transmitter 272 and the receiver 274 may be integrated as a transceiver.
  • the NT-TRP 172 may further include at least one memory 278.
  • the NT-TRP 172 may further include scheduler. Only the transmitter 272, receiver 274, processor 276, memory 278, antenna 280 are illustrated for simplicity, but the NT-TRP may include one or more other components.
  • the NT-TRP 172 include a processor 276 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to T-TRP 170 and/or another NT-TRP 172, and processing a transmission received over backhaul from the T-TRP 170 and/or another NT-TRP 172.
  • Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. MIMO precoding) , transmit beamforming, and generating symbols for transmission.
  • Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols.
  • the processor 276 implements the transmit beamforming and/or receive beamforming based on beam direction information (e.g. BAI) received from the T-TRP 170.
  • the processor 276 may generate signaling, e.g. to configure one or more parameters of the ED 110.
  • the NT-TRP 172 implements physical layer processing, but does not implement higher layer functions such as functions at the medium access control (MAC) or radio link control (RLC) layer. As this is only an example, more generally, the NT-TRP 172 may implement higher layer functions in addition to physical layer processing.
  • MAC medium access control
  • RLC radio link control
  • the memory 278 is configured to store information and optionally data.
  • the memory 258 stores instructions and data used, generated, or collected by the NT-TRP 172.
  • the memory 278 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by the processor 276.
  • the processor 276 may form part of the transmitter 272 and/or part of the receiver 274.
  • the memory 278 may form part of the processor 276.
  • the processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 278.
  • some or all of the processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC.
  • the NT-TRP 172 may actually be a plurality of NT-TRPs that are operating together to serve the ED 110, e.g. through coordinated multipoint transmissions.
  • Signaling may alternatively be called control signaling, control message, control information, or message for simplicity.
  • Signaling between a BS (e.g., the network node 170) and a terminal or sensing device (e.g., ED 110) , or signaling between different terminal or sensing device (e.g., between ED 110i and ED110j) may be carried in physical layer signaling (also called as dynamic signaling) , which is transmitted in a physical layer control channel.
  • physical layer signaling may be known as downlink control information (DCI) which is transmitted in a physical downlink control channel (PDCCH) .
  • DCI downlink control information
  • a different application or service type may be configured with a different scheduling granularity.
  • an URLLC service may need a quicker turn-around traffic to achieve low-latency and high reliability transmission, thus a shorter (than 14 symbols) scheduling granularity such as scheduling unit of 7 or 6 symbols can be configured to accommodate this latency requirement; on the other hand, for transmission of high traffic loading or with high data rate such as eMBB service, a larger scheduling granularity such as scheduling unit of 14 or 28 symbols can be configured to accommodate this data rate requirement.
  • the unit of the number of symbols in a scheduling signaling may be based on a base or reference numerology such as 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz subcarrier spacing (SCS) with either NCP or ECP; for example, a unit of 7 symbols of 15kHz SCS with NCP, a unit of 12 symbols of 60kHz with ECP.
  • a base or reference numerology such as 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz subcarrier spacing (SCS) with either NCP or ECP; for example, a unit of 7 symbols of 15kHz SCS with NCP, a unit of 12 symbols of 60kHz with ECP.
  • SCS subcarrier spacing
  • a PDCCH monitoring occasion is for a PDCCH transmission (that carries out DCI, for example) in a CORESET, which consists of a number of resource element groups (REGs) within specific time and frequency domain resources.
  • a PDCCH uses control channel elements (CCEs) for its structure.
  • a CCE is a group of REGs, and the PDCCH can consist of one or more CCEs.
  • the number of CCEs used by a PDCCH is referred to as its aggregation level. Higher aggregation levels mean lower coding rates or more robust coding, making them more suitable for UEs with poor channel conditions.
  • the CORESET allocations or PDCCH monitor occasions can be configured as one of cell-common, group common or UE specific configuration; and moreover, a configuration of CORESET and/or PDCCH monitoring occasions may be decoupled from or independent of a configuration of a scheduling granularity.
  • a configuration of a scheduling granularity can be UE specific, of cell common or of group common.
  • a configuration of a scheduling granularity can be application or service specific (such as URLLC, eMBB, etc) .
  • a scheduling granularity may be configured or indicated in a semi-static signaling such as RRC, MAC-CE, or/and dynamic signaling such as DCI, or any combination thereof.
  • a scheduling signaling may comprise one or more time domain resource allocations within a scheduling granularity or scheduling unit, each time domain resource allocation may comprise (within the scheduling unit) start-symbol and how many consecutive symbols, which can be denoted by one SLIV.
  • the 15kHz is used as a reference numerology
  • an alignment or reference point 510a-e (generically referred to as 520) is defined/configured based on a frame
  • a time duration 520a, 520b (generically referred to as 520) (e.g., in terms of a number of subframe or symbols) between two reference (or alignment) points 510;
  • a scheduling granularity is also configured as shown in FIG. 5.
  • the time duration between two adjacent reference points may be configured as the scheduling granularity (for example, N symbols) in FIG. 5, where a time for transmitting a scheduling signaling may be referenced to the reference or alignment point.
  • the time duration between two adjacent reference points and the scheduling granularity may be configured separately or independently, where a time for transmitting a scheduling signaling may be referenced to a PDCCH monitoring occasion 530a, 530b, 530 c (generically referred to as 530) .
  • a scheduling signaling, or DCI may comprise an indication of time domain resource allocation (s) in a DCI element field, where the indication may require one or more bits (e.g., 7 bits) to indicate time domain allocation (s) , as well as other information bits to indicate frequency domain resource allocation (s) .
  • the frequency domain allocations can use the same indication techiniques as used in the NR.
  • a scheduling granularity is N symbols in terms of 15kHz numerology, and applied to 30kHz numerology signal scheduling, the scheduling granularity is 2N symbols which is shown in FIG. 5, and this scalable rule may be applied to other numerology options in the 2 k *15KHz numerology family, where k is a non-negative integer.
  • N symbols applied for the reference numerology also applied to other numerologies, i.e., all the numerologies use the same N symbols, but beacause the symbol length for different numerologies are different, the time duration of the scheduling granularity for different numerologies are different in terms of the seconds.
  • the scheduling granularity can be numerolgoy-specific configured, for example, in semi-static way such as RRC or MAC-CE, thus making the scheduling even more flexible due to separate or independent configurations on different numerology options.
  • a time domain resource allocation provided by a scheduling signaling such as DCI may comprise (within a scheduling unit) start-symbol (S) and how many consecutive symbols (L) , which can be denoted by SLIV.
  • the scheduling signaling may comprise an indication of a reference time as a reference for the time domain resource allocation, where the reference time is a starting time point relative to the time domain resource allocation, and the reference time may be in terms of a number of scheduling units, a number of subframes, a number of slots or a number of symbols from a reference point 510 or a PDCCH monitoring occasion 530 as described above.
  • a scheduled time domain resource may be uniquely determined by the reference time and SLIV.
  • a scheduled time domain resource may be located within a scheduling unit at SLIV that is N scheduling units (N is a non-negative integer) away from the scheduling moment, a reference point 510 or a PDCCH monitoring occasion 530.
  • DCI indication option 1 is described where a SLIV for a time domain resource allocation is calculated.
  • a scheduling unit with a granularity of Lz symbols based on a base or reference numerology such as 15kHz SCS (with NCP) , a SLIV (assuming scheduling a time resource with S and L) is determined based on the procedure mentioned above and also shown as 610 in FIG. 6.
  • the indication bits in the table 620 of FIG. 6 is obtained based on the calculation method 610 shown in FIG. 6.
  • a scheduling granularity with smaller number of symbols (Lz) such as 6 or 7 symbols (comparing with slot-based 14 symbols) may require fewer number of bits such as (up to) 5 bits, and these indication bits may be included in a DCI element field for an indication of time domain resource allocation.
  • a scheduling granularity with 14 symbols (Lz) may require (up to) 7 bits, and these indication bits may be included in a DCI element field for an indication of time domain resource allocation.
  • a scheduling granularity with larger number of symbols (Lz) such as 28 symbols (comparing with slot-based 14 symbols) may require more number of bits such as (up to) 9 bits, and these indication bits may be included in a DCI element field for an indication of time domain resource allocation.
  • a different scheduling granularity may be configured for a different UE, application or service type, mobility type or/and numerology usage, etc. Furthermore or alternatively, a different scheduling granularity may be configured based on a different requirements or demands in terms of latency, data rate, reliability or other performance key indicator, etc.
  • a time domain resource allocation may comprise (within the scheduling unit) a start symbol and how many consecutive symbols, where the time domain resource allocation can be indicated by a time allocation resource index (or indices) , which is (or are) predefined or tabulated for a group of time resource allocations, each comprising start-symbol and how many consecutive symbols, as shown in FIG. 7 (for NCP) and FIG. 8 (for ECP) .
  • the total number of (S, L) pairs or time domain allocations can be uniquely determined for a scheduling granularity (or unit) . Part or all of the total number of (S, L) pairs or time domain allocations can be tabulated such as shown in FIG. 7 and FIG. 8. If part of the total number of (S, L) pairs or time domain allocations within a scheduling granularity is tabulated, a reduced number of indication bits can be used for the time resource indication; in this way, the indication bits included in a scheduling signaling or DCI for time domain resource can be reduced.
  • a time domain resource allocation for PDSCH or PUSCH can be indicated by (PDSCH or PUSCH) resource index for a configured scheduling granularity or scheduling unit Lz (for NCP) or Lz’ (for ECP) .
  • the indication bits required to uniquely indicate each time domain resource allocation depend on the total number of time domain resource allocations in each table. In some implementation, part of the total time domain resource allocations is selected. For example, L values of 2, 4 or/and 7 are used, to form a resource allocation table, thus leading to less number of rows in the resource allocation table, where the number of the indication bits can be reduced to indicate a time domain resource allocation (in a row) .
  • a different scheduling granularity may be configured for a different UE, application or service type, mobility type or/and numerology usage, etc. Furthermore or alternatively, a different scheduling granularity may be configured based on a different requirements or demands in terms of latency, data rate, reliability or other performance key indicator, etc.
  • the starting symbol S relative to the start of the SU, and the number of consecutive symbols L counting from the symbol S allocated for the PUSCH are determined from the start and length indicator SLIV of the indexed row.
  • a total number of bits for indication of each row in DCI can be calculated based on candidate values of K 2 , S and L.
  • a subset of all (K 2 , S, L) combinations can be selected to form a reduced table to reduce the number of bits needed to represent the indexes, thus reducing the signaling overhead.
  • the scheduling granularity information indicates that a number of symbols in a first SU corresponding to a first numerology is the same as or different from a number of symbols in a second SU corresponding to a second numerology.
  • the first SU corresponding to a first numerology of 15kHz SCS and NCP and the second SU corresponding to a second numerology of 30kHz SCS and NCP can each include 7 symbols.
  • the first SU corresponding to the first numerology of 15kHz SCS and NCP includes 7 symbols
  • the second SU corresponding to the second numerology of 30kHz SCS and NCP can include 14, 28, or 56 symbols.
  • the scheduling granularity information includes a scheduling granularity index that represents a SU corresonding to a numerology among multiple candidate SUs corresonding to multiple numerologies.
  • a mapping relationship can be eatblished between multiple scheduling granularity indexes and multiple SUs corresponding to multiple numerologies, for example, as shown in Table 1300 in FIG. 13.
  • the scheduling granularity information indicates one of the plurality of SUs is a default SU.
  • the default SU can be a preconfigured SU that the base station 1205 and the UE 1215 understands to use in the absence of any other signaling to inform, change, or update the SU choice.
  • the default SU can be an SU that is compatbile with a legacy standard (e.g., a slot-based SU of 14 symbols per SU) or another SU.
  • the default SU is configured, for example, based on an application or service type of a current data transission between the base station 1205 and the UE 1215.
  • RRC can be unicast, group-cast, or broadcast,
  • the information can include information that indicates a granuality for a PDCCH resource, for example, in terms of a number of symbols in a SU for a resource for transmitting/receiving a PDCCH.
  • the information can indicate to the UE 1215 which one of the at least one SU to use for receiving a DCI in a PDCCH.
  • the information can be initially transmitted by the base station 1205 to the UE 1215 in a system information.
  • the information can be transmitted in an RRC message, MAC-CE or DCI to indicate a SU to use (or switching to a new SU to use) after the multiple SUs are configured (for example, by the RRC message) .
  • a default SU to transmit DCI via PDCCH can be configured as discussed above.
  • the one or more of the above parameters or pieces of information can be sent in one step (e.g., in a same data packet) or can be sent in multiple steps or in multiple occasions.
  • some of the parameters or information e.g., default or intial parameters
  • SIB system infromation block
  • some other parameters or information can be sent in another message or signaling (e.g., RRC message, MAC-CE, or DCI) at another time instance.
  • multiple flexible granuality and scheduling configurations can be pre-configured, and a DCI can include an index to activate one of the pre-configured configurations, without the need to transmit a RRC to indicate the granuality and scheduling parameters.
  • the step 1210 is optional, and when absent, the one or more of the above parmeters are pre-defined, for example, associating with above different scenarios (e.g., different application types, service types, mobility types, use cases, or/and numerologies) .
  • above different scenarios e.g., different application types, service types, mobility types, use cases, or/and numerologies
  • Step 1220 the base station 1205 transmits scheduling information to the UE for scheduling DL data or UL data, and accordingly, the UE 1215 receives the scheduling information.
  • the scheduling information may be DCI.
  • the detailed information inlcuded in DCI is described above.
  • the DCI comprises time offset information indicating a time offset (e.g., K 0 or K 2 ) of a scheduled resource relative to the alignment point or relative to the location of the PDCCH (e.g., a PDCCH occasion as disccused in connection with FIGS. 5 and 9) .
  • the DCI comprises a start and length indicator value (SLIV) field for determining a location of a scheduled resource, wherein the SLIV field indicates a starting symbol index (S) and a number of consecutive symbols (L) within an SU, wherein the SU belongs to or is one of the at least one SU.
  • SLIV start and length indicator value
  • the SU is either the default SU, or other activated/indicated SU.
  • the SLIV field comprises an index indicating one of a total number of (S, L) combinations.
  • the total number of (S, L) combinations include all possible combinations with valid S and L.
  • the SLIV field comprises an index indicating one of a subset of a total number of (S, L) combinations, for example, to save the number of bits used to represent the index.
  • a table or another data structure can be used to store the mapping between the index values and the (S, L) combinations, for example, as shown in one of the tables in FIGS. 7, 8, 10 and 11.
  • the mapping can be pre-configured and pre-defined, for example, before step 1210.
  • the base station may transmit the table to the UE in system information or the UE may store, download, or otherwise receive the table.
  • the subset of the total number of (S, L) combinations includes a reduced number of possible combinations with valid S and L, to save the number of bits used for representing the combinations.
  • the DCI comprises a time allocation index indicating one of a (k, S, L) combination, wherein k represents a time offset (e.g., K 0 or K 2 ) , S represents a starting symbol index (S) , and L represents a number of consecutive symbols (L) of a scheduled resource.
  • the S and L can together be repsrented by a SLIV value.
  • the time resource allocation with combinations of selected (k, S, L) may be predefined in a table (e.g., table 1000 or 1100) or be configured by a RRC message as multiple entries, for example, as discussed above.
  • a subset of the combinations can be selected and stored in one or more tables.
  • the base station 1205 can select one of the one or more tables and select one of the index from the selected table to indicate the time allocation of the schedules resource to the UE 1215.
  • Step 1230 the UE 1215 and base station 1205 perform DL and/or UL data transmission according to the information and the scheduling information.
  • the UE 1215 and base station 1205 communicate with each other based on the at least one SU, for example, by transmitting/receiving DL and or UL data using the scheduled resource (e.g., in PDSCH or PUSCH) indicated by the DCI.
  • the base station 1205 can determine, based on the at least one SU, the scheduled resource in PDSCH for the DL data transmission and/or the scheduled resource in PUSCH for the UL data transmission.
  • the base station 1205 can include in the DCI the time allocation indication (e.g., (k, S, L) or the SLIV field) of the scheduled resource, and use the scheduled resource for the DL and/or UL data transmission.
  • the UE 1215 can receive and decode DCI, for example, based on the information that indicates the granuality for the PDCCH resource.
  • the UE 1215 can determine, based on the at least one SU and the time allocation index (e.g., (k, S, L) or the SLIV field) included in the DCI, the scheduled resource for the DL and/or UL data transmission.
  • the UE 1215 can then use the scheduled resource for the DL and/or UL data transmission.
  • an apparatus/chipset system comprising means (e.g., at least one processor) to implement a method implemented by (or at) a UE of the present disclosure.
  • the apparatus/chipset system may be the UE (that is, a terminal device) or a module/component in the UE.
  • the at least one processor may execute instructions stored in a computer-readable medium to implement the method.
  • the apparatus/chipset system may include corresponding modules or units configured to implement methods and/or embodiments described herein.
  • the apparatus/chipset system can include a processing unit, and a communication unit (including one or more of a transmitting unit and receiving unit) , as shown in FIG. 4.
  • the apparatus/chipset system includes a receiving unit configured to receive scheduling granularity information that indicates a number of symbols in at least one SU for resource scheduling for communications between a user equipment (UE) and a network device; and a communicating unit configured to communicate with the network device based on the at least one SU.
  • the apparatus/chipset system may include one or more processors/processor cores, and an interface circuit.
  • the apparatus/chipset system includes one or more processors; and an interface circuit configured to: receive scheduling granularity information that indicates a number of symbols in at least one SU for resource scheduling for communications between a user equipment (UE) and a network device; and communicate with the network device based on the at least one SU.
  • the apparatus/chipset system includes may further include a storage unit configured to store apparatus program code (or instructions) and/or data.
  • an apparatus/chipset system comprising means (e.g., at least one processor) to implement the method implemented by (or at) a network device (e.g., base station) of the present disclosure.
  • the apparatus/chipset system may be the network device or a module/component in the network device.
  • the at least one processor may execute instructions stored in a computer-readable medium to implement the method.
  • a system comprising at least one of an apparatus in (or at) a UE of the present disclosure, or an apparatus in (or at) a network device of the present disclosure.
  • the apparatus/chipset system may include corresponding modules or units configured to implement methods and/or embodiments described herein.
  • the apparatus/chipset system can include a processing unit, and a communication unit (including one or more of a transmitting unit and receiving unit) , as shown in FIG. 4.
  • the apparatus/chipset system includes a transmitting unit configured to transmit scheduling granularity information that indicates a number of symbols in at least one SU for resource scheduling for communications between a user equipment (UE) and a network device; and a communicating unit configured to communicate with the UE based on the at least one SU.
  • the apparatus/chipset system may include one or more processors/processor cores, and an interface circuit.
  • a method performed by a system comprising at least one of an apparatus in (or at) a UE of the present disclosure, and an apparatus in (or at) a network device of the present disclosure.
  • a computer program comprising instructions.
  • the instructions when executed by a processor, may cause the processor to implement a method of the present disclosure.
  • a non-transitory computer-readable medium storing instructions, the instructions, when executed by a processor, may cause the processor to implement a method of the present disclosure.
  • next generation e.g. sixth generation (6G) or later
  • legacy e.g. 5G, 4G, 3G or 2G
  • any module, component, or device disclosed herein that executes instructions may include, or otherwise have access to, a non-transitory computer/processor readable storage medium or media for storage of information, such as computer/processor readable instructions, data structures, program modules and/or other data.
  • non-transitory computer/processor readable storage media includes magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, optical disks such as compact disc read-only memory (CD-ROM) , digital video discs or digital versatile discs (i.e., DVDs) , Blu-ray Disc TM , or other optical storage, volatile and non-volatile, removable and non-removable media implemented in any method or technology, random-access memory (RAM) , read-only memory (ROM) , electrically erasable programmable read-only memory (EEPROM) , flash memory or other memory technology. Any such non-transitory computer/processor storage media may be part of a device/apparatus or accessible or connectable thereto. Computer/processor readable/executable instructions to implement a method, an application or a module described herein may be stored or otherwise held by such non-transitory computer/processor readable storage media.
  • message in the disclosure could be replaced with information, which may be carried in one single message, or be carried in more than one separate message.
  • the word “a” or “an” when used in conjunction with the term “comprising” or “including” in the claims and/or the specification may mean “one” , but it is also consistent with the meaning of “one or more” , “at least one” , and “one or more than one” unless the content clearly dictates otherwise.
  • the word “another” may mean at least a second or more unless the content clearly dictates otherwise.
  • the words “first” , “second” , etc., when used before a same term does not mean an order or a sequence of the term.
  • first ED and the “second ED” means two different EDs without specially indicated
  • first step and the “second step” means two different operating steps without specially indicated, but does not mean the first step have to happen before the second step.
  • the real order depends on the logic of the two steps.
  • Coupled can have several different meanings depending on the context in which these terms are used.
  • the terms coupled, coupling, or connected can indicate that two elements or devices are directly connected to one another or connected to one another through one or more intermediate elements or devices via a mechanical element depending on the particular context.
  • the present disclosure encompasses various embodiments, including not only method embodiments, but also other embodiments such as apparatus embodiments and embodiments related to non-transitory computer readable storage media. Embodiments may incorporate, individually or in combinations, the features disclosed herein.
  • the term “receive” , “detect” and “decode” as used herein can have several different meanings depending on the context in which these terms are used.
  • the term “receive” may indicate that information (e.g., DCI, or MAC-CE, RRC signaling or TB) is received successfully by the receiving node, which means the receiving side correctly detect and decode it.
  • “receive” may cover “detect” and “decode” or may indicates same thing, e.g., “receive paging” means decoding paging correctly and obtaining the paging successfully, accordingly, “the receiving side does not receive paging” means the receiving side does not detect and/or decoding the paging.
  • paging is not received means the receiving side tries to detect and/or decoding the paging, but not obtain the paging successfully.
  • the term “receive” may sometimes indicate that a signal arrives at the receiving side, but does not mean the information in the signal is detected and decoded correctly, then the receiving side need perform detecting and decoding on the signal to obtain the information carried in the signal. In this scenario, “receive” , “detect” and “decode” may indicate different procedure at receiving side to obtain the information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande concerne des procédés de communication et des appareils de communication. Un procédé donné à titre d'exemple consiste à recevoir des informations de granularité de planification qui indiquent un nombre de symboles dans au moins une unité de planification (SU) pour la planification de ressources pour des communications entre un équipement utilisateur (UE) et un dispositif de réseau ; et communiquer avec le dispositif de réseau sur la base de ladite SU.
PCT/CN2024/096314 2024-03-28 2024-05-30 Procédé, appareil et système de planification flexible Pending WO2025200119A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463571092P 2024-03-28 2024-03-28
US63/571,092 2024-03-28

Publications (1)

Publication Number Publication Date
WO2025200119A1 true WO2025200119A1 (fr) 2025-10-02

Family

ID=97216997

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/096314 Pending WO2025200119A1 (fr) 2024-03-28 2024-05-30 Procédé, appareil et système de planification flexible

Country Status (1)

Country Link
WO (1) WO2025200119A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111602444A (zh) * 2018-01-12 2020-08-28 瑞典爱立信有限公司 调度请求资源配置
WO2021201611A1 (fr) * 2020-04-01 2021-10-07 삼성전자 주식회사 Procédé et dispositif de prise en charge d'un accès aléatoire pour un terminal à faible capacité dans un système de communication sans fil
CN114696979A (zh) * 2020-12-31 2022-07-01 维沃移动通信有限公司 信道的调度方法及通信设备
CN116033564A (zh) * 2022-12-15 2023-04-28 南京南瑞信息通信科技有限公司 5G能源互联网中多粒度FlexE切片调度方法及介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111602444A (zh) * 2018-01-12 2020-08-28 瑞典爱立信有限公司 调度请求资源配置
WO2021201611A1 (fr) * 2020-04-01 2021-10-07 삼성전자 주식회사 Procédé et dispositif de prise en charge d'un accès aléatoire pour un terminal à faible capacité dans un système de communication sans fil
CN114696979A (zh) * 2020-12-31 2022-07-01 维沃移动通信有限公司 信道的调度方法及通信设备
CN116033564A (zh) * 2022-12-15 2023-04-28 南京南瑞信息通信科技有限公司 5G能源互联网中多粒度FlexE切片调度方法及介质

Similar Documents

Publication Publication Date Title
US12219579B2 (en) Method and device for transmitting/receiving downlink control information in wireless communication system
CN115336213B (zh) Harq-ack发送方法、用户设备和存储介质及harq-ack接收方法和基站
US12238713B2 (en) Method and apparatus for transmitting or receiving downlink channel from multiple transmission/reception points in wireless communication system
CN112449746B (zh) 发送/接收下行链路控制信道的方法和设备
US20230422271A1 (en) Apparatus and method for communicating two stage dci
US11310779B2 (en) Method and apparatus for transmitting/receiving control information in wireless communication system
US9894651B2 (en) Methods and apparatus for resource allocation for D2D communications
KR102413069B1 (ko) 무선통신 시스템에서 단말을 위한 제어 채널 전송 방법 및 장치
CN107241178B (zh) 在无线通信系统中接收控制信息的方法和装置
US12133161B2 (en) Method and apparatus of explicit linkage between repetitive transmission and reception for downlink control information in wireless communication system
KR102202612B1 (ko) 다운링크 송신들의 구성
CN116018865A (zh) 无线通信系统中用于分配频率资源的方法和装置
WO2010133043A1 (fr) Procédé de répartition de multiples sous-trames et système, terminal et station de base correspondants
KR20220144706A (ko) 네트워크 협력 통신에서 하향링크 제어정보 반복 전송 방법 및 장치
CN114503635B (zh) 用于针对无线通信传输数据的方法和设备
US20190349919A1 (en) Method and device for transmitting/receiving uplink control information in wireless communication system
US12074822B2 (en) Method and apparatus for reporting channel state information through repeated uplink data transmission in network cooperative communication
US20230224824A1 (en) Control information transmission method and device for network cooperative communication of wireless communication system
CN116724511A (zh) 用于网络协作通信的harq-ack反馈发送或接收的方法和设备
CN116349173A (zh) 无线通信系统中重复发送/接收下行链路控制信息的方法和设备
CN116471673A (zh) 执行通信的方法、用户设备、基站、处理装置和介质
US20250167946A1 (en) Method and apparatus for applying transmission beam of uplink control channel in wireless communication system
CN118743295A (zh) 用于两级下行控制信息的混合自动重传请求确认的系统和方法
US20250212208A1 (en) Method, user device, processing device, and storage medium for uplink signal transmission, and method and base station for uplink signal reception
US10880053B2 (en) Wireless device, a network node and methods therein for handling transmissions in a wireless communications network

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24933135

Country of ref document: EP

Kind code of ref document: A1