Method and apparatus for determining uplink / downlink transport block size and modulation coding scheme

Abstract

The disclosure relates to a method for supporting a fifth generation (5G) communication system or a sixth generation (6G) communication system having a higher data rate than a fourth generation (4G) communication system such as long term evolution (LTE). A non-terrestrial network (NTN) node transmits configuration information including an indication of a maximum transport block size (TBS) for a physical uplink shared channel (PUSCH) transmission or a physical downlink shared channel (PDSCH). A TBS for the PUSCH or the PDSCH is determined based on at least the indicated TBS; and a maximum modulation coding scheme (MCS) for the PUSCH transmission or the PDSCH transmission is signaled, or whether the PUSCH transmission or the PDSCH transmission uses a default MCS, or a MCS is determined based on at least the indicated maximum MCS; and the PUSCH is transmitted or the PDSCH is received based on the determined TBS and the determined MCS. The maximum TBS, the maximum MCS, or a number of hybrid automatic repeat request (HARQ) processes are indicated by a master information block (MIB), a system information block (SIB), or radio resource control (RRC) signaling.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications with large propagation delays, and more specifically to the determination of UL / DL TBS and MCS, optionally considering HARQ operation in conjunction with the large propagation delay between the BS and UE. Background Technology

[0002] To meet the ever-increasing demand for wireless data services since the deployment of 4G or LTE communication systems, and to enable various vertical applications, efforts have been made to develop and deploy improved 5G and / or New Radio (NR) or quasi-5G / NR communication systems. Therefore, 5G / NR or quasi-5G / NR communication systems are also referred to as “super 4G networks” or “post-LTE systems.” 5G / NR communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (such as 6 GHz) to achieve robust coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technology are discussed in 5G / NR communication systems.

[0003] In addition, in 5G / NR communication systems, the development of system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-density networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), receiver interference cancellation, etc., is underway.

[0004] The discussion of 5G systems and related technologies is for informational purposes only. Some embodiments of this disclosure can be implemented in 5G systems, 6th generation (6G) systems, or even newer versions that may use terahertz (THz) frequency bands. However, this disclosure is not limited to any particular type of system or associated frequency band, and embodiments of this disclosure can be used in conjunction with any frequency band. For example, aspects of this disclosure can also be applied to the deployment of 5G communication systems, 6G communication systems, or communications using terahertz frequency bands.

[0005] Given the generational evolution of wireless communication, technologies primarily designed for human services have been developed, such as voice calls, multimedia services, and data services. Following the commercialization of 5G (5th generation) communication systems, the number of connected devices is expected to grow exponentially. These devices will increasingly connect to communication networks. Examples of connected things can include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve due to various forming factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. Efforts are underway to develop improved 6G communication systems to provide a wide range of services by connecting hundreds of billions of devices and things in 6G (6th generation). For these reasons, 6G communication systems are referred to as "beyond 5G" systems.

[0006] The 6G communication system, which is expected to be commercially available around 2030, will have peak data rates in the terabit (1,000 gigabit) range and radio latency of less than 100 μsec, making it 50 times faster than 5G communication systems and with 1 / 10 of their radio latency.

[0007] To achieve such high data rates and ultra-low latency, 6G communication systems have been considered for implementation in terahertz bands (e.g., the 95 GHz to 3 THz band). Given that path loss and atmospheric absorption are more severe in the terahertz band than in the millimeter-wave bands introduced in 5G, technologies to ensure signal transmission distance (i.e., coverage) will become even more critical. Key technologies for ensuring coverage include the development of radio frequency (RF) components, antennas, new waveforms with better coverage than orthogonal frequency division multiplexing (OFDM) schemes, beamforming and massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, and multi-antenna transmission technologies such as massive MIMO. Furthermore, new technologies for improving terahertz band signal coverage have been discussed, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS).

[0008] Furthermore, to improve spectrum efficiency and overall network performance, the following technologies have been developed for 6G communication systems: full-duplex technology for enabling uplink and downlink transmissions to use the same frequency resources simultaneously; network technologies for integrated utilization of satellites, High Altitude Platform Radios (HAPS), etc.; improved network architectures to support mobile base stations and achieve network operation optimization and automation; dynamic spectrum sharing technology based on predictive spectrum use via conflict avoidance; the use of artificial intelligence (AI) in wireless communication to improve overall network operation by leveraging AI from the 6G development design phase and internalizing end-to-end AI support functions; and next-generation distributed computing technologies to overcome the limits of UE computing capabilities and compute network resources (such as mobile edge computing (MEC), cloud, etc.) through achievable ultra-high performance communication. Additionally, efforts continue to be made to enhance connectivity between devices, optimize networks, promote the software-defined networking of network entities, and improve the openness of wireless communication by designing new protocols for use in 6G communication networks, developing mechanisms for achieving hardware-based secure environments and secure data usage, and developing technologies for maintaining privacy.

[0009] Research and development of hyper-connected 6G communication systems, including human-to-machine (P2M) and machine-to-machine (M2M) communication, are expected to enable future hyper-connected experiences. Specifically, 6G communication systems are anticipated to provide services such as truly immersive extended reality (XR), high-fidelity mobile holograms, and digital copies. Furthermore, 6G communication systems will be used to provide services such as enhanced security and reliability in remote surgery, industrial automation, and emergency response, enabling the technology to be applied in various fields such as industry, healthcare, automotive, and home appliances. Summary of the Invention

[0010] [Technical Issues]

[0011] The implementation relates to electronic devices and methods for determining UL / DL TBS and MCS, and optionally, HARQ operation is considered in conjunction with the system having a large propagation delay between the BS and UE.

[0012] [Technical Solution]

[0013] Non-Land Network (NTN) nodes transmit configuration information including an indication of the maximum Transport Block Size (TBS) for Physical Uplink Shared Channel (PUSCH) transmission or Physical Downlink Shared Channel (PDSCH) transmission. The TBS for PUSCH or PDSCH is determined at least based on the indicated TBS; and a signal indicates the maximum Modulation and Coding Scheme (MCS) for PUSCH or PDSCH transmission, or whether a default MCS is used for PUSCH or PDSCH transmission, or at least based on the indicated maximum MCS; and PUSCH is transmitted or PDSCH is received based on the determined TBS and the determined MCS. The maximum TBS, maximum MCS, or Hybrid Automatic Repeat Request (HARQ) process count is indicated by the Master Information Block (MIB), System Information Block (SIB), or Radio Resource Control (RRC) signaling.

[0014] Other technical features can be readily understood by those skilled in the art based on the following figures, description and claims.

[0015] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout this patent document. The term “connection” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether those elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives encompass both direct and indirect communication. The terms “comprise” and “include,” and their derivatives mean including but not limited to. The term “or” is inclusive, indicating and / or. The phrase “associated with” and its derivatives mean including, being included in, interconnected with, comprising, being included in, connected to or connected with, linked to or connected with, can communicate with, cooperate with, intersect, juxtapose, adjacent to, combined with or combined with, having, possessing characteristics of, having a relationship with, etc. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. Whether local or remote, the functionality associated with any particular controller may be centralized or distributed. The phrase “at least one of…” when used with a list of items means that different combinations of one or more of the listed items may be used, and only one item from the list may be required. For example, “at least one of A, B, and C” includes any of the following combinations: A, B, and C; A and B; A and C; B and C; and A and B and C. Similarly, the term “group” refers to one or more items. Therefore, a group of items can be a single item or a collection of two or more items.

[0016] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and contained in a computer-readable medium. The terms "application program" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of media accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data, as well as media that can store data and subsequently rewrite it, such as rewritable optical discs or erasable memory devices.

[0017] Definitions of certain other words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many (if not most) cases, such definitions apply to the prior and future use of such defined words and phrases.

[0018] [Beneficial Effects]

[0019] According to this disclosure, improvements have been made to the uplink / downlink transport block size (TBS) and modulation and coding scheme (MCS) and related aspects. Attached Figure Description

[0020] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein:

[0021] Figure 1 Exemplary networking systems according to various embodiments of the present disclosure are shown;

[0022] Figure 2 Exemplary base stations (BSs) according to various embodiments of the present disclosure are shown;

[0023] Figure 3 Exemplary electronic devices for communication in a networked computing system according to various embodiments of the present disclosure are shown;

[0024] Figure 4 A flowchart illustrating an example of a TBS instruction for scheduling and receiving a PUSCH according to an embodiment of this disclosure is shown.

[0025] Figure 5A flowchart illustrating an example of TBS determination for transmitting PUSCH according to an embodiment of this disclosure is shown.

[0026] Figure 6 A flowchart illustrating an example of an MCS instruction for PUSCH according to an embodiment of this disclosure is shown.

[0027] Figure 7 A flowchart illustrating an example of MCS determination for PUSCH transmission according to an embodiment of this disclosure is shown.

[0028] Figure 8 A flowchart illustrating an example of PUSCH transmission according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be interpreted as an indication of the number of HARQ processes;

[0029] Figure 9 A flowchart illustrating an example of PUSCH transmission according to an embodiment of the present disclosure is shown, wherein one or more bits in the MCS field can be interpreted as an indication of modulation rewriting.

[0030] Figure 10 A flowchart illustrating an example of PUSCH transmission according to an embodiment of the present disclosure is provided, wherein one or more bits in the MCS field can be interpreted as an indication of the number of repetitions.

[0031] Figure 11 A flowchart illustrating an example of a TBS indication for PDSCH transmission according to an embodiment of this disclosure is shown.

[0032] Figure 12 A flowchart illustrating an example of TBS determination for PDSCH reception according to an embodiment of the present disclosure is shown.

[0033] Figure 13 A flowchart illustrating an example of an MCS indication for PDSCH transmission according to an embodiment of this disclosure is shown;

[0034] Figure 14 A flowchart illustrating an example of an MCS indication for PDSCH transmission according to an embodiment of this disclosure is shown;

[0035] Figure 15 A flowchart illustrating an example of PDSCH reception according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be reinterpreted as an indication of the number of HARQ processes;

[0036] Figure 16 A flowchart illustrating an example of PDSCH reception according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be reinterpreted as an indication of HARQ disabling;

[0037] Figure 17 A flowchart illustrating an example of PDSCH reception according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be reinterpreted as an indication of modulation rewriting; and

[0038] Figure 18 A flowchart illustrating an example of PDSCH reception according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be reinterpreted as an indication of the number of repetitions. Detailed Implementation

[0039] The accompanying drawings and various embodiments used to describe the principles of this disclosure are merely exemplary and should not be construed as limiting the scope of this disclosure in any way. Furthermore, those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged wireless communication system.

[0040] References:

[0041] ·[38.811]3GPP, TR 38.811, supports research on NR for non-terrestrial networks.

[0042] ·[38.821]3GPP, TR 38.821, a solution for NR supporting non-terrestrial networks (NTN).

[0043] • [RP-193234] RP-193234, NR solution supporting non-terrestrial networks (NTN), Thales, RAN#86, December 2019.

[0044] • [RP-193235] RP-193235, New Research WID for NB-IoT / eMTC Supporting NTN, MediaTek Inc., RAN#86, December 2019.

[0045] ·[38.331]3GPP, TS 38.331, 5G; NR; Radio Resource Control (RRC); Protocol Specification.

[0046] ·[38.214]3GPP, TS 38.214, 5G; NR; Physical layer procedure for data.

[0047] The above references are incorporated into this paper by way of citation.

[0048] abbreviation:

[0049] THz Terahertz

[0050] NTN non-terrestrial networks

[0051] BS base station

[0052] UE User Equipment

[0053] NR New Radio

[0054] 3GPP 3rd Generation Partnership Project

[0055] WI work items

[0056] SI Research Items

[0057] LEO (Low Earth Orbit)

