Relay device, user equipment and base station apparatus supporting uplink grant-free scheduling

Abstract

The application provides a relay device supporting uplink grant-free scheduling, a user equipment and a base station device, which are used for communication with the user equipment and the base station device, and comprise a receiving circuit configuration and a sending circuit configuration. According to second downlink control information, an uplink shared channel is dynamically scheduled through a backhaul link to forward a received access link grant-free scheduling physical uplink shared channel. The network-controlled relay adopted by the application is an enhanced type of the conventional RF relay, which has the ability to receive and process the side control information from the network. The side control information can make the network-controlled relay perform amplification and forwarding operation in a more effective way. The potential benefits can include reducing unnecessary noise amplification, having better spatial directivity of transmission and reception, and simplifying network integration.

Description

Technical Field

[0001] This invention relates to the field of communication system technology, and more specifically, to a repeater device, user equipment, and base station device that support uplink unlicensed scheduling. Background Technology

[0002] 3GPP Long Term Evolution (LTE) is the name of a project aimed at improving the handphone or device standards of the Universal Mobile Telecommunications System (UMTS) to meet future needs. In one aspect, UMTS has been modified to provide support and specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0003] Certain systems and methods disclosed in this invention may be described in relation to 3GPP LTE, LTE-Advanced (LTE-A), LTE-A-Pro, and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, and / or 15). However, the scope of the invention should not be limited in this respect. Certain systems and methods disclosed in this invention can be used in other types of wireless communication systems.

[0004] Wireless communication equipment is an electronic device used to communicate with a base station, which in turn communicates with a network of devices (e.g., the Public Switched Telephone Network, the Internet, etc.). In describing the systems and methods of this invention, wireless communication equipment may be alternatively referred to as a mobile station, UE, access terminal, user station, mobile terminal, remote station, user terminal, terminal, user unit, mobile device, etc. Examples of wireless communication equipment include mobile phones, smartphones, personal digital assistants (PDAs), laptops, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, wireless communication equipment is typically referred to as UE. However, since the scope of this invention should not be limited to the 3GPP standard, the terms "UE" and "wireless communication equipment" are used interchangeably herein to refer to the more general term "wireless communication equipment." UE may also be more generally referred to as a terminal device.

[0005] In 3GPP specifications, base stations are typically referred to as Node B, evolved Node B (eNB), home enhanced, or evolved Node B (HeNB) or other similar terms. Since the scope of this invention should not be limited to the 3GPP standard, the terms "base station," "Node B," "eNB," "gNB," and / or "HeNB" may be used interchangeably to refer to the more general term "base station." Furthermore, the term "base station" can be used to refer to an access point. An access point can be an electronic device that provides a means for wireless communication devices to access a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication equipment" can be used to refer to wireless communication equipment and / or base stations. An eNB can also be more generally referred to as base station equipment.

[0006] It is worth noting that the term "cell" as used herein may refer to any communication channel designated by standardization or regulatory bodies for International Mobile Telecommunications-Advanced (IMT-Advanced), and 3GPP may use all or part of it as licensed frequency bands (e.g., frequency bands) for communication between the eNB and UE. Furthermore, for the general description of E-UTRA and E-UTRAN, the term "cell" as used herein may be defined as "a combination of downlink and optional uplink resources." The link between the carrier frequencies of the downlink resources and the carrier frequencies of the uplink resources can be indicated in the system information transmitted on the downlink resources.

[0007] A "configured cell" refers to a cell that the UE is aware of and that the eNB allows to send or receive information. A "configured cell" can be a serving cell. The UE can receive system information and perform necessary measurements on all configured cells. A "configured cell for radio connectivity" may include a primary cell and / or none, or one or more secondary cells. An "active cell" is a configured cell that the UE is currently sending and receiving. That is, an active cell is the cell that the UE monitors the Physical Downlink Control Channel (PDCCH), and in the case of downlink transmissions, it is the cell that the UE decodes the Physical Downlink Shared Channel (PDSCH). An "inactive cell" is a configured cell that the UE does not monitor for PDCCH transmissions. It should be noted that a "cell" can be described in different dimensions. For example, a "cell" may have temporal, spatial (e.g., geographical), and frequency characteristics.

[0008] Fifth-generation (5G) cellular communication (also known as "New Radio," "New Radio Access Technology," or "NR" by 3GPP) aims to utilize time, frequency, and / or spatial resources to enable services such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC), as well as massive machine-type communication (MMTC). To meet latency targets and high reliability, it supports mini-slot-based repetition, providing flexible transmission timing. New Radio (NR) base stations can be called gNBs. gNBs can also be more generally referred to as base station equipment.

[0009] A key objective of 5G is to enable connected industry. 5G connectivity can act as a catalyst for the next wave of industrial transformation and digitalization, improving flexibility, enhancing productivity and efficiency, reducing maintenance costs, and improving operational safety. Devices in such environments may include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, and more. Connecting these sensors and actuators to the 5G network and core is desirable. Large-scale Industrial Wireless Sensor Network (IWSN) use cases and requirements encompass not only the very demanding URLLC services but also relatively low-end services requiring small device form factors and / or complete wireless connectivity with battery lifespans of several years. These services have higher requirements than Low Power Wide Area Networks (LPWAs) such as LTE-MTC and / or Narrowband Internet of Things (LTE-M / NB-IoT), but lower requirements than URLLC and eMBB.

[0010] This invention describes the Network Control Repeater (NCR). Coverage is a fundamental aspect of cellular network deployment, and mobile operators rely on different types of network nodes to provide comprehensive coverage for their deployments. Deploying conventional full-stack cells is one option, but it may not always be feasible (e.g., without available backhaul links) or economically viable. Therefore, 5G considers new types of network nodes to increase the network deployment flexibility of mobile operators. For example, Integrated Access and Backhaul (IAB) was introduced in Rel-16 and enhanced in Rel-17 as a new type of network node that does not require wired backhaul links. Another type of network node is the radio frequency (RF) repeater, which simply amplifies and forwards any signals it receives. RF repeaters have been widely deployed in 2G, 3G, and 4G to supplement the coverage provided by conventional full-stack cells. In Rel-17, RAN4 specifies the RF and EMC requirements for such RF repeaters for NR, and for FR1 and FR2. While RF repeaters provide a cost-effective means of extending network coverage, they also have their limitations. RF repeaters only perform amplification and forwarding operations and cannot account for various factors that may improve performance. These factors may include semi-static and / or dynamic downlink / uplink configuration information, adaptive transmitter / receiver spatial beamforming, switching states, etc. Summary of the Invention

[0011] To address the shortcomings of existing technologies, the purpose of this invention is to provide a repeater device, user equipment, and base station device that support uplink unlicensed scheduling.

[0012] The repeater device supporting uplink unlicensed scheduling provided by the present invention is used to communicate with user equipment and base station devices, comprising: Receiver circuit configuration: Receive a first radio resource control (RRC) message, which includes a first subcarrier spacing used by the control link; Receive a second RRC message, which includes a second subcarrier spacing for indicating the backhaul link; Receive a third RRC message, which includes a third subcarrier spacing used to indicate the access link; Receive a fourth RRC message, which includes information on the resources configured for uplink unlicensed scheduling of the access link; A first physical downlink control channel is received, which transmits first downlink control information for an unlicensed scheduling physical uplink shared channel for access links. The cyclic redundancy check code of the first downlink control information is scrambled by a first radio network temporary identifier. The first downlink control information includes resources configured for access link uplink unlicensed scheduling and activation information. Receive a second physical downlink control channel, which transmits second downlink control information containing dynamic scheduling of physical uplink shared channels for backhaul links, wherein the cyclic redundancy check code of the second downlink control information is scrambled by a second radio network temporary identifier, and the second downlink control information includes resources configured for indicating dynamic scheduling of backhaul links; Based on the fourth RRC message and the first downlink control information, the unlicensed scheduling physical uplink shared channel of the access link is received; Transmitter circuit configuration: Based on the second downlink control information, the unlicensed scheduling physical uplink shared channel of the access link is forwarded through the backhaul link via the dynamic scheduling uplink shared channel.

[0013] Preferably, in the uplink physical channel, a physical random access channel is defined for the initial access connection establishment process, handover process, connection re-establishment, periodic adjustment and / or request for uplink shared channel resources.

[0014] Preferably, in the downlink, a physical downlink control channel is defined for transmitting downlink control information, specifically by defining fields in the downlink control information and mapping these fields to information bits.

[0015] Preferably, a Physical Broadcast Channel (PBCH) is defined for broadcasting the Master Information Block (MIB). System information is divided into MIB and System Information Block (SIB). The MIB carries minimal system information, and the SIB carries system information messages.

[0016] Preferably, in the downlink, a synchronization signal SS is defined for obtaining time and / or frequency synchronization with the cell, and for detecting the physical layer cell ID of the cell.

[0017] Preferably, one or more wireless network temporary identifiers are used to transmit downlink control information.

[0018] Preferably, in uplink wireless communication, the uplink reference signal RS is used as the uplink physical signal, and in downlink wireless communication, DL RS is used as the downlink physical signal; or the uplink physical signal and / or the downlink physical signal are used by the physical layer.

[0019] Preferably, the repeater equipment is installed on a mobile facility, and the user equipment it serves is also mobile. In this scenario, the link between the base station device and the repeater equipment, as well as the user equipment served by the repeater equipment, are both dynamic. In uplink transmission, the link between the repeater equipment and the user equipment is dynamically scheduled, that is, uplink transmission is dynamically scheduled through downlink grants in the DCI. At the same time, the link between the base station device and the repeater equipment is also dynamically scheduled, that is, uplink transmission is dynamically scheduled through uplink grants in the DCI. When a repeater device is installed on a fixed building or facility, and the user equipment it serves is also relatively stationary, the link between the base station device and the repeater device, as well as the user equipment served by the repeater device, are both relatively static. Therefore, in uplink transmission, the link between the repeater device and the user equipment adopts an unlicensed uplink transmission type, such as uplink transmission or GF transmission, or through configured licensing. That is, the uplink transmission is semi-statically configured with time domain, frequency domain, and / or spatial domain resources. The link between the base station device and the repeater device also adopts an unlicensed uplink transmission type, meaning that the uplink transmission may be semi-statically configured with time domain, frequency domain, and / or spatial domain resources.

[0020] The user equipment supporting uplink unlicensed scheduling provided by the present invention includes: Receiver circuit configuration: Receive a first RRC message, which includes an indication of the first subcarrier spacing used by the access link; Receive a second RRC message, which includes resources configured for indicating uplink unlicensed scheduling on the access link; Receive a first physical downlink control channel, which transmits first downlink control information for an unlicensed scheduling physical uplink shared channel for accessing the link, the first downlink control information including resources configured for unlicensed scheduling of the access link and activation information; Transmitter circuit configuration: Based on the second RRC message and the first downlink control information, the unlicensed physical uplink shared channel of the access link is sent.

[0021] The base station apparatus supporting uplink unlicensed scheduling provided by the present invention includes: Transmitter circuit configuration: Send a first radio frequency resource control message, which includes a first subcarrier spacing for indicating the control link; Send a second RRC message, which includes a second subcarrier spacing used to indicate the backhaul link; Send a third RRC message, which includes a third subcarrier spacing used to indicate the access link; Send a fourth RRC message, which includes information about the resources configured for uplink unlicensed scheduling on the access link; A first physical downlink control channel is transmitted, which transmits first downlink control information for an unlicensed scheduling physical uplink shared channel for access links. The cyclic redundancy check code of the first downlink control information is scrambled by a first radio network temporary identifier. The first downlink control information includes resources configured for access link uplink unlicensed scheduling and activation information. A second physical downlink control channel is transmitted, which transmits second downlink control information containing dynamic scheduling of the physical uplink shared channel for backhaul links. The cyclic redundancy check code of the second downlink control information is scrambled by a second radio network temporary identifier. The second downlink control information includes resources configured for indicating dynamic scheduling of backhaul links. Receiver circuit configuration: Based on the second downlink control information, the uplink shared channel is dynamically scheduled for the backhaul link.