[0058] MEO (Medium Earth Orbit)

[0059] GEO geosynchronous Earth orbit

[0060] TBS (Transfer Block Size)

[0061] MCS modulation and coding scheme

[0062] SIB System Information Block

[0063] DCI Downlink Control Information

[0064] PDCCH (Physical Downlink Control Channel)

[0065] PDSCH (Physical Downlink Shared Channel)

[0066] PUSCH Physical Uplink Shared Channel

[0067] RRC Radio Resource Control

[0068] MSB Most significant bit

[0069] LSB (Least Significant Bit)

[0070] DL downlink

[0071] UL uplink

[0072] IoT (Internet of Things)

[0073] eMTC Enhanced Machine Type Communication

[0074] Non-terrestrial networks (NTN)

[0075] NTN refers to a network or network segment that uses airborne or spaceborne vehicles to carry transmission equipment, relay nodes, or base stations [38.811]. Compared to conventional terrestrial network equipment, NTN can provide ubiquitous coverage and is less susceptible to disasters. There is increasing interest in supporting NTN in LTE and 5G systems. 3GPP completed a study in Rel-15 on NTN deployment scenarios, channel models, and potential impact areas on NR to support NTN [38.811]. Based on the results of the final technical report [38.811], 3GPP further conducted a set of necessary feature / adaptation studies in Rel-16 to support NTN in NR [38.821]. In Rel-17, the WI for NTN in NR [RP-193234] [RP-193235] and the SI for NB-IoT / eMTC to support NTN were approved.

[0076] As studied in [38.821], the link budget in NTN systems may be more limited compared to conventional terrestrial networks due to the large distances between satellites and UEs. The determination of TBS and MCS in NTN systems should take into account the limited link budget.

[0077] Furthermore, the long propagation delay between the S and UE in NTN scenario B can affect Hybrid Automatic Repeat Request (HARQ) operation, as discussed in [38.821]. [38.821] provides two options for HARQ enhancement:

[0078] Option 1: Retain 16 HARQ process identifiers (IDs) and rely on Radio Link Control (RLC) Automatic Repeat Request (ARQ) for HARQ processes, with UL HARQ feedback disabled via Radio Resource Control (RRC).

[0079] Option 2: Use more than 16 HARQ process IDs, with UL HARQ feedback enabled via RRC.

[0080] Therefore, HARQ operations should be designed for NTN systems to be applied to scenarios with large round-trip delays.

[0081] In summary, for systems such as NTN, the large distance between the BS and UE results in high propagation loss and a limited link budget. Methods capable of handling limited link budgets should be designed. Furthermore, in systems such as NTN, the long propagation delay between the BS and UE affects HARQ operation. Methods to support HARQ operation with long propagation delays should be designed.

[0082] Techniques, apparatus, and methods for determining TBS and MCS, as well as HARQ operation methods for UL transmissions, are disclosed, supporting scenarios with limited link budgets and / or large propagation delays. Specifically, the maximum supported TBS and MCS for UL transmissions can be limited and can be jointly configured with UL HARQ operation, such as a larger number of HARQ processes than predetermined values ​​(e.g., more than the number of HARQ processes supported in an NR system).

[0083] Techniques, apparatus, and methods for determining TBS and MCS, as well as HARQ operation methods for DL ​​transmission, are disclosed, supporting scenarios with limited link budgets and / or large propagation delays. Specifically, the maximum supported TBS and MCS for DL ​​transmission can be limited, and can be jointly configured with DLHARQ operation without affecting or with limited impact on the UE soft buffer size.

[0084] The disclosed design can be applied not only to NTN systems but also to any other wireless communication system. The example of an NTN system should be considered as an inclusion, without excluding other wireless communication systems.

[0085] Figure 1 Exemplary networking systems according to various embodiments of this disclosure are shown. Figure 1 The embodiments of the wireless network 100 shown are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0086] like Figure 1 As shown, the wireless network 100 includes base stations (BS) 101, BS 102, and BS 103. BS 101 communicates with BS 102 and BS 103. BS 101 also communicates with at least one Internet Protocol (IP) network 130 (such as the Internet, a proprietary IP network, or another data network).

[0087] BS 102 provides wireless broadband access to network 130 to a first plurality of user equipments (UEs) within its coverage area 120. The first plurality of UEs includes: UE 111, which may be located in a small business; UE 112, which may be located in an enterprise (E); UE 113, which may be located in a Wi-Fi hotspot (HS); UE 114, which may be located in a first residence (R1); UE 115, which may be located in a second residence (R2); and UE 116, which may be a mobile device (M), such as a cellular phone, wireless laptop computer, wireless PDA, etc. BS 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In some implementations, one or more of BS 101 to 103 may use 5G, LTE, LTE-Advanced (LTE-A), WiMAX, WiFi or other wireless communication technologies to communicate with each other and with UE 111 to 116.

[0088] Depending on the network type, other well-known terms may be used instead of "base station" or "BS," such as Node B, Evolved Node B ("eNodeB" or "eNB"), 5G Node B ("gNodeB" or "gNB"), or "access point." For convenience, the terms "base station" and / or "BS" are used in this disclosure to refer to network infrastructure components that provide wireless access to remote terminals. Additionally, depending on the network type, other well-known terms may be used instead of "user equipment" or "UE," such as "mobile station" (or "MS"), "subscriber station" (or "SS"), "remote terminal," "wireless terminal," or "user equipment." For convenience, the terms "user equipment" or "UE" used in this patent document refer to a remote wireless device that wirelessly accesses the BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered to be a fixed device (e.g., a desktop computer or vending machine).

[0089] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as roughly circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with a BS, such as coverage areas 120 and 125, may have other shapes, including irregular ones, depending on the configuration of the BS and variations in the radio environment related to natural and man-made obstacles.

[0090] Although Figure 1 An example of a wireless network 100 is shown, but more details can be found on other wireless networks. Figure 1Various modifications can be made. For example, wireless network 100 may include any number of BSs and any number of UEs arranged in any suitable configuration. Additionally, BS 101 may communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each BS 102 to 103 may communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. Furthermore, BS 101, BS 102, and / or BS 103 may provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0091] Figure 2 Exemplary base stations (BSs) according to various embodiments of the present disclosure are shown. Figure 2 The embodiment of BS 102 shown is for illustrative purposes only, and Figure 1 BS 101 and 103 can have the same or similar configurations. However, BS has a wide variety of configurations, and Figure 2 This disclosure is not intended to limit the scope to any particular implementation of BS.

[0092] like Figure 2 As shown, BS 102 includes multiple antennas 280a to 280n, multiple radio frequency (RF) transceivers 282a to 282n, transmit (TX or Tx) processing circuitry 284, and receive (RX or Rx) processing circuitry 286. BS 102 also includes a controller / processor 288, a memory 290, and a backhaul or network interface 292.

[0093] RF transceivers 282a to 282n receive incoming RF signals, such as signals transmitted by the UE in network 100, from antennas 280a to 280n. RF transceivers 282a to 282n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 286, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 286 transmits the processed baseband signal to controller / processor 288 for further processing.

[0094] TX processing circuit 284 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller / processor 288. TX processing circuit 284 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 282a to 282n receive the outgoing processed baseband or IF signal from TX processing circuit 284 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 280a to 280n.

[0095] The controller / processor 288 may include one or more processors or other processing devices that control the overall operation of the BS 102. For example, the controller / processor 288 may control the reception of forward channel signals and the transmission of reverse channel signals via RF transceivers 282a to 282n, RX processing circuitry 286, and TX processing circuitry 284, based on known principles. The controller / processor 288 may also support additional functions, such as more advanced wireless communication functions and / or processes described in further detail below. For example, the controller / processor 288 may support beamforming or directional routing operations, wherein outgoing signals from multiple antennas 280a to 280n are weighted differently to effectively direct the outgoing signals in a desired direction. The controller / processor 288 may support any of a wide variety of other functions within the BS 102. In some embodiments, the controller / processor 288 includes at least one microprocessor or microcontroller.

[0096] The controller / processor 288 is also capable of executing programs and other processes residing in the memory 290, such as the basic operating system (OS). The controller / processor 288 can move data into or out of the memory 290 as needed by the executing process.

[0097] The controller / processor 288 is also coupled to a backhaul or network interface 292. The backhaul or network interface 292 allows the BS 102 to communicate with other devices or systems via a backhaul connection or a network. Interface 292 can support communication via any suitable wired or wireless connection. For example, when the BS 102 is implemented as part of a cellular communication system (such as supporting 6G, 5G, LTE, or LTE-A), interface 292 can allow the BS 102 to communicate with other BSs via wired or wireless backhaul. When the BS 102 is implemented as an access point, interface 292 can allow the BS 102 to communicate with a larger network (such as the Internet) via a wired or wireless LAN or via a wired or wireless connection. Interface 292 includes any suitable architecture that supports communication via wired or wireless connections (such as Ethernet or RF transceivers).

[0098] The memory 290 is coupled to the controller / processor 288. A portion of the memory 290 may include RAM, and another portion of the memory 290 may include flash memory or other ROM.

[0099] As described in more detail below, base stations in a networked computing system can be assigned as either a source BS or a slave BS based on their interference relationships with other neighboring BSs. In some implementations, the assignment can be provided by a shared spectrum manager. In other implementations, the assignment can be negotiated by the BSs in the networked computing system. The source BS sends an OSS to the slave BS to establish the slave BS's transmission timing.

[0100] Although Figure 2 An example of BS 102 is shown, but it is possible to compare it with other versions. Figure 2 Various changes can be made. For example, BS 102 can include any number of Figure 2 Each component shown. As a specific example, an access point may include multiple interfaces 292, and the controller / processor 288 may support routing functionality for routing data between different network addresses. As another specific example, although shown as including a single instance of TX processing circuitry 284 and a single instance of RX processing circuitry 286, the gNB102 may include multiple instances of each (such as one instance per RF transceiver). Additionally, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0101] Figure 3 Exemplary electronic devices for communication in a networked computing system according to various embodiments of the present disclosure are shown. In one embodiment, electronic device 300 is a user device implemented as a mobile device, which may represent Figure 1 One of the UEs in the system.

[0102] like Figure 3 As shown, the electronic device 300 includes a bus system 305 that supports communication between at least one processor 310, at least one storage device 315, at least one communication unit 320 and at least one input / output (I / O) unit 325.

[0103] Processing device 310 executes instructions that can be loaded into memory 330. Processing device 310 may include any suitable number and type of processors or other devices arranged in any suitable manner. Exemplary types of processing device 310 include microprocessors, microcontrollers, digital signal processors, field-programmable gate arrays, application-specific integrated circuits, and discrete circuits.

[0104] Memory 330 and permanent storage device 335 are examples of storage device 315, which represent any structure capable of storing and facilitating the retrieval of information (such as data, program code, and / or other suitable information on a temporary or permanent basis). Memory 330 may represent random access memory or any other suitable volatile or non-volatile storage device. Permanent storage device 335 may contain one or more components or devices supporting longer-term data storage, such as read-only memory, hard disk drive, flash memory, or optical disk.

[0105] Communication unit 320 supports communication with other systems or devices. For example, communication unit 320 may include a network interface card or wireless transceiver that facilitates communication via network 130. Communication unit 320 can support communication via any suitable physical or wireless communication link.

[0106] I / O unit 325 allows for data input and output. For example, I / O unit 325 can provide connectivity for user input via a keyboard, mouse, keypad, touchscreen, or other suitable input device. I / O unit 325 can also send output to a monitor, printer, or other suitable output device.

[0107] As described in more detail below, electronic device 300 can be used as a shared spectrum manager in a networked computing system, capable of generating synchronization source / slave allocations and configuring synchronization signals.

[0108] Although Figure 3 It shows multiple base stations (such as Figure 1 Examples of electronic devices 300 in the wireless systems of base stations 101, 102, and 103 (in which base stations 101, 102, and 103) can be used for... Figure 3 Make various changes. For example, Figure 3 The various components within can be combined, further subdivided, or omitted, and additional components can be added as needed. Furthermore, like computing and communication networks, servers can have multiple configurations, and... Figure 3 This disclosure is not intended to be limited to any particular electronic device.

[0109] Indication method for the number of TBS and / or HARQ processes

[0110] As mentioned above, in some systems such as NTN scenarios, the link budget may be limited, and the link quality may be insufficient to support large TBS transmissions. The maximum TBS supporting an NTN system can be configured within a certain range.

[0111] Figure 4 A flowchart illustrating an example of a TBS instruction for scheduling and receiving PUSCH according to an embodiment of this disclosure is shown. Figure 4 The method 400 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0112] At operation 401, the BS generates and sends configuration information including an indication of the maximum TBS for the PUSCH and / or an indication of the number of HARQ processes for the UL, wherein the indication can be explicit or implicit, and can be cell-specific or UE-specific. As an example, the indications of the maximum TBS and the number of HARQ processes can be associated. For example, the maximum TBS can be explicitly indicated, while the number of HARQ processes can be implicitly indicated based on the indicated maximum TBS, and vice versa. Alternatively, the indications of the maximum TBS and the number of HARQ processes can be independent. At operation 402, the BS determines the MCS indication information and carries the MCS indication information in the DCI for scheduling the PUSCH, or in the DCI for unlicensed UL transmissions of activation type 2, or in the RRC signaling for unlicensed UL transmissions of activation type 1. At operation 403, the BS receives the PUSCH based on the configuration and / or the DCI.

[0113] Figure 5 A flowchart illustrating an example of TBS determination for transmitting PUSCH according to an embodiment of this disclosure is shown. Figure 5 The method 500 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0114] At operation 501, the UE receives configuration information including an indication of the maximum TBS for PUSCH and / or an indication of the number of HARQ processes for UL, wherein the indication may be explicit or implicit, and may be cell-specific or UE-specific. As an example, the indications of the maximum TBS and the number of HARQ processes may be associated, as discussed above. Alternatively, the indications of the maximum TBS and the number of HARQ processes may be independent. At operation 502, the UE receives a DCI carrying the number of HARQ processes and a DCI carrying an MCS indication for PUSCH scheduling, or a DCI carrying an MCS indication for activating unlicensed UL transmissions of type 2, or an RRC signaling carrying an MCS indication for activating unlicensed UL transmissions of type 1. At operation 503, the UE calculates the scheduled TBS based on the maximum TBS configuration and the MCS indication in the DCI or RRC signaling, and transmits PUSCH based on the calculated TBS value and the configuration and / or DCI indication. For example, TBS' represents the TBS indicated by the MCS index in DCI or RRC signaling, and TBS max This represents the maximum TBS configured. The determined TBS can be min(TBS', TBS'). max ).

[0115] In one embodiment of operations 401 and 501, the indications of the maximum TBS for PDSCH and PUSCH can be associated. For example, the mapping between the maximum TBS for PDSCH and the maximum TBS for PUSCH can be predefined, such as the maximum TBS for PDSCH being defined as the same as the maximum TBS configured for PUSCH. Alternatively, the configurations of the maximum TBS for PDSCH and PUSCH can be independent.

[0116] Explicit indication of the maximum TBS for PUSCH

[0117] The method for indicating the maximum TBS for PUSCH can be explicit. For example, the maximum TBS configuration can be cell-specific and can be configured by system information such as the Master Information Block (MIB), System Information Block 1 (SIB1), other System Information Blocks (SIBs), and / or new SIBs introduced for the NTN system. An example of explicit indication using SIB1 is shown below, where the information elements (IEs) BWP-UplinkCommon, UplinkConfigCommonSIB, or servingCellConfigCommonSIB in SIB1 can be modified. In the example of Exemplary Abstract Syntax Marker 1 (ASN.1) in Table 1, the IE PUSCH-ConfigCommon in IE BWP-UplinkCommon is modified to include maxTBSPUSCH:

[0118] Table 1

[0119] Example of IE PUSCH-ConfigCommon modification used to indicate the maximum TBS

[0120]

[0121] The parameters N1, N2, ..., NK can be any integer, and the condition label "Cond NTN" refers to the NTN scenario. Throughout this disclosure, the condition label "Cond NTN" is given as an example and should be considered as an inclusion method. For systems other than NTN, the condition label can be changed accordingly.

[0122] In the thematic examples, different maximum TBS can be configured for PDSCH and PUSCH, while in some other examples, the maximum TBS for PDSCH and PUSCH can be configured jointly, for example, by sharing the same value and indicating it in IEservingCellConfigCommonSIB.

[0123] The following table 2 provides an example of introducing a new SIB to indicate the maximum TBS, for example, SIB15 could be introduced:

[0124] Table 2

[0125] Example of IE SIB15 modification used to indicate the maximum TBS.

[0126]

[0127] The parameters N1, N2, ..., NK and M1, M2, ..., ML can be any integers. In the given example, different maximum TBS can be configured for PDSCH and PUSCH, while in some other examples, the maximum TBS for PDSCH and PUSCH can be configured jointly, for example, by sharing the same value.

[0128] As another example of explicit indication, the maximum TBS configuration can be UE-specific and can be configured by UE-specific RRC signaling. An example of this configuration can be shown in ASN.1 of Table 3 below, where IE PUSCH-ServingCellConfig is modified;

[0129] Table 3

[0130] Example of IE PUSCH-ServingCellConfig modification used to indicate the maximum TBS

[0131]

[0132] In the examples above, the same maximum TBS applies to the BWP of all UEs within a serving cell. Alternatively, the maximum TBS for PUSCH can be configured as a UE-specific value for the BWP via IE PUSCH-Config in IE BWP-UplinkDedicated, as shown in ASN.1 of Table 4:

[0133] Table 4

[0134] Example of an IEPUSCH-Config modification used to indicate the maximum TBS.

[0135]

[0136] In some examples, the increased number of HARQ processes can be configured in conjunction with a reduced TBS feature. As an example of the above implementation with an explicit indication of the maximum TBS, the number of HARQ processes can be implicitly indicated based on the configured maximum TBS. curIndicates the maximum TBS supported in the system (e.g., in the current NR system) or a predefined TBS value, and is determined by the TBS. max This represents the maximum TBS configured in the system. The number of HARQ processes in the system can be no more than [number missing]. Any integer or power of 2, where N is a predetermined value (e.g., N = 16).

[0137] In one implementation, the configuration method described above can be applied to both dynamically scheduled PUSCH and non-dynamically licensed UL transmissions (e.g., Type 1 or Type 2). In one example of this implementation, the same maximum TBS value is applied to both dynamically scheduled PUSCH and non-dynamically licensed UL transmissions. In another example of this implementation, different maximum TBS values ​​can be configured for dynamically scheduled PUSCH transmissions and non-dynamically licensed UL transmissions. In this example, the configuration method described above will indicate two parameters, for example, “cg-maxTBSPUSCH” can be added to the IE to indicate the maximum TBS for non-dynamically licensed UL transmissions, while the parameter given in the IE, such as “maxTBSPUSCH”, can indicate the maximum TBS for dynamically scheduled PUSCH. These parameter names are merely examples and should be considered as inclusion (i.e., other names can also be used). Alternatively, the method described above is applied only to dynamically scheduled PUSCH, while the following method for configuring the maximum TBS can be applied to non-dynamically licensed UL transmissions. The maximum TBS for non-dynamically licensed UL transmissions can be explicitly indicated in UE-specific RRC signaling (e.g., in the IE ConfiguredGrantConfig). Parameters N1, N2, ..., NK can be any integer. In one example, the configuration of the maximum TBS for non-dynamically licensed UL transmissions, such as the parameter "cg-maxTBSPUSCH" in the IE within ASN.t of Table 5 below, can be applied to both Type 1 and Type 2 non-dynamically licensed UL transmissions. Alternatively, different configurations of the maximum TBS can be applied to Type 1 and Type 2 non-dynamically licensed UL transmissions. For example, the parameter "cg-maxTBSPUSCH" in the following IE can be applied to Type 2 non-dynamically licensed UL transmissions, while another parameter "cg1-maxTBSPUSCH" can be introduced into the IE ConfiguredGrantConfig to indicate the maximum TBS for Type 1 non-dynamically licensed UL transmissions.

[0138] Table 5

[0139] Example of IE ConfiguredGrantConfig modification used to indicate the maximum TBS.

[0140]

[0141]

[0142]

[0143]

[0144] Implicit indication of maximum TBS for PUSCH

[0145] As another implementation of operations 401 and 501, the indication of the maximum TBS for PUSCH can be implicit. As an example, the mapping between the maximum TBS for PUSCH and the system scenario / mode can be predefined. Once the system scenario / mode is indicated, the maximum TBS for PUSCH, for example, the TBS of system scenario / mode N, can be determined accordingly. max-N Here, N is an index such as 1, 2, etc. In one example, the number of HARQ processes can be configured similarly, and the mapping between the number of HARQ processes and the system scenario / mode can be predefined. Once the system scenario / mode is indicated, the number of HARQ processes can be determined accordingly, for example, X for system scenario / mode N. N As an example of this implementation, the configuration of system scenarios / modes can be cell-specific and can be configured by system information, such as via MIB, SIB1, other SIBs, and / or new SIBs introduced for the system. For example, one reserved bit in the MIB can be used to indicate two scenarios / modes. Another example of using SIB1 for this indication is shown by ASN.1 and Table 6 below, where parameter N can be any integer. The parameters in the following examples use "NTN mode" as an example for NTN systems, while other names can be used for other systems. In one example, the mapping between maximum TBS and system scenarios / modes can be the same for dynamically scheduled PUSCH and unlicensed UL transmissions. Alternatively, different mappings between maximum TBS and system scenarios / modes can be predefined for dynamically scheduled PUSCH and unlicensed UL transmissions. For example, this example can be applied to configure the maximum TBS for dynamically scheduled PUSCH, while the maximum TBS for unlicensed UL transmissions can be configured separately, and vice versa.

[0146] Table 6

[0147] Example of IE SIB1 modification used to indicate system scenario / mode

[0148]

[0149]

[0150] In another example, the maximum TBS for PUSCH can be implicitly indicated based on the maximum amount of frequency resources that can be allocated to PUSCH (e.g., the maximum number of PRBs that can be allocated). The maximum TBS can then be calculated based on a predefined equation, such as the TBS in section 6.1.4.2 of [38.214]. In an example where HARQ enhancement and TBS reduction features are configured together, the number of HARQ processes can be implicitly indicated based on the configured maximum TBS. CUR Indicates the maximum TBS supported in the system (e.g., in the current NR system) or a predefined TBS value, and is determined by the TBS. max This represents the maximum TBS configured in the system. The number of HARQ processes in the system can be no more than [number missing]. Any integer or power of 2, where N is a predefined value (e.g., N = 16).

[0151] The indication of the maximum number of frequency resources can be cell-specific, such as being carried in the MIB, SIB1, or other system information. For example, reserved bits in the MIB can be used to indicate two possible PRB numbers, such as 6 and 25. Alternatively, the SIB1 can carry an explicit indication of the maximum number of frequency resources, where the IEs BWP-UplinkCommon, UplinkConfigCommonSIB, or servingCellConfigCommonSIB in the SIB1 can be modified. In the example shown by ASN.1 in Table 7, the IE PUSCH-ConfigCommon in IE BWP-UplinkCommon is modified. Parameters N1, N2, ..., NK can be any integer, and the condition label “Cond NTN” refers to the NTN scenario. In the thematic example, different maximum amounts of frequency resources can be configured for DL ​​and UL, while in some other examples, the maximum amounts of frequency resources for DL ​​and UL can be jointly configured, for example, sharing the same value and indicating it in IEservingCellConfigCommonSIB.