[0022] Compared with the prior art, the present invention has the following beneficial effects: The network control repeater used in this invention is an enhanced version of the traditional RF repeater, which has the ability to receive and process side control information from the network. The side control information enables the network control repeater to perform amplification and forwarding operations in a more efficient manner. Potential benefits may include reducing unnecessary noise amplification, better spatial directness in transmission and reception, and simplified network integration. Attached Figure Description

[0023] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 It is a block diagram; Figure 2 This is a downlink resource grid diagram; Figure 3 For uplink resource grid diagram; Figure 4 The middle image is a sample diagram of a numberology. Figure 5 (a) to (d) in the diagram are subframe structure diagrams of numberology501; Figure 6 (a) to (e) in the figure are example diagrams of time slot 683 and sub-time slot 607; Figure 7 (a) to (d) in the figure are example diagrams of scheduling timeline 709; Figure 8 (a) and (b) in the figure are example diagrams of the downlink control channel monitoring area; Figure 9 (a) and (b) in the figure are example diagrams of downlink control channels with multiple control channel elements; Figure 10 Figures (a) to (c) in the diagram are example diagrams of the uplink control channel structure; Figure 11 Block diagram of gNB 1160; Figure 12 Block diagram for UE 1202; Figure 13 Diagrams of various components that can be used in UE 1302; Figure 14 A diagram showing the various components that may be used in the gNB 1460; Figure 15 Here is the implementation block diagram for UE 1502; Figure 16 Here is the implementation block diagram for gNB 1660; Figure 17 A schematic diagram of a network control repeater applied to a moving train carriage; Figure 18 A schematic diagram showing the installation of a network control repeater on a fixed building or facility; Figure 19 Modeling diagram for network control repeater. Detailed Implementation

[0024] The present invention will now be described in detail with reference to specific embodiments. These embodiments will help those skilled in the art to further understand the present invention, but do not limit the invention in any way. It should be noted that those skilled in the art can make several changes and improvements without departing from the concept of the present invention. These all fall within the protection scope of the present invention.

[0025] Example This invention introduces a network control repeater support example for UE functions and parameter lists to provide services for the above use cases.

[0026] Network control repeater modeling, such as Figure 19 As shown, this includes NCR-MT and NCR-Fwd. NCR-MT is defined as a functional entity that communicates with the gNB via the control link (C-link) to enable information exchange (e.g., at least side control information for controlling NCR-Fwd). The C-link is based on the NR Uu interface. NCR-Fwd is defined as a functional entity that performs uplink / downlink RF signal amplification and forwarding between the gNB and the UE via the backhaul link and access link. The behavior of NCR-Fwd will be controlled based on the side control information received from the gNB. Furthermore, at least one carrier of NCR-MT should be located within the carrier set forwarded by NCR-Fwd in the same frequency band. As a baseline, the control link and backhaul link (at least when NCR-MT and NCR-Fwd operate on the same carrier) should experience the same large-scale channel characteristics. The control link may deliver a PDCCH with (NCR-specific) RNTI and / or PDSCH. The backhaul link may be defined as one resource (or multiple resources).

[0027] In a Network Control Repeater (NCR), fixed and adaptive beams can be considered for C-link and backhaul-link (including mechanisms for beam indication and determination). Fixed beams refer to situations where the beams for C-link and backhaul-link in the NCR cannot be changed. Support for fixed or adaptive beams may be a capability of the User Equipment (UE). Capability signaling may include a parameter indicating whether the UE supports fixed and / or adaptive beams for the NCR's backhaul link and C-link. Whether fixed and / or adaptive beams for backhaul link and C-link are applied / used / implemented can be indicated / by shared / dedicated / UE-specific RRC messages / signaling and / or SI configuration, or by Layer 2 (L2) signaling (e.g., MAC CE) and / or Layer 1 (L1) signaling (e.g., DCI, PDCCH), and / or provided / fixed in the standard specification. The configuration of fixed and / or adaptive beams for backhaul links and C-links can be configured / indicated via shared / dedicated / UE-specific RRC messages / signaling and / or SI, or indicated via L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / fixed in the standard specifications. The indication of fixed and / or adaptive beams for backhaul links and C-links can be configured / indicated via shared / dedicated / UE-specific RRC messages / signaling and / or SI, or indicated via L2 signaling (e.g., MAC CE) and / or L1 signaling (e.g., DCI, PDCCH), and / or provided / fixed in the standard specifications. For example, the beam set for C-links and / or backhaul links can be configured via RRC messages / signaling, and the beams used by C-links and / or backhaul links can be indicated via MAC messages / signaling (e.g., MAC CE). In another example, the beam set of C-link and / or backhaul-link can be configured via RRC messages / signaling, a portion of the beams of C-link and / or backhaul-link (from the set) can be indicated / activated via MAC messages / signaling (e.g., MAC CE), and then the beams used by C-link and / or backhaul-link (from the subset) can be indicated via L1 messages / signaling (e.g., PDCCH, DCI).

[0028] Certain configurations of the systems and methods described in this invention teach mobile communication network transmission and / or retransmission management methods incorporating network control repeaters to satisfy the constraints and requirements described above.

[0029] Figure 1 This is a block diagram illustrating one implementation of one or more base stations (gNBs) 160 and one or more user equipments (UEs) 102 supporting a network control repeater (NCR). The NCR may be transparent to the UEs, or the UEs may be unaware of the NCR's existence and believe they are communicating directly with the base stations. One or more UEs 102 communicate with one or more gNBs 160 using one or more antennas 122a-n (via the NCR). For example, UE 102 uses one or more antennas 122a-n to send electromagnetic signals to gNB 160 (retransmitted via the NCR) and receive electromagnetic signals from gNB 160 (retransmitted via the NCR). gNB 160 communicates with UE 102 using one or more antennas 180a-n (retransmitted via the NCR).

[0030] UE 102 and gNB 160 can communicate using one or more channels 119 and 121 (forwarded via the network control repeater). For example, UE 102 can use one or more uplink channels 121 to transmit information or data to gNB 160 (forwarded via the network control repeater). Examples of uplink channels 121 include PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), etc. For example, uplink channel 121 (e.g., PUSCH) can be used to transmit uplink data (i.e., transport blocks, MAC PDUs, and / or uplink shared channel (UL-SCH)).

[0031] In some examples, UL data may include URLLC data. URLLC data may be UL-SCH data. In some examples, a URLLC-PUSCH (i.e., a different physical uplink shared channel than a PUSCH) may be defined for transmitting URLLC data. For simplicity, the term “PUSCH” may refer to any of the following: (1) PUSCH only (e.g., regular PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH, (3) PUSCH and URLLC-PUSCH, or (4) URLLC-PUSCH only (e.g., not regular PUSCH).

[0032] Furthermore, for example, uplink channel 121 can be used to transmit Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK), Channel State Information (CSI), and / or Scheduling Request (SR). HARQ-ACK may include information for acknowledging or denying downlink data (i.e., transport blocks, Media Access Control Protocol Data Units (MAC PDUs), and / or Downlink Shared Channel (DL-SCH)).

[0033] CSI can include information indicating downlink channel quality. SR can be used to request uplink shared channel (UL-SCH) resources for new transmissions and / or retransmissions. For example, SR can be used to request UL resources for transmitting UL data.

[0034] One or more gNBs 160 may also use one or more downlink channels 119 to transmit information or data to one or more UEs 102 (forwarded via network control repeaters). Examples of downlink channels 119 include PDCCH, PDSCH, etc. Other types of channels may be used. PDCCH can be used to transmit downlink control information (DCI).

[0035] Each UE 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a UE operation module 124. For example, one or more receive and / or transmit paths may be implemented in the UE 102. For simplicity, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are described in the UE 102, but multiple parallel elements (e.g., transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154) may be implemented.

[0036] The transmit receiver 118 in the UE may include one or more receivers 120 and one or more transmitters 158. One or more receivers 120 may use one or more antennas 122a-n to receive signals from the gNB 160. For example, receiver 120 may receive and down-convert signals to generate one or more received signals 116. These one or more received signals 116 may be provided to demodulator 114. One or more transmitters 158 may use one or more antennas 122a-n to transmit signals to the gNB 160. For example, these one or more transmitters 158 may up-convert and transmit one or more modulated signals 156.

[0037] Demodulator 114 can demodulate one or more received signals 116 to generate one or more demodulated signals 112. These one or more demodulated signals 112 can be provided to decoder 108. UE 102 can use decoder 108 to decode the signals. Decoder 108 can generate decoded signals 110, which include UE decoded signal 106 (also referred to as first UE decoded signal 106). For example, first UE decoded signal 106 may include received payload data, which may be stored in data buffer 104. Another signal included in decoded signal 110 (also referred to as second UE decoded signal 110) may include overhead data and / or control data. For example, second UE decoded signal 110 can provide data that can be used by UE operation module 124 to perform one or more operations.

[0038] Typically, the UE operation module 124 enables the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include the UE scheduling module 126.

[0039] UE102 can utilize UE scheduling module 126 to perform one or more downlink receptions and / or one or more uplink transmissions. Downlink reception may include data reception, downlink control information reception, and / or downlink reference signal reception. Uplink transmission includes data transmission, uplink control information transmission, and / or uplink reference signal transmission.

[0040] In the diagram, gNB can be a ground-based base station or a satellite-based space-based station. The channels in the diagram can be links between user equipment and base stations, and may also include access links, backhaul links, and / or control links.

[0041] Network control repeaters can be located on the ground, such as buildings, infrastructure, vehicles, railway facilities, highway facilities, trains / high-speed trains, etc., or in the air, such as aircraft and / or satellites.

[0042] In wireless communication systems, physical channels (e.g., uplink physical channels and / or downlink physical channels) can be defined. Physical channels (e.g., uplink physical channels and / or downlink physical channels) can be used for communication that delivers information from a higher layer (e.g., sending and / or receiving).

[0043] For example, in the uplink, a Physical Random Access Channel (PRACH) can be defined. In some methods, the PRACH (and / or random access procedure) can be used for initial access connection establishment, handover procedures, connection re-establishment, timing adjustments (e.g., uplink transmission synchronization, for uplink synchronization) and / or requesting uplink shared channel (UL-SCH) resources (e.g., uplink physical shared channel (PSCH) (e.g., PUSCH) resources).

[0044] In some examples, a Physical Uplink Control Channel (PUCCH) can be defined. The PUCCH can be used to transmit Uplink Control Information (UCI). UCI may include a hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK), Channel State Information (CSI), and / or Scheduling Request (SR). HARQ-ACK can be used to indicate a correct authentication (ACK) or negative acknowledgment (NACK) for downlink data (e.g., transport blocks, Media Access Control Protocol Data Units (MAC PDUs), and / or Downlink Shared Channel (DL-SCH)). CSI can be used to indicate the status of downlink channels (e.g., downlink signals). SR can be used to request uplink data resources (e.g., transport blocks, MAC PDUs, and / or Uplink Shared Channel (UL-SCH)).

[0045] DL-SCH and / or UL-SCH can be transport channels used in the MAC layer. In the MAC layer, one or more transport blocks (TBs) and / or MAC PDUs can be defined as units of transport channels. A transport block can be defined as a data unit passed from the MAC layer to the physical layer. The MAC layer can pass transport blocks to the physical layer (e.g., the MAC layer passes data as a transport block to the physical layer). In the physical layer, a transport block can be mapped to one or more codewords.