[0152] Table 7

[0153] Example used to indicate the maximum number of IE PUSCH-ConfigCommon modifications for PRB

[0154]

[0155] Alternatively, the maximum amount of frequency resources used for PUSCH can be UE-specific. The configuration of the maximum amount of frequency resources can be indicated by UE-specific RRC signaling. An example of this configuration can be shown in ASN.1 within Table 8, where IEPUSCH-ServingCellConfig is modified.

[0156] Table 8

[0157] Example of using PRB to indicate the maximum number of IE PUSCH-ServingCellConfig modifications

[0158]

[0159] In the examples above, the same maximum amount of frequency resources used for PUSCH is applied to the Bandwidth Part (BWP) of all UEs in a serving cell. Alternatively, the maximum amount of frequency resources used for PUSCH can be configured as a UE-specific BWP value via IE PUSCH-Config in IE BWP-UplinkDedicated as shown in ASN.1 in Table 9.

[0160] Table 9

[0161] Example used to indicate the maximum number of IE PUSCH-Config modifications for PRB

[0162]

[0163] In one example, the maximum amount of frequency resources indicated above applies to both dynamically scheduled PUSCHs and non-dynamically licensed UL transmissions. Alternatively, the maximum amount of frequency resources indicated above applies to dynamically scheduled PUSCHs, while the maximum amount of frequency resources for non-dynamically licensed UL transmissions can be configured separately, and vice versa. In one example, the maximum amount of frequency resources for non-dynamically licensed UL transmissions can be configured via the parameter "cg-nrofPRB" in the IE ConfiguredGrantConfig, where parameters N1, N2, ..., NK can be any integer. In one example, the configuration of the maximum amount of frequency resources for non-dynamically licensed UL transmissions, such as the parameter "cg-nrofPRB" in the following IE, can be applied to both Type 1 and Type 2 non-dynamically licensed UL transmissions. Alternatively, different configurations of the maximum amount of frequency resources can be applied to Type 1 and Type 2 non-dynamically licensed UL transmissions. For example, the parameter "cg-nrofPRB" in the following IE is applied to type 2 non-dynamically licensed UL transfers, while another parameter "cg1-nrofPRB" can be introduced into IEConfiguredGrantConfig to indicate the maximum TBS for type 1 non-dynamically licensed UL transfers, as shown in ASN.1 in Table 10:

[0164] Table 10

[0165] Example of using IE ConfiguredGrantConfig modifications to indicate the maximum number of PRBs.

[0166]

[0167]

[0168]

[0169] In yet another example, the maximum TBS can be implicitly indicated based on the maximum number of HARQ processes. For example, by TBS cur This represents the current maximum TBS supported for PUSCH in the current system (e.g., an NR system), and L represents the number of configured HARQ processes. The maximum TBS can be any integer or a value not exceeding the number supported in the current system. The maximum number of TBS is calculated using any number of parameters, where N is a predefined number (e.g., N = 16). For the indication of the maximum number of frequency resources, this indication can be the same as the indication for HARQ processes, where the parameter “nrofPRB” is replaced with “nrofHARQ-Processes”, as shown in Tables 7-10 above. An example in Table 9 shows different numbers of HARQ processes configured for different UL BWP configurations. In one example, the calculated maximum TBS can be applied to both dynamically scheduled PUSCHs and unlicensed UL transmissions. In another example, the calculated maximum TBS is applied to dynamically scheduled PUSCHs, while the maximum TBS for unlicensed UL transmissions can be configured separately, and vice versa.

[0170] MCS Determination Method

[0171] Figure 6 A flowchart illustrating an example of an MCS instruction for PUSCH according to an embodiment of this disclosure is shown. Figure 6 The method 600 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0172] At operation 601, the BS generates and sends configuration information that includes an indication of the supported MCS for PUSCH, which can be explicit or implicit, and can be cell-specific or UE-specific. In one example, the maximum MCS index for PDSCH can be the same as the maximum MCS index for PUSCH, and the described configuration method can be applied to both PDSCH and PUSCH. Alternatively, the configuration of the maximum MCS index for PDSCH and PUSCH can be independent. At operation 602, the BS generates and sends a DCI for PUSCH scheduling, or a DCI for unlicensed UL transmissions of activation type 2, or an RRC signaling for unlicensed UL transmissions of activation type 1, carrying the MCS indication and possibly using certain bits in the MCS field for other indications. For example, some bits in the MCS field can be used in conjunction with the HARQ process number field to indicate the number of HARQ processes. As another example, if a repetition feature is configured, some bits in the MCS field can be used to indicate the number of repetitions. In yet another example, some bits in the MCS field can be used to indicate whether the modulation order indicated by the MCS field should be rewritten to some predefined modulation scheme, such as QPSK. In one example, this modulation rewrite indication is only used when repetition is configured. Alternatively, this modulation rewrite indication can be enabled by higher-layer signaling, such as cell-specific signaling or UE-specific RRC signaling. At operation 603, the BS receives the PUSCH based on DCI and / or RRC signaling.

[0173] Figure 7 A flowchart illustrating an example of MCS determination for PUSCH transmission according to an embodiment of this disclosure is shown. Figure 7 The method 700 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0174] At operation 701, the UE receives configuration information including an indication of the supported MCS for PUSCH, which can be explicit or implicit, and can be cell-specific or UE-specific. At operation 702, the UE receives DCI or RRC signaling containing the MCS indication. The DCI can be a DCI for dynamically scheduling PUSCH or a DCI for activating unlicensed UL transmissions of type 2. The RRC signaling can be signaling for activating unlicensed UL transmissions of type 1. In one example, the maximum MCS index can be limited (e.g., less than 31 in an NR system), and some bits in the MCS field can be used for other indications, such as a joint indication of the number of HARQ processes, an indication of the number of repetitions, and / or an indication of modulation order rewriting. At operation 703, the UE transmits PUSCH based on the DCI indication and / or RRC signaling.

[0175] In one implementation of operations 601 and 701, the indications of the maximum MCS indexes for PDSCH and PUSCH are associated. For example, the mapping between the maximum MCS index for PDSCH and the maximum MCS index for PUSCH can be predefined, such as the maximum MCS index for PUSCH being defined as the same as the maximum MCS index configured for PDSCH. Alternatively, the configurations of the maximum MCS indices for PDSCH and PUSCH can be independent.

[0176] Explicit indication of the largest MCS index for PUSCH

[0177] In one implementation of operations 601 and 701, the indication for the maximum MCS index used for PUSCH can be explicit. For example, the maximum MCS index configuration can be cell-specific and can be configured by system information such as MIB, SIB1, other SIBs, and / or new SIBs introduced for the NTN system. An example of explicit indication using SIB1 is shown in ASN.1 of Table 11, where IE BWP-UplinkCommon, UplinkConfigCommonSIB, or servingCellConfigCommonSIB in SIB1 can be modified. In this example, IEPUSCH-ConfigCommon in IE BWP-UplinkCommon is modified. Parameters Y1, Y2, ..., Yn can be any integer, and the condition label “Cond NTN” refers to the NTN scenario. For other systems, the condition label can be changed accordingly.

[0178] Table 11

[0179] Example of IE PUSCH-ConfigCommon modification used to indicate the maximum MCS index.

[0180]

[0181] Table 12, ASN.1 below provides examples of introducing new SIBs to indicate the maximum TBS; for example, SIB15 could be introduced into the system. Parameters X1, X2, ..., Xn and Y1, Y2, ..., Yn can be any integers. In the given example, different maximum MCS indices can be configured for PDSCH and PUSCH, while in some other examples, the maximum MCS indices for PDSCH and PUSCH can be configured jointly, for example, sharing the same value.

[0182] Table 12

[0183] Example of IE SIB15 modification used to indicate the maximum MCS index

[0184]

[0185] In yet another explicitly indicated example, the maximum MCS index configuration can be UE-specific and can be configured by UE-specific RRC signaling. An example of this configuration is shown in ASN.1 of Table 13, where the IE PUSCH-ServingCellConfig is modified.

[0186] Table 13

[0187] Example of IE PUSCH-ServingCellConfig modification used to indicate the maximum MCS index.

[0188]

[0189] In the examples above, the same maximum MCS index is applied to the BWP of all UEs in a serving cell. Alternatively, the maximum MCS index for PUSCH can be configured as a UE-specific value for the BWP via IE PUSCH-Config in IE BWP-UplinkDedicated, as shown in ASN.1 of Table 14.

[0190] Table 14

[0191] Example of IE PUSCH-Config modification used to indicate the maximum MCS index.

[0192]

[0193] In one example, the maximum MCS configuration can be the same for both dynamically scheduled PUSCH and non-dynamically authorized UL transports. Alternatively, different maximum MCS configurations can be set for dynamically scheduled PUSCH and non-dynamically authorized UL transports. For example, the configuration method described above would indicate that two parameters, such as "sps-pusch-maxMCSindex", can be added to the above IE to indicate the maximum MCS index for non-dynamically authorized UL transports, while the parameter given in the above IE, such as "pusch-maxMCSindex", can indicate the maximum MCS index for dynamically scheduled PUSCH. These parameter names are merely examples and should be considered as inclusion (i.e., other names can also be used). Alternatively, the configuration method described above for the maximum MCS can be applied to dynamically scheduled PUSCH, while the maximum MCS for non-dynamically authorized UL transports can be configured separately, for example via RRC signaling as shown in ASN.1 of Table 15 below.

[0194] Table 15

[0195] Example of IE ConfiguredGrantConfig modification used to indicate the maximum MCS for PUSCH

[0196]

[0197]

[0198]

[0199]

[0200] Implicit indication of the maximum MCS index used for PUSCH

[0201] In one implementation of operations 601 and 701, the configuration of the supported MCS for PUSCH can be implicit. In one example, the configuration can be cell-specific. As an example, the mapping between the maximum MCS index for PUSCH and the system scenario / mode can be predefined. Once the system scenario / mode is indicated, the maximum MCS index for PUSCH, e.g., the MCS for system scenario / mode N, can be determined accordingly. max-N Where N is an index such as 1, 2, etc. As an example of this implementation, the configuration of system scenarios / modes can be cell-specific and can be configured by system information, such as via MIB, SIB1, other SIBs, and / or new SIBs introduced for the system. For example, one reserved bit in the MIB can be used to indicate two scenarios / modes. Another example of using SIB1 for this indication is shown in Table 6 above. In one example, the mapping between the maximum MCS and system scenarios / modes can be the same for dynamically scheduled PUSCH and non-dynamically licensed UL transmissions. Alternatively, different mappings between the maximum MCS and system scenarios / modes can be predefined for dynamically scheduled PUSCH and non-dynamically licensed UL transmissions.

[0202] Modulation rewrite configuration

[0203] In one implementation of operations 601 and 701, the indicated modulation scheme can be rewritten. For example, when modulation rewriting is enabled, the modulation scheme indicated by the MCS field can be rewritten to a predefined modulation scheme, such as rewriting to use a lower-order modulation, such as π / 2 binary phase shift keying (BPSK) or quadrature phase shift keying (QPSK). The modulation scheme to be rewritten can be predefined, such as pi / 2-BPSK or QPSK. In one example of this implementation, modulation rewriting can be configured by higher-layer signaling, such as cell-specific signaling via MIB, SIB1, or other SIBs, or modulation rewriting can be configured by UE-specific RRC signaling. The signaling method can be similar to the indication of the TBS for PUSCH, for example, introducing a parameter such as “modulationOverriden-pusch” into the IEs in Tables 1 through 5. Alternatively, the signaling method can be predefined as whether modulation rewriting is configured for certain system scenarios / modes, which can be indicated, for example, by the IEs in Table 6. In one example, the modulation rewriting configuration may depend on other configurations; for example, modulation rewriting may be configured when configuring repetition and / or transmission time interval (TTI) bundling. In one example, modulation rewriting for PDSCH and PUSCH may be configured jointly. Alternatively, modulation rewriting for PDSCH and PUSCH may be configured separately; for example, there may be cases where modulation rewriting for PDSCH is configured but not for PUSCH, or vice versa.