[0046] In the downlink, a Physical Downlink Control Channel (PDCCH) can be defined for transmitting Downlink Control Information (DCI). In some cases, multiple DCI formats can be defined for transmitting DCI on the PDCCH. For example, fields can be defined in a DCI format and mapped to information bits (e.g., DCI bits).

[0047] In some cases, DCI format 1_0 used for scheduling PDSCH in a cell can be defined as the downlink DCI format. As described in this invention, DCI format 1_0 can be transmitted using one or more radio network temporary identifiers (e.g., cell RNTI(s) (C-RNTI(s)), configured scheduling RNTI(s) (CS-RNTI(s)), system information RNTI(s) (SI-RNTI(s)), and / or random access RNTI(s) (RA-RNTI(s))). In some cases, DCI format 1_0 can be monitored (e.g., transmitted, mapped) in the common search space (CSS) and / or user equipment specific search space (USS). In some cases, DCI format 1_0 can only be monitored (e.g., transmitted, mapped) in the CSS.

[0048] For example, the DCI included in DCI format 1_0 can be a frequency domain resource allocation (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_0 can be a time domain resource allocation (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_0 can be a modulation and coding scheme (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_0 can be a new data indicator. Alternatively, the DCI included in DCI format 1_0 can be a HARQ process number. Alternatively, the DCI included in DCI format 1_0 can be a Transmission Power Control (TPC) command for scheduling scheduled PUCCHs. DCI format 1_0 and / or modified / enhanced DCI format 1_0 can be used to schedule de-capacitated user equipment (UE) and its served PDSCH and / or downlink.

[0049] Alternatively, the DCI format 1_1 used for scheduling the downlink data sharing channel (PDSCH) in a cell can also be defined as a downlink DCI format. Furthermore, or alternatively, DCI format 1_1 can be transmitted using C-RNTI and / or CS-RNTI. Additionally, or alternatively, DCI format 1_1 can be monitored (e.g., transmitted and / or mapped) in the CSS and / or USS.

[0050] For example, a DCI included in DCI format 1_1 might be a bandwidth portion (BWP) indicator (e.g., for PDSCH). Alternatively, a DCI included in DCI format 1_1 might be a frequency domain resource allocation (e.g., for PDSCH). Alternatively, a DCI included in DCI format 1_1 might be a time domain resource allocation (e.g., for PDSCH). Alternatively, a DCI included in DCI format 1_1 might be a modulation and coding scheme (e.g., for PDSCH). Alternatively, a DCI included in DCI format 1_1 might be a new data indicator. Alternatively, a DCI included in DCI format 1_1 might be a HARQ process number. Alternatively, a DCI included in DCI format 1_1 might be a TPC command for scheduling PUCCH. Alternatively, a DCI included in DCI format 1_1 might be a CSI request for requesting (e.g., triggering) a CSI transmission (e.g., a CSI report (e.g., an aperiodic CSI report)). Alternatively, as described below, the DCI included in DCI format 1_1 may be information used to indicate the DL semi-static scheduling (SPS) configuration index (e.g., the SPS configuration index). DCI format 1_1 and / or modified / enhanced DCI format 1_1 can be used to plan PDSCH and / or downlink channels for UE(s) and their services(s) with reduced capabilities.

[0051] Alternatively, a new DCI format (e.g., DCI format 1_2) can be defined for scheduling the downlink data sharing channel (PDSCH) in the cell as the downlink DCI format. Alternatively, C-RNTI and / or CS-RNTI can be used to transmit DCI format 1_2. Alternatively, DCI format 1_2 can be monitored (e.g., transmitted and / or mapped) in the CSS and / or USS.

[0052] For example, the DCI included in DCI format 1_2 can be a bandwidth portion (BWP) indicator (e.g., for PDSCH). Additionally, the DCI included in DCI format 1_2 can be defined as a downlink DCI format. Alternatively, C-RNTI and / or CS-RNTI can be used to transmit DCI format 1_2. DCI format 1_2 in CSS and / or USS can also be monitored (e.g., transmitted and / or mapped). Furthermore, the DCI included in DCI format 1_2 can be a frequency domain resource allocation (e.g., for PDSCH) or a time domain resource allocation (e.g., for PDSCH). Furthermore, the DCI included in DCI format 1_2 can be a modulation and coding scheme (e.g., for PDSCH) or a new data indicator. Additionally, the DCI included in DCI format 1_2 can be a HARQ process number or a TPC command for a scheduled PUCCH. Alternatively, the DCI included in DCI format 1_2 can be a CSI request used to request (e.g., trigger) a CSI transmission (e.g., a CSI report (e.g., an aperiodic CSI report)). Furthermore, the DCI included in DCI format 1_2 can also be a configurable field, such as antenna port (0... 2 bits), transmission configuration indication (0) 3 bits), rate matching indicator (0) 2 bits), Detect Reference Signal (SRS) Request (0 3 bits), PRB binding size indicator (0 1 bit), carrier indication (0 bits) 3 bits), CSI request (0 3 bits), ZP CSI-RS trigger (0 2 bits), Beta offset indicator (0 2 bits), SRS resource indicator (0 4 digits), repeat factor (0) 2 bits) and / or priority indication (0 bits) (3 bits). Furthermore, as described below, the DCI included in DCI format 1_2 can be information used to indicate the DL semi-persistent scheduling (SPS) configuration index (e.g., the SPS configuration index). DCI format 1_2 and / or modified / enhanced DCI format 1_2 can be used to schedule PDSCH and / or downlink for degraded UEs and their services.

[0053] In addition, a new DCI format (e.g., DCI format 1_3) may be defined to schedule the PDSCH in the cell as the downlink DCI format. Alternatively, C-RNTI and / or CS-RNTI may be used to transmit the new DCI format (e.g., DCI format 1_3). Alternatively, DCI format 1_3 may be monitored (e.g., transmitted and / or mapped) in the CSS and / or USS.

[0054] Alternatively or additionally, the DCI format 0_0 used for scheduling PUSCH in a cell can be defined as the uplink DCI format. Additionally or additionally, C-RNTI, CS-RNTI, and / or temporary C-RNTI can be used to transmit DCI format 0_0. Additionally or additionally, DCI format 0_0 can be monitored (e.g., transport, mapping) in the CSS and / or USS. In some examples, DCI format 0_0 can only be monitored (e.g., transport, mapping) in the CSS.

[0055] For example, the DCI included in DCI format 0_0 can be a frequency domain resource allocation (e.g., PUSCH). Alternatively, the DCI included in DCI format 0_0 can be a time domain resource allocation (e.g., PUSCH). Alternatively, the DCI included in DCI format 0_0 can be a modulation and coding scheme (e.g., PUSCH). Alternatively, the DCI included in DCI format 0_0 can be a new data indicator. Alternatively, the DCI included in DCI format 0_0 can be a HARQ process number. Alternatively, the DCI included in DCI format 0_0 can be a redundant version. Alternatively, the DCI included in DCI format 0_0 can be a TPC command for planned PUSCH. DCI format 0_0 and / or modified / enhanced DCI format 0_0 can be used to schedule PUSCH and / or uplink for UEs with reduced functionality and their services.

[0056] Alternatively, a DCI format 0_1 ​​can be defined for scheduling PUSCH in the cell as the uplink DCI format. DCI format 0_1 ​​can be transmitted using C-RNTI and / or CS-RNTI. DCI format 0_1 ​​can be monitored (e.g., transmitted, mapped) in the CSS and / or USS.

[0057] For example, the DCI included in DCI format 0_1 ​​may be a BWP indicator (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_1 ​​may be a frequency domain resource allocation (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_1 ​​may be a time domain resource allocation (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_1 ​​may be a modulation and coding scheme (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_1 ​​may be a new data indicator. Alternatively, the DCI included in DCI format 0_1 ​​may be a HARQ process number. Alternatively, the DCI included in DCI format 0_1 ​​may be a TPC command for scheduling PUSCH. Alternatively, the DCI included in DCI format 0_1 ​​may be a CSI request for requesting a CSI report. Additionally or alternatively, as described below, the DCI included in DCI format 0_1 ​​may be information such as a configuration index (e.g., a CG configuration index) used to indicate configuration authorization. DCI format 0_1 ​​and / or modified / enhanced DCI format 0_1 ​​can be used to schedule PUSCH and / or uplink channels to serve low-capability UEs and their services.

[0058] Additionally, DCI format 0_2 used for scheduling intra-cell PUSCH can be defined as the uplink DCI format. Additionally, C-RNTI and / or CS-RNTI can be used to transmit DCI format 0_2. Additionally, DCI format 0_2 can be monitored (e.g., transmission, mapping) in the CSS and / or USS.

[0059] For example, the DCI included in DCI format 0_2 can be a BWP indicator (e.g., for PUSCH). Additionally, the DCI included in DCI format 0_2 can be a frequency domain resource allocation (e.g., for PUSCH). Additionally, the DCI included in DCI format 0_2 can be a time domain resource allocation (e.g., for PUSCH). Additionally, the DCI included in DCI format 0_2 can be a modulation and coding scheme (e.g., for PUSCH). Additionally, the DCI included in DCI format 0_2 can be a new data indicator. Additionally, the DCI included in DCI format 0_2 can be a HARQ process number. Additionally, the DCI included in DCI format 0_2 can be a TPC command for a scheduled PUSCH. Additionally, the DCI included in DCI format 0_2 can be a CSI request for requesting a CSI report. Additionally, the DCI included in DCI format 0_2 can be a configurable field, such as antenna port [0]. 2 bits], Transmission configuration indication [0 3 bits], Rate Matching Indicator [0 2 bits], SRS request [0 3 bits], PRB bundle size indicator [0 1 bit], carrier indicator [0 3 bits], CSI request [0 3 bits], ZP CSI-RS trigger [0 2 bits], Beta offset indicator [0 2 bits], SRS resource indicator [0 4 digits], repeat factor [0] 2 bits] and / or priority indication [0 [3 bits]. Additionally, as described below, the DCI included in DCI format 0_2 may be information used to indicate a configured and granted configuration index (e.g., CG configuration index). DCI format 0_2 and / or modified / enhanced DCI format 0_2 can be used to schedule PUSCH and / or uplink channels for UEs with reduced capabilities and their services.

[0060] Alternatively, a new DCI format (e.g., DCI format 0_3) for scheduling PUSCH in the cell may be defined as the uplink DCI format. Alternatively, C-RNTI and / or CS-RNTI may be used to transmit DCI format 0_3. Alternatively, DCI format 0_3 may be monitored (e.g., transmitted, mapped) in the CSS and / or USS.

[0061] Alternatively, upon receiving DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 and / or DCI format 1_3 (e.g., based on the detection of DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 and / or DCI format 1_3), UE 102 may perform PDSCH reception. Alternatively, upon receiving DCI format 0_0 and / or DCI format 0_1 ​​and / or DCI format 0_2 and / or DCI format 0_3 (e.g., based on the detection of DCI format 0_0 and / or DCI format 0_1 ​​and / or DCI format 0_2 and / or DCI format 0_3), UE 102 may perform PUSCH transmission.

[0062] In some examples, as described above, the RNTI (e.g., Radio Network Temporary Identifier) ​​assigned to UE 102 can be used for DCI transmission (e.g., DCI format, DL control channel (e.g., PDCCH)). For example, gNB 160 can transmit information for configuring (e.g., assigning) the RNTI(S) to UE 102 using RRC messages (e.g.).

[0063] For example, a Cyclic Redundancy Check (CRC) bit (which may be simply referred to as CRC) can be generated based on the DCI and appended to it. Then, the RNTI(s) can scramble the CRC bit after appending. UE 102 can attempt to decode (e.g., blind decoding, monitoring, detecting) the appended DCI after the RNTI(s) scramble. For example, UE 102 can detect downlink control channels (e.g., PDCCH, DCI, DCI format) based on blind decoding. For example, UE 102 can use the CRC scrambled by the RNTI to decode the downlink control channel; in other words, UE 102 can use the RNTI to monitor the downlink control channel. For example, UE 102 can use the RNTI to detect the DCI format.

[0064] In some examples, RNTI(s) may include C-RNTI (Unit RNTI), CS-RNTI (Configuration Scheduling C-RNTI), SI-RNTI (System Information RNTI), RA-RNTI (Random Access RNTI), and / or ad hoc C-RNTI. For example, C-RNTI(s) may be unique identifiers used to identify RRC connections and / or scheduling. Furthermore, CS-RNTI(s) may be unique identifiers used for scheduling based on configuration grants. Additionally, SI-RNTIs may be used to identify system information mapped to the BCCH and dynamically transmitted on the DL-SCH (e.g., SI messages). Furthermore, SI-RNTIs may be used to broadcast SIs. Furthermore, RA-RNTIs may be identifiers used for random access procedures (e.g., Msg.2 transmission). Additionally, ad hoc C-RNTIs may be used for random access procedures (e.g., scheduling Msg.3 (re)transmissions (e.g., Msg.3 PUSCH (re)transmissions)).

[0065] Alternatively, a new RNTI (e.g., NCR-RNTI) can be introduced for NCR and its services. For example, upon receiving DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 and / or DCI format 1_3 scrambling using NCR-RNTI (e.g., detection based on DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 and / or DCI format 1_3), UE 102 can perform PDSCH reception for NCR transport services. Alternatively, if DCI format 0_0 and / or DCI format 0_1 ​​and / or DCI format 0_2 and / or DCI format 0_3 with NCR-RNTI scrambling is received (e.g., detection based on DCI format 0_0 and / or DCI format 0_1 ​​and / or DCI format 0_2 and / or DCI format 0_3), UE 102 may perform PUSCH transmission for NCR transmission service.

[0066] Alternatively, UL and DL can introduce different RNTIs. For example, a new RNTI (e.g., NCR-UL-RNTI) can be introduced for the UE and its UL transport service, while a new RNTI (e.g., NCR-DL-RNTI) can be introduced for the UE and its DL transport service. If DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 and / or DCI format 1_3 encrypted using NCR-DL-RNTI is received (e.g., detection based on DCI format 1_0 and / or DCI format 1_1 and / or DCI format 1_2 and / or DCI format 1_3), UE 102 can perform PDSCH reception for the NCR transport service. Alternatively, if DCI format 0_0 and / or DCI format 0_1 ​​and / or DCI format 0_2 and / or DCI format 0_3 encrypted using NCR-UP-RNTI is received (e.g., based on detection of DCI format 0_0 and / or DCI format 0_1 ​​and / or DCI format 0_2 and / or DCI format 0_3), UE 102 may perform PUSCH transmission for NCR transmission service.

[0067] Alternatively, a Physical Downlink Shared Channel (PDSCH) and a Physical Uplink Shared Channel (PUSCH) can be defined. For example, if a DCI format is used to schedule a PDSCH (e.g., a PDSCH resource), UE 102 can receive downlink data on the scheduled PDSCH (e.g., the PDSCH resource). Alternatively, if a DCI format is used to schedule a PUSCH (e.g., a PUSCH resource), UE 102 can transmit uplink data on the scheduled PUSCH (e.g., the PUSCH resource). For example, a PDSCH can be used to transmit downlink data (e.g., DL-SCH(S), downlink transport block(S)). Alternatively, a PUSCH can be used to transmit uplink data (e.g., UL-SCH(S), uplink transport block(S)).

[0068] In some examples, PDSCH and / or PUSCH can be used to transmit information from higher layers (such as the Radio Resource Control (RRC) layer and / or MAC layer). For example, PDSCH (e.g., from gNB 160 to UE 102) and / or PUSCH (e.g., from UE 102 to gNB 160) can be used to transmit RRC messages (e.g., RRC signals). Additionally or alternatively, PDSCH (e.g., from gNB 160 to UE 102) and / or PUSCH (e.g., from UE 102 to gNB 160) can be used to transmit MAC control elements (MAC CEs). In some examples, RRC messages and / or MAC CEs may be referred to as higher-layer signals.

[0069] In some methods, a Physical Broadcast Channel (PBCH) can be defined. For example, the PBCH can be used to broadcast the Master Information Block (MIB). In some examples, system information can be divided into MIBs and System Information Blocks (SIBs). For example, the MIB can be used to carry minimal system information. Alternatively, the SIB can be used to carry system information messages.

[0070] In the downlink, a synchronization signal (SS) can be defined. The SS can be used to obtain time and / or frequency synchronization with the cell. Alternatively, the SS can be used to detect the physical layer cell ID of the cell.

[0071] In uplink wireless communication, the uplink reference signal (RS) can be used as the uplink physical signal. Alternatively, in downlink wireless communication, the DL RS can be used as the downlink physical signal. In some examples, the uplink physical signal and / or downlink physical signal may not be used to transmit information from higher layers, but rather are used by the physical layer.

[0072] In some implementations, the aforementioned downlink physical channels and / or downlink physical signals may be assumed to be included in the downlink signals (e.g., DL signals) for simplification. Additionally or alternatively, in some implementations, the uplink physical channels and / or uplink physical signals may be assumed to be included in the uplink signals (i.e., UL signals) for simplification.

[0073] The UE operation module 124 can provide information 148 to one or more receivers 120. For example, the UE operation module 124 can notify the receiver 120 when a retransmission is received.

[0074] The UE operation module 124 can provide information 138 to the demodulator 114. For example, the UE operation module 124 can inform the demodulator 114 of the modulation mode of the transmission from the gNB 160.

[0075] The UE operation module 124 can provide information 136 to the decoder 108. For example, the UE operation module 124 can inform the decoder 108 of the expected encoding of the transmission from the gNB 160.

[0076] The UE operation module 124 may provide information 142 to the encoder 150. Information 142 may include data to be encoded and / or encoding instructions. For example, the UE operation module 124 may instruct the encoder 150 to encode transmitted data 146 and / or other information 142. Other information 142 may include PDSCH HARQ-ACK information.

[0077] Encoder 150 can encode transmission data 146 and / or other information 142 provided by UE operation module 124. For example, the encoded data 146 and / or other information 142 may involve error detection and / or correction coding, mapping data to spatial, temporal and / or frequency resources for transmission, multiplexing, etc. Encoder 150 can provide the encoded data 152 to modulator 154.

[0078] The UE operation module 124 can provide information 144 to the modulator 154. For example, the UE operation module 124 can inform the modulator 154 of the modulation type (e.g., constellation mapping) to be used for transmission to the gNB 160. The modulator 154 can modulate coded data 152 and provide one or more modulated signals 156 to one or more transmitters 158.

[0079] The UE operation module 124 can provide information 140 to one or more transmitters 158. This information 140 may include instructions from one or more transmitters 158. For example, the UE operation module 124 can instruct one or more transmitters 158 when to transmit signals to the gNB 160. For example, one or more transmitters 158 may transmit in an uplink subframe. One or more transmitters 158 may upconvert the modulated signal 156 and transmit it to one or more gNBs 160.

[0080] Each gNB 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operation module 182. For example, one or more receive and / or transmit paths may be implemented in the gNB 160. For convenience, this document only describes a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 in the gNB 160, although multiple parallel elements (e.g., transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113) can be implemented.

[0081] Transceiver 176 may include one or more receivers 178 and one or more transmitters 117. One or more receivers 178 may use one or more antennas 180a-n to receive signals from UE 102. For example, receiver 178 may receive and down-convert signals to generate one or more received signals 174. One or more received signals 174 may be provided to demodulator 172. One or more transmitters 117 may use one or more antennas 180a-n to transmit signals to UE 102. For example, one or more transmitters 117 may up-convert and transmit one or more modulated signals 115.

[0082] Demodulator 172 can demodulate one or more received signals 174 into one or more demodulated signals 170. These one or more demodulated signals 170 can be provided to decoder 166. gNB 160 can use decoder 166 to decode the signals. Decoder 166 can generate one or more decoded signals 164, 168. For example, the first decoded signal 164 may contain received payload data, which can be stored in data buffer 162. The second decoded signal 168 may contain overhead data and / or control data. For example, the second decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information), which can be used by gNB operation module 182 to perform one or more operations.

[0083] Generally, gNB operation module 182 enables gNB 160 to communicate with one or more UEs 102. gNB operation module 182 may include gNB scheduling module 194. gNB scheduling module 194 can perform operations such as enhanced uplink transmission resource allocation, as described herein.

[0084] gNB operation module 182 can provide information 188 to demodulator 172. For example, gNB operation module 182 can inform demodulator 172 of the modulation mode expected to be transmitted from UE(s) 102.

[0085] gNB operation module 182 can provide information 186 to decoder 166. For example, gNB operation module 182 can inform decoder 166 of the encoding method expected to be transmitted from UE(s) 102.

[0086] The gNB operation module 182 can provide information 101 to the encoder 109. Information 101 may include data to be encoded and / or encoding instructions. For example, the gNB operation module 182 may instruct the encoder 109 to encode information 101, which includes transmission data 105.

[0087] Encoder 109 can encode the transmitted data 105 and / or other information in information 101 provided by gNB operation module 182. For example, encoding the data 105 and / or other information contained in information 101 may involve error detection and / or correction coding, mapping data to spatial, temporal, and / or frequency resources for transmission, multiplexing, etc. Encoder 109 can provide encoded data 111 to modulator 113. Transmitted data 105 may include network data to be forwarded to UE 102.

[0088] gNB operation module 182 can provide information 103 to modulator 113. This information 103 may include instructions for modulator 113. For example, gNB operation module 182 can inform modulator 113 of the modulation type (e.g., constellation mapping) for transmission to UE(s) 102. Modulator 113 can modulate coded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0089] gNB operation module 182 can provide information 192 to one or more transmitters 117. This information 192 may include instructions from one or more transmitters 117. For example, gNB operation module 182 can instruct one or more transmitters 117 when (or when not) to send signals to UE(s) 102. One or more transmitters 117 can upconvert the frequency and send a modulated signal 115 to one or more UEs 102.

[0090] gNB operation module 182 can provide information 190 to one or more receivers 178. For example, gNB operation module 182 can notify receiver 178 when to receive a transmission.

[0091] It is worth noting that DL subframes can be transmitted from gNB 160 to one or more UE 102, while UL subframes can be transmitted from one or more UE 102 to gNB 160. Furthermore, both gNB 160 and one or more UE 102 can transmit data in standard special subframes.

[0092] It should be noted that one or more elements or components included in gNB(s) 160 and UE(s) 102 may be implemented in hardware. For example, one or more of these elements or components may be implemented as chips, circuits, or hardware components. It should also be noted that one or more functions or methods described herein may be implemented and / or performed in hardware. For example, one or more methods described herein may be implemented and / or performed in chipsets, application-specific integrated circuits (ASICs), large-scale integrated circuits (LSIs), or integrated circuits.

[0093] The network control trunk may have all or part of the modules and functions of the gNB(s) 160 mentioned above, and the network control trunk may also have all or part of the modules and functions of the UE(s) 102 mentioned above. The network control trunk may also be any combination of all or part of the modules and functions of the gNB(s) 160 and all or part of the modules and functions of the UE(s) 102.

[0094] Figure 2 This is an example illustrating the downlink resource grid. Figure 2 The resource grid shown in the document can be used in the implementation of some of the systems and methods disclosed herein.

[0095] exist Figure 2 In this context, a downlink subframe 269 may include two downlink slots 283. DL R B is the downlink bandwidth configuration for the serving cell, with N... RB Multiples of sc are represented by N, where N is a multiple of sc. RB sc is the size of resource block 289, which represents the number of subcarriers in the frequency domain, while N DL symb is the number of OFDM symbols 287 in downlink slot 283. Resource block 289 may include multiple resource elements (REs) 291.

[0096] For PCell, N DL RB is broadcast as part of system information. For SCells (including Licensed Assisted Access (LAA) SCells), N DL RBs are configured by RRC messages dedicated to UE 102. For PDSCH mapping, available RE 291s may be RE 291s that satisfy index l ≥ ldata, start and / or ldata, end ≥ l in the subframe.

[0097] The downlink can employ an OFDM access scheme with a cyclic prefix (CP), also known as CP-OFDM. In the downlink, PDCCH, Enhanced PDCCH (EPDCCH), PDSCH, etc., can be transmitted. A downlink radio frame can include multiple downlink resource block (RB) pairs, also known as physical resource blocks (PRBs). A downlink RB pair is a unit for allocating downlink radio resources, defined by a predetermined bandwidth (RB bandwidth) and time slot. A downlink RB pair consists of two consecutive downlink RBs in the time domain.

[0098] Downlink RBs comprise 12 subcarriers in the frequency domain and 7 (for standard CP) or 6 (for extended CP) OFDM symbols in the time domain. The area defined by a subcarrier and one OFDM symbol is called a resource element (RE), uniquely identified in a time slot by an index pair (k, l), where k and l are the frequency and time indices, respectively. Although downlink subframes within a single component carrier (CC) are discussed here, each CC defines its own downlink subframe and is substantially synchronized with each other.

[0099] In 5G NR, RB typically represents frequency resources, with one RB representing 12 subcarriers; time slots typically represent time-domain resources, with one time slot consisting of 14 (for ordinary CP) or 12 (for extended CP) OFDM symbols. The absolute time length of a time slot is determined by the OFDM symbol time length, which is determined by the subcarrier spacing.

[0100] The control link (C-link), backhaul link, and access link can use the same downlink resource mesh configuration, or they can each use different downlink resource mesh configurations.

[0101] Figure 3 This is a diagram illustrating an example of an uplink resource grid. Figure 3 The resource grid shown in the document can be used in the implementation of some of the systems and methods disclosed in this paper.

[0102] exist Figure 3 In this context, an uplink subframe 369 can include two uplink slots 383. NULRB is the uplink bandwidth configuration of the serving cell, in N... RB Multiples of sc are represented by N, where N is a multiple of sc. RB sc is the size of resource block 389 in the frequency domain, expressed in terms of the number of subcarriers, N UL symb is the number of SC-FDMA symbols 393 in uplink slot 383. Resource block 389 may include multiple resource elements (REs) 391.

[0103] For PCell, N UL RB is broadcast as part of system information. For SCells (including LAA SCells), N UL RB is configured by RRC messages dedicated to UE 102.

[0104] In the uplink, besides CP-OFDM, a single-carrier frequency division multiple access (SC-FDMA) scheme, also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-S-OFDM), can be used. PUCCH, PUSCH, PRACH, etc., can be transmitted in the uplink. An uplink radio frame can include multiple uplink resource block pairs. An uplink resource block pair is a unit used to allocate uplink radio resources, defined by a predetermined bandwidth (resource block bandwidth) and time slot. An uplink resource block pair consists of two contiguous uplink resource blocks in the time domain.