[0204] In one example, modulation rewriting is enabled when it is configured. In another example, modulation rewriting is enabled when modulation rewriting is configured and a PUSCH or non-dynamically authorized UL transmission dynamically scheduled by the DCI is indicated to have a specific number of repetitions (e.g., repetitions > 1) and / or a specific number of TTIs for TTI bundling. In this example, there is no dynamic indication of modulation rewriting. In another example, the DCI can dynamically indicate whether modulation rewriting is enabled or disabled when it is configured. In yet another example, modulation rewriting is enabled when it is configured, provided the coding rate is within a certain range, for example, the coding rate using the rewritten modulation scheme is no greater than a specific value X, where X can be predefined or configured by higher-layer signaling.

[0205] DCI Design

[0206] In one implementation, the MCS field in the DCI can be configurable. The number of bits in the MCS field can be adjusted according to the configured maximum MCS index. For example, with a configured maximum MCS index of 15, the MCS field in the DCI can be 4 bits.

[0207] In another implementation, the supported MCSs can be limited, and the MCS field can have some bits available for other indications. For example, the MCS index can be configured to have up to 7 or 15, and the MCS field can have 1 or 2 available bits available for other indications.

[0208] Figure 8 A flowchart illustrating an example of PUSCH transmission according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be interpreted as an indication of the number of HARQ processes. Figure 8 The method 800 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0209] At operation 801, the UE receives configuration information, which may include configuration of the supported MCS and / or the number of HARQ processes used for PUSCH. At operation 802, the UE receives the PDCCH for transmitting the DCI that schedules the PUSCH. At operation 803, the UE checks whether the configured maximum MCS index is less than M, where M is a predefined number, such as 8 or 16. The UE also checks whether the number of HARQ processes configured for the PUSCH is greater than L, where L is a predefined number, such as 16. If the configured maximum MCS index is less than M and the configured number of HARQ processes is greater than L, then at operation 804, the UE transmits the PUSCH based on the configuration and DCI indication, where the UE interprets the NK bits (e.g., NK MSBs) in the MCS field of the DCI as indicating the MCS index, and interprets one or more bits in the remaining K bits (e.g., K LSBs) in the MCS field as indicating the number of HARQ processes, where N and K can be any integers, for example, N can be 5 and K can be 1 or 2. For example, the existing HARQ process number field in the DCI indicates the MSB in the HARQ process number, while the K LSBs in the MCS field can be reinterpreted as LSBs indicating the HARQ process number. If the configured maximum MCS index is not less than M or the configured HARQ process number is less than or equal to L, the UE sends a PUSCH at operation 805 based on the configuration and DCI indication, where the UE interprets N bits in the MCS field of the DCI as indicating the MCS index, where N can be any integer, such as 5. This example can be applied to dynamically scheduled PUSCH.

[0210] Figure 9 A flowchart illustrating an example of PUSCH transmission according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be interpreted as an indication of modulation rewriting. Figure 9The method 900 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0211] At operation 901, the UE receives configuration information, which may include configuration for supported MCS and / or modulation rewriting. Modulation rewriting can be configured, for example, via SIB1 or other system information, or UE-specific RRC signaling. At operation 902, the UE receives a PDCCH for transmitting DCI, which schedules PUSCH or activates unlicensed UL transmissions of type 2. At operation 903, the UE checks whether the configured maximum MCS index is less than M, where M is a predefined number, such as 8 or 16. The UE also checks whether modulation rewriting is configured. If the configured maximum MCS index is less than M and modulation rewriting is configured, the UE transmits a PUSCH at operation 904 based on the configuration and DCI indication, where the UE interprets NK bits (e.g., NK MSBs) in the MCS field of the DCI as indicating the MCS index, and interprets one or more of the remaining K bits (e.g., K LSBs) in the MCS field as indicating modulation rewriting, where N and K can be any integers, for example, N can be 5 and K can be 1 or 2. For example, K can be 1, and when this bit is 0, modulation rewriting is disabled, but when this bit is 1, modulation rewriting is enabled, and vice versa. If the configured maximum MCS index is not less than M or modulation rewriting is not configured, the UE sends a PUSCH at operation 905 based on the configuration and DCI indication, where the UE interprets N bits in the MCS field of the DCI as indicating the MCS index, where N can be any integer, such as 5. This can be applied to dynamically scheduled PUSCHs, for example, using a DCI for PUSCH scheduling, and / or unlicensed UL transmissions, for example, using a DCI for activating type 2 unlicensed UL transmissions. For unlicensed UL transmissions, disabling / enabling modulation rewriting can be applied to all UL transmissions activated by the active DCI.

[0212] Figure 10 A flowchart illustrating an example of PUSCH transmission according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be interpreted as an indication of the number of repetitions. Figure 10 The method 1000 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0213] At operation 1001, the UE receives configuration information, which may include configuration for supported MCS and / or repetition. Repetition of PUSCH and / or PDCCH can be configured, for example, via SIB1 or other system information or UE-specific RRC signaling. At operation 1002, the UE receives a PDCCH for transmitting DCI, which schedules PUSCH or activates unlicensed UL transmissions of type 2. At operation 1003, the UE checks whether the configured maximum MCS index is less than M, where M is a predefined number, such as 8 or 16. The UE also checks whether repetition is configured. If the configured maximum MCS index is less than M and repetition is configured, the UE sends a PUSCH at operation 1004 based on the configuration and DCI indication. The UE interprets NK bits (e.g., NK MSBs) in the MCS field of the DCI as indicating the MCS index, and interprets one or more bits of the remaining K bits (e.g., K LSBs) in the MCS field as indicating the number of PDCCH and / or PUSCH repetitions. N and K can be arbitrary integers, e.g., N can be 5 and K can be 1 or 2. For example, one or more sets of repetitions can be configured via RRC signaling, where each set contains X repetitions, e.g., for {Nrep1, Nrep2}, X = 2, where Nrep1 and Nrep2 can be any integer, such as 1, 2, 4, 8, 16, ..., 1024. K can be log2X to indicate which of the configured repetition sets should be used for PDCCH or PUSCH; e.g., for X = 2, K = 1 bit, where 0 indicates Nrep1 and 1 indicates Nrep2. If the configured maximum MCS index is not less than M or no repetition is configured, the UE sends a PUSCH at operation 1005 based on the configuration and DCI indication, where the UE interprets N bits in the MCS field of the DCI as indicating the MCS index, where N can be any integer, such as 5. This can be applied to dynamically scheduled PUSCHs, for example, using a DCI for PUSCH scheduling, and / or unlicensed UL transmissions, for example, using a DCI for activating type 2 unlicensed UL transmissions. For unlicensed UL transmissions, the repetition count can be applied to all PUSCHs activated by the activating DCI.

[0214] Reinterpret certain bits in the resource allocation field of the DCI to provide additional PUSCH instructions.

[0215] In implementations where the number of PRBs that can be allocated to a PUSCH is limited, one or more bits in the frequency domain resource allocation can be reinterpreted for other indications. For example, for scheduling flexibility, the configured BWP size can still be large, and the number of PRBs that can be allocated to a PUSCH can be limited, for example, one or two PRBs.

[0216] In one example, when the value of the HARQ process number is configured to be greater than a predefined value (e.g., 16), Y bits (e.g., Y LSBs) in the frequency domain resource allocation field of the DCI can be reinterpreted as an indication of the HARQ process number, where Y can be any integer (e.g., Y can be 1 or 2). This example can be applied to dynamically scheduled PUSCH.

[0217] In another example, when modulation rewriting is configured, Y bits (e.g., Y LSBs) in the frequency domain resource allocation field of the DCI can be reinterpreted as an indication of modulation rewriting. Y can be any integer, such as Y = 1, where one bit is 0 to disable modulation rewriting and one bit is 1 to enable it, and vice versa. This can be applied to dynamically scheduled PUSCHs, such as those using a DCI for PUSCH scheduling, and / or unlicensed UL transmissions, such as those using a DCI for activating type 2 unlicensed UL transmissions. For unlicensed UL transmissions, modulation rewriting enable / disable can be applied to all PUSCHs activated by the active DCI.

[0218] In some other examples, when PDCCH and / or PUSCH repetition is configured, the Y bits (e.g., Y LSBs) in the frequency domain resource allocation field of the DCI can be reinterpreted as an indication of the number of repetitions. For example, one or more groups of repetitions can be configured via RRC signaling (e.g., MIB, SIB1 or other SIBs, or UE-specific RRC signaling) where each group contains X repetitions, e.g., for {Nrep1, Nrep2}, X = 2, where Nrep1 and Nrep2 can be any integer, such as 1, 2, 4, 8, 16, ..., 1024. Y can be log2X to indicate which of the configured repetition groups should be used for PDCCH or PUSCH, e.g., for X = 2, Y = 1 bit, where 0 indicates Nrep1 and 1 indicates Nrep2. This can be applied to dynamically scheduled PUSCH, e.g., using DCI for PUSCH scheduling, and / or unlicensed UL transmissions, e.g., using DCI for activating unlicensed UL transmissions of type 2. For unauthorized UL transmissions, the repetition count can be applied to all PUSCHs activated by the active DCI.

[0219] Figure 11 A flowchart illustrating an example of a TBS indication for PDSCH transmission according to an embodiment of this disclosure is shown. Figure 11 The method 1100 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0220] At operation 1101, the BS generates and sends configuration information including an indication of the maximum TBS used for the PDSCH and / or an indication of the number of HARQ processes, wherein the indication can be explicit or implicit, and can be cell-specific or UE-specific. As an example, the indications of the maximum TBS and the number of HARQ processes can be associated. For example, the maximum TBS can be explicitly indicated, while the number of HARQ processes can be implicitly indicated based on the indicated maximum TBS, and vice versa. Alternatively, the indications of the maximum TBS and the number of HARQ processes can be independent. At operation 1102, the BS determines MCS indication information, and the MCS indication information is included in the DCI for scheduling the PDSCH, or in the DCI for DL ​​semi-permanent scheduling (SPS). At operation 1103, the BS receives the PDSCH based on the configuration and the DCI.

[0221] Figure 12 A flowchart illustrating an example of TBS determination for PDSCH reception according to an embodiment of this disclosure is shown. Figure 12 The method 1200 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0222] At operation 1201, the UE receives configuration information including an indication of the maximum TBS for the PDSCH and / or an indication of the number of HARQ processes, wherein the indication may be explicit or implicit, and may be cell-specific or UE-specific. As an example, the indications of the maximum TBS and the number of HARQ processes may be associated, as discussed above. Alternatively, the indications of the maximum TBS and the number of HARQ processes may be independent. At operation 1202, the UE receives a PDCCH carrying a DCI with an MCS indication. In one example, the DCI may be a DCI for dynamic scheduling of the PDSCH. In another example, the DCI may be a DCI for DL ​​SPS activation. At operation 1203, the UE calculates the scheduled TBS based on the configured maximum TBS and the MCS indication in the DCI. For example, TBS' represents the TBS indicated by the MCS field in the DCI, and TBS' represents the maximum TBS. max This represents the maximum TBS configured. The determined TBS can be min(TBS', TBS'). max At operation 1204, considering the calculated TBS value, the UE receives the PDSCH based on the configuration and DCI indication. In the example of dynamic PDSCH scheduling, the DCI may include a HARQ process number indication, and the UE determines the HARQ process number based on the configuration and DCI indication.