[0105] An uplink resource block may contain twelve subcarriers in the frequency domain and seven (normal CP) or six (extended CP) OFDM and / or DFT-S-OFDM symbols in the time domain. The region defining one subcarrier and one OFDM and / or DFT-S-OFDM symbol in both the time and frequency domains is called a resource element (RE) and is uniquely identified within a time slot by an index pair (k, l), where k and l are the indices in the frequency and time domains, respectively. Although uplink subframes within a component carrier (CC) are discussed in this paper, uplink subframes are defined for each CC and synchronized between CCs.

[0106] In 5G NR, RB typically represents frequency resources, with one RB representing 12 subcarriers; time slots typically represent time-domain resources, with one uplink time slot consisting of 14 (for a normal CP) or 12 (for an extended CP) OFDM and / or DFT-S-OFDM symbols. The absolute time length of a time slot is determined by the time length of the OFDM and / or DFT-S-OFDM symbols, i.e., by the subcarrier spacing (i.e., numberology).

[0107] The control link (C-link), backhaul link, and access link can use the same uplink resource mesh configuration or different uplink resource mesh configurations.

[0108] Figure 4 Several examples of numerology 401 are shown. Numerology #1 401a can be a basic numerology (e.g., a reference numerology). For example, RE 495a of basic numerology 401a can be defined in the frequency domain with a subcarrier spacing of 15 kHz 405a and in the time domain with an OFDM symbol length #1 403a of 2048Ts + CP length (e.g., 160Ts or 144Ts), where Ts is defined as 1 / (15000). The baseband sampling time unit is 2048 seconds. For the i-th numberology, the subcarrier spacing of 405 may equal 15. 2i, and the effective OFDM symbol length is 2048. 2-i Ts. This could result in a symbol length of 2048. 2-i Ts+CP length (e.g., 160) 2-i Ts or 144 2-i In other words, the subcarrier spacing of the (i+1)th numberology is twice that of the ith numberology, and the symbol length of the (i+1)th numberology is half that of the ith numberology. Figure 4 Four numeric methods are shown, but the system may support other numbers of numeric methods. Furthermore, the system does not necessarily need to support all numeric methods from 0 to I, i = 0, 1, ..., I.

[0109] For example, as described above, the first UL (DL) transmission on the first uplink (downlink) resource may only be performed on numberology #1 (e.g., with a subcarrier spacing of 15 kHz). In some examples, UE 102 may acquire (detect) numberology #1 based on a synchronization signal. Furthermore, UE 102 may receive a dedicated RRC signal that includes information configuring numberology #1 (e.g., a handover command). The dedicated RRC signal may be a UE-specific signal. In some examples, the first UL (DL) transmission may be performed on numberology #1, numberology #2 (with a subcarrier spacing of 30 kHz), and / or numberology #3 (with a subcarrier spacing of 60 kHz).

[0110] Additionally, as mentioned above, the second UL (DL) transmission on the second uplink (downlink) resource may only be performed on numberology #3. In some examples, UE 102 may receive system information (e.g., Master Information Block (MIB) and / or System Information Block (SIB)) that includes information configuring numberology #2 and / or numberology #3.

[0111] UE 102 may also receive dedicated RRC signals that include information configuring numberology #2 and / or numberology #3 (e.g., handover commands). System information (e.g., MIB) can be transmitted via the broadcast channel (BCH) and / or dedicated RRC signals. System information (e.g., SIB) may contain information relevant to assessing whether UE 102 is permitted to access the base station and defines the scheduling of other system information. System information (SIB) may contain radio resource configuration information common to multiple UE 102s. For example, dedicated RRC signals may include multiple numerical configurations (first value, second value, and / or third value) for each UL transmission (e.g., each UL-SCH transmission, each PUSCH transmission). Furthermore, dedicated RRC signals may include multiple numerical configurations (first value, second value, and / or third value) for each DL transmission (each PDCCH transmission).

[0112] The uplink (downlink) resources of the control link (C-link), backhaul link, and access link can use the same numeric configuration or different numeric configurations.

[0113] Figure 5 An example of the subframe structure for numberology 501 is shown. Given that a slot 283 includes NDLsymb (or NULsymb) = 14 symbols, the slot length of the (i+1)th number 501 is half that of the ith number 501, and the final number of slots 283 in the subframe (i.e., 1 ms) will double. It should be noted that a radio frame can include 10 subframes, and the radio frame length can be equal to 10 milliseconds.

[0114] Figure 6 An example of time slot 683 and sub-time slot 607 is shown. If sub-time slot 607 is not configured by a higher layer, UE 102 and eNB and / or gNB 160 may only use time slot 683 as the scheduling unit. More specifically, a given transport block can be allocated to time slot 683. If sub-time slot 607 is configured by a higher layer, UE 102 and eNB and / or gNB 160 can use both sub-time slot 607 and time slot 683 simultaneously. Sub-time slot 607 may include one or more OFDM symbols. The maximum number of OFDM symbols constituting sub-time slot 607 can be NDLsymb-1 (or NULsymb-1).

[0115] The sub-slot length can be configured via higher-layer signaling. Alternatively, the sub-slot length can be indicated by the physical layer control channel (e.g., via DCI format).

[0116] Sub-slot 607 can begin from any symbol in slot 683 unless it conflicts with the control channel. There may be limitations on the micro-slot length based on the starting position. For example, sub-slot 607 with a length of NDLsymb-1 (or NULsymb-1) can begin from the second symbol of slot 683. The starting position of sub-slot 607 can be indicated by the physical layer control channel (e.g., via DCI format). Alternatively, the starting position of sub-slot 607 can be derived from information in the physical layer control channel (e.g., search space index, blind decoding candidate index, frequency and / or time resource index, PRB index, control channel element index, control channel element aggregation level, antenna port index, etc.) that schedules data in sub-slot 607.

[0117] With sub-slot 607 configured, a given transport block can be allocated to any one of slot 683, sub-slot 607, aggregated sub-slot 607, or aggregated sub-slot 607 and slot 683. This unit can also be the unit where HARQ-ACK bits are generated.

[0118] Figure 7 An example of scheduling timeline 709 is shown. For a normal downlink (DL) scheduling timeline 709a, the DL control channel is mapped to the initial portion of slot 783a. DL control channel 711 schedules DL shared channel 713a within the same slot 783a. HARQ-ACKs in DL shared channel 713a (each HARQ-ACK indicating whether a transport block in each DL shared channel 713a was successfully detected) are reported in a later slot 783b via uplink (UL) control channel 715a. In this case, a given slot 783 can contain either a DL transport or a UL transport.

[0119] For a normal UL scheduling timeline 709b, the DL control channel 711b is mapped to the initial portion of time slot 783c. The DL control channel 711b schedules the UL shared channel 717a in a later time slot 783d. In these cases, the timing of the association between DL time slot 783c and UL time slot 783d (time offset) can be fixed or configured by higher-layer signaling. Alternatively, it can be indicated by a physical layer control channel (e.g., DL assigns a DCI format, UL grants a DCI format, or another DCI format, such as a UE common signaling DCI format, which can be monitored in the common search space).

[0120] For the self-contained basic DL scheduling timeline 709c, the DL control channel 711c is mapped to the initial portion of time slot 783e. The DL control channel 711c schedules the DL shared channel 713b in the same time slot 783e. The HARQ-ACK report of the DL shared channel 713b is mapped to the UL control channel 715b at the end of time slot 783e.

[0121] For a self-contained basic UL scheduling timeline 709d, the DL control channel 711d is mapped to the initial portion of time slot 783f. The DL control channel 711d schedules the UL shared channel 717b in the same time slot 783f. In these cases, time slot 783f may contain both DL and UL portions, and there may be a guard interval between DL and UL transmissions.

[0122] Self-contained time slots can be used based on the configuration of self-contained time slots. Alternatively, they can be used based on the configuration of sub-time slots. Self-contained time slots can also be used based on the configuration of shortened physical channels (e.g., PDSCH, PUSCH, PUCCH, etc.).

[0123] Figure 8 An example of a downlink control channel monitoring area is shown. One or more PRB sets can be configured for downlink control channel monitoring. In other words, a control resource set is a group of PRBs in the frequency domain that UE 102 attempts to blindly demodulate downlink control information. The PRBs can be frequency-contiguous or discontinuous. UE 102 can have one or more control resource sets, and a DCI message can reside within one control resource set. In the frequency domain, a PRB is the resource element size of the control channel (potentially including a demodulation reference signal (DMRS)). A downlink shared channel may begin on an OFDM symbol later than the OFDM symbol that detected the downlink control channel. Alternatively, a downlink shared channel may begin on an OFDM symbol earlier (or the same) than the last OFDM symbol that carried the detected downlink control channel. In other words, at least in the frequency domain, it supports the dynamic reuse of a portion of the control resource set for data from the same UE 102 or other UE 102.

[0124] Figure 9 An example of a downlink control channel comprising multiple control channel elements is shown. When the control resource set spans multiple OFDM symbols, control channel candidates can be mapped to multiple OFDM symbols or to a single OFDM symbol. A downlink control channel element can be mapped to an RE defined by a single PRB and a single OFDM symbol. If a downlink control channel transmission uses multiple downlink control channel elements, downlink control channel element aggregation may be performed.

[0125] The number of downlink control channel elements aggregated is called the downlink control channel element aggregation level. The downlink control channel element aggregation level can be an integer power of 1 or 2. gNB 160 can inform UE 102 which control channel candidates are mapped to each OFDM symbol subset. If a downlink control channel is mapped to a single OFDM symbol and does not span multiple OFDM symbols, then the downlink control channel elements are aggregated within the OFDM symbol; for example, multiple downlink control channel elements are aggregated within one OFDM symbol. Otherwise, downlink control channel elements from different OFDM symbols can be aggregated.

[0126] Figure 10 An example of an uplink control channel structure is shown. The uplink control channel can be mapped to a PRB in both the frequency and time domains and an RE defined in a timeslot. This uplink control channel can be called the long format (or simply the first format). The uplink control channel can also be mapped to a finite number of OFDM symbols in the time domain. This can be called the short format (or simply the second format). The short format uplink control channel can be mapped to an RE in a single PRB. Alternatively, the short format uplink control channel can be mapped to REs in multiple PRBs. For example, interleaved mapping can be applied, such that the uplink control channel can be mapped to every N PRBs (e.g., 5 or 10) within the system bandwidth.

[0127] Figure 11 This is an example showing a block diagram of a gNB 1160. The gNB 1160 may include a higher-layer processor 1123, a downlink transmitter 1125, an uplink receiver 1133, and one or more antennas 1131. The downlink transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The uplink receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.

[0128] The higher-layer processor 1123 can manage the behavior of the physical layer (the behavior of the downlink transmitter and the uplink receiver) and provide higher-layer parameters to the physical layer. The higher-layer processor 1123 can obtain transport blocks from the physical layer. The higher-layer processor 1123 can send and / or obtain higher-layer messages, such as RRC messages and MAC messages, to and / or from the higher layers of the UE. The higher-layer processor 1123 can provide PDSCH transmitter transport blocks and provide PDSCH transmitter transport parameters associated with the transport blocks.

[0129] Downlink transmitter 1125 can multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them through transmit antenna 1131. Uplink receiver 1133 can receive the multiplexed uplink physical channels and uplink physical signals through receive antenna 1131 and demultiplex them. PUCCH receiver 1135 can provide UCI to higher-layer processor 1123. PUSCH receiver 1137 can provide received transport blocks to higher-layer processor 1123.

[0130] Figure 12 This is an example showing a block diagram of a UE 1202. UE 1202 may include a higher-layer processor 1223, an uplink transmitter 1251, a downlink receiver 1243, and one or more antennas 1231. The uplink transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255. The downlink receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.

[0131] The higher-layer processor 1223 can manage the behavior of the physical layer (the behavior of the UL transmitter and DL receiver) and provide higher-layer parameters to the physical layer. The higher-layer processor 1223 can obtain transport blocks from the physical layer. The higher-layer processor 1223 can send and / or obtain higher-layer messages, such as the UE's higher-layer RRC and MAC messages. The higher-layer processor 1223 can provide PUSCH transmitter transport blocks and provide the UCI of the PUCCH transmitter 1253.

[0132] DL receiver 1243 can receive multiplexed downlink physical channels and downlink physical signals through receiving antenna 1231 and demultiplex them. PDCCH receiver 1245 can provide DCI to higher-layer processor 1223. PDSCH receiver 1247 can provide the received transport blocks to higher-layer processor 1223.

[0133] The network control trunk may have all or some of the modules / components and functions of the gNB 1160 mentioned above, and the network control trunk may also have all or some of the modules / components and functions of the UE 1202 mentioned above. The network control trunk may also be any combination of all or some of the modules / components and functions of the gNB 1160 and all or some of the modules / components and functions of the UE 1202.

[0134] It should be noted that the physical channel names described in this invention are merely examples. Other names may be used, such as "NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH", "new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH" or similar names.

[0135] Figure 13 This describes the various components that can be used with UE 1302. Figure 1 Similar to UE 102 described in [the document], it can be based on [the following]. Figure 13 The UE 1302 described herein is implemented. UE 1302 includes a processor 1303 that controls the operation of UE 1302. Processor 1303 may also be referred to as a central processing unit (CPU). Memory 1305 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any device capable of storing information) provides instructions 1307a and data 1309a to processor 1303. A portion of memory 1305 may also include non-volatile random access memory (NVRAM). Instructions 1307b and data 1309b may also reside in processor 1303. Instructions 1307b and / or data 1309b loaded in processor 1303 may also include instructions 1307a and / or data 1309a loaded from memory 1305, which are loaded for execution or processing by processor 1303. Instruction 1307b can be executed by processor 1303 to implement the methods described above.

[0136] UE 1302 may include one or more transmitters 1358 and one or more receivers 1320 to allow data transmission and reception. Transmitters 1358 and receivers 1320 may be combined into one or more transceivers 1318. One or more antennas 1322a-n are attached to the housing and electrically coupled to transceivers 1318.

[0137] The various components of UE 1302 are coupled to each other through a bus system 1311, which may include a power bus, a control signal bus, a status signal bus, and a data bus. However, for clarity, the various buses are... Figure 13 The UE 1302 is described as a bus system 1311. The UE 1302 may also include a digital signal processor (DSP) 1313 for signal processing. The UE 1302 may also include a communication interface 1315 to provide user access to the functions of the UE 1302. Figure 13 The UE 1302 shown is a function block diagram rather than a list of specific components.

[0138] Figure 14 This describes the various components that the gNB 1460 might use. (and...) Figure 1 Corresponding to the gNB 160 described in the document, and with Figure 14The described gNB 1460 can be implemented. The gNB 1460 includes a processor 1403 that controls the operation of the gNB 1460. The processor 1403 can also be referred to as a central processing unit (CPU). A memory 1405, which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any device capable of storing information, provides instructions 1407a and data 1409a to the processor 1403. A portion of the memory 1405 may also include non-volatile random access memory (NVRAM). Instructions 1407b and data 1409b may also reside in the processor 1403. Instructions 1407b and / or data 1409b loaded into the processor 1403 may also include instructions 1407a and / or data 1409a loaded from the memory 1405 for execution or processing by the processor 1403. Instructions 1407b can be executed by the processor 1403 to implement the methods described above.

[0139] The gNB 1460 may also include a housing containing one or more transmitters 1417 and one or more receivers 1478 to allow data transmission and reception. Transmitters 1417 and receivers 1478 may be combined into one or more transceivers 1476. One or more antennas 1480a-n are attached to the housing and electrically coupled to the transceivers 1476.

[0140] The various components of the gNB 1460 are coupled to each other via a bus system 1411, which may include a power bus, control signal buses, status signal buses, and a data bus. However, for clarity, the various buses are... Figure 14 The gNB 1460 is described as a bus system 1411. The gNB 1460 may also include a digital signal processor (DSP) 1413 for processing signals. The gNB 1460 may also include a communication interface 1415 for providing user access to the gNB 1460's functionality. Figure 14 The gNB 1460 depicted is a function block diagram rather than a list of specific components.

[0141] The network control trunk may have all or some of the modules / components and functions of the gNB 1460 mentioned above, and the network control trunk may also have all or some of the modules / components and functions of the UE 1302 mentioned above. The network control trunk may also be any combination of all or some of the modules / components and functions of the gNB 1460 and all or some of the modules / components and functions of the UE 1302.

[0142] Figure 15This is a block diagram depicting an implementation of UE 1502, in which a system and method for enhanced uplink transmission resource allocation can be implemented. UE 1502 includes a transmitting means 1558, a receiving means 1520, and a control means 1524. The transmitting means 1558, the receiving means 1520, and the control means 1524 can be configured to perform operations related to... Figure 1 One or more functions described in the figure. Figure 13 above depicts... Figure 15 This is an example of a specific device structure. Various other structures can be implemented to achieve... Figure 1 One or more functions within a DSP. For example, a DSP can be implemented in software.

[0143] Figure 16 This is a block diagram depicting an implementation of a gNB 1660, in which a system and method for enhanced uplink transmission resource allocation can be implemented. The gNB 1660 includes a transmitting means 1623, a receiving means 1678, and a control means 1682. The transmitting means 1623, the receiving means 1678, and the control means 1682 can be configured to perform... Figure 1 One or more functions described in the figure. Figure 14 above depicts... Figure 16 This is an example of a specific device structure. Various other structures can be implemented to achieve... Figure 1 One or more functions within a DSP. For example, a DSP can be implemented in software.

[0144] The network control trunk may have all or some of the modules / components and functions of the gNB 1660 mentioned above, and the network control trunk may also have all or some of the modules / components and functions of the UE 1502 mentioned above. The network control trunk may also be any combination of all or some of the modules / components and functions of the gNB 1660 and all or some of the modules / components and functions of the UE 1502.

[0145] In a mobile communication network, there may be multiple uplink transmissions. For example, uplink transmissions can be dynamically scheduled via uplink grants in the DCI (e.g., an uplink DCI format scrambled by C-RNTI). Furthermore, uplink transmissions may correspond to configured grant type 1 and / or configured grant type 2. For configured grant type 1, the transmission may be semi-statically configured to operate upon receiving configured parameters (including the ConfiguredGrantConfig parameter of rrc-ConfiguredUplinkGrant) without detecting an uplink grant in the DCI (e.g., the uplink DCI format). For configured grant type 2, the transmission can be scheduled via uplink grants in a valid active DCI (e.g., an active DCI format scrambled by CS-RNTI) upon receiving a ConfiguredGrantConfig parameter that does not include rrc-ConfiguredUplinkGrant.

[0146] For example, uplink transmissions corresponding to configuration grants may be scheduled using a DCI format scrambled by CS-RNTI (e.g., activation). Furthermore, two types of uplink transmissions correspond to configuration grants. For example, one type of uplink transmission can be referred to as a transmission of configuration grant type 1 (e.g., a transmission of configuration grant type 1 for uplink transmissions of configuration grant type 1). Similarly, one type of uplink transmission can be referred to as a transmission of configuration grant type 2 (e.g., a transmission of configuration grant type 2 for uplink transmissions of configuration grant type 2).

[0147] In some instances, for a configuration grant type 1 transport, RRC (e.g., the RRC layer) can provide an uplink grant. For example, if UE 102 receives an RRC message that includes an uplink grant (e.g., a configuration for a configuration grant type 1 transport), UE 102 can store the uplink grant as a configuration grant.

[0148] Furthermore, for configuration grant type 2, the PDCCH (e.g., for indicating an activated DCI format, configuration grant activation, and / or configuration grant activation (e.g., configuration grant corresponding to a configuration grant configuration)) can provide uplink grants. For example, when UE 102 receives an uplink grant (e.g., activated DCI format), UE 102 can store the uplink grant as a configuration grant. Additionally, when UE 102 receives an uplink grant (e.g., for indicating a deactivated DCI format, configuration grant deactivated, and / or configuration grant deactivated (e.g., a configured grant (index) corresponding to a deactivated configuration grant configuration)), UE 102 will clear the configured uplink grant (e.g., the configuration grant (index) corresponding to the deactivated configuration grant configuration). For example, the uplink grant provided by the PDCCH can be stored based on the DCI format indicating configuration grant activation (e.g., L1 signaling) (e.g., the DCI format indicating configuration grant activation). Alternatively, the uplink grant provided by the PDCCH can be cleared based on the DCI format (e.g., L1 signaling) that indicates the configuration grant to be deactivated.