[0223] Clear indication of the maximum TBS for PDSCH

[0224] In one implementation of operations 1101 and 1202, the method of indicating the maximum TBS can be explicit. For example, the maximum TBS configuration can be cell-specific and can be configured by system information such as MIB, SIB1, other SIBs, and / or new SIBs. An example of explicit indication using SIB1 is shown in ASN.1 of Table 16, where IEs BWP-DownlinkCommon, DownlinkConfigCommonSIB, or servingCellConfigCommonSIB in SIB1 can be modified. In this example, IE PDSCH-ConfigCommon in IE BWP-DownlinkCommon is modified. Parameters N1, N2, ..., NK can be any integer, and the condition label "Cond NTN" refers to the NTN scenario. Throughout this disclosure, the condition label "Cond NTN" is given as an example and should be considered as an inclusion method. For systems other than NTN, the condition label can be changed accordingly.

[0225] Table 16

[0226] Example of IE PDSCH-ConfigCommon modification used to indicate the maximum TBS

[0227]

[0228] In the given example, different maximum TBS can be configured for PDSCH and PUSCH, while in some other examples, the maximum TBS for PDSCH and PUSCH can be configured jointly, for example, by sharing the same value and indicating it in IEservingCellConfigCommonSIB.

[0229] The following table 17 provides an example of introducing a new SIB to indicate the maximum TBS; for example, SIB15 could be introduced:

[0230] Table 17

[0231] Example of IE SIB15 modification used to indicate the maximum TBS.

[0232]

[0233] The parameters N1, N2, ..., NK and M1, M2, ..., ML can be any integers. In the given example, different maximum TBS can be configured for PDSCH and PUSCH, while in some other examples, the maximum TBS for PDSCH and PUSCH can be configured jointly, for example, by sharing the same value.

[0234] As another example of explicit indication, the maximum TBS configuration can be UE-specific and can be configured by UE-specific RRC signaling. An example of this configuration can be shown in ASN.1 of Table 18 below, where the IE PDSCH-ServingCellConfig is modified;

[0235] Table 18

[0236] Example of IE PDSCH-ServingCellConfig modification used to indicate the maximum TBS

[0237]

[0238] In the examples above, the same maximum TBS applies to the BWP of all UEs within a serving cell. Alternatively, the maximum TBS can be configured as a UE-specific value for the BWP via the IE PDSCH-Config in IE BWP-DownlinkDedicated, as shown in ASN.1 of Table 19:

[0239] Table 19

[0240] Example of IE PDSCH-Config modification used to indicate the maximum TBS

[0241]

[0242] In some examples, the increased number of HARQ processes can be configured in conjunction with the TBS reduction feature. As an example of the above implementation with an explicit indication of the maximum TBS, the number of HARQ processes can be implicitly indicated based on the configured maximum TBS. cur Indicates the maximum TBS supported in the system (e.g., in the current NR system) or a predefined TBS value, and is determined by the TBS. max This represents the maximum TBS configured in the system. The number of HARQ processes in the system can be no more than [number missing]. The size of the UE soft buffer can be any integer or a power of 2, where N is a predefined number (e.g., N = 16). Using this option, the UE soft buffer size can be kept the same as some predefined systems (e.g., in NR systems) or kept to a certain predefined value.

[0243] In one implementation, the above configuration method can be applied to both dynamically scheduled PDSCH and SPS PDSCH. In one example of this implementation, the same maximum TBS value is applied to both dynamically scheduled PDSCH and SPS PDSCH. In another example of this implementation, different maximum TBS values ​​can be configured for dynamically scheduled PDSCH and SPS PDSCH. In this example, the configuration method above will indicate two parameters, for example, "sps-maxTBSPDSCH" can be added to the above IE to indicate the maximum TBS used for SPS PDSCH, while the parameter given in the above IE, such as "maxTBSPDSCH", can indicate the maximum TBS used for dynamically scheduled PDSCH. These parameter names are merely examples and should be considered as inclusion (that is, other names can also be used).

[0244] Alternatively, the above method is only applied to dynamically scheduled PDSCHs, while the following method can be applied to SPPSDSCHs for configuring the maximum TBS. The maximum TBS for SPS PDSCHs can be explicitly indicated in UE-specific RRC signaling, such as in IE SPS-Config. Parameters N1, N2, ..., NK can be any integer.

[0245] Table 20

[0246] Example of IE SPS-Config modification used to indicate the maximum TBS for SPS PDSCH.

[0247]

[0248] Implicit indication of maximum TBS for PDSCH

[0249] As another implementation of operations 1101 and 1201, the method for indicating the maximum TBS used for PDSCH can be implicit. As an example, the mapping between the maximum TBS and the system scenario / mode can be predefined. Once the system scenario / mode is indicated, the maximum TBS, for example, the TBS of system scenario / mode N, can be determined accordingly. max-N Here, N is an index such as 1, 2, etc. In one example, the number of HARQ processes can be configured similarly, and the mapping between the number of HARQ processes and the system scenario / mode can be predefined. Once the system scenario / mode is indicated, the number of HARQ processes can be determined accordingly, for example, X for system scenario / mode N. NAs an example of this implementation, the configuration of system scenarios / modes can be cell-specific and can be configured by system information, such as via MIB, SIB1, other SIBs, and / or new SIBs introduced for the system. For example, one reserved bit in the MIB can be used to indicate two scenarios / modes. Another example of using SIB1 for this indication is shown by ASN.1 and Table 21 below, where parameter N can be any integer. The parameters in the following examples use "NTN mode" as an example for NTN systems, while other names can be used for other systems. In one example, the mapping between maximum TBS and system scenarios / modes can be the same for dynamically scheduled PDSCH and SPS PDSCH. Alternatively, different mappings between maximum TBS and system scenarios / modes can be predefined for dynamically scheduled PDSCH and SPS PDSCH. For example, this implementation can be applied to configure the maximum TBS for dynamically scheduled PDSCH, while the maximum TBS for SPS PDSCH can be configured separately, and vice versa.

[0250] Table 21

[0251] Example of IE SIB1 modification used to indicate system scenario / mode

[0252]

[0253]

[0254] As another example, the maximum TBS can be implicitly indicated based on the configured number of HARQ processes. CUR This represents the maximum TBS supported by the system or a predefined TBS value, and L represents the number of configured HARQ processes. The maximum TBS can be any integer or a predefined value supported by the system (e.g., NR system) not exceeding [a certain value]. The maximum TBS is calculated using any TBS, where N is a predefined number (e.g., N = 16). In one example, the calculated maximum TBS can be applied to both dynamically scheduled PDSCH and SPS PDSCH. In another example, the calculated maximum TBS is applied to dynamically scheduled PDSCH, while the maximum TBS for SPS PDSCH can be configured separately, and vice versa.

[0255] In one example, the configuration for the number of HARQ processes can be cell-specific, carried in the MIB, SIB1, or other system information. For example, reserved bits in the MIB can be used to indicate two possible numbers of HARQ processes, such as 16 and 32. Alternatively, SIB1 can carry an explicit indication of the number of HARQ processes, where the IEs BWP-DownlinkCommon, DownlinkConfigCommonSIB, or servingCellConfigCommonSIB in SIB1 can be modified. In this example shown by ASN.1 in Table 22, the IE pdsch-ConfigCommon is modified. Parameters N1, N2, ..., NK can be any integer, and the condition label “Cond NTN” refers to the NTN scenario. In the given example, different numbers of HARQ processes can be configured for DL ​​and UL, while in some other examples, the number of HARQ processes for DL ​​and UL can be configured jointly, for example, sharing the same value and indicated in the IE servingCellConfigCommonSIB.

[0256] Table 22

[0257] Example of IE PDSCH-ConfigCommon modification used to indicate the number of HARQ processes.

[0258]

[0259] Alternatively, the number of HARQ processes can be UE-specific. The configuration of the number of HARQ processes can be indicated by UE-specific RRC signaling. An example of this configuration can be shown in ASN.1 of Table 23, where the IE PDSCH-ServingCellConfig is modified:

[0260] Table 23

[0261] Example of IE PDSCH-ServingCellConfig modification used to indicate the number of HARQ processes.

[0262]

[0263] In the examples above, the same number of HARQ processes is applied to the BWP of all UEs in a serving cell. Alternatively, the number of HARQ processes can be configured as a UE-specific value for the BWP via IE PDSCH-Config in IE BWP-DownlinkDedicated. In one example shown in ASN.1 of Table 24, the number of HARQ processes configured for different DL BWPs can be different.

[0264] Table 24

[0265] Example of IE PDSCH-Config modification used to indicate the number of HARQ processes

[0266]

[0267] In one example, the number of HARQ processes indicated above applies to dynamically scheduled PDSCH, while the number of HARQ processes for SPSPDSCH is configured by IE SPS-Config. Alternatively, the number of HARQ processes indicated above can be the total number of HARQ processes including both dynamically scheduled PDSCH and SPS PDSCH. In some examples, the number of HARQ processes for SPS PDSCH can be configured via the parameter “nrofHARQ-Processes” in IE SPS-Config, where the possible values ​​of “nrofHARQ-Processes” can be expanded, for example, from the integers (1..8) in Table 20 to the integers (1..N), where N can be any integer, such as 16 or 32.

[0268] In yet another example, the maximum TBS can be implicitly indicated based on the maximum number of frequency resources that can be allocated to the PDSCH (e.g., the maximum number of PRBs that can be allocated to the PDSCH). The maximum TBS can then be calculated based on the TBS determination in section 5.1.3.2 of [38.214]. In an example where the features of HARQ enhancement and TBS reduction are jointly configured, the number of HARQ processes can be implicitly indicated based on the configured maximum TBS. As described above, the TBS... CUR This indicates the current maximum number of TBS supported in the system, and is determined by the number of TBS. max This represents the maximum TBS for the system configuration under consideration; the number of HARQ processes can be no more than [number missing]. Any integer or power of 2.

[0269] Using this option, the UE soft buffer size can remain the same as the current system or remain at a predefined value. For indicating the maximum number of frequency resources, the indication method can be the same as or similar to the method for indicating HARQ processes, where the parameter “nrofHARQ-Processes” is replaced with “nrofPRB”, as shown in Tables 22 to 24, for example.

[0270] In one example, the above configuration of the maximum number of frequency resources can be applied to both dynamically scheduled PDSCH and SPS PDSCH. Alternatively, the above configuration of the maximum number of frequency resources can be applied to dynamically scheduled PDSCH, while the maximum number of frequency resources for SPS PDSCH can be configured separately, and vice versa. For example, the maximum number of frequency resources for SPS PDSCH can be configured in IE SPS-Config, as shown in Table 25 below, where N1, N2, ..., NK can be any integer. The maximum TBS can then be calculated based on the TBS determination in part 5.1.3.2 of [38.214].

[0271] Table 25

[0272] Example of an IE SPS-Config modification used to indicate the maximum number of PRBs for SPS PDSCH.

[0273]

[0274] MCS Determination Method