[0149] For example, for a configured license type 2 transport, a DCI format scrambled by CS-RNTI can be used to indicate activation (e.g., configured license activated). Similarly, for a configured license type 2 transport, a DCI format scrambled by CS-RNTI can be used to indicate deactivation (e.g., configured license deactivated).

[0150] In some examples, a DCI format scrambled with CS-RNTI can be used to indicate retransmissions (e.g., retransmissions of TBs with configured license type 1 transmissions and / or configured license type 2 transmissions, e.g., retransmissions of TBs). For example, setting NDI to "1" (i.e., setting the NDI field to "1", NDI="1") can be used to indicate a retransmission. In some examples, as described above, NDI (i.e., the NDI field) can be included in a DCI format scrambled with CS-RNTI. For example, a PDCCH scrambled with CS-RNTI (e.g., a DCI format for uplinks) can be used to schedule PUSCH retransmissions with NDI set to "1".

[0151] In some examples, for a configured grant type 1 transmission, based on the configured grant type 1 (e.g., configuration for the serving cell), UE 102 can store the uplink grant as the configured grant (e.g., for the serving cell). Furthermore, UE 102 can initialize (if inactive) or reinitialize (if activated) the configured grant to start with a symbol of a parameter (e.g., time-domain offset) and reappear in the recurrence of parameters (e.g., periodicity). After configuring the uplink grant for the configured grant type 1, UE 102 can sequentially consider the Nth uplink grant associated with a symbol, where: [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slotnumber in the frame × numberOfSymbolsPerSlot) + symbol number in the slot]= (timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot+ timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity) modulo(1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) Furthermore, for example, for a transmission with a configured license type 2, after configuring an uplink license for the configured license type 2, UE 102 may sequentially consider the Nth uplink license associated with a symbol, where: [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) + (slotnumber in the frame × numberOfSymbolsPerSlot) + symbol number in the slot]= [(SFNstarttime × numberOfSlotsPerFrame × numberOfSymbolsPerSlot +slotstarttime × numberOfSymbolsPerSlot + symbolstarttime) + N ×periodicity]modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) In some examples, SFNstart time, slotstart time, and symbolstart time are the SFN (i.e., system frame number), slot, and symbol, respectively, at the time of the configured uplink grant (re)initialization. For example, parameters (e.g., periodicity) can be configured via gNB 160 using RRC messages.

[0152] For example, for a transmission configured with license type 1, UE 102 can initiate an uplink transmission based on parameters contained in the received RRC message. Furthermore, for a transmission configured with license type 2, UE 102 can initiate an uplink transmission based on parameters received using an uplink DCI format (CRC) scrambled with C-RNTI. Additionally, UE 102 can perform TB retransmissions (e.g., retransmissions on UL-SCH, retransmissions on PUSCH) based on the received uplink DCI format (CRC) scrambled with C-RNTI, which includes setting the NDI in the uplink DCI format to "1".

[0153] For example, gNB 160 can transmit parameters for configured authorization type 1 transmission using RRC messages (e.g., dedicated RRC messages, UE-specific RRC messages). UE 102 can then perform configured authorization type 1 transmission based on the parameters contained in the RRC messages. Furthermore, gNB 160 can transmit parameters for configured authorization type 2 transmission using RRC messages (e.g., dedicated RRC messages, UE-specific RRC messages). UE 102 can then perform configured authorization type 2 transmission based on the parameters contained in the RRC messages.

[0154] In some examples, the following parameters can be configured for transports corresponding to configured authorizations (i.e., configured authorization type 1 transports and / or configured authorization type 2 transports). For example, the following parameters can be included in the ConfiguredGrantConfig of the ConfiguredGrantConfig information element (IE). For example, an RRC message can include a ConfiguredGrantConfig IE.

[0155] -frequencyhopping: “intraSlot” indicates that “intra-slot frequency hopping” is enabled, and “interSlot” indicates that “inter-slot frequency hopping” is enabled.

[0156] -mcs-Table: Indicates the MCS table that UE 102 should use for PUSCH (e.g., PUSCH transmission without transformation precoding).

[0157] -mcs-TableTransformPrecoder: Indicates the MCS table that UE 102 should use for PUSCH (e.g., PUSCH transmission using transform precoding).

[0158] -powerControlLoopToUse: The closed-loop control loop of the application. Parameters used to determine the transmission power of a PUSCH transmission (e.g., corresponding to a configured licensed transmission).

[0159] -p0-PUSCH-Alpha: The index of the P0-PUSCH-AlphaSet to use for this configuration. A parameter used to determine the transmission power of PUSCH transmissions (e.g., corresponding to a configured licensed transmission).

[0160] -transformPrecoder: Enables or disables transform precoding for transports that have been configured with licenses (i.e., transports configured with license type 1 and / or transports configured with license type 2).

[0161] -nrofHARQ-Processes: The number of HARQ processes configured for transports with license type 1 and / or license type 2.

[0162] -repK: The number of repetitions to apply to transports configured with license type 1 and / or license type 2.

[0163] -repK-RV: A sequence of redundant versions to be applied to transports configured with license type 1 and / or license type 2.

[0164] Alternatively, for transports configured with grant type 1, the following parameters might be configured. For example, these parameters might be included in rrc-ConfiguredUplinkGrant within the ConfiguredGrantConfig IE.

[0165] -timeDomainOffset: An offset value associated with the system frame number (SFN) = 0. For example, an offset value used to indicate the timing of a configured type 1 transfer.

[0166] -timeDomainAllocation: Indicates the combination of start symbol, length, and PUSCH mapping type.

[0167] -frequencyDomainAllocation: Indicates the allocation of frequency domain resources.

[0168] -antenna port: Indicates the antenna port used for this configuration.

[0169] -mcsAndTBS: Indicates the modulation order, target coding rate, and / or TB size.

[0170] -frequencyHoppingOffset: The frequency hop offset used when frequency hopping is enabled.

[0171] -pathlossReferenceIndex: A parameter used for power control of the configured type 1 transmission (i.e., for this configuration).

[0172] In some examples, multiple `ConfiguredGrantConfig` configurations may be supported. For example, one or more `ConfiguredGrantConfig` configurations may be configured. Similarly, multiple `rrc-ConfiguredUplinkGrant` configurations may be supported. For example, one or more `rrc-ConfiguredUplinkGrant` configurations may be configured. In some examples, the configurations of `ConfiguredGrantConfig` and / or `rrc-ConfiguredUplinkGrant` may be referred to as configured-authorized configurations. For example, a single configured-authorized configuration may be supported. At the same time, multiple configured-authorized configurations may also be supported.

[0173] For example, the gNB 160 can use RRC messages to transmit a third piece of information for configuring the enabling (e.g., allowing) of multiple configurations of a configured authorization. For example, the gNB 160 can use RRC messages to transmit a third piece of information for indicating whether a single configuration of the configured authorization or multiple configurations of the configured authorization are used for a transmission corresponding to the configured authorization.

[0174] For example, when configuring a single configuration of an already configured license, that single configuration can be used to correspond to a transmission of the already configured license. Similarly, when configuring multiple configurations of an already configured license, multiple configurations can be used to correspond to a transmission of the already configured license. Furthermore, when not configuring multiple configurations of an already configured license, a single configuration can be used to correspond to a transmission of the already configured license.

[0175] In some examples, the third information can be configured on a serving cell basis. For example, the third information can be configured for each serving cell (e.g., a primary cell and / or one or more secondary cells). Alternatively, the third information can be configured on an uplink bandwidth portion (UL BWP). For example, the third information can be configured for each UL BWP (e.g., each UL BWP in the serving cell). Alternatively, the third information can be configured for configured licensed Type 1 transports and / or configured licensed Type 2 transports. For example, the third information can typically be used to configure both configured licensed Type 1 transports and configured licensed Type 2 transports. Alternatively, the third information can be configured separately for each configured licensed Type 1 transport and configured licensed Type 2 transport.

[0176] For example, as described below, when the third piece of information is typically configured for both Type 1 and Type 2 transmissions, the index for the configuration authorization can be configured. Furthermore, if the third piece of information is configured separately for Type 1 and Type 2 transmissions, the index for the configuration authorization and / or the configuration index for rrc-ConfiguredUplinkGrant can be configured.

[0177] Furthermore, a single, already authorized configuration can be activated. For example, a single active configuration with already authorized settings can be supported. Additionally, multiple, already authorized configurations can be activated. For example, multiple active configurations with already authorized settings for a given BWP (e.g., a UL BWP) of a serving cell for a given service / traffic type can be supported to enhance reliability and reduce latency.

[0178] For example, a single authorized configuration can be configured (and / or activated) for a given BWP (e.g., UL BWP) of a single serving cell, or multiple authorized configurations can be configured (and / or activated) for a given BWP (e.g., UL BWP) of a single serving cell.

[0179] UE 102 can perform a configuration authorization type 1 transfer based on a single configuration that has been configured and authorized (if a single configuration that has been configured and authorized is used) and / or multiple configurations that have been configured and authorized (if multiple configurations that have been configured and granted are used).

[0180] The Configured Grant (CG) can support the NCR. The current NR CG configuration / mechanism can be directly applied to the NCR, and / or the Control Link (C-link), Backhaul Link, Access Link, and / or any combination thereof.

[0181] NCR devices and / or terminal devices can support several types of unlicensed uplink transmissions (also known as unlicensed (GF) uplink transmissions, GF transmissions, or configured licensed (CG) transmissions). Type 1 CG transmissions may be a UL data transmission that requires no license and is based solely on RRC (re)configuration without any L1 signaling. Type 2 CG transmissions, where UL data transmissions do not require license, are based on RRC configuration and the activation and / or deactivation of L1 signaling.

[0182] For Type 2, PDCCH activation is required. DCI format 0_0 (e.g., backup DCI), DCI format 0_1, DCI format 0_2 and / or a new DCI format (e.g., DCI format 0_3) can be used to activate Type 2 configuration licenses and / or retransmit Type 2 configuration licenses and / or Type 1 configuration licenses.

[0183] NCR devices and / or terminal devices may support multiple unlicensed uplink transport types, or they may not support any. For example, some NCR devices and / or terminal devices may only support Type 1 configuration licensing. In another example, some may only support Type 2 configuration licensing. In yet another example, some NCR devices and / or terminal devices may support both Type 1 and Type 2 configuration licensing. Whether Type 1 and Type 2 configuration licensing apply to NCR devices and / or terminal devices may be configured by RRC, and / or dynamically indicated by L1 (e.g., PDCCH, DCI), and / or indicated by MAC CE, and / or fixed by the specification (e.g., a default behavior specified in the specification).

[0184] Network Control Repeaters (NCRs) can be used in various scenarios. For example, such as... Figure 17As shown, network control repeaters may be used on moving train carriages. In this scenario, the link between the base station and the network control repeater (e.g., control link (C-link), backhaul link) will be highly dynamic, while the user equipment in the carriage served by the network control repeater may be relatively static. Therefore, in uplink transmission, dynamic scheduling of the link between the base station and the network control repeater can be considered, that is, uplink transmission can be dynamically scheduled through uplink grant in DCI (e.g., downlink DCI format scrambled by C-RNTI). The link between the network control repeater and the user equipment (e.g., access link) can adopt an unlicensed uplink transmission type (also known as unlicensed (GF) uplink transmission or GF transmission or configured licensed (CG) transmission), that is, uplink transmission may be semi-statically configured (e.g., activated / deactivated through RRC configuration parameters and PDCCH (DCI format(s)), or through RRC configuration parameters) time domain, frequency domain and / or spatial domain (e.g., beam) resources.

[0185] For example, such as Figure 18 As shown, network control repeaters may be installed on fixed buildings or facilities. In this scenario, the links between the base station and the network control repeater (e.g., control links (C-link), backhaul links) are relatively static, while the user equipment served by the network control repeater may be dynamic. Therefore, in uplink transmission, the links between the network control repeater and the user equipment (e.g., access links) can be dynamically scheduled, meaning that uplink transmission can be dynamically scheduled through uplink grants in the DCI (e.g., downlink DCI format scrambled by C-RNTI). The links between the base station and the network control repeater can use unlicensed uplink transmission types (also known as unlicensed (GF) uplink transmission or GF transmission or configured licensed (CG) transmission), meaning that uplink transmission may be semi-statically configured (e.g., activated / deactivated via RRC configuration parameters and PDCCH (DCI format(s)), or via RRC configuration parameters) time-domain, frequency-domain, and / or spatial-domain (e.g., beam) resources.

[0186] For example, a network repeater may be installed on a mobile facility, and the user equipment it serves may also be mobile. In this scenario, both the link between the base station and the network control repeater (e.g., control link (C-link), backhaul link) and the user equipment served by the network control repeater may be dynamic. Therefore, in uplink transmission, dynamic scheduling can be considered for the link between the network control repeater and the user equipment (e.g., access link), meaning that uplink transmission can be dynamically scheduled through the uplink grant in the DCI (e.g., uplink DCI format scrambled by C-RNTI). Simultaneously, the link between the base station and the network control repeater can also be dynamically scheduled, meaning that uplink transmission can be dynamically scheduled through the uplink grant in the DCI (e.g., uplink DCI format scrambled by C-RNTI).

[0187] For example, a network repeater may be installed on a fixed building or facility, and the user equipment it serves may also be relatively static. In this scenario, the link between the base station and the network control repeater (e.g., control link (C-link), backhaul link) and the user equipment served by the network control repeater may both be relatively static. Therefore, in uplink transmission, the link between the network control repeater and the user equipment (e.g., access link) can be considered to use an unlicensed uplink transmission type (also known as unlicensed (GF) uplink transmission or GF transmission or configured licensed (CG) transmission), that is, the uplink transmission may be semi-statically configured (e.g., activated / deactivated via RRC configuration parameters and PDCCH (DCIformat(s)), or via RRC configuration parameters) time domain, frequency domain, and / or spatial domain (e.g., beam) resources. The link between the base station and the network control repeater can also use an unlicensed uplink transmission type (also known as unlicensed (GF) uplink transmission or GF transmission or configured licensed (CG) transmission), that is, the uplink transmission may be semi-statically configured (e.g., activated / deactivated by RRC configuration parameters and PDCCH (DCI format(s)), or activated by RRC configuration parameters) time domain, frequency domain and / or spatial domain (e.g., beam) resources.

[0188] It should be noted that the one or more methods described herein can be implemented and / or executed in hardware. For example, the one or more methods described herein can be implemented and / or executed using chipsets, application-specific integrated circuits (ASICs), large-scale integrated circuits (LSIs), or integrated circuits.

[0189] It should be understood that the claims are not limited to the precise configuration and components described above. Various modifications, alterations, and variations can be made to the arrangement, operation, and details of the systems, methods, and apparatus without departing from the scope of the claims.

[0190] In the described system and method, the program running on the gNB 160 or UE 102 is a program (a program for making the computer run) that controls the CPU, etc., to implement the functions of the described system and method. During processing, the information processed in these devices is temporarily stored in RAM. Subsequently, this information is stored in various ROMs or HDDs, and the CPU reads and modifies or writes it whenever needed. The recording medium for storing the program can be any medium such as semiconductor (e.g., ROM, non-volatile memory cards, etc.), optical storage media (e.g., DVD, MO, MD, CD, BD, etc.), magnetic storage media (e.g., magnetic tape, floppy disk, etc.). Furthermore, in some cases, the functions of the described system and method are implemented by running a loaded program, and the functions of the described system and method are implemented based on an operating system or other application according to the instructions of the program.

[0191] Furthermore, if the program is commercially available, the program stored on a portable recording medium can be distributed, or it can be transferred to a server computer connected via a network such as the Internet. In this case, the server computer also includes a storage device. Additionally, according to the described system and method, some or all of the gNB 160 and UE 102 can be implemented as LSIs of typical integrated circuits. Each functional block of the gNB 160 and UE 102 can be built as a separate chip, and some or all functional blocks can be integrated into a single chip. Furthermore, the technology of integrated circuits is not limited to LSIs; integrated circuits of functional blocks can be implemented using dedicated circuits or general-purpose processors. Moreover, if an integrated circuit technology that replaces the LSI emerges with advancements in semiconductor technology, the integrated circuit for which the technology is applicable can also be used.

[0192] Furthermore, each functional block or feature of the base station equipment and terminal equipment used in the foregoing various embodiments can be implemented or executed by a circuit, which is typically an integrated circuit or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific or general-purpose integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general-purpose processor may be a microprocessor, or the processor may be a conventional processor, controller, microcontroller, or state machine. Each of the above circuits or general-purpose processors may also be configured with digital circuitry or analog circuitry. Furthermore, with advancements in semiconductor technology, if an integrated circuit manufacturing technology surpasses current integrated circuit manufacturing techniques, integrated circuits manufactured using such technology may be available.

[0193] Those skilled in the art will understand that, in addition to implementing the system, apparatus, and their modules provided by this invention in purely computer-readable program code, the same program can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system, apparatus, and their modules provided by this invention can be considered a hardware component, and the modules included therein for implementing various programs can also be considered structures within the hardware component; alternatively, modules for implementing various functions can be considered both software programs implementing the method and structures within the hardware component.

[0194] Specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the claims, which do not affect the essence of the present invention. Unless otherwise specified, the embodiments and features described in this application can be arbitrarily combined with each other.

Claims

1. A repeater device supporting uplink unlicensed scheduling, characterized in that, Used for communicating with user equipment and base station devices, including: Receiver circuit configuration: Receive a first radio resource control (RRC) message, which includes a first subcarrier spacing used by the control link; Receive a second RRC message, which includes a second subcarrier spacing for indicating the backhaul link; Receive a third RRC message, which includes a third subcarrier spacing used to indicate the access link; Receive a fourth RRC message, which includes information on the resources configured for uplink unlicensed scheduling of the access link; A first physical downlink control channel is received, which transmits first downlink control information for an unlicensed scheduling physical uplink shared channel for access links. The cyclic redundancy check code of the first downlink control information is scrambled by a first radio network temporary identifier. The first downlink control information includes resources configured for access link uplink unlicensed scheduling and activation information. Receive a second physical downlink control channel, which transmits second downlink control information containing dynamic scheduling of physical uplink shared channels for backhaul links, wherein the cyclic redundancy check code of the second downlink control information is scrambled by a second radio network temporary identifier, and the second downlink control information includes resources configured for indicating dynamic scheduling of backhaul links; Based on the fourth RRC message and the first downlink control information, the unlicensed scheduling physical uplink shared channel of the access link is received; Transmitter circuit configuration: Based on the second downlink control information, the unlicensed scheduling physical uplink shared channel of the access link is forwarded through the backhaul link via the dynamic scheduling uplink shared channel.

2. The repeater device supporting uplink unauthorized scheduling according to claim 1, characterized in that, In the uplink physical channel, a physical random access channel is defined for the initial access connection establishment process, handover process, connection re-establishment, periodic adjustment and / or request for uplink shared channel resources.

3. The repeater device supporting uplink unauthorized scheduling according to claim 1, characterized in that, In the downlink, a physical downlink control channel is defined to transmit downlink control information. Specifically, fields are defined in the downlink control information and these fields are mapped to information bits.

4. The repeater device supporting uplink unauthorized scheduling according to claim 1, characterized in that, Define the Physical Broadcast Channel (PBCH) for broadcasting the Master Information Block (MIB). System information is divided into MIB and System Information Block (SIB). MIB carries minimal system information, while SIB carries system information messages.

5. The repeater device supporting uplink unauthorized scheduling according to claim 1, characterized in that, In the downlink, a synchronization signal SS is defined to obtain time and / or frequency synchronization with the cell, and to detect the physical layer cell ID of the cell.

6. The repeater device supporting uplink unauthorized scheduling according to claim 1, characterized in that, Use one or more temporary wireless network identifiers to transmit downlink control information.

7. The repeater device supporting uplink unlicensed scheduling according to claim 1, characterized in that, In uplink wireless communication, the uplink reference signal RS is used as the uplink physical signal, and in downlink wireless communication, DL RS is used as the downlink physical signal; or the uplink physical signal and / or the downlink physical signal are used by the physical layer.

8. The repeater device supporting uplink unlicensed scheduling according to claim 1, characterized in that, Repeater equipment is installed on mobile facilities, and the user equipment it serves is also mobile. In this scenario, the link between the base station and the repeater equipment, as well as the user equipment served by the repeater equipment, are both dynamic. In uplink transmission, the link between the repeater equipment and the user equipment is dynamically scheduled, that is, uplink transmission is dynamically scheduled through downlink grants in the DCI. At the same time, the link between the base station and the repeater equipment is also dynamically scheduled, that is, uplink transmission is dynamically scheduled through uplink grants in the DCI. When a repeater device is installed on a fixed building or facility, and the user equipment it serves is also relatively stationary, the link between the base station device and the repeater device, as well as the user equipment served by the repeater device, are both relatively static. Therefore, in uplink transmission, the link between the repeater device and the user equipment adopts an unlicensed uplink transmission type, such as uplink transmission or GF transmission, or through configured licensing. That is, the uplink transmission is semi-statically configured with time domain, frequency domain, and / or spatial domain resources. The link between the base station device and the repeater device also adopts an unlicensed uplink transmission type, meaning that the uplink transmission may be semi-statically configured with time domain, frequency domain, and / or spatial domain resources.

9. A user equipment supporting uplink unlicensed scheduling, characterized in that, Communicating with the repeater device supporting uplink unlicensed scheduling as described in any one of claims 1-8, comprising: Receiver circuit configuration: Receive a first RRC message, which includes an indication of the first subcarrier spacing used by the access link; Receive a second RRC message, which includes resources configured for indicating uplink unlicensed scheduling on the access link; Receive a first physical downlink control channel, which transmits first downlink control information for an unlicensed scheduling physical uplink shared channel for accessing the link, the first downlink control information including resources configured for unlicensed scheduling of the access link and activation information; Transmitter circuit configuration: Based on the second RRC message and the first downlink control information, the unlicensed physical uplink shared channel of the access link is sent.

10. A base station apparatus supporting uplink unlicensed scheduling, characterized in that, Communicating with the repeater device supporting uplink unlicensed scheduling as described in any one of claims 1-8, comprising: Transmitter circuit configuration: Send a first radio frequency resource control message, which includes a first subcarrier spacing for indicating the control link; Send a second RRC message, which includes a second subcarrier spacing used to indicate the backhaul link; Send a third RRC message, which includes a third subcarrier spacing used to indicate the access link; Send a fourth RRC message, which includes information about the resources configured for uplink unlicensed scheduling on the access link; A first physical downlink control channel is transmitted, which transmits first downlink control information for an unlicensed scheduling physical uplink shared channel for access links. The cyclic redundancy check code of the first downlink control information is scrambled by a first radio network temporary identifier. The first downlink control information includes resources configured for access link uplink unlicensed scheduling and activation information. A second physical downlink control channel is transmitted, which transmits second downlink control information containing dynamic scheduling of the physical uplink shared channel for backhaul links. The cyclic redundancy check code of the second downlink control information is scrambled by a second radio network temporary identifier. The second downlink control information includes resources configured for indicating dynamic scheduling of backhaul links. Receiver circuit configuration: Based on the second downlink control information, the uplink shared channel is dynamically scheduled for the backhaul link.

Images