[0275] Figure 13 A flowchart illustrating an example of an MCS indication for PDSCH transmission according to an embodiment of this disclosure is shown. Figure 13 The method 1300 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0276] At operation 1301, the BS generates and sends configuration information including an indication of the supported MCS for PDSCH, which can be explicit or implicit, and can be cell-specific or UE-specific. In one example, the maximum MCS index for PUSCH can be the same as the maximum MCS index for PDSCH, and the configuration method discussed above for PDSCH can be applied without requiring other configuration methods for PUSCH. Alternatively, the configuration of the maximum MCS index for PDSCH and PUSCH can be independent. At operation 1302, the BS generates and sends a DCI for PDSCH scheduling or for activating SPS PDSCH, where the DCI may carry MCS indication information and may use certain bits in the MCS field of the DCI for other indications. For example, some bits in the MCS field may be used in conjunction with the HARQ process number field, which indicates the number of HARQ processes. As another example, some bits in the MCS field may be used to indicate that HARQ-ACK feedback is disabled. In another example, if the repetition feature is configured, some bits in the MCS field can be used to indicate the number of repetitions. Some bits in the MCS field can also be used to indicate whether the modulation order indicated by the MCS field should be rewritten to some predefined modulation scheme, such as QPSK. In one example, this modulation rewrite indication is only used when repetition is configured. Alternatively, this modulation rewrite indication can be enabled by higher-layer signaling, such as cell-specific signaling or UE-specific RRC signaling. At operation 1303, the BS transmits the PDSCH based on the DCI and / or configuration.

[0277] Figure 14 A flowchart illustrating an example of an MCS indication for PDSCH transmission according to an embodiment of this disclosure is shown. Figure 14 The method 1400 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0278] At operation 1401, the UE receives configuration information including an indication of the supported MCS for PDSCH, which can be explicit or implicit, and can be cell-specific or UE-specific. At operation 1402, the UE receives a DCI for PDSCH scheduling or for activating SPS PDSCH, and interprets the MCS indication and other indications based on the configuration. In one example, the maximum MCS index can be limited (e.g., less than 31 in an NR system), and some bits in the MCS field can be used for other indications, such as a joint indication of the number of HARQ processes, disabling HARQ-ACK feedback, an indication of the number of repetitions, and / or an indication of modulation order rewriting. At operation 1403, the UE receives PDSCH based on the configuration and DCI indications.

[0279] In one embodiment of operations 1301 and 1401, the indications of the maximum MCS indexes for PDSCH and PUSCH are associated. For example, the mapping between the maximum MCS index for PDSCH and the maximum MCS index for PUSCH can be predefined, such as the maximum MCS index for PUSCH being defined as the same as the maximum MCS index configured for PDSCH. Alternatively, the configurations of the maximum MCS indices for PDSCH and PUSCH can be independent.

[0280] Explicit indication of the largest MCS index for PDSCH

[0281] In one implementation of operations 1301 and 1401, the configuration of the supported MCS can be explicit. In one example, the configuration can be cell-specific and can be configured by system information such as MIB, SIB1, other SIBs, and / or new SIBs. An example of explicit indication using SIB1 is shown in ASN.1 within Table 26, where IEsBWP-DownlinkCommon, DownlinkConfigCommonSIB, or servingCellConfigCommonSIB in SIB1 can be modified. In this example, IE PDSCH-ConfigCommon in IE BWP-DownlinkCommon is modified. Parameters X1, X2, ..., Xn can be any integers, and the condition label “Cond NTN” refers to the NTN scenario. For other systems, the condition label can be changed accordingly.

[0282] Table 26

[0283] Example of IE PDSCH-ConfigCommon modification used to indicate the maximum MCS index

[0284]

[0285] Table 27, ASN.1, provides examples of introducing new SIBs to indicate the maximum TBS; for example, SIB15 could be introduced into the system. Parameters X1, X2, ..., Xn and Y1, Y2, ..., Yn can be any integers. In the given example, different maximum MCS indices can be configured for PDSCH and PUSCH, while in some other examples, the maximum MCS indices for PDSCH and PUSCH can be configured jointly, for example, sharing the same value.

[0286] Table 27

[0287] Example of IE SIB15 modification used to indicate the maximum MCS index

[0288]

[0289] Alternatively, the explicit indication of the supported MCS can be UE-specific and can be configured by UE-specific RRC signaling. An example of this configuration can be shown in ASN.1 of Table 28, where the IE PDSCH-ServingCellConfig is modified.

[0290] Table 28

[0291] Example of IE PDSCH-ServingCellConfig modification used to indicate the maximum MCS index.

[0292]

[0293] In the examples above, the same maximum MCS index is applied to the BWP of all UEs in a serving cell. Alternatively, the maximum MCS index can be configured as a UE-specific value for the BWP via IE PDSCH-Config in IE BWP-DownlinkDedicated, as shown in ASN.1 in Table 29.

[0294] Table 29

[0295] Example of IE PDSCH-Config modification used to indicate the maximum MCS index

[0296]

[0297] In one example, different maximum MCS indices can be configured for PDSCH and PUSCH, while in some other examples, the maximum MCS indices for PDSCH and PUSCH can be configured together, for example, sharing the same value and being configured by any of the methods mentioned above.

[0298] In one example, the configured maximum MCS can be applied to both dynamically scheduled PDSCH and SPS PDSCH. Alternatively, the configured maximum MCS can be applied to dynamically scheduled PDSCH, while the maximum MCS for SPS PDSCH can be configured separately, and vice versa. In the latter example, two parameters can be introduced for the maximum MCS configuration, one for dynamically scheduled PDSCH, such as "pdsch-maxMCSindex", and another for SPS PDSCH, such as "sps-pdsch-maxMCSindex", which can be added to the IEs discussed above (e.g., IEs in SIB1, such as PDSCH-ConfigCommon, the new SIB, PDSCH-ServingCellConfig, or PDSCH-Config). As another example, the maximum MCS for SPS PDSCH can be configured by UE-specific RRC signaling, for example, in the IE SPS-Config. Parameters N1, N2, ..., NK can be any integer, such as 0, 1, 2, ..., 31.

[0299] Table 30

[0300] Example of IE SPS-Config modification used to indicate the maximum MCS for SPS PDSCH.

[0301]

[0302] Implicit indication of the maximum MCS index used for PDSCH

[0303] In one implementation of operations 1301 and 1401, the configuration of the supported MCS can be implicit. In one example, the configuration can be cell-specific. As an example, the mapping between the maximum MCS index and the system scenario / mode can be predefined. Once the system scenario / mode is indicated, the maximum MCS index, for example, the MCS of scenario / mode N, can be determined accordingly. max-NWhere N is an index such as 1, 2, etc. As an example of this implementation, the configuration of system scenarios / modes can be cell-specific and can be configured by system information, such as via MIB, SIB1, other SIBs, and / or new SIBs introduced for the system. For example, one reserved bit in the MIB can be used to indicate two scenarios / modes. Table 21 above shows another example of using SIB1 for this indication. In one example, the mapping between the maximum MCS and system scenarios / modes can be the same for dynamically scheduled PDSCH and SPSPDSCH. Alternatively, different mappings between the maximum MCS and system scenarios / modes can be predefined for dynamically scheduled PDSCH and SPS PDSCH.

[0304] Modulation rewrite configuration

[0305] In one implementation of operations 1302 and 1402, the indicated modulation scheme can be rewritten. For example, when modulation rewriting is enabled, the modulation scheme indicated by the MCS field can be rewritten to a predefined modulation scheme, such as rewriting to use a lower-order modulation, such as QPSK. The modulation scheme to be rewritten can be predefined, such as QPSK. In one example of this implementation, modulation rewriting can be configured by higher-layer signaling, such as cell-specific signaling via MIB, SIB1, or other SIBs, or modulation rewriting can be configured by UE-specific RRC signaling. The signaling method can be similar to the indication of TBS for PDSCH, for example, introducing a parameter such as “modulationOverriden-pdsch” into the IE in Tables 15 to 20. Alternatively, the signaling method can be predefined as whether modulation rewriting is configured for certain system scenarios / modes, which can be indicated, for example, by the IE in Table 21. In one example, the configuration of modulation rewriting can depend on other configurations, for example, modulation rewriting is configured when configuration repeats and / or TTI bundling.

[0306] In one example, modulation rewriting is enabled when it is configured. In another example, modulation rewriting is enabled when modulation rewriting is configured and the PDSCH or SPS PDSCH dynamically scheduled by the DCI is indicated to have a specific number of repetitions (e.g., repetitions > 1) and / or a specific number of TTIs for TTI bundling. In this example, there is no dynamic indication of modulation rewriting. In another example, the DCI can dynamically indicate whether modulation rewriting is enabled or disabled when it is configured. In yet another example, modulation rewriting is enabled when the coding rate is within a certain range when it is configured, for example, the coding rate using the rewritten modulation scheme is no greater than a specific value X, where X can be predefined or configured by higher-layer signaling.

[0307] DCI Design

[0308] In one implementation, the MCS field in the DCI can be configurable. The number of bits in the MCS field can be adjusted according to the configured maximum MCS index. For example, with a configured maximum MCS index of 15, the MCS field in the DCI can be 4 bits.

[0309] In one implementation, the supported MCSs may be limited, and the MCS field may have some bits available for other indications. For example, the MCS index may be configured to have up to 7 or 15, and the MCS field may have 1 or 2 available bits available for other indications.

[0310] Figure 15 A flowchart illustrating an example of PDSCH reception according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be reinterpreted as an indication of the number of HARQ processes. Figure 15 The method 1500 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0311] At operation 1501, the UE receives configuration information, which may include configuration of the supported MCS and / or the number of HARQ processes used for PDSCH. At operation 1502, the UE receives the PDCCH of the DCI that transmits the PDSCH. At operation 1503, the UE checks whether the configured maximum MCS index is less than M, where M is a predefined number, such as 8 or 16. The UE also checks whether the number of HARQ processes configured for the PDSCH is greater than L, where L is a predefined number, such as 16. If the configured maximum MCS index is less than M and the configured number of HARQ processes is greater than L, then at operation 1504, the UE receives the PDSCH based on the configuration and DCI indication, where the UE interprets the NK bits (e.g., NK MSBs) in the MCS field of the DCI as indicating the MCS index, and interprets one or more bits in the remaining K bits (e.g., K LSBs) in the MCS field as indicating the number of HARQ processes, where N and K can be any integers, for example, N can be 5 and K can be 1 or 2. For example, the existing HARQ process number field in the DCI indicates the MSB in the HARQ process number, while the K LSBs in the MCS field can be reinterpreted as LSBs indicating the HARQ process number. If the configured maximum MCS index is not less than M or the configured HARQ process number is less than or equal to L, the UE receives the PDSCH at Operation 1505 based on the configuration and the DCI indication, where the UE interprets the N bits in the MCS field of the DCI as indicating the MCS index, where N can be any integer, such as 5. This example can be applied to dynamically scheduled PDSCHs.

[0312] Figure 16 A flowchart illustrating an example of PDSCH reception according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be reinterpreted as an indication of HARQ disabling. Figure 16 The method 1600 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0313] At operation 1601, the UE receives configuration information that may include configuration for disabling supported MCS and / or HARQ. HARQ-ACK feedback disabling can be configured, for example, via SIB1 or other system information, or UE-specific RRC signaling. In one example, HARQ disabling means disabling HARQ-ACK feedback for PDSCH. When HARQ is enabled, the UE is not expected to receive another (different) PDSCH for a given HARQ process until after the expected transmission of HARQ acknowledgment (HARQ-ACK) for that HARQ process has ended (e.g., as described in [38.214]). When HARQ is disabled, the UE can receive another PDSCH (different from the previous PDSCH) to end a given HARQ process without waiting until after the transmission of HARQ-ACK feedback for that HARQ process has ended. In one example, if HARQ is disabled, the UE can skip the transmission of HARQ-ACK feedback for that HARQ process. At operation 1602, the UE receives the PDCCH transmitting the DCI, which schedules the PDSCH or activates the SPS PDSCH. At operation 1603, the UE checks whether the configured maximum MCS index is less than M, where M is a predefined number, such as 8 or 16. The UE also checks whether HARQ is disabled. If the configured maximum MCS index is less than M and HARQ is disabled, the UE receives the PDSCH at operation 1604 based on the configuration and the DCI indication, where the UE interprets NK bits (e.g., NK MSBs) in the MCS field of the DCI as indicating the MCS index, and interprets one or more of the remaining K bits (e.g., K LSBs) in the MCS field as indicating HARQ disable, where N and K can be any integers, such as N being 5 and K being 1 or 2. For example, K can be 1, and when this bit is 0, HARQ is disabled; when this bit is 1, HARQ is not disabled (enabled), and vice versa. If the configured maximum MCS index is not less than M or HARQ is not configured to be disabled, the UE receives PDSCH at Operation 1605 based on the configuration and DCI indication, where the UE interprets N bits in the MCS field of the DCI as indicating the MCS index, where N can be any integer, such as 5. This can be applied to dynamically scheduled PDSCH, for example, using the DCI used for PDSCH scheduling and / or SPS PDSCH, for example, using the DCI used to activate SPS PDSCH. In the case of SPS PDSCH, HARQ disabling / enabling can be applied to all SPS PDSCH activated by the activating DCI.

[0314] Figure 17A flowchart illustrating an example of PDSCH reception according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be reinterpreted as an indication of modulation rewriting. Figure 17 The method 1700 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0315] At operation 1701, the UE receives configuration information, which may include configuration for supported MCS and / or modulation rewriting. Modulation rewriting can be configured, for example, via SIB1 or other system information, or UE-specific RRC signaling. At operation 1702, the UE receives a PDCCH for transmitting DCI, which schedules PDSCH or activates SPS PDSCH. At operation 1703, the UE checks whether the configured maximum MCS index is less than M, where M is a predefined number, such as 8 or 16. The UE also checks whether modulation rewriting is configured. If the configured maximum MCS index is less than M and modulation rewriting is configured, the UE receives the PDSCH at operation 1704 based on the configuration and DCI indication, where the UE interprets NK bits (e.g., NK MSBs) in the MCS field of the DCI as indicating the MCS index, and interprets one or more of the remaining K bits (e.g., K LSBs) in the MCS field as indicating modulation rewriting, where N and K can be any integers, for example, N can be 5 and K can be 1 or 2. For example, K can be 1, and when this bit is 0, modulation rewriting is disabled, and when this bit is 1, modulation rewriting is enabled, and vice versa. If the configured maximum MCS index is not less than M or modulation rewriting is not configured, the UE receives PDSCH at operation 1705 based on the configuration and DCI indication, where the UE interprets N bits in the MCS field of the DCI as indicating the MCS index, where N can be any integer, such as 5. This can be applied to dynamically scheduled PDSCHs, for example, using the DCI used for PDSCH scheduling and / or SPS PDSCHs, for example, using the DCI used to activate SPS PDSCHs. In the case of SPS PDSCHs, disabling / enabling modulation rewriting can be applied to all SPS PDSCHs activated by the activating DCI.

[0316] Figure 18 A flowchart illustrating an example of PDSCH reception according to an embodiment of this disclosure is shown, wherein one or more bits in the MCS field can be reinterpreted as an indication of the number of repetitions. Figure 18 The method 1800 described herein is for illustrative purposes only. Other embodiments may be used without departing from the scope of this disclosure.

[0317] At operation 1801, the UE receives configuration information, which may include configuration for supported MCS and / or repetition. Repetition of PDSCH and / or PDCCH can be configured, for example, via SIB1 or other system information or UE-specific RRC signaling. At operation 1802, the UE receives a PDCCH for transmitting DCI, which schedules PDSCH or activates SPS PDSCH. At operation 1803, the UE checks whether the configured maximum MCS index is less than M, where M is a predefined number, such as 8 or 16. The UE also checks whether repetition is configured. If the configured maximum MCS index is less than M and repetition is configured, the UE receives PDSCH at Operation 1804 based on the configuration and DCI indication. The UE interprets NK bits (e.g., NK MSBs) in the MCS field of the DCI as indicating the MCS index and one or more bits of the remaining K bits (e.g., K LSBs) in the MCS field as indicating the number of repetitions used for PDCCH and / or PDSCH. N and K can be any integers, e.g., N can be 5 and K can be 1 or 2. For example, one or more sets of repetition numbers can be configured via RRC signaling, where each set contains X repetitions, e.g., for {Nrep1, Nrep2}, X = 2, where Nrep1 and Nrep2 can be any integers, such as 1, 2, 4, 8, 16, ..., 1024. K can be log2X to indicate which of the configured repetition number sets should be used for PDCCH or PDSCH, e.g., for X = 2, K = 1, where 0 indicates Nrep1 and 1 indicates Nrep2. If the configured maximum MCS index is not less than M or no repetition is configured, the UE receives PDSCH at Operation 1805 based on the configuration and DCI indication, where the UE interprets N bits in the MCS field of the DCI as indicating the MCS index, where N can be any integer, such as 5. This can be applied to dynamically scheduled PDSCHs, for example, using the DCI used for PDSCH scheduling and / or SPS PDSCHs, for example, using the DCI used to activate SPS PDSCHs. In the case of SPS PDSCHs, the repetition count can be applied to all SPS PDSCHs activated by the activating DCI.

[0318] Reinterpret certain bits in the resource allocation field of the DCI to provide additional indications for PDSCH.

[0319] In implementations where the number of PRBs that can be allocated to the PDSCH is limited, one or more bits in the frequency domain resource allocation can be reinterpreted for other indications. For example, for scheduling flexibility, the configured BWP size can still be large, and the number of PRBs that can be allocated to the PDSCH can be limited, for example, one or two PRBs.

[0320] In one example, when the number of HARQ processes is configured to be greater than a predetermined value (e.g., 16), Y bits (e.g., Y LSBs) in the frequency domain resource allocation field of the DCI can be reinterpreted as an indication of the number of HARQ processes, where Y can be any integer (e.g., Y can be 1 or 2). This example can be applied to dynamically scheduled PDSCH.

[0321] In another example, when HARQ is disabled, Y bits (e.g., Y LSBs) in the frequency domain resource allocation field of the DCI can be reinterpreted as an indication of HARQ disabling. Y can be any integer, such as Y = 1, where this bit is 0 for HARQ disabled and 1 for HARQ enabled, and vice versa. This can be applied to dynamically scheduled PDSCHs, for example, using a DCI for PDSCH scheduling and / or SPS PDSCHs, for example, using a DCI for activating SPS PDSCHs. In the case of SPS PDSCHs, HARQ enabling / disabling can be applied to all SPS PDSCHs activated by the activating DCI.

[0322] In another example, when modulation rewriting is configured, Y bits (e.g., Y LSBs) in the frequency domain resource allocation field of the DCI can be reinterpreted as an indication of modulation rewriting. Y can be any integer, such as Y = 1, where this bit is 0 for disabling modulation rewriting and 1 for enabling modulation rewriting, and vice versa. This can be applied to dynamically scheduled PDSCHs, for example, using a DCI for PDSCH scheduling and / or SPS PDSCHs, for example, using a DCI for activating SPPS PDSCHs. In the case of SPS PDSCHs, enabling / disabling modulation rewriting can be applied to all SPS PDSCHs activated by the activating DCI.

[0323] In some other examples, when repetitions are configured for PDCCH and / or PDSCH, the Y bits (e.g., Y LSBs) in the frequency domain resource allocation field of the DCI can be reinterpreted as an indication of the number of repetitions. For example, one or more groups of repetition numbers can be configured via RRC signaling (e.g., MIB, SIB1, or other SIBs, or UE-specific RRC signaling) where each group contains X repetitions, e.g., for {Nrep1, Nrep2}, X = 2, where Nrep1 and Nrep2 can be any integers, such as 1, 2, 4, 8, 16, ..., 1024. Y can be log2X to indicate which of the configured repetition number groups should be used for PDCCH or PDSCH, e.g., for X = 2, Y = 1, where 0 indicates Nrep1 and 1 indicates Nrep2. This can be applied to dynamically scheduled PDSCH, e.g., using the DCI for PDSCH scheduling and / or SPS PDSCH, e.g., using the DCI for activating SPSPDSCH. For the case of SPSPDSCH, the number of repetitions can be applied to all SPSPDSCH activated by the activation DCI.

[0324] While this disclosure has been described using exemplary embodiments, various changes and modifications will be apparent to those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A base station in a wireless communication system, comprising: transceiver, and A controller, which is connected to and configured to: Configuration information is sent to the terminal, including one of several defined Non-Land Network (NTN) modes, where each NTN mode is mapped to a Maximum Transport Block Size (TBS) and a Hybrid Automatic Repeat Request (HARQ) process count, and... Based on the TBS determined according to the maximum number of TBS and the number of HARQ processes, the Physical Uplink Shared Channel (PUSCH) is received from the terminal or the Physical Downlink Shared Channel (PDSCH) is sent to the terminal.

2. The base station according to claim 1, wherein, The maximum TBS is determined based on the maximum number of frequency domain resources.

3. The base station according to claim 2, wherein, The maximum number of frequency domain resources is indicated by the Master Information Block (MIB) or the System Information Block (SIB).

4. The base station according to claim 1, wherein, The maximum TBS is determined based on the configured number of HARQ processes.

5. A method performed by a base station in a wireless communication system, comprising: Configuration information is sent to the terminal, including one of several defined Non-Land Network (NTN) modes, where each NTN mode is mapped to a Maximum Transport Block Size (TBS) and a Hybrid Automatic Repeat Request (HARQ) process count, and... Based on the TBS determined according to the maximum number of TBS and the number of HARQ processes, the Physical Uplink Shared Channel (PUSCH) is received from the terminal or the Physical Downlink Shared Channel (PDSCH) is sent to the terminal.

6. The method according to claim 5, wherein, The maximum TBS is determined based on the maximum number of frequency domain resources.

7. The method according to claim 6, wherein, The maximum number of frequency domain resources is indicated by the Master Information Block (MIB) or the System Information Block (SIB).

8. The method according to claim 5, wherein, The maximum TBS is determined based on the configured number of HARQ processes.

9. A terminal in a wireless communication system, comprising: transceiver, and A controller, which is connected to and configured to: Configuration information is received from the base station, which includes one of several defined Non-Terrestrial Network (NTN) modes, where each NTN mode is mapped to a Maximum Transport Block Size (TBS) and a Hybrid Automatic Repeat Request (HARQ) process count. The TBS is determined based on the maximum TBS, and Based on the determined TBS and the number of HARQ processes, the Physical Uplink Shared Channel (PUSCH) is sent to the base station or the Physical Downlink Shared Channel (PDSCH) is received from the base station.

10. The terminal according to claim 9, wherein, The maximum TBS is determined based on the maximum number of frequency domain resources.

11. The terminal according to claim 10, wherein, The maximum number of frequency domain resources is indicated by the Master Information Block (MIB) or the System Information Block (SIB).

12. The terminal according to claim 9, wherein, The maximum TBS is determined based on the configured number of HARQ processes.

13. A method performed by a terminal in a wireless communication system, comprising: Configuration information is received from the base station, which includes one of several defined Non-Terrestrial Network (NTN) modes, where each NTN mode is mapped to a Maximum Transport Block Size (TBS) and a Hybrid Automatic Repeat Request (HARQ) process count. The TBS is determined based on the maximum TBS, and Based on the determined TBS and the number of HARQ processes, the Physical Uplink Shared Channel (PUSCH) is sent to the base station or the Physical Downlink Shared Channel (PDSCH) is received from the base station.

14. The method according to claim 13, wherein, The maximum TBS is determined based on the maximum number of frequency domain resources.

15. The method according to claim 14, wherein, The maximum number of frequency domain resources is indicated by the Master Information Block (MIB) or the System Information Block (SIB).

16. The method according to claim 13, wherein, The maximum TBS is determined based on the configured number of HARQ processes.

Images